Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
Booking the call is one job. Running the day once the calls are booked is a different one entirely — and it's the one that quietly decides whether your trucks finish six jobs or four, whether the emergency gets covered without blowing up three other appointments, and whether your best tech spends the afternoon driving across town instead of turning wrenches. That job belongs to the dispatcher.
Most owners hire someone to "answer phones and schedule" and never realize they've actually created two roles wearing one hat. The person who books the call and the person who coordinates the field once it's booked need different instincts, and treating them as interchangeable is why so many plumbing days fall apart by 2 p.m. The dispatcher isn't a receptionist with a map. They're the air-traffic controller for your revenue.
BOOKED CALLS ──▶ [ DISPATCHER ] ──▶ THE FIELD
│
┌──────────────┼──────────────┐
▼ ▼ ▼
who goes? what's next? emergency in
(right tech) (protect flow) (reshuffle)
└──────────────┴──────────────┘
a good day │ a wrecked dayOwner symptoms
Techs finish early or sit idle while other jobs pile up — the day isn't balanced.
Every emergency reroute turns into chaos, missed appointments, and angry callbacks.
When your dispatcher is out, the whole day limps, because it all lives in their head.
Why this happens
Dispatch gets treated as a clerical task instead of a coordination role, so it's staffed and trained like one. The person handling it may be excellent on the phone and still have no framework for the harder work: matching the right tech to the right job, sequencing calls so trucks aren't crisscrossing the service area, and deciding — in real time — what gives when an emergency lands. Those are judgment skills, and they rarely come bundled with a warm phone voice. When no one owns that judgment, the schedule runs on luck and the field runs on whoever complains loudest.
Common mistakes
Merging dispatch with call-booking and assuming one person naturally does both well.
Hiring for phone friendliness only, ignoring the coordination and pressure-handling the role actually demands.
No real training, so the dispatcher learns your field by trial, error, and callbacks.
Letting techs self-dispatch, choosing their own next stop and quietly wrecking the day's flow.
Building no backup, so everything the dispatcher knows walks out the door when they take a day off.
Business consequences
A weak dispatch seat leaks money in ways that never show up as a single line item: wasted windshield time, techs idling between poorly sequenced jobs, the wrong person sent to a job they can't finish, and emergencies that torch a whole afternoon of booked work. Each is small; together they can cost you a job or two of capacity every single day. The owner who builds the role deliberately gets more completed jobs out of the same trucks and techs, fewer frantic reschedules, and a day that holds together even when it gets busy — which is exactly when most shops come apart.
How experienced operators think about it
They treat the dispatcher as the person who protects the schedule, not just fills it. The mental model is throughput: every decision is about keeping trucks productive and jobs flowing, not about placating whoever's on the line right now. A strong dispatcher knows the techs — who's fast, who's thorough, who handles a tricky repipe versus a routine drain — and routes accordingly. They hold the schedule's integrity against constant pressure to bend it, and they know when bending it is the right call. Experienced owners hire for that judgment and temperament first, then teach the software and the service area. You can train the tools; you can't easily train the head.
Practical actions
Separate the roles on paper first. Write down what call-booking owns versus what dispatch owns, even if one person does both for now — you'll hire and train far better once the second job is visible.
Hire for judgment under pressure. In interviews, hand them a messy day — two emergencies, a running-late tech, a VIP customer — and listen to how they'd sequence it, not just whether they're pleasant.
Teach them the field. Make sure the dispatcher knows each tech's real strengths and how long common jobs actually take, so routing is informed, not guessed.
Give dispatch authority over the schedule. Techs execute the plan; they don't rewrite it. Self-dispatching quietly undoes everything the role exists to protect.
Write down how the day runs. Document the routing logic and emergency priorities so it doesn't all live in one person's head — and so a backup can step in.
Build a backup before you need one. Cross-train a second person so a sick day or vacation doesn't take the whole schedule down with it.
Questions every owner should ask
Is one person quietly doing two different jobs — and paying for it in a rough day?
Does my dispatcher actually know my techs and my jobs, or just my calendar?
If my dispatcher didn't show up tomorrow, who runs the day — and how badly does it go?
Frequently asked questions
Isn't the dispatcher just the same person who answers the phone and books jobs?
Often they're the same seat, especially in a smaller shop — but they're two different jobs. Booking the call is front-of-phone work: capturing the lead, being helpful, getting the appointment on the calendar. Dispatch is field coordination: deciding which tech goes where, in what order, and what moves when an emergency lands. One is customer-facing intake; the other is real-time logistics. Even if one person handles both, treat them as distinct responsibilities so you can hire, train, and eventually split them without the whole thing falling apart.
Should I let my experienced techs pick their own jobs and route themselves?
It feels efficient, but it usually undermines the day. Techs optimize for their own convenience — the easy job, the nearby stop, the customer they like — not for the shop's overall throughput or fairness across the crew. That's not a character flaw; it's just a different vantage point. The dispatcher sees the whole board and can balance the day in a way no individual tech can from the field. Let techs give input, but keep the routing decision in the dispatch seat.
Related articles
Running a Profitable Plumbing Company — the pillar.
Building the Office Side of a Plumbing Company — where the dispatch seat fits in the office.
Closing the Gap Between the Field and the Office — the two-way flow dispatch depends on.
Why Jobs Take Longer Than You Quoted — the time problem dispatch helps contain.
Where Time Leaks on a Typical Job — the routing and idle time a strong dispatcher recovers.
Every business has more decisions than time
Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.
Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.