How to write SOPs for an outsourced dispatcher

The gap between a dispatch desk that nails your calls and one that fumbles them is almost always the SOPs. Vague instructions force agents to guess, and guessing on a live call costs you fares. Tight, specific procedures let a remote team handle your phones like they’ve worked there for years. Here is what to write and how.

Start with the call flow

The first and most-used SOP is the script for a standard booking call — how to answer, what to capture, and how to close. Write it as the actual words and steps, not a vague description. An agent should be able to follow it on their first call without improvising the parts that matter.

• The exact greeting, word for word
• The fields to capture in order — name, pickup, destination, time, vehicle type
• How to quote or confirm pricing
• How to enter the booking in your software
• How to close the call and what to confirm back

Document your zones and rules

Geography and pricing are where remote agents stumble most, because they don’t know your city the way your in-house team does. Spell out your service zones, what’s in and out of area, surcharge boundaries, and any rules that aren’t obvious — the airport run that’s a flat rate, the neighborhood you don’t serve after midnight. Assume zero local knowledge and write accordingly.

Write the exception SOPs

Standard bookings are easy. The procedures that earn their keep are the ones for when things go sideways — and they go sideways constantly in dispatch. Write a short, clear SOP for each common exception.

• Cancellation — how to handle it, any fee, what to record
• No-show — the wait window, who to notify, how to log it
• Complaint — what the agent resolves vs what gets escalated, and the words to use
• VIP or key account — special handling, who to alert
• Out-of-scope request — when to escalate to the owner instead of guessing

Make the escalation path unmissable

The single most important SOP is when to stop and call a human on your side. Agents need to know exactly which situations they handle and which they hand up — a major complaint, a VIP, a request outside the rules, a safety issue. Write it as a clear list with names and numbers. A desk that escalates the right things at the right time is worth more than one that tries to solve everything and gets some of them wrong.

Keep them short, specific, and current

Long SOPs don’t get read. The best ones are a page or less each, written as if-this-then-that steps, with real examples. Use the language your customers and drivers actually use. And treat them as living documents — when the soft launch or the first month surfaces a gap, fix the SOP that night so the next agent doesn’t hit the same wall.

A simple SOP template

You don’t need a fancy system. Each SOP fits a four-line frame: the situation it covers, the trigger that starts it, the steps in order, and the escalation point if the steps don’t resolve it. Write every procedure to that shape and a new agent — remote or not — can pick up your phones and sound like they belong on your team.

Common questions