Taxi Dispatch Software

Taxi Real-Time Location and Trip Track Playback for the Dispatch Desk

A radio channel full of “where is that car?” questions is not a location system. It is a habit. The dispatcher asks a driver to describe an intersection. A supervisor later tries to reconstruct a complaint from memory and a fare total. Without a desk map, you cannot tell which cars are actually out, and you cannot play a finished trip back when the rider says the route was wrong.

Ptaxi’s taxi dispatch software documents two admin surfaces for that work. Real-time location, under vehicle management, lets staff look up on-duty and monitored online drivers, vehicles, and their location information, filtered by company. Track records, in the same vehicle area, let staff view an order trip and the vehicle’s location track, and then play, pause, stop, or resume. A trip list under order management also shows a driver’s trips and track information, and an order detail record can include a trip track among other fields.

The desk needs a now view and a later view

Buyers usually want two answers from a map, and they often get them mixed together in a sales demo.

The first answer is current: which drivers are out, which vehicles are online, and where those units are right now, for the company this dispatcher is allowed to watch. That is a shift question. It helps you decide whether a street is covered before the next phone booking.

The second answer is historical: after the job, can someone play the trip track and see the path the vehicle recorded? That question shows up when a rider argues about the route, or when a supervisor needs to understand a finished order.

Those two views share a map metaphor, but they are not the same tool. Live location is about units that are out and monitored as online. Playback is about a recorded trip you can start, pause, stop, and resume. If you brief them as one automatic screen, staff will look for a replay button on a car that was never online, or treat a live pin as proof of a finished route.

Keep a third question out of this briefing. Passengers sometimes want a family member to follow the car. That is a separate passenger action — trip sharing and privacy number protection — not the same as the desk location and playback tools. Do not train the control room to read an admin map out loud as a substitute for the rider sharing the trip.

Real-time location is filtered by company and online status

Under vehicle management, real-time location lets you view, by company, drivers and vehicles that are out, monitored as online, and their location information. Three limits already sit in that sentence.

First, the view is filtered by company. A desk that runs more than one company should not assume a single unfiltered map of every car on the platform. In a demo, switch company context, confirm which units appear, and write that down. If staff need a wider or narrower view, that is a permissions question, not a reason to invent a global live map.

Second, drivers go on duty and off duty in this product. The location view is about drivers and vehicles that are out and monitored as online. Do not tell a buyer that every parked car, every offline device, and every driver who already signed off still streams a continuous pin. If a unit is not out and not online, it may simply be absent from the view.

Third, the product names location information. It does not name a map vendor, a refresh interval, or a stated accuracy in meters. In a walkthrough, show the live view for one company with a few drivers actually on duty, and stop at what the screen shows. If you need a stale-pin rule, write it after you have watched the build — not on a sales slide as a guarantee. Location tells you who is out. It does not, by itself, put the next booking on a car.

Track playback is a recorded path you can control

Track records under vehicle management let staff view an order trip and the vehicle location track, and then play, pause, stop, or resume.

Treat playback as a recording tool, not as a live coaching feed. You open a track, start it, pause if you need to talk through a corner, stop, and resume if you want to keep going. Those four controls are what you are given. Do not add a speed graph or a sensor strip unless your staging build actually shows them, and do not claim that every vehicle is recorded all day, online or not. The documented object is an order trip and a vehicle location running track, not a 24-hour black box for the fleet.

In training, pick a completed metered taxi order, use all four controls in front of the buyer, and close the player. That is a better demo than a long story about “full visibility.”

The trip list and the order detail are another way in

You will not always start from vehicle management. Under order management, the trip list lets staff view a driver’s trips and track information. That is useful when the question arrives as “pull this driver’s jobs from yesterday,” not “open the vehicle track library.”

An order detail record can also include a trip track, alongside other field groups such as order information, order logs, operations data, a network-security data group, fee details, complaint information, push logs, and trip audio. Name those groups to orient a new supervisor, but do not turn any of them into a certification claim. The network-security data group is a labeled block on the order, not a public compliance certificate. This article will not speculate about what sits inside it. Trip audio is a different tool on the same record: open that field group for audio, and the trip track for the path.

A track can help a person understand a route argument. It does not automatically attach itself to a taxi order dispute file. Opening a dispute is not documented as copying the track into the case, and a refund is not documented as blocked until playback is watched. If your policy requires a supervisor to play the track first, write that as your policy, then use the dispute tools that already exist.

What not to promise on the live map

Stay inside what these screens actually do. Do not name a GPS or map vendor. Do not sell the desk map as a passenger live-share screen; trip sharing is a separate rider action. Do not promise automatic ETA texts, fuel savings, empty-kilometer cuts, or a route the system rewrites to reduce deadhead. Do not invent geofence alerts when a car enters a depot, leaves a zone, or idles too long. Do not claim continuous recording of cars that are offline or off duty, and do not add speed graphs or “safety scores” to a player whose documented controls are play, pause, stop, and resume.

A short ops checklist for the control room

Keep this to one page.

  • The live location view is checked by company, with drivers actually on duty and online, before a shift lead says “we can see the fleet.”
  • Offline or off-duty units are not described as continuously tracked.
  • Playback is demonstrated on a completed order using play, pause, stop, and resume — not described as a sensor dashboard.
  • Staff who need a driver’s jobs start from the trip list or the order detail when that is faster than the vehicle track library.
  • A route argument may include watching the trip track. The track is not assumed to auto-attach to a dispute file.
  • If a family member asks where the car is, the rider is still asked to share the trip. The admin map is not the public share tool.
  • No one in sales names a map vendor, an ETA text, a fuel-saving result, or a geofence alert as part of this module.

If the script starts promising a passenger-facing live map, cut it back to the desk tools you can actually open.

Close

Location questions at a taxi desk come in two tenses. Right now: which on-duty, online vehicles can this company see? After the fact: can someone play the trip track, pause it, and talk through the path? Those two admin surfaces are in the product, plus a trip list and an order detail that can include the track.

That is enough to stop arguing from memory, if you train the tools as they are. It is not enough to sell automatic ETAs, fuel cuts, or a public tracking page. Look at the location and track tools on the taxi dispatch software product page. If you want a walkthrough, ask for a demo and bring one live shift question and one finished trip you would actually need to replay.

Frequently asked questions

Can the dispatch desk see every taxi in the fleet at all times?

No. Real-time location is filtered by company and shows drivers and vehicles that are out and monitored as online, along with their location information. Drivers go on duty and off duty in this product. Do not promise a continuous pin for offline or off-duty units.

What controls does trip track playback actually include?

Track records let staff view an order trip and the vehicle’s location track, then play, pause, stop, or resume. The same track information can also be opened from a driver’s trip list or from an order detail that includes a trip track. The list does not describe speed graphs, sensor overlays, or all-day recording of cars that were never online.

Is the desk location map the same as passenger trip sharing?

No. Desk location and playback are admin tools. Passenger trip sharing is a separate rider action, already covered in its own post. Do not train the control room to read an admin map out loud as a substitute for the passenger sharing the trip.

Does a trip track automatically attach to an order dispute?

No. An order detail can include a trip track among other field groups, and a supervisor may play that track when a route is in question. The list does not say the track is copied into a dispute file, or that a refund is blocked until playback is watched. If your policy requires a review of the track, write that as your policy.

Related articles

Taxi Trip Sharing, Privacy Numbers, and Emergency Contacts

A family member who only has a driver’s personal number is not a safety process. Taxi dispatch software lets the passenger share the trip, store emergency contacts, complete real-name verification, and protect numbers. Those are four separate tools, and none of them should be sold as an automatic alert chain.

· 8 min read

Talk to our team about your platform

Tell us your market and business model. We will reply with a feature plan, a demo of the apps and a quote.