These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Taxi / Ride-hailing Platform
- Who it's for
- Partner fleet dispatch
Partner fleet dispatch
A dispatch desk working with partner fleets needs to know which organization owns the work and which resource is serving the booking. Resource records distinguish Fleet Operator, Affiliate Network, Independent Driver and Corporate Fleet. Use their contact and eligibility notes when coordinating an accepted match, then retain the actual driver and vehicle on the booking resource.
How Taxi / Ride-hailing Platform is set up for you
Keep partner identity clear
Admin maintains the operating organization and resource records. Dispatcher selects the counterparty associated with the booking and confirms that the resource line identifies the driver and vehicle actually being used.
Review the accepted match
Check current availability before confirming the assignment. If a partner cannot supply the accepted match, retain the escalation reason so the next shift understands why the request still needs attention.
Compare evidence sources
Trip events can identify Partner as their source. Trip Coordinator checks the observed time and booking reference before using those events to explain arrival or completion.
Resolve the exception together
Operations Reviewer compares completion evidence with the booking and request. Keep a disputed result visible while the desk asks the partner for the supporting record, then trace any authorized correction through its operation receipt.
A dispatch desk working with partner fleets needs to know which organization owns the work and which resource is serving the booking. Resource records distinguish Fleet Operator, Affiliate Network, Independent Driver and Corporate Fleet. Use their contact and eligibility notes when coordinating an accepted match, then retain the actual driver and vehicle on the booking resource.
Pilot a familiar partner relationship with agreed contact details and a clear service zone. Decide how accepted matches arrive at the dispatch desk and which documents support completed rides. Configure any partner feed with stable booking references and rehearse delayed or repeated messages before relying on the connection during a busy shift.
Use a ride that completes normally and another for which the partner supplies evidence for the wrong request. Ask the reviewer to identify the difference and explain the Failed receipt. Staff access to rider and partner information needs explicit setup; partner participation in a ride does not decide staff permissions. Review the relevant accounts during the pilot.
Start with [roles](/taxi-ride-hailing-platform/roles) and [integrations](/taxi-ride-hailing-platform/integrations), then rehearse [cancellation and correction](/taxi-ride-hailing-platform/processes/cancellation-and-correction).
Features to start with
Roles on the team
- Dispatcher
- Prepares ride bookings and confirms accepted driver and vehicle assignments.
- Operations Reviewer
- Independently reviews booking revisions and reconciles completion and correction evidence.
- Trip Coordinator
- Records pickup progress, trip events and evidence of completed rides.
- Finance Operator
- Reviews fare components and records provider-backed payment outcomes.
- Fleet Coordinator
- Maintains driver and vehicle records and follows defects, inspections and planned upkeep.
- Admin
- Configures organization, staff membership and access for the agreed operating scope.
Set up Taxi / Ride-hailing Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.