Buyer Guides
Dispatching Made Simple: Getting Urgent Calls to the Right Tech
Dispatching is the job nobody wants and everybody needs. Someone has to decide which tech goes where, which call cannot wait, and which customer gets the bad news that their appointment moved. In a small shop that someone is usually the owner, answering the phone from a crawl space. There is a simpler way to run it.
The real job of a dispatcher
Strip away the title and a dispatcher does three things: answer the call, figure out how urgent it is, and get it to the right person. The right person might be the on-call tech for a burst pipe, the office for a billing question, or the schedule for a routine tune-up. Most of that is pattern matching, not judgment. Urgent goes to the phone that is awake. Routine goes to the calendar. Billing goes to the office.
Writing the routing rules down
Whatever answers your phones needs your rules in writing, because nobody can guess them. Start with your techs: who is on call, which tech covers which area, who handles what kind of work. Then the urgency tiers. Tier one is the stuff that cannot wait: gas smells, active water leaks, no heat in freezing weather, sparking panels. Tier one goes to the on-call phone immediately, while the caller is still on the line.
Tier two is urgent but not tonight: a system that is limping along, a repair that can wait until morning. Tier two gets a booked morning slot and a summary text. Tier three is routine: quotes, maintenance, questions. Tier three gets a booked appointment and nobody gets paged.
Write it on one page. That page becomes the routing logic for an AI receptionist for contractors, and honestly it makes a human dispatcher better too, because now there is something to train from.
What the caller experiences
Done right, the caller never knows there was routing at all. They call, someone answers on the first ring, asks what is going on and where, and then either connects them to the on-call tech or books them in. Compare that to the usual small-shop experience: voicemail, a callback an hour later, a second call to confirm the address, a text with a window that might change.
Learn how AI receptionists transfer calls to the right person if you want the mechanics of the warm transfer, where the caller is connected to your tech with the job details already passed along.
The morning summary
The part owners end up liking most is the morning read. Every call from the night before arrives as a short summary: who called, what the problem was, what tier it fell into, what got booked. You scan it with coffee and you know the day before the day starts. No voicemails to decode, no wondering whether the 2 am call was important.
When you still need a human
Routing handles the intake. It does not handle the day’s chaos: the tech who calls in sick, the job that runs four hours over, the customer who insists on speaking to the owner. That is real dispatching judgment, and it stays with a person. The point of routing the phones well is to free that person up for the part that actually needs them, instead of spending the morning playing back voicemails.
Simple dispatching is not about technology. It is about deciding in advance where each kind of call goes, and then making sure every call actually gets there.
I write the agents that run on clinic phone lines and inboxes: the conversation engine and the booking logic behind them, plus the integrations with Pabau, Fresha and Phorest. Everything here comes out of systems we have actually shipped, not a content plan.
