Outsourced dispatch handles emergencies with a written escalation protocol agreed before it goes live: a clear list of what counts as an emergency, who the agent calls and in what order, how fast, and a defined fallback if your on-call manager does not answer. The agent does not improvise; they follow the plan you built together.
Two calls come into the same overnight desk within an hour. The first: a passenger wants to move a 7 a.m. pickup to 7:30. The second: a driver has been in a collision on the ring road, a passenger is hurt, and he does not know what to do. The same agent takes both. What separates a professional operation from a risky one is that the agent treats those two calls as completely different events — and knows exactly what to do with the second one before it ever comes in.
That knowledge is not instinct. It is a protocol, written and agreed in advance.
How does an agent tell routine from emergency?
By working from a defined list, not a gut feeling. Before an outsourced desk takes a live call for you, you agree what counts as an emergency for your operation, so the agent is matching each call against a known set rather than deciding in the moment how serious something is.
For most transportation fleets the emergency list includes a road traffic collision or any injury, a vulnerable or distressed passenger, a driver who feels unsafe or threatened, a medical incident on board, a safeguarding concern, and a vehicle breakdown that leaves a passenger stranded. Everything else — time changes, cancellations, complaints, running-late calls — is routine, and the agent handles it on the desk without escalating. Drawing that line in advance is what lets an agent act in seconds instead of hesitating.
The escalation ladder: who gets called, in what order
When a call clears the emergency bar, the agent does not guess who to phone. They follow a ladder you defined, top to bottom, until someone answers:
- Emergency services first, when life or safety is at stake — the agent does not wait for your permission to get help moving.
- Your primary on-call manager, by the number and method you specified.
- A named second contact if the first does not answer within the agreed time.
- A defined fallback — a third contact or a standing instruction — so the chain never simply ends in silence.
The order matters as much as the list. An agent who calls the owner before calling for an ambulance has the protocol backwards. A good escalation ladder makes the priority unambiguous: get help to the person first, then reach the people who run the fleet.
Real-time driver coordination and routing around the clock — overnight, weekends, holidays, and peak surges covered.
How fast should escalation happen?
For a genuine emergency, in seconds, not after the agent has finished the rest of their queue. A real protocol sets the expectation explicitly: an emergency interrupts everything, the agent stays on the line with the caller where safety requires it, and the escalation call goes out immediately rather than after a shift note is written.
This is where the difference between a dispatch desk and a message service becomes stark. A message service logs the call and passes it on when convenient. A dispatch desk running an escalation protocol treats the clock as part of the job, because in the situations that matter the delay is the damage.
What happens when your on-call manager does not pick up
This is the question that separates a real protocol from a hopeful one, and it is the one owners most often forget to answer. Phones are on silent. People sleep through calls. If your escalation plan quietly assumes the manager always answers, it has no plan for the night they do not.
A proper protocol names the fallback out loud: how many attempts, over how long, before the agent moves to the second contact; who that second contact is; and what standing instruction the agent follows if the whole chain is unreachable. The point is that the agent is never left improvising a life-safety decision at 3 a.m. because the person they were told to call did not wake up.
Why this has to be agreed before day one
An escalation protocol written after the first emergency is written too late. It has to exist before the desk takes a single live call, because the whole value of it is that the agent already knows the answer when the collision call comes in. You build it together during onboarding: the emergency list, the ladder, the timings, the fallbacks, all in writing and both sides holding a copy.
When you are evaluating an outsourced dispatch provider, this is the conversation that tells you who you are dealing with. Ask them to walk you through exactly how a collision call is handled, who gets called, how fast, and what happens if you do not answer. A provider who has crisp answers has done this many times. A provider who gets vague here is telling you the emergency will be improvised, and that is the one thing it must never be.
Common questions
Where this guide fits: it is part of the operator guide library. Next step: start a free week of 24/7 coverage.
Daniel Okoro is TransportBPO's Content Editor and Dispatcher — a former dispatcher who moved into editorial after years running live boards for taxi, NEMT and trucking accounts. He writes from dispatch-floor experience, not the marketing department, on what actually keeps a 24/7 desk running.
Connect on LinkedIn