Plumbing Dispatch Software: The Hold-Back Rule

The short answer

Plumbing scheduling and dispatch software assigns plumbers to jobs and pushes the details to the truck. Every serious platform in the category does that competently, which is why comparing feature grids tells you almost nothing.

The difference that matters to a plumbing company is how the board behaves when a call arrives that did not exist when the day was built. Plumbing runs the highest interrupt rate of the major trades, so the buying question is not "can it route six trucks efficiently" but "can it absorb three unplanned jobs at 10am without bumping three customers who were already promised a window."

Two things decide that, and neither is on a feature grid: whether you hold capacity back on purpose, and whether you have movable work to fill the held capacity when nobody's pipe bursts.

Plumbing is the highest-interrupt trade, and the numbers say so

The category sells one generic product to HVAC, plumbing and electrical shops. The demand shapes are not the same.

AInora's 2026 compilation of Service Roundtable, ACCA, CallRail and ServiceTitan benchmarks lines the three trades up directly:

Read the peak-season row carefully, because it is where plumbing and HVAC diverge. HVAC's spike is a curve: you can see July coming in February, and an HVAC shop can plan its board around a demand table it could have printed a year in advance.

Plumbing's spike is a step function. Northern-tier contractors report 2 to 4 times baseline volume during the first deep-freeze week, triggered by a weather event with about 72 hours of warning. No dispatch board plans for that. It either degrades gracefully or it does not.

Routing saves minutes. The interrupt costs a day

Almost every vendor page in this category leads with route optimisation and a live technician map. Both are real features. Neither addresses the failure mode plumbers actually describe.

Here is what it looks like from the truck. A plumber described a 12-hour day ending with dispatch adding one more: "Whole house clog, 35 minutes away, on septic, no clean out." He declined and went home. The thread drew 134 comments, and the top reply, at 119 upvotes, was not about software: "They use you up until you can't give anymore, then fire you or try to get you to quit." The third-highest comment is the actual specification: "Your work should have set hours. Like 8-430. There should be a rotation for on call. Emergency only."

That is a board with no reserved capacity, where every emergency is inserted on top of committed work and the technician absorbs the difference. Optimising the drive between stops does not touch it.

The hold-back rule

Here is the arithmetic the buying guides skip. Same-day calls are a surprise individually and a statistic collectively. If 35 percent of your booked jobs are same-day, roughly 35 percent of tomorrow's work does not exist yet when you build tomorrow's board, and booking that capacity to somebody else guarantees a bump.

Held slots per technician = (daily job count x same-day share) / technicians.

Worked for a five-truck residential shop running six jobs per tech:

Use your own same-day share, not the benchmark. Pull last quarter's invoices, count the ones where the call and the visit were the same date, and divide. Drain and sewer shops run higher; a repipe-heavy shop that holds two slots a day is burning money.

The counter-argument is obvious, and it is why almost nobody does this. Ten held slots at a $300 to $500 residential ticket is $3,000 to $5,000 a day of capacity you did not sell.

The alternative is not free either. Homeowners with an active emergency call two to three competitors within 10 to 15 minutes. A same-day call you cannot take today is not deferred revenue, it is a job at your competitor, at $350 to $750 a booked call.

Neither number is the answer, though, because held slots are not supposed to sit empty.

What fills the held slots when nobody's pipe bursts

This is the part the category has no vocabulary for, and it is the whole trick.

Reserve capacity is only affordable if you have a standing backlog of work with two properties: a deadline measured in weeks or months, and no promised arrival window. Call it movable work. In a plumbing shop it already exists and it is almost always managed badly:

• Backflow assembly tests. Annual in most jurisdictions, higher-hazard sites more often, typically $50 to $200 per assembly. The deadline is a compliance date months out, not a day. This is such a distinct scheduling problem that it has spawned its own software category, which most general dispatch boards do not touch.
• Water heater flushes and anode checks on maintenance-plan customers, where the plan says "annually" and not "on the 14th."
• Camera inspections sold on a previous visit and never booked, and estimate visits for non-urgent replacements, which have no deadline at all.
• Warranty returns and commercial PM visits, which carry a customer expectation or a monthly window but rarely a fixed time.

The rule: your movable backlog needs to be larger than the gap between held capacity and actual emergency demand. If you hold ten slots a day and emergencies fill seven, you need three movable jobs a day, fifteen a week, and a standing pool deep enough that the dispatcher can always find one near where a technician already is. Thirty to sixty jobs in the pool is a reasonable working depth for a five-truck shop.

That yields a specification almost nothing on the market advertises, and three demo questions:

1. Can the system hold a job assigned to a technician and a date with no customer-facing appointment time, and not notify anybody?
2. Can a dispatcher pull that job back off the board in one action, without a cancellation email firing?
3. Can it report on held slots: how many existed, how many emergencies filled, how many movable jobs filled, how many went empty?

The third one is the one that keeps the discipline alive after month three.

The interrupt has to reach the board first

Held capacity is worth nothing if the call that should have filled it went to voicemail. For most plumbing shops this leak is larger than the dispatch problem sitting underneath it.

The numbers are not close. Plumbing carries a 30 to 45 percent after-hours share, the highest of the three trades, and the same compiled report puts home-service missed-call rates at 20 to 30 percent of inbound volume, rising to 40 to 50 percent at seasonal peaks. Roughly 80 percent of callers who hit voicemail leave no message, and CallRail puts the share who never call back at 85 percent. Simpro, citing HomePros News, adds that 54 percent of homeowners research and hire a plumber within four hours.

Stack those together and the emergency call you built reserve capacity for has a real chance of never appearing on your board at all.

A plumber in the r/Plumbing software thread described the mechanism exactly: "Customer calls, I'm elbow deep in a drain, call goes to voicemail, they never leave a message. By the time I call back they already booked someone off Google." His conclusion is the one to take into a demo: "The best software in the world doesn't help if the lead never makes it into your system."

On-call depth is a dispatch specification

The board runs during the day. The rotation runs the other 16 hours, and it is the part most shops manage in a group text.

A plumber running service for a family shop posted the shape of it: six people doing service work, three in the office, full 24 hour emergency service, "for multiple reasons only three of us are able to cover the call rotation, so we're on call every 3 weeks." He had taken it over after his father's emergency heart surgery, and his summary was blunt: "I'm not getting compensated enough for the inconvenience and time spent, but even if I was, I wouldn't want to do it any more."

That is a six-technician shop with a rotation depth of three. On-call frequency is one over depth, so every plumber in it is on call a third of the year.

The reason this belongs in a software evaluation and not just an HR conversation is supply. Simpro's 2026 industry work puts the United States roughly 550,000 plumbers short by 2027, with 25 percent of the current workforce already over 55 and BLS projecting about 44,000 openings a year through 2034. You cannot buy your way out of a shallow rotation, so the rotation has to be visible and it has to be measured.

The same operator named the split most shops live with. On FieldEdge: "Their field technician app is hot trash, but the dispatching side of it is powerful and pretty intuitive." Office-strong and field-weak is the normal shape of this category, and it is worth knowing which half you are buying.

Concretely, ask your shortlist:

• Is on-call a schedulable resource on the calendar, or a note?
• Can the after-hours answering service read the current on-call assignment without you retraining them every Monday? The r/Plumbing thread's whole ask was for a service that could "train on and use our dispatching software."
• Can you report after-hours calls absorbed per technician per month? That is the number that predicts who resigns.

The triage disposition is a field, not a decision

Every after-hours call gets one of four dispositions: roll now, roll at first light, book normal hours, or decline and refer. Most shops make that call well. Almost none record it.

Both errors cost cash. Rolling a truck at 2am for a three-day slow drip burns overtime at the 1.5x to 2x after-hours premium on a job that would have been ordinary work at 9am. Booking a genuine active leak for Tuesday loses the job and the customer.

Store the disposition, the symptom that drove it, and who chose it. After a quarter you can audit which symptoms get mis-triaged, which is a training fix worth more than any routing feature. It also feeds the hold-back calculation for free, since "roll at first light" is exactly what your held morning slots are for.

What it costs, and where the breakeven actually sits

ServiceTitan does not publish pricing, and every figure above for it comes from third-party 2026 breakdowns rather than a rate card. For a five-technician shop that puts year one between roughly $19,700 and $80,000, against $1,200 to $3,600 a year at the entry end of the market.

Dispatch efficiency does not cover a gap that size. Marketing spend large enough that call attribution and CSR book-rate reporting move real money does, which is why the honest trigger is around ten technicians and a real advertising budget, not a feature you are missing.

The adoption risk is the other half. A solo plumber in the same r/Plumbing thread put the overshoot plainly: "i tried servicetitan because everyone talks about it but it's like trying to fly a boeing 747 just to fix a leaky faucet." A field service manager in r/fieldservicemanagers put it well: "I've seen companies buy powerful tools like ServiceTitan, but techs end up using only a small part of them because there's too much friction in the field. A simpler tool can sometimes work better because the team actually uses it."

The demo script

Six asks. Book 45 minutes and do not let them drive.

1. Build a full day, then break it. Five techs, six jobs each, all with committed windows. Add a sewer backup at 10:40am. Watch what happens to the four jobs behind it and what those customers receive.
2. Hold a slot. Assign a job to a tech and a date with no customer-facing time. Confirm nothing is sent.
3. Pull it back. Remove it from the board in one action, mid-morning, with no cancellation firing.
4. Show me the on-call calendar. Not the phone tree. The rotation, schedulable, with history.
5. Run the held-slot report. Held, filled by emergency, filled by movable, empty. If it does not exist, ask what you would export to build it.
6. Price the exit. Contract length, early termination, and what your data looks like on the way out.

What to measure once it is live

Four weekly numbers, and only four.

If you want the scheduling discipline underneath all of this, the fundamentals of clustering, buffering and window-keeping apply to any trade. The hold-back rule is the plumbing-specific version.

The bottom line

Buy plumbing scheduling and dispatch software as an interrupt handler. The category will try to sell you routing, because routing demos well and interrupts do not.

Measure your own same-day share first. Derive your hold-back from it. Build a movable backlog deep enough to make the held slots free. Fix intake so the interrupt actually reaches the board, and put the on-call rotation on the calendar where you can count it. Then test a shortlist against the 10:40am scenario rather than the feature grid, and pick the cheapest thing that survives.

If nothing on the list can hold a job without promising a customer a time, you have found a genuine gap rather than a preference, and that is when a custom build earns its keep.

Sources

• AInora, HVAC / Plumbing / Electrical Service Call Statistics 2026, compiling Service Roundtable, ACCA, CallRail, ServiceTitan and BLS benchmarks
• Simpro, Plumbing Industry Trends 2026, on the 550,000-plumber shortfall, workforce age and speed-to-hire
• The Plumbers Coach, The Magic Number
• Projul, ServiceTitan Pricing 2026
• Vocaly AI, Emergency Plumbing Call Triage
• Backflow Authority, Annual Backflow Preventer Testing Requirements
• r/fieldservicemanagers, Best CRM for a Small Plumbing Business
• r/Plumbing, what plumbers actually use for scheduling and dispatch
• r/Plumbing threads on dispatcher load and after-hours answering