Hire a Dispatcher, or Fix the Schedule? A Decision Framework

There is a moment in most growing field service companies, usually somewhere between the fifth and the tenth truck, when scheduling stops working. It rarely arrives as a crisis. It arrives as the owner or the office manager quietly losing their mornings to the board.

The instinctive fix is to hire a dispatcher. Sometimes that is exactly right. Often it makes a structural problem permanent and adds a salary to it.

The way to tell is to ask a specific question: what would this person actually spend their day doing?

Two very different jobs wear the same title

Coordination

Genuine dispatch work. Talking to customers about access and timing. Handling the emergency that just came in and deciding what it displaces. Chasing a part. Knowing that the Hendersons need a call twenty minutes ahead because of the dog, and that this particular technician is the right one for that particular commercial account.

This is judgment, relationship and exception handling. It does not automate, it scales roughly with job volume, and a good dispatcher doing it is worth considerably more than they cost.

Repair

Rebuilding a day that was broken before it started. Moving the 1:00 because the 10:00 is forty minutes north and was never going to work. Calling a customer to push a window because the morning ran over. Re-sequencing the afternoon for the third time.

This work feels urgent and looks like dispatch. It is not. It is the cost of a booking process that promised appointments without checking whether they fit together, and every hour of it is an hour spent undoing a decision made earlier by a system that could have known better.

Hiring to do repair work does not solve the problem. It funds it, permanently, and grows it linearly with your truck count.

The diagnostic: measure the split

Do not estimate this. Measure it for one week.

Have whoever currently owns the board tally their time in two columns. Coordination in one; repair in the other. A tick every fifteen minutes is enough resolution.

Three supporting numbers make the answer clearer, and you likely have all three already:

• Same-day reschedule rate. High means the day is not surviving contact with reality. That is repair work, generated daily.
• Productive utilization. If crews are productive roughly half the shift, there is capacity inside your existing trucks that a dispatcher will not recover — because the losses are travel and slack, not coordination.
• Backtracking frequency. How often a truck crosses its own path. Common backtracking means the driving was created at booking. No dispatcher fixes that after the fact; they can only shuffle it.

If the answer is "fix booking"

The specific change is narrow, and it happens one step earlier than dispatch. When a slot is requested, the system should answer can a qualified crew physically reach this address by then, given everything else already on their day — with travel computed from where that truck will actually be at that hour — rather than is that block empty.

Slots that fail never get offered. The repair work does not get automated; it stops being generated.

Two supporting pieces make that check meaningful: service durations that reflect what the work actually takes, and travel treated as an explicit scheduled quantity rather than something absorbed inside an appointment block.

If the answer is "hire"

Then hire, and hire well — but set the role up so it stays coordination.

• Give them authority over the board. A dispatcher who has to ask permission to move a job is a message-taker.
• Define the exception rules in advance. What displaces what. Which accounts get priority. What the emergency threshold is. Written down, these decisions stop being litigated daily.
• Do not make them the phone queue. If every inbound call routes to the dispatcher, coordination time collapses into reception time, and you will be having this conversation again in six months.
• Measure their impact on adherence and same-day reschedules, not on call volume. Activity metrics will make a busy dispatcher look productive while the board gets worse.

The case for both, in order

For most companies past a certain size, the honest answer is both — with a sequence.

Fix the booking process first, so the schedule stops generating repair work. Then hire a dispatcher into a role that is genuinely coordination, and give them a board that holds together well enough that their judgment goes into customers and exceptions rather than into damage control.

Done in that order, one dispatcher covers considerably more trucks, the role is more satisfying, and the person lasts. Done in the other order, you hire someone into a job that consists mostly of absorbing a structural problem, and then hire a second one when the first burns out.

Common questions

When should a field service company hire a dispatcher?

When the volume of genuine coordination work — customer communication, exceptions, emergencies, parts and access — exceeds what the current team can absorb. If the prospective dispatcher's day would instead be spent rebuilding schedules that did not survive the morning, that is repair work created by the booking process, and hiring makes the cost permanent.

How many trucks can one dispatcher handle?

It varies far too much with job type and how the schedule is built to give a useful number. A dispatcher handling short, dense, repetitive maintenance work manages far more trucks than one coordinating long installs with parts dependencies. Measure how your dispatcher's time is actually split before using anyone's ratio.

Can scheduling software replace a dispatcher?

No, and vendors claiming otherwise are overselling. Software can remove the repair work — the reshuffling of days that were infeasible when booked. It does not replace judgment, customer relationships or exception handling, which is what a good dispatcher is actually for.