The 2am burst-pipe call: how a plumbing triage rule should work
Water on the floor, a caller who does not know the shut-off, and a slow drain that phoned in an hour earlier are not the same job. A written rule ranks them and writes the reason to your board. A gut feeling at 2am does not.
The short version
5 things that decide this
- 01Two signals outrank your whole ranking: a gas smell and sewage in a living space. Neither is a triage decision. Both route to a human immediately, with no queue position assigned.
- 02Below that line, your rule weighs active water damage, the occupant, the account type, and the season, in that order. You can't let a burst pipe with the shut-off unknown sit behind a slow drain just because both came in as plumbing calls.
- 03Keep the rule in a decision table your office manager can edit, not a paragraph buried in a vendor's prompt. It should run the same way by phone, web form, text, or your on-call tech's app.
- 04Give the shut-off instruction first, before any other question on a flood call, so the caller can stop the damage before your truck arrives.
- 05What writes back to ServiceTitan, Housecall Pro, Jobber or whatever you run is the ranked priority and the reason. Your tech glances at the board and sees why a job jumped the line.
Why does every emergency call get treated the same?
If your shop runs one urgent bucket, a burst pipe, a sewer backup, and a slow drain the caller called 'urgent' all land in it together. Whoever picks up the phone decides what goes first, and that's often a script-reader, not a dispatcher who knows the account.
You already know the stakes are high. A ServiceTitan analysis of 50,000-plus contractor phone lines puts the industry missed-call rate near 62 percent, and 80 to 86 percent of callers who reach voicemail never leave one, per CallJolt. They call the next shop instead. Without a rule to sort them, your burst pipe and your dripping faucet compete for the same slot on the board.
What outranks a routine service call, and why?
A working triage rule checks four things in order, and each one only matters once the one above it has cleared. Run it the same way whether a person or an AI phone agent is asking the questions.
Active water damage comes first. Put a burst or frozen pipe with water on the floor, a sewer backup into a finished basement, and a failed sump pump during a storm at the top together, because the damage compounds by the minute. If your caller knows the main shut-off valve or the angle stop, get that instruction out before anything else. If they don't, finding it becomes the first question, ahead of scheduling.
Second is no water versus no hot water, which sound similar and aren't. No water to a house with an infant, an elderly resident, or someone on medical equipment jumps your queue regardless of the hour. No hot water on a Sunday is an inconvenience, rarely a safety issue, and it can usually hold for the next slot.
Third is the account. Rank a commercial account with a service agreement and a walk-in cooler above a comparable residential call, because the loss compounds into spoiled inventory. A membership customer breaks a tie against a non-member at the same tier. None of this reorders past active flooding or a vulnerable occupant; it only settles ties within a tier.
Fourth is the season. During a cold snap, frozen and burst pipes spike across your service area at once, and your on-call rotation fills fast. Widen the same-day window when that happens, and move slow drains and fixture installs to the callback list your office works at 7am, once overnight emergencies clear.
How four calls sort against each other on a cold-snap night
This is a shape your dispatcher, your CSR, or an AI phone agent should be able to read and apply without asking an engineer for help.
| The call | Rank | Deciding factor |
|---|---|---|
| Active flooding, caller does not know the shut-off location | Human now, first truck | Damage compounds by the minute and the caller cannot stop it alone |
| Sewer backup into a finished basement | Same-night, first slot | Active water damage plus contamination risk to the finished space |
| No water to a house with an infant | Same-night, first slot | Vulnerable occupant with no workaround for feeding or bathing |
| No hot water on a Sunday, no medical need cited | Next available slot | Uncomfortable, not dangerous; the account tier breaks the tie |
| Slow kitchen drain, standing water clears within an hour | Standard queue, callback list | Lowest urgency tier; the household has a working kitchen |
Script or table: where should the rule live?
A common mistake is keeping the triage rule only inside a vendor's system prompt. That works fine until your office manager wants to widen the same-day window during a cold snap, and the only way to change it is a support ticket.
Put it in a decision table instead: rows for call type, occupant flags, account tier, and season, columns for the rank and the reason. Your CSR, your on-call plumber checking the app, and an AI agent answering the phone at 2am all read the same table. When a cold front moves in, someone edits a threshold, not a prompt.
This is where automation earns its place next to the phone: run the rule on every intake channel you use, phone, web form, text, and the tech's app. Each one hits the same table and writes the same ranked priority to ServiceTitan, Housecall Pro, Jobber or whatever you run.
Your CSR opens the board at 7am and sees the callback list already sorted, not a stack of voicemails. Office hours cover about a quarter of the week (76 percent of the week is outside them, per CallJolt), and even answered calls book at only 65 to 75 percent by ServiceTitan's CSR benchmark. The rest of the week runs on your table, unattended.
- 01Send the shut-off instruction out first on every flood call, before scheduling, whether a human or an AI agent is on the line.
- 02Set the freeze threshold that widens the same-day window during a cold snap yourself, as a number your office controls, not the vendor.
- 03Write the reason code so a technician glancing at their board can read it, not a transcript dump.
- 04A rule you can't edit without a support ticket isn't a rule you own.
What happens to calls after the truck is already out?
One truck can't answer two flooding calls at once, so your rule needs a capacity check. If the on-call tech is already dispatched, send a second flooding call to the next tech in rotation, or to a service manager. Don't let it stack silently behind the first job.
Anything that doesn't clear the top two tiers overnight lands on your 7am callback list, sorted by the same table, so the no-hot-water Sunday call sits above the slow drain. HeyRosie's analysis of 50,000 contractor reviews found 'poor communication' among the top three complaints, with callers describing five calls straight to voicemail before they gave up. A written callback list fixes that: your table decides when a customer hears back, not luck.
Some of the systems we have shipped
What plumbing owners ask about triage rules
01Does a service-agreement customer always get dispatched first?+
No. Account tier only breaks a tie within the same urgency level. A sewer backup at a non-member's house still outranks a routine no-hot-water call from a member. Active flooding and vulnerable occupants come before the account, every time.
02What should the AI agent ask before anything else on a flood call?+
Ask where the main shut-off valve or the nearest angle stop is, and whether the caller can safely reach it. Send that out before any scheduling question, because stopping the water matters more than booking the slot.
03How does the rule treat a commercial account differently from residential?+
Rank a commercial account with a service agreement and water-dependent equipment, like a walk-in cooler, above a comparable residential call at the same tier. It still sits behind any active flooding or safety hazard, residential or commercial.
04Does the triage rule apply the same way to a text message as a phone call?+
It should. Your rule reads the same table whether the call comes by phone, web form, text, or the on-call tech's field app. Only how the information arrives changes; how it gets ranked doesn't.
05Why does a gas smell skip the ranking table entirely?+
A gas smell near a water heater or gas line is a safety hazard, not a plumbing priority to weigh against other calls. It routes to a human immediately with no queue position, the same way sewage in a living space does.
06Do we need a ServiceTitan integration for a triage table to work?+
No, not for the table itself. Writing the priority back automatically depends on your platform's access model, which we confirm during an audit of what your credentials allow. Housecall Pro and Jobber expose booking through their APIs; the table and the write-back are separate pieces of work either way.
Related
- AI and automation for plumbing contractors →Every stage from intake through sales, dispatch and retention.
- Plumbing AI voice agents →Where triage fits inside the intake and booking build.
- How many calls does a plumbing company miss? →The missed-call data behind why a triage rule has to run on every channel.
- How to automate plumbing and electrical dispatch with AI →The dispatch side of the same write-back pattern.
