Speed to Lead for Plumbers: Emergency Calls First

6:47pm. A pipe bursts under a customer's kitchen sink. Water is spreading across the hardwood. She calls three plumbers. The first two go to voicemail — she's not leaving a message, she's hanging up and dialing the next number. The third picks up, or texts back in 60 seconds, and gets a $450 emergency call plus a customer for life. Plumbing leads don't go stale in hours. They go stale in minutes, while water is running.

This is the plumbing layer on the speed-to-lead framework — the general case is Speed to Lead: Why the First Contractor to Respond Wins the Job, and the missed-call foundation is the complete missed-call text-back guide (Pillar A: Capture Every Lead). Plumbing's twist: your leads split into emergencies (water running, sewage backing up, no hot water with kids in the house) and everything else — and the system has to sort them before a human is involved, because the human is under a sink somewhere.

Why plumbing speed is different: the panic window

An HVAC no-cool caller is uncomfortable. A burst-pipe caller is watching damage happen in real time. That changes the psychology completely:

• They call, they don't form-fill. Plumbing emergencies come by phone. Your speed system has to start with missed-call text-back (System 1) — the form-notification layer is secondary for this trade.
• Voicemail is a death sentence. An emergency caller who hits voicemail hangs up and dials the next plumber. There is no "they'll leave a message." The auto-text has to fire in under 60 seconds.
• The first question is triage, not booking. Before you schedule anything, you need to know: is water actively running? That one answer decides whether this is a dispatch-now emergency or a tomorrow-morning job.

The emergency-first routing build

Every missed call and web lead gets the same first text — and that text's job is sorting, not scheduling:

The routing behind it:

• "URGENT" reply → immediate phone call. This fires a high-priority notification to the on-call tech — a phone call to them, not just a push. Ring the human. The tech calls the customer within 5 minutes.
• Routine reply → scheduled callback. Goes into the normal queue with the standard acknowledgment. Same-day or next-day scheduling, handled by dispatch.
• No reply → the follow-up. One text 15 minutes later: "Still need help with [issue]? We're available." Emergency callers who don't reply usually booked someone else — but the routine ones often just got distracted.

The damage-control text: what to send while they're waiting

Here's the plumbing-specific move most shops miss. Between "we're coming" and arrival, the customer is standing in water feeling helpless. A good shop sends the mitigation text — it reduces damage (which reduces the angry-customer risk) and it makes you look like the professional in the room:

Send this the moment the job is dispatched, not the moment it's booked. It does three jobs: it limits the damage (smaller mess = calmer customer = better review later), it fills the waiting silence (the #1 complaint during emergencies is "nobody told me anything"), and it positions you as the expert before you arrive.

Protecting the emergency rate

Emergency calls command premium pricing — but only if the system treats them as emergencies. Two rules:

• The URGENT path never quotes a price by text. Emergency pricing by text gets screenshot-shopped. The tech calls, assesses, and quotes on the phone or on arrival. The text's job is speed and triage, not estimating.
• Define "emergency" in your setup guide (standard operating procedure) so the on-call tech isn't deciding at midnight. Active water intrusion, sewage backup, gas smell (refer to gas company first, then dispatch), no hot water with infants/elderly in winter. Everything else waits for morning. Write the list down; tired techs make bad judgment calls.

Worked example: the 6:47pm burst pipe

Example: 6:47pm — burst supply line, kitchen, water spreading. Customer calls, you're under a house on another job. Missed-call text-back fires at 6:47:30 with the triage script. She replies "URGENT — pipe burst under sink, water everywhere" at 6:49. Your on-call phone rings at 6:49 (the URGENT escalation). You call her at 6:52, talk her through the main shutoff, quote the emergency diagnostic, dispatch yourself after the current job. Mitigation text sent at 6:55. You arrive 7:40. The two competitors she called first? Both went to voicemail. She never called a fourth plumber — because you answered first, and then you told her what to do while she waited.

The numbers that justify it (attributed honestly)

Compliance note

Business texting requires 10DLC business-texting registration (application-to-person 10-digit long code — the carrier system for business texting from local numbers) before you send: 1–7 day approval, ~$15–$20 in carrier/campaign fees. Include opt-out language ("Reply STOP to opt out") in automated texts, and observe TCPA (federal telemarketing law) quiet hours — no marketing texts before 8am or after 9pm recipient local time. Emergency transactional replies to someone who just called you are the lowest-risk texting there is, but register anyway. General information, not legal advice.

Related guides in this series

The foundation is the complete missed-call text-back guide (Pillar A) plus the framework in Speed to Lead: Why the First Contractor to Respond Wins the Job. For the after-hours half, read the plumber's missed-call text-back build.

The done-for-you version

This post is System 2 from the Leveraged Owner Starter Pack — the done-for-you version with the full emergency-routing setup guide, every triage script (including all trade-specific variants), the on-call escalation rules, and click-by-click setup instructions for all 8 systems.

Stats sourced as labeled: 27% unanswered inbound calls (Invoca call-analytics research); 42–47 hour typical response (HBR’s 2011 audit of 2,241 companies; 2026 benchmarks of 250K+ inbound leads) — directionally useful, measure your own numbers.