RideVoy uses a hybrid model: monthly platform fee plus per-completed-ride pricing, with included rides based on your selected plan.
FAQ
Answers for operations, finance, and compliance teams.
Use this page to evaluate pricing fit, implementation expectations, workflow behavior, and security posture before rollout.
Pricing and plans
No setup fee is required. Implementation planning and onboarding support are covered during launch.
No. Core product workflows are available across plans to avoid adoption friction and feature-based churn.
Yes. Annual commitments can be used for budget predictability and include a platform-fee discount.
Rides beyond your included allocation are billed at your plan's per-ride rate. There are no overage penalties or service interruptions — you simply pay for the additional completed rides at the end of the billing cycle. You can monitor usage in real time from the analytics dashboard.
RideVoy supports automated invoice generation and finalization workflows, including billing-period advancement and optional Stripe synchronization when configured. This reduces month-end manual steps for operations and finance teams.
Organizations begin with a trial period and can be configured with grace-period behavior. Depending on subscription status, access can remain full, shift to read-only windows, or become restricted until billing is resolved.
Yes. Annual plans include a discount on the monthly platform fee compared to month-to-month billing. This option is designed for organizations that prefer budget predictability and want to lock in pricing for the year. Contact our team for a custom annual quote based on your expected ride volume.
Absolutely. Many organizations start with a single facility or a subset of riders to validate workflows before expanding. Our Starter plan is designed for exactly this use case — you can test with a small team and scale to Growth or Enterprise as your operation grows. See pricing details.
Implementation and workflow
Launch timelines depend on your team structure and process complexity, but many organizations can begin quickly with phased rollout.
Yes. Driver self-registration is supported with administrator approval workflows before full activation.
Yes. Recurring rides can be configured for patterns like daily, weekly, biweekly, and monthly appointment schedules.
Yes. Admin users can assign pending rides directly when operations require manual intervention.
Yes. RideVoy supports bulk rider import during onboarding so you can migrate existing patient profiles, addresses, and accommodation notes from spreadsheets or other systems. Our team assists with data mapping to ensure a clean transition. See rider profiles for the fields supported.
Yes. RideVoy is fully web-based and responsive on phones, tablets, and desktops. Drivers can use browser access or install the RideVoy web app experience for faster mobile entry without app-store dependency.
Yes. Drivers can enable push notifications in their profile and receive assignment or workflow updates through the RideVoy mobile web app experience.
When scheduling a ride, facility staff can flag it as a round trip. This creates visibility for the return leg so dispatch and drivers know to plan for both pickup and return. Round-trip intent is captured during the guided scheduling flow and displayed on ride details.
Yes. RideVoy's multi-facility architecture allows all facilities within an organization to share a common driver pool. Drivers see rides from any facility on the live ride board, while facility staff only see their own rides — providing shared capacity with role-appropriate visibility.
If a driver cancels an accepted ride, it returns to the available ride board for other drivers to claim. Administrators are notified and can manually reassign it if needed. The cancellation is logged for operational tracking and performance reporting.
Security and reporting
RideVoy includes TLS transport security, encrypted field storage, role-scoped access controls, authentication safeguards, PHI audit logging, and operational event traceability.
Yes. RideVoy records PHI access events and supports filterable review workflows for administrators.
Yes. Consent status can be managed for SMS, email, voice, and data-sharing permissions with grant and revoke tracking.
Yes. CSV exports are available for downstream reporting and billing workflows.
Yes. Security and operational controls can be reviewed with your technical and compliance stakeholders during procurement.
Use the contact page for sales, support, and security-specific questions that require direct follow-up.
Yes. All data is encrypted in transit using TLS/SSL, and sensitive fields are encrypted at rest using AES-256 encryption. Database access is restricted to authenticated application processes, and all API endpoints require token-based authentication. See our security overview for more detail.
RideVoy implements technical safeguards aligned with HIPAA requirements including access controls, audit logging, encrypted data handling, and role-based permissions. While HIPAA compliance is an organizational responsibility, our platform provides the controls healthcare transportation teams need to support their compliance programs.
Yes. RideVoy uses role-based access control with five distinct roles: facility staff, drivers, organization administrators, account managers, and platform administrators. Each role has specific permissions — for example, facility staff can only see rides for their facility, while org admins have visibility across all facilities and drivers in the organization.
NEMT operations
Fulfillment rate is the percentage of requested rides that are successfully completed — calculated as (completed rides / total requested rides) × 100 over a given period. It's the primary operational KPI for NEMT programs because it directly measures whether patients are reaching their appointments. Well-run operations typically maintain 90-95% fulfillment. Learn more in our NEMT glossary.
NEMT software reduces no-shows by removing transportation as a barrier. Key mechanisms include: recurring ride scheduling that pre-books transport for standing appointments, SMS notifications that keep patients informed about ride status, and real-time tracking that enables early intervention when delays occur. Read our full guide on reducing medical no-shows.
RideVoy supports flagging wheelchair accessibility, portable oxygen equipment, walker storage, stretcher transport, bariatric capacity, and attendant/aide accompaniment on each ride request. These flags are visible to drivers before they accept a ride, ensuring they arrive with the appropriate vehicle and equipment. Accommodation preferences can be saved in rider profiles for automatic application on future rides.
Yes. Ride workflows can capture GPS verification at pickup and dropoff with optional signature attestation for documentation-heavy operations and payer-facing evidence requirements.
Yes. The analytics dashboard provides driver-level metrics including completed ride counts, acceptance rates, on-time performance, and cancellation patterns. Administrators can filter by date range and compare performance across drivers to identify training needs or recognize top performers.
Spreadsheet dispatch relies on manual data entry, phone-based status updates, and periodic reporting — which creates gaps in visibility and increases error rates as ride volume grows. RideVoy replaces this with structured scheduling, automated SMS updates, a live ride board with 15-second refresh, and built-in analytics. Most teams report 60-80% reduction in scheduling overhead when transitioning from spreadsheets to RideVoy.
Still evaluating platform fit?
We can run a focused Q&A session with your operations and finance stakeholders.