The Hidden Load on the Dispatcher

Why this matters

When a tech wears out, the shop sees it: slower calls, a sore back, a callback. When the dispatcher wears out, the shop sees nothing until the morning they give notice, and then it finds out how much of the business lived in one person's head. The dispatcher's load is invisible because it is made of things nobody logs: the hundredth interruption, the customer who yelled, the fifth "we can't get there today." This card names those loads, shows how to measure them in one week, and covers the two fixes that actually move them, rotation and protected breaks.

Three loads nobody writes down

Interruption. A dispatcher's job is to be interrupted. Phones, tech texts, a walk-up from the warehouse, a tablet ping. Each one is small. The cost is not the interruption itself but the re-entry: rebuilding where you were in the board, which tech was about to be moved, which customer was waiting for a callback. Research on task switching consistently finds that resuming a complex task after an interruption takes longer than the interruption, and errors cluster right after the switch. On a dispatch board, that error is the wrong address texted to a tech or a double-booked window.

Absorbed anger. The customer cannot yell at the broken furnace, so they yell at the person who answers. Techs do this too, more politely: the tech who just found the wrong part on the truck takes it out on the voice on the radio. The dispatcher is expected to stay level through all of it, which psychologists call emotional labor: managing your own visible feelings as a condition of the job. It is real work, and it draws down the same reserve that patience and judgment run on.

Being the one who says no. Someone has to tell the third no-heat call of the afternoon that the earliest slot is tomorrow at eight. The owner sold the capacity, the techs did the work, and the dispatcher delivers the bad news. Over months, the person who only ever delivers the limit starts to feel responsible for it. That is where the dispatcher who stays two hours late "to fit one more in" comes from.

None of these show up in a ticket count. A shop can watch a dispatcher's call volume hold flat while the load underneath it doubles, because volume was never the load.

What dispatcher burnout looks like before the resignation

The general signs of crew burnout belong to another card (see related). These are the ones specific to the desk, roughly in the order they tend to appear:

• Lunch at the desk, every day. Not occasionally. The dispatcher has stopped believing anyone else can hold the phone for thirty minutes, and usually they are right, because nobody has been trained to.
• Shrinking callbacks. "I'll call you back with a window" turns into the customer having to call again. Not laziness: the dispatcher is triaging their own attention and the promise is the first thing dropped.
• A flatter, shorter phone voice, and more calls ending on the customer's frustration rather than a booked slot. Listen to a few recordings if you record calls.
• Board errors after the busy hours. Double-booked windows, a tech sent to yesterday's address. Errors that rise after a surge are the re-entry cost showing up on the board.
• Irritability with techs over things that used to be routine, especially late-afternoon radio traffic.
• Coming in early and leaving late without being asked, and checking the schedule from home on weekends. Owners often read this as commitment. It is frequently the opposite: the dispatcher no longer trusts the system to run for an hour without them.
• Using sick days in pairs, or a sudden run of short absences after a long stretch of none.

One of these is a bad week. Three or more held for a month is a load problem, and the fix is in the work design, not a pep talk.

Measuring it: one week of tallies

You cannot fix what you are guessing at. The cheapest instrument is a tally sheet the dispatcher keeps for one ordinary week (not a holiday week, not a storm week): a tick per inbound call, per tech contact, per walk-up, a mark for every call that ended angry or ended in a no, and a note of the longest stretch without any interruption, in minutes.

Worked example. A nine-tech HVAC and plumbing shop, one full-time dispatcher on the desk 7:00 to 4:30, so 9.5 hours a day, with a part-time CSR who works mornings on billing.

Over five days the tally averaged:

• Inbound customer calls: 60 a day.
• Tech contacts (calls, texts, radio): 45 a day.
• Walk-ups from the warehouse or the owner: 10 a day.

That is 60 plus 45 plus 10, or 115 interruptions a day. Across 9.5 hours, 115 divided by 9.5 is about 12 an hour, one every five minutes on average. But the average hides the shape: 33 of the 115 landed between 7:00 and 9:00, when every tech is starting and every overnight no-heat customer calls. Thirty-three in 120 minutes is one every 3.6 minutes. The longest quiet stretch of the whole week was 22 minutes, on Wednesday, and it was the lunch hour, which the dispatcher spent at the desk.

The hard-call tally: 19 calls that ended angry over the week, and 23 that ended in a no, so 42 of the week's 300 customer calls (60 a day times 5) were bad-news calls, 14 percent. Lunch eaten at the desk: 5 of 5 days.

What the numbers say. The customer calls are mostly irreducible; that is the business. The tech contacts are the lever. When the owner read the tech-contact column with the dispatcher, roughly half were questions that did not need an answer that minute: "what's my next one," "can you send me the model number from last visit," "did the part come in." They could wait for a scheduled check-in or be answered from the job record on the tech's own tablet.

What the shop changed. Two fixed tech check-in windows, 10:00 and 2:00, for anything non-urgent; urgent means a safety issue, a customer dispute on site, or a tech who cannot proceed. Job history and parts status pushed to the techs' tablets so they could look it up themselves. And the CSR, already in the building mornings, trained to take the phone 12:00 to 12:30 and for fifteen minutes at 3:00.

The result, measured the same way a month later. Tech contacts fell from 45 to 24 a day. Calls and walk-ups held at 60 and 10. Total interruptions went from 115 to 94 a day, about 10 an hour. That is an 18 percent drop in interruptions overall (21 of 115), but a 47 percent drop in the column the shop controlled (21 of 45). The longest quiet stretch rose to the 30-minute lunch, now actually away from the desk, plus a 15-minute afternoon break. The dispatcher's own comment was that the afternoons stopped feeling like the mornings.

What would change the answer. If the tally had shown customer calls at 90 a day instead of 60, check-in windows would not have been enough: that is a second person on the phones for the morning surge, or an answering service for overflow during the 7:00 to 9:00 peak. If the angry-call count had been concentrated in one call type (say, rescheduled maintenance), the fix would have been upstream, in how those appointments are confirmed, not at the desk.

Rotation: spreading the hardest part

A one-dispatcher shop cannot rotate the desk, but it can rotate the hardest hour and the hardest calls.

• Cover the surge with a second voice. Whoever else is in the building at 7:00 (owner, service manager, CSR) takes overflow calls until 9:00. Even 20 percent of the morning calls taken by someone else is real relief at the moment the re-entry cost is highest.
• Hand up the worst calls. A standing rule that any call that turns abusive, or any customer demanding an exception the dispatcher cannot grant, goes to the owner or manager. The dispatcher's job becomes "I'm getting you to the person who can decide," which is a different emotional position from being the wall. Script it so the handoff sounds like service, not escape.
• Cross-train a backup. At least one other person who can run the board for a full day. Without this, the dispatcher cannot take a vacation without dread, and a dispatcher who cannot take a vacation is on a countdown. In a shop of 12 or more people, a second trained board operator is a staffing decision, not a luxury.
• Rotate on-call phone duty after hours instead of letting it default to the dispatcher's cell. On-call design is its own card (see related).

Protected breaks, and what the law layer says

A break the dispatcher spends answering the phone is not a break, legally or physically.

Federal floor. The Fair Labor Standards Act does not require employers to give breaks at all. But if you give short rest breaks, typically 5 to 20 minutes, they are counted as hours worked and must be paid under the Department of Labor's rule at 29 CFR 785.18. A meal period of 30 minutes or more can be unpaid only if the employee is completely relieved from duty (29 CFR 785.19). A dispatcher eating at the desk while answering calls is not relieved, so that "unpaid" half hour is compensable time at the federal level, and if it pushes the week past 40 hours for a non-exempt dispatcher, it is overtime.

State layer, which routinely goes further. Some states mandate meal and rest breaks outright. California requires a 30-minute meal period before the end of the fifth hour and a paid 10-minute rest break per four hours worked or major fraction, with a premium of one hour's pay owed for each workday a required meal period is missed, and a separate hour for each workday a required rest break is missed (Labor Code section 226.7). Washington and Oregon have their own mandatory meal and rest rules. Many states, including large parts of the South and Midwest, have no adult break requirement beyond the federal floor. Check your own state labor department, and this is not legal advice; a wage-and-hour attorney is the person to see if your office staff have been working through unpaid meals for months.

Making it physical, not just legal. The break has to leave the desk. Phone forwarded to the covering person, dispatcher out of earshot of the board. The CSR covering at noon in the example above only worked because the dispatcher went to the break room, not to a chair three feet away "just in case."

How to tell it worked

Re-run the same one-week tally a month after any change, same days of the week, same season if you can. Look for three things: tech contacts down, longest quiet stretch up and spent away from the desk, and board errors after the morning surge down. Then ask the dispatcher one question in private: "Is the afternoon better than it was?" If the numbers improved and the answer is no, the load you have not found yet is usually the hard calls, and the fix is the hand-up rule, enforced.

References

• U.S. Department of Labor, Wage and Hour Division: 29 CFR 785.18 (rest periods) and 29 CFR 785.19 (meal periods)
• California Labor Code section 226.7 and the applicable IWC wage order (meal and rest period premiums)
• See related: Spotting and Stopping Crew Burnout
• See related: Designing an On-Call Rotation Around Sleep
• See related: What an Employee Assistance Program Is and How a Small Shop Gets One