Plumbing emergency intake checklist for an AI receptionist
A practical call-intake checklist for plumbing emergencies: burst pipes, sewer backups, active leaks, no hot water, gas smell, access details, and when to wake the on-call plumber.
A plumbing emergency call is not a normal lead.
The caller may have water actively entering the house. They may have a sewer backup. They may have no hot water, an overflowing toilet, a leaking water heater, or a burst pipe behind a wall.
The wrong intake script wastes time. The right script tells the plumber exactly what they are walking into.
This is the checklist I would use for a plumbing AI receptionist.
The first distinction: active damage or not
The AI should separate active damage from routine service immediately.
Ask:
“Is water actively leaking, flooding, backing up, or causing damage right now?”
If yes, the call moves into emergency intake.
If no, it may still be urgent, but it can usually follow a normal service flow.
That one question prevents a clogged sink and a burst pipe from landing in the same queue.
Emergency categories
The system should recognize at least these:
- Burst pipe
- Active leak
- Sewer backup
- Overflowing toilet
- Water heater leak
- No hot water
- Gas smell if the plumber handles gas lines
- Main line clog
- Sump pump failure
- Frozen pipe concern
- Shutoff valve failure
Each category needs slightly different fields.
The AI does not need to diagnose. It needs to collect enough information for the plumber to prioritize, price, route, and prepare.
Core fields every emergency call needs
Every plumbing emergency intake should capture:
- Caller name
- Callback number
- Service address
- Homeowner, tenant, property manager, or business
- Type of issue
- When it started
- Whether water is active now
- Whether the main water is shut off
- Whether electricity or standing water is involved
- Photos available by text if your workflow supports it
- Access details
- Pets, gate codes, or lockbox details
- Whether caller accepts emergency or after-hours rates if applicable
That is the minimum.
If a plumber gets only “leak in kitchen,” they still have to call back and ask five questions. The AI should eliminate that callback.
Burst pipe path
For a burst pipe, capture:
- Is water still running?
- Has the main water shutoff been turned off?
- Where is the pipe located?
- Ceiling, wall, crawlspace, basement, garage, exterior line, or unknown?
- Is water near electrical outlets, panels, or appliances?
- Is there visible damage?
- Is the property occupied?
- Is temporary shutoff possible?
If your approved script includes basic safety language, the AI can mention it. For example, many public emergency guides recommend shutting off the water supply where safe. But the AI should avoid giving instructions beyond your approved policy.
The business should decide how much safety guidance belongs in the script.
Sewer backup path
For sewer backup, capture:
- Where is the backup showing?
- Toilet, tub, shower, floor drain, basement, yard cleanout?
- Is sewage present?
- Is it one fixture or multiple fixtures?
- Is the caller in a single-family home, apartment, restaurant, or commercial building?
- Is the property usable?
- Has this happened before?
- Are children, elderly, or vulnerable occupants exposed?
Sewer backups are high-urgency and messy. They also need careful language. The AI should not discuss legal responsibility or cause. It should document facts and route quickly.
Water heater path
For water heater calls:
- No hot water or active leak?
- Tank or tankless?
- Gas or electric if known?
- Age if known?
- Water pooling?
- Pilot light issue if caller volunteers it?
- Any smell of gas?
- Location of heater?
- Is this a residential or commercial property?
No hot water may be urgent, but a leaking tank is a different priority. The AI should split those paths.
Clogged drain path
For clogs:
- One drain or multiple drains?
- Toilet, shower, tub, kitchen sink, main line?
- Is water backing up into other fixtures?
- Is there sewage?
- Is the property unusable?
- Has the caller tried anything already?
- Is this residential or commercial?
A single slow sink is not the same as a main line backup. The AI should know the difference.
Emergency routing rules
Common wake-the-plumber triggers:
- Active flooding
- Burst pipe
- Sewer backup
- Water heater actively leaking
- Main line backup
- No water to entire property if you handle that
- Gas smell where your business policy routes it
- Commercial property unable to operate
Common normal queue calls:
- Slow drain
- Routine fixture install
- Estimate request
- Dripping faucet
- Non-urgent water heater replacement quote
- General pricing question
The owner should define these rules before deployment. The AI should not invent urgency rules during a call.
Summary format
The handoff should look like:
“Emergency plumbing call. Caller: Laura P. Callback: 555-0191. Address: 88 Cedar St. Issue: active leak from ceiling below upstairs bathroom. Water still running. Caller has not found shutoff. Water near hallway light fixture. Home occupied. Accepts emergency rate. Needs immediate callback.”
That is dispatch-ready.
Compare that to a normal voicemail:
“Hi, we have a leak, please call me back.”
The difference is the business outcome.
Why AI works well here
Plumbing calls are often urgent, but the first two minutes are repeatable.
The AI receptionist can ask the same field-tested questions every time. It can wake the owner for real emergencies, queue routine work, block spam, and send structured notes into Jobber, Housecall Pro, ServiceTitan, Google Sheets, or whatever the owner actually uses.
The value is not that the AI sounds impressive. The value is that no emergency lead disappears because the plumber was under a sink and could not answer.
What not to automate
Do not let the AI diagnose cause.
Do not let it promise exact pricing unless you have a scripted policy.
Do not let it discuss liability for sewer backups or property damage.
Do not let it route every drip as an emergency.
Do not let it bury active flooding in a next-day queue.
The AI is a structured intake and routing layer. The plumber still makes the technical call.
The deployment I would build
For a plumbing company, I would build:
- Emergency-first call classification.
- Category-specific intake for leaks, clogs, sewer, water heater, and estimates.
- On-call routing only for defined emergency categories.
- Caller confirmation by SMS.
- Owner or dispatcher summary by text/email.
- Optional job creation in the existing dispatch system.
That is the phone layer behind AI Receptionist for Plumbing Companies.
If your after-hours plumbing calls are still going to voicemail, send the call types through the free workflow audit. I will map the routing logic.
