Taxi call taking and dispatch, explained

At a taxi stand, most of customer satisfaction is decided in the time between a ringing phone and a car showing up at the door. Instant call and dispatch exists to compress that time to seconds, combining free/busy status, an assignment rule and driver acceptance into one flow. Here is what happens between a call coming in and a car being assigned.

What the screen shows when a call comes in

The moment a dispatcher — or the automatic dispatch logic — takes a call, it sees the live status of every car tied to the stand: free, busy, on break, or off shift. If that status is stale, the assignment lands on a busy car and the customer waits for nothing. That’s why letting the driver flip free/busy from their own screen, with it reflecting on the dispatch screen instantly, is the backbone of the whole system.

Assignment rule: nearest car, or next in line?

Every stand has its own assignment habit: some prioritize the nearest free car, others rotate assignments to keep things fair between drivers. Keeping that rule configurable per firm lets a stand move to dispatch software without changing how it actually runs.

The driver’s short acceptance window

Once an assignment reaches the driver’s phone, there’s a short window to accept or decline; if nothing comes back in that window, the call moves automatically to the next free car. That handoff being automatic, not manual, is what keeps a customer from waiting long minutes because one driver happened to be unreachable.

The tunnel and covered parking problem

In city taxi work, a driver’s location signal can drop inside a tunnel or covered parking; dispatch needs to keep working from what the driver reports by hand, not only from the last known position. Letting a driver mark “trip done” or “free” manually even while the signal is out is a real field need, not an edge case.

Repeat callers and a complaint counter

Dispatch isn’t only about assigning an incoming call to the nearest car; it also surfaces a complaint a given customer has already raised, or a recurring problem, right on the same screen. Counting complaints per driver and flagging them once they cross a threshold catches a problem before it grows. That counter isn’t a separate screen — the dispatcher sees the caller’s history the moment the call comes in.

When the connection drops in the field

The dispatch surface on a driver’s phone needs to hold its state — the last call taken, whether a passenger is on board — even while the signal drops completely, and sync once the connection returns. In city taxi work, where tunnels and covered parking are routine, that isn’t a nice-to-have; it’s a daily need.

A repeat customer’s address is remembered

When the same number calls again, the address they used last time is suggested automatically on the dispatch screen, so the dispatcher doesn’t have to ask for it twice. The same logic applies when a contracted corporate customer calls: their address, preferred vehicle type, and any standing instruction appear on screen. That matters most for routine calls that repeat the same route every morning, like a factory shuttle, where it saves the dispatcher from keeping notes by hand.

Example: a 25-car stand at rush hour

Between 18:00 and 19:00, a stand takes 3-4 calls a minute, and its 25-car fleet runs close to full utilization in that window. When the dispatch screen shows the seven free cars live and assigns the nearest one, the dispatcher no longer has to ask over the radio which car is free. If a driver doesn’t respond quickly, the call moves automatically to the next free car, and the customer never has to call back.

How this works in Rotenta

1. The Instant Call and Dispatch screen logs the incoming call and shows the free/busy status of every car tied to the stand.
2. The assignment rule (nearest car or rotation) is set in firm settings; the screen flags the recommended car accordingly.
3. The assignment appears on the driver’s mobile surface; acceptance or decline is expected within a short window, and the call moves to the next car if not.
4. The Vehicle and Driver card in the fleet module keeps a car with an expired document blocked from assignment (vehicle and driver management).
5. A completed call is logged on the customer record, so a repeat caller’s history is visible.

Frequently asked questions

Does dispatch keep working if the signal drops?

The screen itself needs a connection, but a driver’s manually reported free/busy status keeps assignment working correctly even while location signal is out.

Can we change the assignment rule later?

Yes, you can switch between nearest-car and rotation assignment in firm settings.

What happens if a driver declines the call?

It moves automatically to the next free car, so the customer never has to call again.

Is dispatch tied to plate rent settlement?

No, they’re separate modules, but since they share the same shift record, completed calls also show up in settlement calculations.

What threshold triggers the complaint counter?

The threshold is defined per firm; by default, a third complaint about the same driver flags the stand manager.

See how dispatch works together with the document gate in shifts, drivers and documents, or how it feeds settlement in plate rental and driver settlement. To talk through setup for your stand, reach out. For the overview, see taxi dispatch software.