Missed-Call Text-Back for Septic Companies

Sewage in the bathtub can't wait until morning; a routine pump can. The septic-specific text-back build that triages backup emergencies from scheduled work in the first text exchange — and protects your nights.

System 1 from the Leveraged Owner Starter Pack

It's 9:47pm. A homeowner's toilets are backing up into the shower, and they're standing in their yard in socks calling every septic company in the county. You miss the call because you're already on another job. The next morning you call back — and learn they paid your competitor's emergency rate at midnight. In septic, a missed call isn't just a lost lead. It's a health hazard that found someone else.

If you haven't built the base system yet, start with the complete missed-call text-back guide (Pillar A) — the tool lanes, 10DLC compliance, and the 11-step setup guide. This post is the septic layer: the triage wording, the emergency sort, and the scripts.

Septic calls fall into two buckets — your text-back must sort them

Every other trade's missed calls are roughly equal in urgency. Septic's aren't. There are two completely different calls hiding behind the same ring:

A generic "sorry we missed you" text treats both the same. A septic text-back asks one sorting question first: "Is sewage backing up into your home right now?" Everything downstream — your reply priority, your pricing, your sleep — flows from that answer.

85%

of callers who reach voicemail never call back — and 67% immediately dial a competitor (commonly cited in sales literature — primary source unverified; directionally useful, measure your own). A septic caller with sewage in the house isn't an exception. They're the rule.

21x

more likely to qualify a lead when responding within 5 minutes (MIT/Oldroyd, HBR 2011). For backup emergencies, the "5-minute" version is a text that arrives in 60 seconds.

Script 1: The triage text (fires on every missed call)

This is your default missed-call text. Note the first question — it's the whole system:

Hi, this is [Business Name] — sorry we missed your call. Quick question so we get you the right help: is sewage backing up into your home RIGHT NOW? Reply YES and tell us what's happening + your address. If it's not an emergency (routine pump, inspection, maintenance), reply with your address + when it was last pumped and we'll call first thing in the morning. Reply STOP to opt out. — [Your Name]

Script 2: The emergency branch (backup confirmed)

When the caller replies YES, your system — or your on-call phone — needs to respond fast with the emergency protocol. Set up an auto-reply keyword (most texting tools support keyword triggers) so YES fires this:

Got it — we're treating this as an emergency. Two things: 1) Stop running water and don't flush — it makes it worse. 2) Reply with your address and we'll call you in the next [X] minutes with an ETA. Emergency service rates apply after hours — we'll confirm the rate on the call. — [Your Name]

That "stop running water" line does two things: it genuinely helps the homeowner, and it establishes you as the expert who's already on their side. Keepers of this script report it calms panicked callers down immediately.

Script 3: The routine branch (morning callback)

Thanks — that's a routine job, no emergency pricing involved. We'll call you first thing in the morning to schedule. In the meantime: if you can find it, your last pump date helps us plan (county records often have it). Talk tomorrow. — [Your Name]

This message does quiet, important work: it tells the routine caller they're safe, sets the callback expectation, and removes the incentive to keep calling competitors at 10pm — which is exactly what a routine caller at night will otherwise do.

The diagnostic questions that sharpen the triage

If the caller gives you a vague answer ("drains are slow"), these are the follow-up texts that sort a real emergency from a tomorrow job:

Build these as quick-reply templates in your texting tool so your on-call person can fire them with two taps instead of typing at midnight.

Example: the Saturday night sort

Example: Saturday, 8:20pm. You miss two calls back to back while finishing a job. The triage text fires on both. Caller A replies: "YES, toilets backing up, water in the tub. 1234 County Rd 8." Caller B replies: "No emergency, just need a pump, last done 2019 maybe." You dispatch Caller A at emergency rates that night — a job your competitor would have taken. Caller B gets the routine message and a Monday-morning call, and books a $400 pump for Thursday. Before the triage system, both calls went to voicemail, Caller A hired someone else, and Caller B forgot you existed by Monday.

Protecting your nights: the rotation behind the text

The triage text only works if someone actually responds to the YES replies. For a 1–3 person shop, that means an on-call rotation with rules:

Pair this with the on-call rotation system for the scheduling mechanics.

Compliance notes for septic texting

Related guides in this series

Start with the complete missed-call text-back guide for the base setup, then read handling after-hours emergency calls for the dispatch side. For the on-call mechanics, see the on-call rotation system — and the plumbers' version of this build is at missed-call text-back for plumbers.

Get System 1 free: the complete Missed-Call Safety Net

The full setup guide, all four copy-paste scripts (including the owner notification), the "Your Numbers" missed-call worksheet, and the step-by-step setup guide — free, no catch. Fix your missed calls this week.

Get the AI Automation Starter Pack — $27, one-time: https://leveragedowner.com/starter-pack/

The done-for-you version

This post is System 1 from the Leveraged Owner Starter Pack — the done-for-you version with the full 11-step setup guide, every script, the worksheets, and complete setup guides for all 8 systems, including the keyword-triggered triage branches.

Stats sourced as labeled: MIT/Oldroyd via HBR 2011; commonly cited in sales literature — primary source unverified noted as directionally useful — measure your own.

Keep building your systems

Related guides from the Leveraged Owner blog: