Arrival-time planning
The ride is planned backwards from the time the patient has to be at the clinic, not from the moment somebody books.
Ride-needs classification
Every request is classified A to D, so a patient who needs a ramp never gets a standard car.
Multiple carrier options
We are not tied to one fleet. For each ride we choose a carrier that is licensed for what the patient needs.
Primary and backup dispatch
Each launched city has a primary scheduled partner and a backup carrier, so a cancellation does not end the journey.
Return-trip workflow
The return leg stays open as "patient ready" and is dispatched when the visit actually ends.
Patient and family communication
Reminders and confirmations go to the patient or family in their language, not only to the ordering organisation.
Human exception handling
Anything unusual is escalated to a person. Automation never drives an exception on its own.
Audit trail and partner reporting
Every request keeps a record of what was ordered, confirmed and delivered, as a basis for invoicing and review.