Plumbing Dispatcher Script: Template + Call Guide
A burst pipe at 11 PM is your job if you answer it. It’s a competitor’s invoice if you don’t. And the homeowner on the other end has more riding on the call than a service ticket — water damage and freezing losses average $13,954 per claim and make up 27.6% of all homeowners insurance claims, per Insurance Information Institute facts and statistics on homeowners insurance. A plumbing dispatcher script is what stands between that call and that claim.
This guide gives you a working plumbing call script you can use today, covering emergency calls, standard bookings, after-hours routing, and the three call types most scripts forget. It also covers which intake fields matter, why the order of questions changes outcomes, how to score whether your dispatchers are actually following the script, and how AI now runs these scripts 24/7 without a dispatcher in the chair.
Why a Structured Plumbing Dispatcher Script Matters
An unstructured inbound call costs money in two ways. First, incomplete intake — the tech shows up without the right parts because no one asked whether the water heater is gas or electric. Second, caller drop-off — a confused or slow intake pushes an anxious homeowner to call the next plumber in their search results.
Intake is also where a shop decides how bad the job gets before a truck ever moves. The EPA’s WaterSense program reports that nine percent of U.S. homes have leaks wasting 50 gallons or more per day — the kind of slow failure a caller downplays and a rushed dispatcher books for Thursday. A good plumbing call script:
- Triages severity before scheduling so the right tech and parts are dispatched
- Captures address, access notes, and contact details in one pass (no morning callback required)
- Sets realistic arrival windows instead of vague “someone will call you” promises
- Identifies the call type early so the dispatcher doesn’t waste turns on the wrong branch
The sequence matters as much as the words. Emergency scripts front-load safety questions. Standard booking scripts front-load fixture and scope so the truck is loaded correctly. After-hours scripts route quickly to whoever is on call without dead air.
The Core Plumbing Dispatcher Script — Emergency Calls
Use this plumbing call script for burst pipes, active leaks, flooding, no hot water, and sewer backups. The script opens with safety/mitigation before address capture — deliberately. Stopping the water is worth more than any scheduling step.
[DISPATCHER] “Thanks for calling [Shop Name]. Are you calling about an emergency or a scheduled service?”
Purpose: Routes the call in two words. Don’t ask “How can I help?” — the caller will start narrating and you’ll lose 30 seconds.
[CALLER confirms emergency]
[DISPATCHER] “Got it — we’ll take care of you. Have you been able to shut the water off at the [valve near the fixture / main shutoff]?”
Purpose: Mitigation before scheduling. If the answer is no, walk them through locating the shutoff before continuing. Every minute of uncontained flooding is drywall, flooring, and subfloor — the categories that push the average water-damage claim to $13,954. Containment first, calendar second.
[DISPATCHER — after mitigation confirmed] “Good. What’s happening — can you describe what you’re seeing?”
Let the caller use two or three sentences. Listen for: water type (clean vs. sewage), location in the home, whether it’s contained.
[DISPATCHER] “What’s the service address, and is there anything we need to know to access the property — gate code, pet in the yard, that kind of thing?”
Capture: full address including unit number, access notes. Do not skip access — a locked gate at 1 AM costs everyone.
[DISPATCHER] “Is this gas or electric? And do you have any idea how old the unit is?” (water heater calls only — skip for pipe/drain/sewer)
[DISPATCHER] “Alright — I have our next emergency slot [time window] with [tech name]. Does that work, or do you need someone earlier?”
Offer a real window. “As soon as possible” is not a window.
[DISPATCHER] “You’re booked. I’ll send a text confirmation to the number you’re calling from. Keep [the shutoff closed / area clear / gas off] until the tech arrives. Anything else?”
Standard Booking Plumbing Call Script
For non-emergency work — drain cleaning, fixture replacement, water heater annual service, repiping quotes. The goal here is scope capture and truck loading, not speed.
[DISPATCHER] “Thanks for calling [Shop Name]. Are you looking to book a service, or do you have an emergency?”
[CALLER confirms standard booking]
[DISPATCHER] “Happy to help. What’s the job — what are you seeing or needing done?”
Let the caller describe in their own words. Listen for fixture type, failure symptom, and whether it’s a repair or replacement.
[DISPATCHER] “Is this for a [house / condo / rental property], and are you the owner?”
For rentals: confirm authorization to approve service before going further. If the caller is a tenant, get the property owner’s contact before scheduling.
[DISPATCHER] “What’s the service address, and best phone number to reach you?”
[DISPATCHER] “We have availability [day/window] with [tech name]. Does that work?”
[DISPATCHER] “Booked — I’ll send a confirmation text. The tech will confirm scope and pricing on site. Anything else?”
After-Hours Routing Script
The after-hours plumbing call script has one job: qualify whether it’s a true emergency or can wait until morning, then route accordingly. Dispatching a tech for a dripping faucet at 2 AM helps no one.
[DISPATCHER / AI] “You’ve reached [Shop Name] after hours. I can help you book an emergency call or schedule a service for the next business day. Are you dealing with an active leak or emergency?”
[If YES — emergency] Proceed with the emergency script above. Capture intake, then page the on-call tech with a full call summary.
[If NO — non-emergency] “Got it. I can book you for first thing tomorrow [day] or schedule for later in the week. Which works better?”
Capture address and contact, confirm the slot, send SMS confirmation.
[If UNCLEAR — caller unsure] “Can you describe what’s happening? I want to make sure we’re getting the right help to you at the right time.”
This prevents two things: under-triaging a slow leak that will worsen overnight, and rolling a tech for a job that could wait six hours.
The Three Calls Your Script Doesn’t Cover
Most plumbing dispatcher scripts stop at emergency, booking, and after-hours. Then the phone rings and it’s none of those. These three account for a large share of daily volume in a working shop, and an unscripted dispatcher handles each one badly in a predictable way.
The price shopper. “How much to unclog a main line?” The wrong answer is a number. The second-wrong answer is “we can’t quote over the phone,” which sounds like a dodge and ends the call.
“Depends on where the clog is and whether it needs a camera — that’s why we don’t guess over the phone. What I can tell you is the diagnostic fee is [$X] and it comes off the repair if you book with us. When’s a good window for you?”
That does three jobs: it explains why there’s no number, it gives a real number the caller can hold onto, and it moves to booking. Price shoppers who get a straight answer convert far better than price shoppers who get stonewalled.
The status call. “Your tech was supposed to be here at 2.” This is not a booking call and shouldn’t be scripted like one. Never say “he’s on his way” unless you’ve confirmed it.
“Let me pull that up — you’re at [address], and you’re on [tech]‘s route. Give me sixty seconds to reach him and I’ll call you right back with a real time.”
Then actually call back. A status call handled badly turns a completed job into a one-star review, which is a more expensive failure than a missed booking.
The out-of-area call. The caller is 40 miles outside your radius. Book it and you burn a truck; hang up and you burn goodwill.
“You’re just outside where we run trucks, so I don’t want to promise you a window we can’t hit. Here’s who I’d call in [area].”
Referrals cost nothing and come back. What costs money is a dispatcher who books the job because the script had no branch for saying no. That’s why service-area boundaries belong in the script itself, not in the dispatcher’s memory. Plumbing call triage covers the severity side of this same sorting problem.
Intake Fields Every Plumbing Call Should Capture
A good plumbing dispatcher script is not the words — it is the data it produces. Every call should leave a record in your CRM or dispatch log with these fields filled. Anything missing means a callback or a tech rolling blind.
| Field | Emergency Call | Standard Booking |
|---|---|---|
| Call type | Required | Required |
| Fixture / system type | Required (gas vs. electric, pipe vs. drain) | Required (scope the truck) |
| Failure symptom | Required | Required |
| Mitigation taken | Required (is shutoff closed?) | N/A |
| Service address + access notes | Required | Required |
| Caller name + callback number | Required | Required |
| Authorization confirmed (rental) | If applicable | If applicable |
| Appointment window + tech assigned | Required | Required |
| SMS confirmation sent | Required | Required |
| AI disclosure given | If AI-handled | If AI-handled |
Missing fixture type → wrong parts on the truck. Missing access notes → tech sits at a locked gate at midnight. Missing authorization → unauthorized work on a rental, liability exposure. The script exists to make these misses impossible.
Grade Your Own Calls: A 10-Point Dispatcher Rubric
Writing the script is the easy half. Getting it followed on call 40 of a Friday is the other half, and you can’t manage that on vibes. Pull five recorded calls a week and score them. One point each, pass at 8.
| # | Check | Pass condition |
|---|---|---|
| 1 | Branch identified | Call type established within the first two exchanges |
| 2 | Mitigation first | On emergencies, shutoff asked before scheduling |
| 3 | Symptom captured | Caller’s own description recorded, not paraphrased into a category |
| 4 | Fixture/system specified | Gas vs. electric, pipe vs. drain vs. sewer noted |
| 5 | Address + access | Unit number, gate code, pets — all captured in one pass |
| 6 | Authorization | Rental/tenant calls confirm the owner before booking |
| 7 | Real window offered | A time range, not “as soon as we can” |
| 8 | Confirmation sent | SMS goes out before the call ends |
| 9 | Dead air | No gap longer than five seconds without narration |
| 10 | Escalation correct | Human-request, gas smell, and out-of-area branches handled per script |
Score trends tell you more than any single call. If line 4 fails repeatedly, your techs are rolling with wrong parts and the fix is a script change, not a lecture. If line 7 fails, your dispatcher doesn’t trust the schedule — that’s a dispatch software problem wearing a script costume. If line 9 fails, the dispatcher is typing while the caller waits, and the intake form needs fewer required fields.
The rubric is also the honest way to compare a human dispatcher against an automated one. Score both on the same ten lines, same call types, same week. Lines 1 through 8 are mechanical, and a scripted system should hit them on every call. Line 10 is where judgment lives.
What to Do About Plumbing After-Hours Calls
After-hours volume is where most plumbing shops bleed the most revenue. A homeowner with a burst pipe at 10 PM will call until someone answers — and the first plumber to answer wins the job. Plumbing after-hours calls represent a disproportionate share of emergency revenue precisely because the barrier to answer is high.
The options for after-hours coverage are limited:
- Owner on-call forward. Works when the owner answers. Fails at 3 AM, on weekends, on vacation, or when another call is already in progress.
- Third-party answering service. Answers, but captures a fraction of the intake fields above. The morning dispatcher re-calls every message to fill gaps — adding labor cost and callback lag.
- Voicemail. Costs nothing up front, and costs you the caller — a homeowner standing in water dials the next result rather than leaving a message. The revenue math is in the plumber missed calls revenue breakdown.
- AI dispatcher. Runs the script above without a human in the chair, captures all intake fields, and routes to the on-call tech only for calls that genuinely need one.
The after-hours window is the clearest use case for a scripted AI dispatcher: the call type is mostly predictable (emergency or “is someone coming?”), the intake is structured, and the cost of not answering is highest.
How AI Runs This Script Automatically
The transcript in AI receptionist for plumbers: 47-sec demo shows this script running live — a homeowner with a leaking water heater, handled in 47 seconds, appointment booked and SMS confirmation sent before the caller put their phone down. That is the plumbing dispatcher script above, executed in real time by a voice AI.
An ai answering service for plumbers handles the same call types documented here: emergency triage, standard bookings, after-hours routing, job status inquiries, and non-service-area calls. The difference from a human dispatcher is not speed — a good dispatcher matches the script on a clean daytime call. The difference is that the AI delivers the same intake at 3 AM on a Sunday that a dispatcher delivers at 10 AM on a Tuesday, for every call, without coverage gaps.
The AI’s script branches exactly as documented above: an active gas smell stops the intake and tells the caller to evacuate and call 911. A rental caller gets an authorization check before booking. An ambiguous call gets the clarifying question. The script handles the structure; the human dispatcher handles the handful of calls that genuinely need judgment.
One thing to check before you buy anything: whether the booking step is actually connected. If the AI can see a live calendar, it offers a real window and the appointment is confirmed before the caller hangs up. If it can’t, the AI produces a complete intake record and a human still keys the appointment into your plumbing dispatch software the next morning. Both beat voicemail. Only the first one closes the loop on the call, so ask any vendor which scheduling tools they actually write to — not which ones they display on a logo wall.
Plumbing Call Center Script vs. In-House Dispatch
Same skeleton — route, triage, capture, confirm — but two things change. A call center agent juggles several shops in a shift, so everything an in-house dispatcher keeps in their head has to be written down: service-area boundaries, the on-call rotation, the “we don’t do that” disqualifiers. And escalation has to be explicit, because the agent can’t walk down the hall and ask the owner. Which calls page the on-call tech, which get a next-day callback, which get a flat “a manager will call you back by 8 AM” — spell it out or it won’t happen.
Why shops end up here at all is a staffing question. The U.S. Bureau of Labor Statistics projects about 44,000 plumber, pipefitter, and steamfitter openings a year through 2034 against just 4% employment growth — meaning almost all of that hiring is replacing people who retired or left, at a May 2024 median wage of $62,970. When you’re already competing that hard for techs, adding a second dispatcher to payroll is the line item that loses. The full version of this comparison is in the plumbing call center script post.
Frequently Asked Questions
Q: What’s the most important question in a plumbing dispatcher script? A: “Have you been able to shut the water off?” on emergency calls. Mitigation before scheduling prevents property damage from compounding during the intake and the dispatch window. Get containment confirmed before anything else.
Q: Should the dispatcher identify itself as an AI on the call? A: Yes. Disclose at the open of every AI-handled call. Be precise about why, though, because the internet is full of bad legal shorthand here. The FCC’s February 2024 declaratory ruling confirmed that AI-generated voices count as “artificial” under the TCPA, which is what forces prior express consent — but that rule targets outbound calls, not a homeowner who dialed you. The FCC has since proposed dedicated AI-disclosure rules for calls, and state AI-disclosure statutes so far cover narrow categories rather than service dispatch. So disclose because the direction of travel is obvious and because callers who find out later feel deceived — not because someone told you a specific statute names plumbers.
This is general information, not legal advice. Check the current rules in your states with counsel before relying on any of it.
Q: How do I get dispatchers to actually follow the script? A: Score calls, don’t lecture. Pull five recordings a week and run them against the 10-point rubric above. Patterns show up fast, and most repeat failures are script or software problems rather than people problems — a dispatcher who never offers a real window usually doesn’t trust the schedule they’re looking at.
Q: Do commercial calls need a different script? A: Yes, at the intake stage. Commercial and property-management calls need three fields residential calls don’t: who authorizes the spend, a PO or work-order number, and after-hours building access — badge, lockbox, or a super to meet on site. Skip those and you get a tech standing outside a locked mechanical room at 2 AM with an approved job he can’t start.
Q: How long should a plumbing dispatcher call take? A: Clean emergency calls run 45–90 seconds with a tight script. Standard booking calls run 60–120 seconds. Calls with complications (active flooding, access issues, authorization questions) will run longer and should — rushing a complex intake produces an incomplete record. The 47-second demo in the AI receptionist for plumbers post is a best-case clean call, not a target for every call type.
Q: What happens if the caller can’t locate the shutoff valve? A: Walk them through it before continuing intake. For water heaters: cold supply valve on top of the tank. For pipes: nearest branch valve or the main shutoff at the meter. If the caller cannot locate or operate any shutoff, escalate to the on-call tech immediately — this is now a time-critical job, not a scheduled booking.
Q: Can this script handle callers who speak Spanish? A: A bilingual dispatcher handles this by switching languages. An AI script handles it by detecting the caller’s language in the first few words and routing to a parallel Spanish-language flow — if one is configured. Whether a Spanish flow is worth building depends on your service area demographics and whether you have Spanish-speaking techs to dispatch.
Q: How do I handle a caller who insists on speaking to a human? A: Escalate. The script’s job is to serve the caller, not to hold the line. Route immediately to the on-call tech or a human dispatcher with the intake already captured. The caller who gets a human after a quick AI handoff is far better served than one left on hold or sent to voicemail.
Q: What if a caller reports a gas smell? A: Stop the intake. The script tells them to leave the structure immediately, not touch switches or open flames, call their gas utility emergency line, and call 911 if needed. Do not book a service call. Do not attempt to troubleshoot. This branch is non-negotiable and identical to what any trained dispatcher should say.
Put This Script to Work on Every Call
The plumbing dispatcher script above gives your shop a starting framework. Your real script will need your service menu, your on-call rotation, your CRM fields, and your service area mapped in. The skeleton is the same; the tuning is what separates a generic template from one that actually reduces dispatcher re-work.
Book a 15-minute demo and we’ll show you what the script sounds like on a live test call for your shop — using your actual call types and service area.