BLOG

The Plumbing Dispatch Myth: Why 'Experienced Eyes' Still Beat Route Optimization (And When They Don't)

Field Operations LINQ Platform

Ask a plumbing owner with 20 years in the business whether software should dispatch their trucks, and you'll often get the same answer: "My dispatcher knows things an algorithm never will." They're not wrong. But they're not entirely right either — and the gap between those two truths is where a lot of plumbing companies quietly lose two, three, sometimes five hours of billable truck time every day.

The quick version: experienced dispatchers genuinely outperform software when a job requires judgment — reading a difficult customer, knowing which tech can't be trusted alone on commercial backflow work, sensing that a "simple leak" call from a particular address is never simple. But the moment a dispatch decision is really just math — which of six technicians is closest, who finishes their current job soonest, which route burns the least drive time — software wins every time, and it's not close. The real myth isn't that experience doesn't matter. It's that experience and optimization have to compete at all.

Myth: A good dispatcher can hold the whole day in their head

Most plumbing dispatch boards run on a whiteboard, a spreadsheet, or a sticky-note system that lives in one person's head. That works fine at four trucks. At nine or ten trucks running six to eight calls a day, a dispatcher is juggling roughly 60-80 moving variables — job priority, drive time, tech skill match, parts on hand, customer history — simultaneously, in real time, all day.

Cognitive research on working memory puts the realistic limit at somewhere around seven items tracked accurately at once. Past that, dispatchers aren't failing because they're bad at their jobs — they're failing because no human brain is built to run that many variables without dropping some. The jobs that get dropped are almost always the same ones: the ones that don't scream for attention, like a maintenance call that could wait a day but shouldn't wait three.

Myth: Route optimization only matters for big fleets

Plenty of plumbing owners with six or seven trucks assume route software is for the 50-truck operations. The math says otherwise. A tech who drives 40 extra minutes a day because of a poorly sequenced route loses roughly three billable hours a week — at a $150-$250 average plumbing ticket, that's $450 to $750 of lost revenue capacity per truck, per week, just from drive time nobody optimized.

Multiply that by six trucks and you're looking at $2,700 to $4,500 a week in capacity that never shows up on an invoice because it was never scheduled. Small fleets feel this more acutely than large ones, not less, because there's no slack in the system to absorb it.

Where the experienced dispatcher genuinely wins

This is the part software still can't touch, and plumbing owners are right to protect it.

  • Reading the customer, not just the address. A dispatcher who knows Mrs. Alvarez gets anxious and needs a 30-minute call-ahead, or that the property manager at the strip mall will cancel if you're even five minutes late, is making a relationship decision no algorithm captures.
  • Matching skill to risk, not just skill to task. Knowing that your newest tech shouldn't go alone to a slab leak under a finished basement — even though the system says he's "qualified" — is judgment built from watching him work, not data entry.
  • Triage during true emergencies. When three gas leak calls come in during a cold snap, a dispatcher who understands real urgency versus panicked urgency makes better calls than a system optimizing purely for distance.
  • Holding the line on bad customers. Recognizing a repeat no-show or a chronic lowballer before the tech wastes a trip is pattern recognition built over years, not something a route engine flags.

Where "experienced eyes" quietly cost you money

The failure mode isn't dramatic — it's a dispatcher defaulting to the tech they trust most for every decent-sized job, because trust is easier than optimization. That tech ends up overbooked and driving across town twice a day while two other trucks sit half-utilized. It's also the dispatcher sequencing jobs in the order they came in rather than the order that minimizes drive time, because reordering six jobs manually at 7am is slower than just going down the list.

None of this is a skill problem. It's a bandwidth problem, and bandwidth problems don't get fixed by hiring a more experienced dispatcher — they get fixed by giving the experienced dispatcher a tool that does the math so they can spend their attention on judgment calls instead.

The dispatcher's job was never supposed to be mental math — it was supposed to be judgment, and judgment is what you should be paying for.

What the combination actually looks like

The plumbing companies getting this right aren't choosing between experience and software — they're using software to handle the routing math automatically, freeing the dispatcher to handle the calls that actually need a human. The system suggests the closest, soonest-available, skill-matched tech; the dispatcher overrides it when they know something the data doesn't. That override happens on maybe 10-15% of jobs. The other 85% run cleaner and faster than any whiteboard ever could.

This same pattern — protecting the judgment calls that make a trade business good at its job while automating the repetitive math around it — shows up across service trades. It's part of why dispatcher burnout and turnover often mirrors what we've seen with technician retention in other trades: the people doing the job well get worn down by work the job was never supposed to require.

If your dispatch board is still a whiteboard or a spreadsheet and you want to see what automated routing actually frees up for your team, take a look at how lınq's dispatch and routing features work, or check pricing to see what fits a plumbing operation your size. We'd also be glad to walk through your current dispatch setup and show you exactly where the hours are hiding.

Frequently asked questions

Does route optimization software replace the need for a dispatcher?

No. It replaces the manual math — closest tech, best sequence, fastest route — so your dispatcher can focus on judgment calls like customer history, skill matching, and emergency triage that software can't make well.

How much does poor dispatch routing actually cost a plumbing company?

A single truck losing 40 minutes a day to unoptimized routing can cost $450-$750 a week in lost billable capacity at typical plumbing ticket prices. Across a six-truck fleet, that's often $2,700-$4,500 weekly.

At what fleet size should a plumbing business consider dispatch software?

Most owners assume it's only worth it past 15-20 trucks, but the math shows meaningful returns starting around four to six trucks, since smaller fleets have less slack to absorb inefficient routing. See how this plays out across field service industries we work with.

Ready to run the loop yourself?

Spin up a workspace in minutes, or book a 20-minute walkthrough with your live numbers in mind.