Dispatching service technicians is deciding, over and over all day, which tech goes to which job next. That’s it. The trouble is you’re making that call fifteen times before lunch while the phone keeps ringing, and every wrong call costs you a truck roll or an SLA miss.
If you dispatch 5 to 25 techs, you don’t need a control room. You need a repeatable way to sort the day and a single board everyone reads off of. Here’s how I run it.
Triage before you assign anything
The first move every morning isn’t assigning. It’s sorting. Line up every open work order and rank it by two things: how bad it is, and when it’s due.
Priority is about the site, not the caller’s tone. A rooftop unit down at a restaurant in July is an emergency because they lose the dining room. A flickering light in a back hallway is not, even if the caller is louder about it. Learn to hear past the volume.
Then layer in the SLA. If you do contract work for property managers, most of your accounts have a response window written into the agreement. Four hours for a no-cool. Next business day for a general repair. Miss those and you eat a chargeback or a scorecard ding. Sort your board so the tightest clock is at the top, not the newest ticket.
Once it’s sorted, most of your day is decided. You’re not reacting anymore, you’re working a list.
Match the tech to the job, not just the map
Now you assign. Two things drive it: skill and geography, in that order.
Skill first, because sending your best generalist to a job that needs an EPA cert or a backflow tester is a wasted trip. You’ll roll a second truck to do it right and pay for both. If a job needs a specific ticket, the pool of techs shrinks to whoever holds it, and geography sorts out from there.
Geography second, and this is where most shops lose money without noticing. A tech stuck in cross-town traffic is a tech you’re paying to drive. Cluster jobs by area. If two calls come in near the same industrial park, the same tech takes both even if a different guy is technically “next up.” Windshield time is the most expensive thing on your P&L that nobody puts on the P&L.
The trap is over-optimizing the route while ignoring the clock. A perfectly tight loop that blows a four-hour SLA on the third stop isn’t tight, it’s late. SLA wins ties.
Keep the board current or it lies to you
Here’s the part that separates a shop that runs clean from one that runs on adrenaline. The board has to be true in real time, and everyone has to be reading the same one.
The failure mode is texts and phone calls. You text Mike a job. Mike’s already on another call so he doesn’t answer for forty minutes. Meanwhile you’ve mentally assigned it to him, so you don’t give it to anyone else. The job just sat for forty minutes and nobody was working it. Multiply that by a full crew and you’ve got a dispatcher who thinks the day is handled and a board full of jobs that aren’t moving.
One shared source of truth kills that. When you assign a work order, the tech sees it on his phone. When he marks it en route, you see that without asking. When he closes it, it drops off the active board on its own. Nobody’s guessing, nobody’s texting “you done yet?”, and you’re not holding the whole day’s state in your head.
That’s the real argument for running dispatch on software instead of a whiteboard and a group text. Not that it’s fancy. That the board can’t drift from reality, because the techs update it by doing their jobs. You can see how the work order flow moves a job from open to assigned to complete, and how the dispatch and scheduling tools keep every tech looking at the same board you are.
If you’ve been comparing options, the honest version of the tradeoffs is on the Jobber comparison page. Pick whatever keeps one board true. That’s the whole job.
Handle the mid-day blowup without torching the plan
Your clean morning board survives until about 11am. Then a compressor dies at a grocery store with a two-hour SLA and everything shuffles.
Don’t rebuild the day. Ask one question: who’s closest that has the skill, and what’s the cheapest thing to bump? Usually the answer is pulling the tech off a low-priority general repair that has a next-day window. That job can slide. The grocery store can’t.
Reassign the emergency, push the bumped job to the next slot, and tell both techs. The tech you pulled needs to know why so he doesn’t drive to a job you just moved. Two taps if your board is live, a round of phone tag if it isn’t.
The shops that survive emergencies calmly aren’t the ones with fewer emergencies. They’re the ones who can see the whole board at once and know instantly what’s safe to move. That only works if the board was true before the blowup started.
Get the morning triage right, keep the board honest, and the reshuffles stop feeling like fires. If your current setup is a group text and a spreadsheet, see how the scheduling board works and run a week on it before you decide.