Plumbing dispatch software: what a small shop actually needs

Every plumbing shop plans the day at 7 a.m. and rebuilds it by 10. A water heater is leaking through a ceiling, a drain call turns into a camera job, a tech is stuck waiting on a part. The plan was fine. It just didn't survive the phone.

Dispatch is the job of rebuilding that plan all day long without losing anyone in the process: the customer who was promised a morning visit, the tech who's now driving across town twice, the job that quietly fell off the board. This post is about doing that well in a small shop, and what plumbing dispatch software should take off the dispatcher's plate.

The problem: emergencies don't wait for the schedule

Plumbing has more unplanned work than most trades. The Bureau of Labor Statistics puts it plainly: "Plumbers are often on call for emergencies, so evening and weekend work is common." The calls that pay well are often the ones nobody booked.

At the same time, the people who do the work are scarce. The PHCC Educational Foundation says the plumbing-heating-cooling industry is "facing a major skilled labor shortage" and will need about 114,500 more workers by 2028. When you can't easily hire another plumber, every hour of a plumber's day matters. An hour spent driving past a job to get to another one is an hour you can't sell.

So a small shop is squeezed from both sides. The work is unpredictable, and the capacity to absorb it is fixed. Here's where it usually breaks:

• The emergency bumps everyone. One urgent call gets slotted in, and three booked customers are now late without knowing it.
• The wrong plumber goes. The closest tech gets the gas line job they're not set up for, or the apprentice gets sent alone to something that needs a licensed hand.
• Drive time piles up. Jobs get assigned in the order the phone rang, so the day zigzags across the service area.
• Customers aren't told. The office knows the tech is running an hour behind. The customer who took the morning off doesn't.
• Jobs fall through the cracks. A tech can't finish because they need a part, says so in a phone call, and the return visit never gets booked.

Why the usual fixes fall short

Most small shops dispatch from a whiteboard, a shared calendar, a group text, or the owner's head. All of them work at two plumbers. They start to fail somewhere around four, for the same reason: they hold the plan, but they don't help you change it.

A whiteboard can't tell you that moving a job to Mike double-books him at 2:00. A shared calendar doesn't know that Mike is off Thursday, or that he's twenty minutes closer to the new call than Dave. The group text tells the tech, but not the customer. And none of them notice the visit nobody has been assigned to yet. That one only surfaces when the customer calls to ask where you are.

The deeper problem is that the dispatcher becomes the system. Everything works as long as one person remembers everything, and it falls apart the day that person is out sick or buried in phone calls.

How plumbing dispatch software works

Underneath, dispatch software keeps three things in one place and keeps them in sync:

1. The board. Every plumber's day side by side, plus the work nobody has yet. Moving a job is one action, and the software checks it against everything else on the board.
2. The crew's phones. Each plumber sees their own stops in order, with the address, notes and gate code. When the plan changes, their day changes with it.
3. The customer. Confirmations, reminders and "on the way" messages go out from the same record, so what the customer is told matches what the board says.

A worked example

Here's an illustrative Tuesday at a three-plumber shop.

At 10:40, a customer calls with water coming through a kitchen ceiling. Dave is on a water heater install until about 1:00. Mike has two drain calls this morning on the north side. Sam, the newest hire, has a faucet replacement and a toilet rebuild.

On a whiteboard, the call goes to whoever answers the phone first. With dispatch software, the dispatcher sees in one view that Mike's second drain call is 2 miles from the leak, that Sam's toilet rebuild could slide to the afternoon without a clash, and that Sam is close to Mike's second stop. Mike takes the leak, Sam picks up the drain call, and the toilet rebuild moves to 2:00. The dispatcher calls the customer whose visit moved before they start wondering. The whole thing takes about two minutes, and nobody had to remember anything.

Arrival windows, not exact times

Most shops give customers a window instead of a time, and for plumbing that's the honest choice. A two-hour window absorbs a job that runs 30 minutes long. An exact time promises something you can't control. Pick a window you can actually hit most days, then keep the customer posted when you can't. A Contractor Magazine piece on plumbing scheduling makes the same point: when a tech is en route or running late, "the customer should find out automatically, by text or email."

Don't let drive time decide itself

Contractor Magazine put it bluntly: "unnecessary drive time isn't a minor inefficiency. It's a margin problem." You don't need route optimization to fix most of it. You need to see where each plumber's stops are before you assign the next one, and to put each plumber's day in a sensible order once it's set.

What to look for

If you're comparing tools, these questions separate dispatch software from a calendar with a nicer screen:

1. Does it catch conflicts before you commit? Double-bookings and time off should be flagged the moment you move a job, not discovered when two customers are waiting. You should still be able to book anyway when you mean to.
2. Does it help you pick who goes? Look for suggestions that weigh who's free, who has the skills the job needs, and how far they'd drive, rather than leaving it all to memory.
3. Does unassigned work stay in your face? A job with nobody on it should be impossible to miss, days ahead, not when the customer calls.
4. Does the customer hear about it? Confirmations, a reminder, and an "on the way" message with a way to follow the visit should go out from the job record, without anyone typing them.
5. Can the tech tell the office when a job can't be finished? "Need parts, come back Thursday" should land on the dispatcher's screen as a visit to rebook, not as a voicemail.

How TradePath HQ does it

When the leak call comes in, you create the job and click "Find a time." It suggests up to three bookable slots, putting plumbers with the job's required skills first and ranking the rest by the least drive time added. Book one and the time and plumber are saved together. To shuffle the rest of the day, drag a visit to another plumber's lane on the dispatch board. If that double-books them or lands on their time off, you're asked first, and you can book anyway. Anything with nobody on it sits in its own lane, and visits for the next two weeks that still need a person are listed above the board. "Order this day by distance" proposes a sensible order for one plumber's stops and changes nothing until you confirm. The customer gets a confirmation and a day-before reminder by email, told as the arrival window you set, with a button to ask for a different time. When your plumber taps "Start driving," the customer is emailed a link to follow the visit. If they tap "Can't finish" and choose "Need parts / come back," it shows up on your board.

See more about scheduling and dispatch, and how it fits a plumbing shop's day.

Getting started

You don't have to change everything on Monday. Start by putting one week of booked work on a real board, with every plumber's time off entered, and run your morning from it. Once the conflicts are visible, the habits follow: give customers a window instead of a time, book the return visit before the tech leaves, and look at the map before you assign the next call.

As the trade association ASPE's CEO told Plumbing & Mechanical, "Consistent success comes from being available when the phone rings." Good dispatch is what lets you answer that call without letting down the customers you already booked.

For the bigger picture of what this kind of software covers, see field service software for small businesses. And once the tech is on site, getting paid before you leave the job is the next habit worth building.