Text-Back for Plumbing Emergencies: Burst Pipes Can't Wait

It's 11:40 on a February night and a pipe just burst in a customer's laundry room. Water is spreading across the floor toward the hallway. She calls three plumbers from her Google results. All three go to voicemail — but one phone buzzes thirty seconds later: how to shut off her main valve right now, plus "our on-call tech is being notified." She turns the valve. Then the tech calls her. Who gets the job? Not the shop with the best reviews. The shop that answered first.

This post is the emergency-focused extension of Missed-Call Text-Back: The Complete Setup Guide, our Pillar A guide to the base System 1 setup. It assumes your basic missed-call auto-text is already running and bolts the emergency layer on top: the keyword triage, the shutoff-valve reply, and the dispatch priority that decides who gets called back first.

The 5-minute window is even smaller when water is involved

A routine estimate request can wait until morning. A burst pipe cannot. Homeowners with water pouring into their house don't leave voicemails — they hang up and dial the next number. The speed-to-lead numbers already make the case: call-analytics research from Invoca found 27% of inbound calls to home-service businesses go unanswered, and research from MIT and James Oldroyd, published in Harvard Business Review (2011), found that responding within five minutes makes you 21 times more likely to qualify a lead and roughly 100 times more likely to reach the contact. A related HBR finding: responding within an hour still makes you 7 times more likely to qualify.

Emergency plumbing compresses all of that. The commonly cited sales-literature figure is that 85% of callers who reach voicemail never call back and 67% immediately dial a competitor — directionally useful, measure your own numbers before banking on them — and in an emergency the dial-a-competitor instinct is at its strongest. Your only shot is the text that lands seconds after the missed call.

This system is a standard operating procedure — an SOP, a written step-by-step playbook — that buys you the ten to fifteen minutes you need to finish the job you're on and call the emergency back like a professional who had it handled all along. You run it from your CRM (customer relationship management software) or your FSM (field service management software) platform's texting feature.

The emergency-keyword triage: sort the flood from the faucet drip

A plain missed-call text-back treats every caller the same. For a plumber, that's backwards. The emergency-keyword triage scans the caller's reply for keywords and sorts them into three tiers:

Tier 1 — water is actively damaging the home

• Burst pipe, broken pipe, pipe burst — supply-line failures
• Flooding, water everywhere, water pouring, gushing — active intrusion
• Sewage backup, sewage coming up — unsanitary conditions
• Can't stop the water, water won't stop — uncontrolled flow
• No water at all — supply failure, possible main-line break

Tier 1 skips every queue: the caller gets the shutoff-valve reply immediately and a human callback target of under five minutes — nights, weekends, holidays included. This is the tier that saves ceilings.

Tier 2 — urgent, but not destroying anything this minute

• No hot water, water heater leaking — especially in winter
• Clogged main line, multiple drains backing up
• Standing basement water without active flow

Tier 2 jumps the routine queue: callback within the hour during business hours, first-call priority when the shop opens. Urgent enough to matter, not urgent enough to wake the on-call tech at 3 a.m. — unless it escalates, which the system watches for.

Tier 3 — everything else

• Drip, slow drip, faucet, running toilet, estimate, quote, remodel, install

Tier 3 flows into your normal text-back sequence and next-day scheduling. The triage's hidden job is protecting your on-call tech from this tier — every false alarm that wakes someone at 2 a.m. is a tech who quits the rotation.

Write the keyword lists to match how panicked customers actually talk: "water pouring out," "basement is filling up," "poop coming up the shower drain." Review the first month's replies, fix the miscategorizations, and update the lists. That's the entire maintenance routine.

Script 1: the shutoff-valve first reply

When a Tier 1 reply comes in, this fires immediately — before any human is involved. It gives the customer the one action that matters in the next sixty seconds and proves you're a professional who handles emergencies:

Three deliberate choices. First, it leads with the shutoff instruction instead of asking questions — a homeowner with a burst pipe needs the bleeding stopped, not a diagnosis. Second, the "reply CANT FIND IT" fallback: half of homeowners have no idea where their valve is, and the ones who can't find it are the ones whose ceilings you're saving. Third, it sets the callback expectation — "within 5 minutes" — which becomes your dispatch commitment.

Script 2: the "is this an emergency?" clarifier

Not every reply matches your keyword lists. "Leak under the sink." "Water in the basement." Treat them all as Tier 1 and you'll burn out your on-call tech; treat them all as Tier 3 and you'll miss real floods. When the triage can't classify a reply, fire one clarifying text:

A YES routes to Tier 1 and fires the shutoff-valve reply. A description gets keyword-scanned again. No reply within ten minutes during business hours still triggers a human callback — silence from a possible-flood caller is itself a signal. After hours, silence gets the Tier 2 morning-first treatment, not the 3 a.m. wakeup.

The 3-tier dispatch priority: the step that actually wins the job

Triaging the customer is half the system. The other half is triaging your response — three automation rules in your CRM or FSM platform that fire alongside the customer texts:

Tier 1 rule — wake someone up. The on-call tech gets an immediate notification — a phone call from the system, not just a text — with the customer's name, number, address, and exact reply text. Callback target: under five minutes. No acknowledgment within five minutes escalates to the backup. Include the address in the notification; a tech who has to dig through the CRM before calling back has already lost three minutes.

Tier 2 rule — jump the queue. The office gets flagged and the customer becomes first-call priority: callback within the hour during business hours. After hours, Tier 2 callers get a text confirming they're first in line at opening, with the option to reply URGENT if things escalate — which re-runs the triage and can promote them to Tier 1.

Tier 3 rule — normal flow. The reply drops into your standard text-back sequence and next-available scheduling. No special handling, no wakeups. This is the tier that keeps the system honest.

The most common failure mode isn't the technology — it's the on-call rotation falling apart after three quiet weeks. Fix it with the boring stuff: a written rotation, a backup for every slot, and a monthly ten-minute review confirming next month's schedule, on the calendar as a recurring event. Systems nobody maintains quietly die.

Here's a worked example: the 2 a.m. burst pipe

Example: 2:14 a.m. on a February Saturday, a supply line bursts behind a homeowner's washing machine. She calls your shop — you're asleep, it goes to voicemail. Minute by minute: 2:14 — the base text-back fires: "Sorry we missed you — is this an emergency? Reply with what's going on." 2:15 — she replies "pipe burst water everywhere." The triage matches "pipe burst" and "water everywhere" → Tier 1. The shutoff-valve reply fires; she runs to the basement and turns the main valve. The flooding stops. 2:16 — the on-call tech's phone rings with her name, number, address, and exact reply. 2:19 — the tech calls: "Did you get the water shut off? I'm twenty minutes out." 3:00 — the tech arrives, caps the line, quotes the repair. The job is booked before sunrise.

Now the math, using the illustrative range from our stats list: a lost emergency call sits somewhere in the $275–$1,200 ticket range — illustrative, not a promise; plug in your own average emergency job value. One captured emergency per month at your average ticket, times twelve months, is the annual value of a system that costs less than a tank of gas per month to run. And the benchmark context: the typical business takes 42–47 hours to respond to an inbound lead (2026 benchmark studies of 250K+ inbound leads; HBR's 2011 audit of 2,241 companies found the same 42-hour average). Your text-back answered in under sixty seconds.

Setting it up in an afternoon

1. Enable texting on your business number. If the shop still runs on a landline, your carrier or texting platform can enable texting on the existing number — customers text the number they already have.
2. Connect the missed-call trigger. Missed call → wait 60 seconds → send the first text-back. Sixty seconds, not zero — it gives you a chance to call back yourself if you just stepped away.
3. Build the keyword lists. Create the three tiers as tags, enter the keyword lists from this post, and wire the routing: Tier 1 reply → shutoff-valve text plus on-call notification; Tier 2 → queue-jump flag; Tier 3 → normal sequence; unclassifiable → the clarifier script.
4. Write the on-call rotation. Names, order, backup for every slot, escalation timing. In the SOP, with the monthly review on the calendar.
5. Test it with your own phone. Call the shop number after hours, let it go to voicemail, and walk through every branch: Tier 1, Tier 2, Tier 3, and the ambiguous reply. Fix misfires before a real customer finds them.

Compliance rails for emergency texting

Because this system sends business texts automatically, build the compliance setup in before the first text goes out:

• A2P 10DLC registration comes first. A2P (application-to-person) 10DLC (ten-digit long code) is the registered channel businesses use to send automated texts from a standard ten-digit number. Registration is required before you send business texts: approval typically takes 1–7 days and costs roughly $15–$20 as a one-time fee through your texting provider. Do it during setup week, not the night before a freeze.
• Opt-out language in the first text. Every automated first text includes "Reply STOP to opt out" — both scripts above carry it. Honor every STOP immediately; your platform handles this automatically when configured.
• TCPA quiet hours still apply. The TCPA (Telephone Consumer Protection Act) sets quiet hours for marketing texts: nothing before 8 a.m. or after 9 p.m. in the recipient's local time. Emergency-response texts are generally relationship or transactional rather than marketing — a customer who called about a burst pipe at 2 a.m. expects a reply at 2 a.m. — but keep quiet-hour discipline anyway: restrict after-hours automation to genuine Tier 1 and Tier 2 replies, and never let a promotional message ride the emergency rails.

This is general information, not legal advice. If your texting volume grows or you add promotional campaigns, talk to a telecom attorney or your provider's compliance team. The Starter Pack's System 1 SOP includes the full compliance checklist with the registration walkthrough.

Related guides in this series

Build the foundation first with Missed-Call Text-Back: The Complete Setup Guide, then layer this emergency triage on top. For the plumber-specific base scripts, see Missed-Call Text-Back for Plumbers: Emergency Calls Can't Wait. Once the emergency job is captured, the follow-up cadence closes it — Emergency-Job Estimates Need a Faster Cadence covers the hours-not-days sequence that wins emergency work.

The done-for-you version

This post is System 1 from the Leveraged Owner Starter Pack — the done-for-you version with the full step-by-step SOP, every script, the worksheets, and screen-by-screen setup instructions for all 8 systems. The emergency tier includes the complete keyword list, all scripts above plus the on-call notification template, the rotation worksheet, and the compliance checklist with the 10DLC registration walkthrough.

Stats sourced as labeled: Invoca call-analytics research; MIT/James Oldroyd via Harvard Business Review (2011); 2026 benchmark studies of 250K+ inbound leads. Ticket range illustrative — plug in your own average job value. Texting compliance notes are general information, not legal advice.

Keep building your systems

Related guides from the Leveraged Owner blog: