The Dispatcher Role in a Commercial Kitchen Service Company

The dispatcher makes 5 decisions on every job and 3 of them affect margin directly. It is treated as an administrative role and priced like one, and in a service company past three or four technicians it is the second most commercially important seat in the building.

The short version

The job description says answering phones and assigning work. What the role actually does is allocate a finite resource, technician hours, against demand that arrives unpredictably, under constraints nobody wrote down.

Every assignment is a decision about who goes, when, with what, and at what cost. A good dispatcher makes those decisions with information. A dispatcher without it is guessing efficiently.

The difference between those two shows up as first-time fix, drive time, overtime and the pattern of second visits, none of which appear on the dispatcher's job description.

The 5 decisions the role owns

Decision	What it affects
Which job goes first	SLA compliance on portal work, and relationships on direct work
Which technician goes	First-time fix, through skills and familiarity with the equipment
Whether the parts are available	Whether it is one visit or two
What the technician is told before leaving	Diagnosis time on site, and whether the right questions get asked
When to say no	Overtime, coverage at the edge of your area, and the scorecard

The third and fourth rows are the ones that separate a dispatcher with good information from one without. Both are answerable in seconds where the equipment has a record, and unanswerable where the job is an address and a description.

What the dispatcher needs in front of them

Six things, and most dispatch boards show two of them.

• Which equipment the job is on, by manufacturer, model and serial, rather than a description of a symptom
• What was done to it before, and what was recommended and declined
• Its warranty position, because that decides who is billed and whether authorization is needed first
• Whether the part is in a van or the store, and which van
• Real drive times, at the hour of dispatch rather than distances on a map
• The account's rules, meaning response windows, spending limits and site access

Roopairs holds equipment records with manufacturer, model, serial, service history and warranty alongside parts inventory, which is what puts the first four on the board rather than in somebody's memory.

Without those, the dispatcher optimizes for the only variable they can see, which is who is nearest. That is the right answer often enough to feel correct and wrong often enough to be expensive.

The morning is not the job, the rebuild is

Anybody can build a schedule. The role is what happens when it breaks.

A kitchen goes down at 10am and the afternoon has to be rebuilt around it. That is the actual work: which of the six scheduled jobs moves, which customer gets a call, whether the emergency needs the nearest technician or the one who knows the equipment, and whether anybody is now going to run into overtime.

How often that happens is worth measuring, because it is the load nobody quantifies. Count reschedules per week for a month and the result usually surprises the owner.

It also explains why dispatchers burn out. The role is continuous interruption with commercial consequences and no visible output, and a service company that never acknowledges that loses good ones.

3 rules that should be written down rather than judged

Each is currently decided under pressure, differently each time.

1. Which work wins when two jobs need the same slot. A portal ticket with a four hour window against a direct customer who called first is a relationship against a scorecard, and it should not be settled at 10am by whoever is loudest
2. When to decline. A written service area in drive time, and a rule for jobs outside it
3. When to escalate. Which situations the dispatcher decides and which go to the owner, with a value or a customer threshold

Writing these down is not bureaucracy. It removes the three decisions a dispatcher is least equipped to make alone and most often blamed for afterwards.

What to measure about the role

Four numbers, and none of them is calls answered.

Second visits and their causes, because dispatch information is behind two of the four common ones. Realized revenue per technician day, which absorbs travel and rescheduling without needing either attributed. Response compliance on portal accounts. And overtime hours, which are frequently a scheduling symptom rather than a demand one.

Reviewing those with the dispatcher monthly changes the conversation from activity to outcomes, and it is where the role's commercial weight becomes visible to everyone including them.

When the service company outgrows one person

The signals are consistent and they arrive before anybody names them.

Calls going unanswered at peak. The schedule being rebuilt more than once a day. Technicians phoning the office for information they should be able to see. And the dispatcher unable to take leave without the week degrading.

The last is the clearest test. If one person's absence measurably damages a week, the role has no redundancy, and that is a risk rather than a compliment to the person.

The answer is not always a second dispatcher. Frequently it is giving technicians self-serve access to the information they keep phoning for, which removes a large share of the interruptions without adding headcount.

What good looks like

A dispatcher who can answer three questions instantly about any open job.

What equipment is it, has anybody been to it before, and is the part available. Where those three take seconds, the role is properly equipped and the decisions above get made well.

Where they take a phone call each, the service company has a records problem that presents as a dispatch problem, and hiring another dispatcher will not fix it.

Roopairs runs a product tour where you can see the dispatch board with equipment records, history and parts inventory behind it.

What service companies in the trade say

“Learning to use this software was easy, it really is self-intuitive, everything makes sense which is nice that you don't have to go through formal training to understand how to use this software.” — Greg Austin

Also worth reading

• Warranty Expiry Reporting: Catching the Cliff Before Your Customer Does
• Are Dispatchers Expendable for Commercial Service?
• The future of IoT for commercial kitchen repair companies

Frequently asked questions

What does a field service dispatcher actually do?

Allocates technician hours against unpredictable demand, making five decisions per job: which job goes first, who goes, whether the parts are available, what the technician is told beforehand, and when to say no. Three of the five affect margin directly.

What does a dispatcher need to see?

The equipment by manufacturer, model and serial, its service history, its warranty position, where the part is, real drive times at the hour of dispatch, and the account's response and spending rules. Most dispatch boards show the last two at best.

Why does dispatch affect first-time fix?

Because two of the four common causes of a second visit are the part not being on the van and the equipment not being what was expected. Both are information the dispatcher either had or did not have before the technician left.

What should be written down rather than judged?

Which work wins when two jobs need the same slot, when to decline a job outside your service area, and which situations escalate to the owner. All three are currently decided under pressure and differently each time.

How should the role be measured?

Second visits and their causes, realized revenue per technician day, response compliance on portal accounts, and overtime hours. Calls answered measures activity rather than outcome.

When do you need a second dispatcher?

When calls go unanswered at peak, the schedule is rebuilt more than once a day, or one person's leave degrades the week. Often the better answer is giving technicians access to the information they keep phoning for.