THE CHALLENGEManual Dispatch Loses Trips and Trust
A taxi operation lives or dies on how fast it puts the right cab in front of the rider. Manual dispatch sends the wrong vehicle, leaves cabs idle while riders wait, and keeps no record to settle a fare dispute later. Drivers and passengers have no reliable safety line, and operators in regulated markets face compliance demands that a basic tracker cannot meet. The dispatch platform matches cabs by real road ETA, records every trip end to end, and puts a panic button in every vehicle.
Built within the Telematics and GPS Tracking ecosystem, and frequently paired with Fleet Tracking and Monitoring.
WHAT'S INCLUDED
Hardware and Software for Cab Operations
In-Vehicle GPS Tracker
Each cab carries a GPS tracker that streams position, ignition, and speed, and provides the wiring for a panic button and emergency reporting. It is the data source for dispatch, metering, and the safety chain.
Dispatch Console
A control-room console shows every cab live and assigns new bookings to the best vehicle by road-network ETA, with automatic reassignment on timeout. Manual and app bookings flow through the same queue.
Driver and Rider Apps
The driver app handles trip offers, navigation, and earnings. The rider app handles booking, live ETA, and driver and vehicle details. Both run on the same backend as the console so the whole operation stays in sync.
Trip Metering and Fare
Distance and time are metered from the GPS track with configurable tariffs for waiting, night rates, and zones. The route and fare breakdown are stored per trip, so a dispute is settled by replaying the recorded trip.
Panic Button and Safety
A panic button in the vehicle, mirrored in the rider app, raises an immediate control-room alert with live location and trip context. Trip sharing and journey-deviation alerts escalate a driver or passenger in distress.
Geofenced Zones
Airport, city-limit, and surge zones are defined as geofences. Entry and exit log automatically for billing and compliance, and dispatch can prioritize or restrict bookings to keep cabs within their permitted area.
STANDARDS AND COMPLIANCE
Built to Operate Where the Rules Are Strict
In regulated markets a taxi platform has to meet positioning, safety, and reporting mandates. Those are folded into the same system rather than adding a separate compliance box.
AIS 140 Where Mandated
Built to the AIS 140 framework where required, with the emergency button, NavIC and IRNSS positioning support, and the prescribed reporting to the backend control centre.
Real-Time Matching Engine
A routing engine computes road-network ETA with live traffic where available. Dispatch and the rider ETA share that engine, so the estimate the rider sees matches the decision dispatch made.
Auditable Trip Records
Every trip stores the full route, distance, time, and fare. That record is the single source of truth for billing, driver settlement, and dispute resolution.
FAQ
Common Questions
How does nearest-cab assignment work?
The dispatch console holds the live position of every available cab and matches a new booking to the best vehicle by road-network ETA, not straight-line distance. It accounts for one-way streets and current direction of travel, then offers the trip and reassigns automatically if the driver does not accept within the timeout.
Do you build the driver and rider apps too?
Yes. The driver app handles trip offers, turn-by-turn navigation, and earnings, and the rider app handles booking, live ETA, and driver and vehicle details. Both share the same backend as the dispatch console so a manual booking and an app booking flow through one system.
How is the fare metered and disputes avoided?
Trip metering runs off the GPS track with distance and time, plus configurable tariffs for waiting, night rates, and zones. The full route, distance, and fare breakdown are stored per trip, so a billing dispute is settled by replaying the recorded trip instead of arguing over an estimate.
What safety features are included?
Every vehicle has a panic button that raises an immediate alert to the control room with live location and trip context, and the rider app can trigger the same. Trip sharing and journey-deviation alerts escalate a driver or passenger in distress quickly.
Do you support AIS 140 where it is mandated?
Yes. For markets and vehicle categories that require it, the platform is built to the AIS 140 framework, including the emergency button, NavIC and IRNSS positioning support, and the prescribed reporting to the backend control centre. This fits into the same platform rather than bolting on a separate compliance box.
How accurate is the live ETA shown to riders?
ETA is computed on the road network with live traffic where data is available and updates continuously as the cab moves. Because it uses the same routing engine as dispatch, the rider estimate and the dispatch decision stay consistent rather than drifting apart.
Can you enforce operating zones for drivers?
Yes. Geofenced zones cover airports, city limits, and surge areas. Entry and exit are logged for billing and compliance, and dispatch can prioritize or restrict bookings by zone so cabs stay within their permitted operating area.
Run a Faster, Safer Cab Operation
Share your fleet size, the markets you operate in, and your compliance needs to get a tailored approach and a realistic view of how nearest-cab dispatch and trip recording change your numbers.
Schedule a Free Consultation