Questions, answered

Click Get started, then use Proto to configure Taxi / Ride-hailing Platform for your business. Begin with a familiar service zone, current driver and vehicle records, and a representative booking. Rehearse its review, accepted match, completion and payment evidence before expanding the operating scope.

Dispatcher uses the booking interval and linked ride request, then confirms the driver and vehicle through the booking resource. The request retains the rider’s pickup and dropoff details. Operations Overview brings operating work and exceptions together for the desk’s review.

Operations Reviewer independently examines the booking in Review and records the decision, reason and source revision. Configure that authority separately from Dispatcher preparation access and rehearse a changed booking before the pilot begins.

Dispatcher checks an accepted match against current driver and vehicle availability, then confirms the resource and its time. If a suitable match cannot be confirmed, keep the request visible and record an escalation for Operations Reviewer.

Trip Coordinator follows the request through En Route, Arrived and Completed as the journey occurs. Trip events retain observed time and source. Completion evidence connects the booking and request so Operations Reviewer can verify a complete, consistent result. Missing evidence stays Captured; discrepancies become Disputed. Both need an escalation and a Failed receipt for follow-up.

Follow the agreed cancellation policy and record an evidenced no-show as Missed on the request. Release an existing assignment when appropriate and retain the cancellation review and receipt. Examine any performed work before choosing a correction path.

Finance Operator links each supported component to its booking and provider event. Agree the currency convention and fare-provider connection during setup. Retain the fare breakdown when a Base Fare, Waiting Time Charge or Toll needs explanation.

Use Paid when the corresponding provider evidence supports the outcome. Trip completion gives the payment review its journey context. Keep the provider event identifier available for investigation, and follow the provider’s confirmation process for adjustments.

Fleet Coordinator maintains vehicle inspections, defects and maintenance plans. Dispatcher checks the selected vehicle’s status and relevant condition evidence before confirming it. Agree the return-to-service policy and rehearse a vehicle withdrawn after it was proposed for a ride.

Yes. Prepare organization and staff identities, then load resources before open rides and their linked evidence. Preserve the source identifiers used by reviews and provider events. Reconcile the imported work and rehearse repeated incoming messages before enabling the pilot connections.