Emergency Calls for Plumbers, HVAC and Roofers: AI Dispatch Rules
How an AI receptionist can sort real emergencies from routine calls, reach the right on-call tech, stay careful about price, and hand techs the details they need.
It is Sunday night and a homeowner has water coming through the kitchen ceiling. They call your number. What happens next decides three things. Do you get the job? Does your on-call tech get a clear picture? Does someone get woken up for a dripping faucet that could have waited until morning?
Plumbing, HVAC and roofing companies live on these calls. They are also where things go wrong. A voicemail nobody checks. A tech who gets a callback number and nothing else. A price mentioned on the phone that the tech never agreed to.
An AI receptionist can answer those calls day and night. But it is only as good as the rules you give it. This post walks through the dispatch rules worth writing down before you turn one on: what counts as urgent, who gets the call, what it can say about price, and how the details reach the tech.
Start with a plain list of what counts as urgent
The receptionist should not guess. It should follow your definitions, written the way you would explain them to a new office hire on their first day.
Here is how that list might look for each trade.
Plumbing. Urgent: an active leak that cannot be shut off, sewage backing up into the house, no water at all, a water heater leaking onto the floor. Can wait: a slow drain, a running toilet, a dripping faucet, a request for a quote on a remodel.
HVAC. Urgent: no cooling during a heat wave when there is a baby, an older person or someone sick in the home, a burning smell from the unit, water pouring from the air handler. Can wait: a maintenance visit, a thermostat question, a unit that is noisy but still cooling.
Roofing. Urgent: water coming in during or right after a storm, a tree on the roof, a tarp that blew off. Can wait: a missing shingle with no leak, an inspection for a home sale, a replacement estimate.
Then write the questions that sort one from the other. Is water coming in right now? Can you shut off the main valve? Is anyone in the home at risk from the heat? Is the ceiling sagging? The receptionist asks these in order and lands the call in one of three buckets: dispatch now, first thing in the morning, or regular booking.
That middle bucket matters. Plenty of calls feel urgent to the caller but do not need a tech at midnight. The receptionist can say so kindly, book the first slot, and tell them what to do in the meantime, using only advice you have approved.
The calls it should never try to handle
Some calls are not dispatch calls at all. A smell of gas. Smoke. A sparking electrical panel. A carbon monoxide alarm going off. Someone hurt. Part of a ceiling coming down.
For these, the rule is simple: the receptionist tells the caller to get everyone out and call emergency services or the gas company's emergency line. It does not troubleshoot. It does not ask them to go look at the furnace. After the call, it alerts the owner or on-call lead so a human can follow up.
Write the exact sentence it says in these moments, and ask your attorney or insurance agent to look at it. The same goes for any safety tips you want it to give, like where to find the main water shutoff. If it is not on the approved list, the receptionist does not say it.
Who is on call, and what happens when nobody answers
Your on-call schedule probably lives somewhere already: a shared calendar, a spreadsheet, or your dispatch software. The receptionist should read from that same place, so nobody has to update two lists when techs swap a weekend.
Next, decide the chain. A typical one looks like this: try the on-call tech, then the backup, then the owner or service manager. Decide how each person gets reached (a call, a text with the summary, or both) and how long the receptionist waits before moving to the next name.
Then decide what the customer hears. Honest beats hopeful. Something like: I have sent your details to our on-call technician and they will call you back shortly. It should not promise an arrival time unless the tech has confirmed one.
A few more rules to settle:
Service area. If the address is outside the area you cover, the receptionist says so up front instead of taking the details and leaving the caller waiting.
Existing customers. If the caller has a maintenance plan with you, flag it. You may want those calls to jump the line.
Language. In South Florida, a good share of emergency calls may come in Spanish. A bilingual AI receptionist can follow the same rules in both languages and note the caller's language so the tech knows how to greet them.
What it can quote, and what it should not
Price is where phone calls get companies in trouble. A tech shows up, sees the real problem, and the customer says the person on the phone told them something different.
So keep the list of things the receptionist may say short and fixed.
It can say: your after-hours or emergency dispatch fee, if you charge a set one. That the tech will give a price on site before any work starts. Whether you offer financing, if you do. Which payment types you take.
It should not say: what a repair will probably cost. What is likely wrong (it sounds like your compressor). Whether insurance will cover a roof leak. That a part is in stock. That someone will be there by a certain time.
If you want the receptionist to take a card for the dispatch fee before sending a tech, that is a business decision with real tradeoffs. Talk to your accountant and your payment provider about how to set it up and what to tell the caller about refunds.
How the tech gets the details
The whole point of good intake is that the tech walks in knowing what they are walking into. A missed call turned into a name and a number is not enough.
When the receptionist sends a job to the on-call tech, the message should include:
- Caller name and a callback number that has been read back and confirmed
- Full address, with gate code, unit number and where to park
- What is happening, in the caller's own words
- Answers to each triage question (is water still coming in, was the main shut off, who is in the home)
- Photos or video, if the caller texted any in
- Which bucket the call landed in and why
- Exactly what was said about fees, so nobody is surprised at the door
- Preferred language and whether this is an existing customer
- Any pets, ladders needed, or access notes the caller mentioned
The same record should land in the tool your office already uses, whether that is your field service software, your CRM or a shared inbox. That way the morning crew sees every overnight call without asking the tech to retell it.
One more helpful step: when the tech replies to accept the job, the receptionist can text the customer that help is on the way. That small confirmation cuts down on repeat calls from a worried homeowner.
If you want a closer look at how this works across trades, our page on AI for home services covers the rest of the day, not just the emergency line.
Test it before the next storm
Rules on paper are a starting point. Before the receptionist goes live, have people on your team call in and play customers. Make some calls clearly urgent, some clearly routine, and some messy on purpose. A caller who is panicking. A caller who will not give an address. A caller who keeps asking how much it will cost.
After launch, read the call summaries every week for a while and ask a few questions. Did urgent calls reach a tech? Did routine calls stay out of the on-call phone? Did any price talk slip through? Did techs have what they needed when they arrived? Where the answer is no, tighten the rule.
Roofing and HVAC companies should also plan a storm mode. After a big system rolls through, the phone fills up with calls that are all real but not all equal. A storm version of the rules might dispatch only active leaks overnight and book inspections in order the next day, while telling every caller plainly how the wait works.
Your next step
If you want an AI receptionist that follows your dispatch rules instead of a generic script, NURO Growth can help. We are a Florida-based AI integration company for local businesses. We build the receptionist into the phone and the tools you already use, or build the tools if you need them, write the rules with you, train your team, and report the return every month. It works in English and Spanish.
The first step is a free AI audit. We look at how your calls, leads and dispatch work today and where things slip, then give you a fixed quote. You can also call (877) 229-4447 or email info@nurogrowth.com.