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 the 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, the rule weighs active water damage, the occupant, the account type, and the season, in order. A burst pipe with the shut-off unknown does not sit behind a slow drain just because both came in as plumbing calls.
- 03The rule belongs in a decision table the office manager can edit, not a paragraph buried in a vendor's prompt. It runs the same way by phone, web form, text, or the on-call tech's app.
- 04The shut-off instruction is the first line of every flood call, before any other question, so the caller can stop the damage before the truck arrives.
- 05What the system writes back to ServiceTitan, Housecall Pro, Jobber or whatever you run is the ranked priority and the reason. A tech glancing at the board sees why a job jumped the line.
Why does every emergency call get treated the same?
Most shops run one urgent bucket. A burst pipe, a sewer backup, and a slow drain the caller called 'urgent' all land in it. Whoever picks up the phone decides what goes first, often a script-reader, not a dispatcher who knows the account.
A ServiceTitan analysis of 50,000-plus contractor phone lines puts the industry missed-call rate near 62 percent. 80 to 86 percent of callers who reach voicemail never leave one, per CallJolt. They call the next shop instead. The burst pipe and the dripping faucet compete for the same slot on a board with no rule to sort them.
What outranks a routine service call, and why?
A working triage rule checks four things in order. Each one only matters once the one above it has cleared. The rule runs the same whether a person or an AI phone agent asks the questions.
Active water damage comes first. 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 all sit at the top. The damage compounds by the minute. If the caller knows the main shut-off valve or the angle stop, that instruction goes out before anything else. If they do not, finding it becomes the first question, ahead of scheduling.
Second is no water and no hot water, which sound similar and are not. No water to a house with an infant, an elderly resident, or someone on medical equipment jumps the queue regardless of the hour. No hot water on a Sunday is an inconvenience, rarely a safety issue. It can usually hold for the next slot.
Third is the account. A commercial account with a service agreement and a walk-in cooler outranks a comparable residential call at the same tier. The loss compounds into spoiled inventory. A residential 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 the service area at once. The on-call rotation fills fast, so the rule should widen the same-day window. Slow drains and fixture installs move to the callback list the office works at 7am, once overnight emergencies clear.
How four calls sort against each other on a cold-snap night
The shape a dispatcher, a 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 a triage rule that lives only inside a vendor's system prompt. It works until the office manager wants to widen the same-day window during a cold snap. The only way to change it is a support ticket.
It should live as a decision table instead. Rows for call type, occupant flags, account tier, and season. Columns for the rank and the reason. A CSR, an 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. The rule runs on every intake channel: the phone, the web form, a text, and the tech's app for a field follow-up. Each channel hits the same table and writes the same ranked priority to ServiceTitan, Housecall Pro, Jobber or whatever you run.
A CSR opening the board at 7am 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 the same table, unattended.
- 01The shut-off instruction goes out first on every flood call, before scheduling, whether a human or an AI agent is on the line.
- 02The freeze threshold that widens the same-day window during a cold snap is a number the office sets, not the vendor.
- 03The reason code written to the FSM has to be legible to a technician glancing at their board, not a transcript dump.
- 04A rule that cannot be edited without a support ticket is not a rule the business owns.
What happens to calls after the truck is already out?
One truck cannot answer two flooding calls at once. The rule needs a capacity check: if the on-call tech is already dispatched, a second flooding call goes to the next tech in rotation, or to a service manager. It does not stack silently behind the first job.
Everything that does not clear the top two tiers overnight lands on the 7am callback list, sorted by the same table. 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: the table decided when they would hear 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. The 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.
02What should the AI agent ask before anything else on a flood call?+
Where the main shut-off valve or the nearest angle stop is, and whether the caller can safely reach it. That goes 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?+
A commercial account with a service agreement and water-dependent equipment, like a walk-in cooler, ranks 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. The rule reads the same table whether the call comes by phone, web form, text, or the on-call tech's field app. The channel changes how the information arrives, not how it gets ranked.
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?+
The table itself does not require one. Writing the priority back automatically depends on the platform's access model, confirmed during an audit of what the tenant's 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
- Plumbing software development →Where triage fits inside the wider dispatch and back-office build.
- Should an AI receptionist handle emergency calls? →The escalation design behind the shut-off and safety-hazard rules.
- How many calls does a plumbing company miss? →The missed-call data behind why a triage rule has to run on every channel.
