Almost every service business hires its first dispatcher too late, and the delay is expensive in a way that never appears on a profit and loss statement. It shows up as missed calls, technicians idling between jobs, work scheduled in the wrong order, and an owner who spends the day on the phone instead of running the company. The question was never whether to hire one — it is why it took this long.
In this article
The signals that say it is time
Almost every service business hires its first dispatcher too late, and the delay is expensive in a way that never appears on a profit and loss statement. The cost shows up as missed calls, technicians idling between jobs, jobs scheduled in the wrong order, and an owner who spends the day on the phone instead of running the company.
Six signals, and three or more usually means the hire is already overdue:
- You are answering the phone during technician conversations. Both jobs get done badly.
- Missed calls exceed 15% of inbound volume. At a $340 average ticket and a 40% booking rate, twenty missed calls a week is $2,720 a week walking away.
- Technicians call you to ask where to go next. That is a dispatcher's job being done by the most expensive person in the company.
- Schedules are built the night before, in your head. Nobody else can run the day if you are sick.
- Crews average fewer than 3.5 jobs a day in a trade where 4 to 6 is normal.
- You have stopped selling. The owner is the best salesperson in most service businesses, and dispatch consumes exactly the hours selling requires.
Count how many hours a week you spend on scheduling, dispatch and phones. If it is 18 hours and your effective value doing anything else is $120 an hour, dispatch is costing the company $2,160 a week — roughly $112,000 a year — against a dispatcher who costs $52,000 fully burdened. The question was never whether to hire one. It was why it took this long.
What a dispatcher actually does
The title misleads people. A dispatcher does not simply assign jobs to trucks. In a well-run service business the role has five distinct functions, and confusing them at hiring time is why so many dispatcher hires disappoint.
Booking. Answering inbound calls and converting them into scheduled work. This is a sales function, not an administrative one, and the difference between a 45% and a 70% booking rate is enormous.
Scheduling. Building days that make geographic and skill sense. Grouping by area, matching technician capability to job type, leaving room for emergencies.
Live dispatch. Managing the day as it degrades — because it always degrades. Jobs run long, parts are missing, a customer is not home. The dispatcher is the person who reshuffles without the day collapsing.
Communication. Keeping customers informed. A text saying the technician is running forty minutes late prevents most negative reviews in this industry.
Follow-through. Unsold estimates, parts on order, callbacks, and rebooking. This is where most of the recoverable revenue in a service business sits, and it is nobody's job in a company without a dispatcher.
The mistake is hiring for function two and three — the visible logistics — and then being disappointed that booking rate and follow-up did not improve. Hire for booking and communication first; scheduling can be taught in weeks.
Keep reading — free
The rest of this article is worth the 20 seconds
Tell us where to send it and the full piece unlocks right here, along with everything else on this blog.
Rather just talk? Message us on WhatsApp.
Who to hire, and who not to
The instinct is to hire someone from the trade, on the theory that they will understand the work. It is usually wrong.
The best dispatchers tend to come from restaurants, hotels, medical front offices, call centers and retail management. What those jobs teach is exactly what dispatch requires: staying calm while several people want something at once, prioritizing without panicking, and talking to strangers all day without losing warmth.
What to test for in the interview, concretely:
A live role-play call. Have them book a job from you, playing an ordinary customer. Then do a second one where you are annoyed about a late technician. This single exercise predicts performance better than any resume.
Simultaneous-demand handling. Describe a real Tuesday: a technician is stuck, a customer is calling about a missed window, a new emergency comes in, and a supplier needs an answer. Ask what they do first and why. You are listening for a reasoning process, not a right answer.
Comfort saying no. A dispatcher who cannot tell a customer that today is full will destroy your schedule to avoid an uncomfortable sentence.
Written communication. Have them write two customer texts. Most of the role is now typing, and clarity matters.
What to weight less: trade knowledge, software experience, and industry background. All three are learnable in far less time than temperament.
What it costs
Typical compensation for a service dispatcher in the United States runs $19 to $30 an hour, or roughly $40,000 to $62,000 annually, with fully burdened cost landing 22% to 32% above that.
Two structural decisions matter as much as the number:
Include a booking-rate bonus. Dispatch is a revenue role, and paying purely hourly for a revenue role wastes the leverage. A monthly bonus tied to booking rate, average lead-to-appointment time and rebooking of unsold estimates aligns the seat with the outcome. Keep it simple enough to be calculated in five minutes.
Do not tie it to revenue alone. A dispatcher incentivized purely on booked revenue will overbook the schedule, which produces late technicians and bad reviews. Booking rate and on-time performance need to sit side by side.
The break-even is usually fast. A dispatcher who moves booking rate from 48% to 65% on 1,900 inbound calls a year at a $340 average ticket adds roughly $110,000 in revenue — before counting the additional job per crew per day that better scheduling produces.
One year, with a dispatcher
A four-technician plumbing company hired its first dispatcher after the owner spent a full week tracking his own time and found 21 hours going to phones and scheduling.
Before: 1,840 inbound calls, 812 booked (44%), 3.1 jobs per technician per day, average ticket $318. Revenue: $1,004,000. Missed calls: 296. Unsold estimates never followed up: 141, worth an estimated $263,000 in quoted work.
The hire: a former hotel front desk supervisor with no trade background, at $24 an hour plus a booking bonus. Fully burdened first-year cost including training and software: $71,400.
After twelve months: 1,910 inbound calls, 1,242 booked (65%), 3.9 jobs per technician per day, average ticket $341 — higher because technicians stopped rushing to squeeze in poorly sequenced jobs. Revenue: $1,463,000. Missed calls: 61. Unsold estimates followed up: 100%, producing 47 recovered jobs worth $88,000.
Revenue difference: $459,000. Dispatcher cost: $71,400.
And the number the owner cared about most, which does not appear in any of the above: he went from 21 hours a week on dispatch to four, and used the recovered time to open a second service line that produced $190,000 in its first year.
Not the schedule. The unsold estimate list. Every service business is sitting on months of quoted work that nobody ever called back about, and it is the fastest possible way for a new hire to pay for themselves in their first sixty days. It also builds their credibility with the technicians, who watch closely to see whether the new person makes their lives better or just adds a layer.
The first ninety days
Dispatcher hires fail on onboarding more than on selection. A structured ninety days:
Weeks 1 to 2 — Ride along. Two full days in a truck with different technicians. A dispatcher who has watched a job happen schedules realistically; one who has not will book a two-hour job into a one-hour slot forever.
Weeks 2 to 4 — Take calls with a script, with you listening. Not a rigid script, but a defined structure: qualify, quote the diagnostic fee, offer two windows, confirm details, set expectations. Review recordings together daily.
Weeks 4 to 8 — Own booking, shadow scheduling. They book everything; you still build the day. This separates the two skills so neither is learned badly.
Weeks 8 to 12 — Own the board. They build the schedule, you review it each morning for two weeks, then stop.
Two artifacts need to exist before day one, and their absence is the most common cause of a struggling dispatcher: a written booking script and a job-duration reference saying how long each common job actually takes. Without the second, no dispatcher can build a workable day, and the failure will be blamed on them.
The tools the seat needs
A dispatcher without the right tooling spends the day doing manual work that software should absorb, and the company concludes the hire underperformed. Five capabilities matter, in this order:
A single schedule everyone can see. Technicians on their phones, the dispatcher on a board, updated live. The moment there are two versions of the day, the day is already lost.
Call tracking with recording. Not for surveillance — for coaching. Listening to five booking calls a week together is the fastest way to move a booking rate, and it is impossible without recordings.
Automated customer messaging. Appointment confirmation, on-the-way notification and a follow-up after the visit. These three messages, sent automatically, remove a large share of the dispatcher's repetitive typing and simultaneously improve reviews.
A list of every open item. Unsold estimates, parts on order, callbacks, customers waiting on a date. If this lives in someone's memory or in a notebook, it is not a system, and it will leak.
Job durations attached to job types. So the schedule builds itself realistically instead of optimistically.
What matters less than owners expect: which specific software. Companies switch platforms hoping to solve a process problem and discover the same chaos in a new interface. The order of operations is to define the process, run it manually for a month, and then buy the tool that fits what you actually do.
One caution worth stating plainly. Do not let the dispatcher be the only person who understands the system. Cross-train at least one other person on booking and schedule building, even if they only cover vacations. A company where a single person holds the entire operating rhythm has traded one bottleneck for another, and the second one is harder to see coming.
Five mistakes when hiring a dispatcher
- Hiring from the trade for the wrong reasons. Technical knowledge is learnable; temperament under simultaneous pressure is not.
- Treating it as an administrative role. It is the highest-leverage revenue seat in a small service company.
- No job-duration reference. Guarantees an unrealistic schedule and an unfair judgment of the new hire.
- Owner keeps taking calls. Splits authority, confuses customers and prevents the dispatcher from ever owning the role.
- Bonusing on revenue alone. Produces an overbooked schedule, late technicians and reviews that cost more than the extra jobs earned.
The numbers to watch
- Booking rate — booked jobs divided by qualified inbound calls, the primary metric of the seat.
- Missed and abandoned calls, by hour of day, which tells you when coverage is thin.
- Jobs per technician per day, before and after.
- On-time arrival percentage, the counterweight that keeps booking honest.
- Unsold estimates followed up, and revenue recovered from them.
- Owner hours spent on dispatch, tracked monthly, because that number is the entire reason for the hire.
The first dispatcher is the hire that converts an owner-operated business into a company. It is also the one owners resist longest, because dispatch feels like something they are uniquely good at — and they usually are. But being good at the $30 task while the $200 task goes undone is the most common way a capable service business stops growing at exactly the point it could have doubled.
Find out what dispatch is costing you today
Send us your inbound call count, your booking rate and the hours you personally spend on scheduling each week. We will run the cost of the seat against the cost of not filling it.
Frequently asked questions
When should a service business hire a dispatcher?
When three or more of six signals are present, at which point the hire is usually already overdue. You are answering the phone during technician conversations, so both jobs get done badly. Missed calls exceed 15% of inbound volume — at a $340 average ticket and 40% booking rate, twenty missed calls a week is $2,720 walking away. Technicians call you to ask where to go next, which is a dispatcher's job being done by the most expensive person in the company. Schedules are built the night before in your head, so nobody else can run the day if you are sick. Crews average fewer than 3.5 jobs a day in a trade where 4 to 6 is normal. And you have stopped selling, because dispatch consumes exactly the hours selling requires. The decisive calculation: 18 hours a week on dispatch at a $120 effective value is roughly $112,000 a year against a dispatcher who costs $52,000 burdened.
What does a service dispatcher actually do?
Five distinct functions, and confusing them at hiring time is why so many dispatcher hires disappoint. Booking, which is answering inbound calls and converting them into scheduled work — a sales function, not an administrative one, where the gap between a 45% and a 70% booking rate is enormous. Scheduling, meaning days built to make geographic and skill sense with room left for emergencies. Live dispatch, managing the day as it degrades, because it always degrades. Communication, keeping customers informed, since a text saying the technician is running forty minutes late prevents most negative reviews in this industry. And follow-through on unsold estimates, parts on order, callbacks and rebooking — where most of the recoverable revenue sits and which is nobody's job in a company without a dispatcher. Hire for booking and communication first; scheduling can be taught in weeks.
Who makes a good dispatcher?
Usually not someone from the trade, despite the instinct. The best dispatchers tend to come from restaurants, hotels, medical front offices, call centers and retail management, because those jobs teach exactly what dispatch requires: staying calm while several people want something at once, prioritizing without panicking, and talking to strangers all day without losing warmth. Test four things in the interview. A live role-play call where they book a job from you, followed by a second call where you are annoyed about a late technician — this predicts performance better than any resume. Simultaneous-demand handling, described through a real Tuesday, listening for a reasoning process rather than a right answer. Comfort saying no, because a dispatcher who cannot tell a customer that today is full will destroy your schedule. And written communication, since most of the role is now typing.
How much does a dispatcher cost and what do they return?
Typical compensation runs $19 to $30 an hour, roughly $40,000 to $62,000 annually, with fully burdened cost landing 22% to 32% above that. Two structural decisions matter as much as the number. Include a booking-rate bonus, because dispatch is a revenue role and paying purely hourly for a revenue role wastes the leverage — tie it to booking rate, lead-to-appointment time and rebooking of unsold estimates, kept simple enough to calculate in five minutes. And do not tie it to revenue alone, because a dispatcher incentivized purely on booked revenue will overbook the schedule, producing late technicians and bad reviews. The break-even is usually fast: moving booking rate from 48% to 65% on 1,900 inbound calls at a $340 average ticket adds roughly $110,000 in revenue, before counting the extra job per crew per day that better scheduling produces.
How do you onboard a new dispatcher?
In a structured ninety days, because dispatcher hires fail on onboarding more often than on selection. Weeks one and two are ride-alongs — two full days in a truck with different technicians, because a dispatcher who has watched a job happen schedules realistically while one who has not will book a two-hour job into a one-hour slot forever. Weeks two to four, they take calls with a defined structure while you listen and review recordings daily. Weeks four to eight, they own booking while you still build the day, which separates the two skills so neither is learned badly. Weeks eight to twelve, they own the board with your morning review for two weeks, then without it. Two artifacts must exist before day one: a written booking script and a job-duration reference, without which no dispatcher can build a workable day.