The 11pm Burst Pipe, and What Your AI Receptionist Should Do With It
It is 23:12 on a Tuesday in February. A woman is standing in her kitchen with water coming through the ceiling, and she has just found your number.
You are asleep. So is your engineer. Something has to answer this call, and what it does in the next ninety seconds decides whether you have a job in the morning, a complaint, or neither.
This is that call, followed from the first ring to the job appearing in your system. Everything here applies to plumbers, heating engineers, electricians, roofers and locksmiths, because the shape of the emergency call is the same across all of them. Only the keywords change.
The first ten seconds
The agent answers. It does not run a greeting script, it does not say the office is closed, and it does not ask how it can help.
Two things have to happen before anything else. It has to establish what is happening and whether this is your job at all. Almost every badly built trade agent gets this wrong by treating an emergency like an enquiry: name, postcode, how did you hear about us, what service are you interested in. By question three she has hung up.
The opening that works is short and asks the only question that matters:
"You're through to the out-of-hours line for [firm]. Tell me what's happening and I'll get someone to you."
Then it listens for the words that change everything.
The three sentences that stop the booking
Some emergencies are not yours, and the agent taking a booking instead of saying so is a safety failure rather than a service failure. There are three of these and every trade agent needs all three, regardless of what you actually do.
"I can smell gas"
The agent must stop. It does not book a job, it does not offer a morning slot, it does not transfer to you. The official advice from the gas networks is to open doors and windows, put out naked flames, not smoke, not touch any electrical switches, keep people away from the area, and call the National Gas Emergency Service on 0800 111 999, which is free and staffed 24 hours. The agent gives that number and stays until she has it.
"My carbon monoxide alarm is going off"
Same number, 0800 111 999. The advice is to open windows and doors, turn off the fuel-burning appliance if it is safe to, get everyone out, and seek medical help urgently if anyone feels unwell. One thing worth putting in the agent's words: do not assume it is a false alarm. People do, and the official guidance is explicit that you should assume CO is present.
"There's a cable down"
A downed cable or a damaged substation is 105, free from any phone in England, Scotland and Wales, which routes to the local network operator whoever supplies the electricity. If anyone is in immediate danger, 999 as well.
Water, the one with no national line
Water is the exception, and it is the one that makes trades different from every other business we write about. There is no national line to hand a leak to. A burst main in the street belongs to the water company, and anything inside the property boundary is yours. So put your local water company's emergency number in the agent's knowledge base, not a generic one, and let the agent decide by asking where the water is coming from.
Write these as hard refusals in the prompt, not as guidance. The prompt generator bakes all three branches in for you. The pattern is the same one that stops a restaurant agent guessing about allergens, which we covered in the guardrails guide. An agent that will bend a safety rule under pressure does not have a safety rule.
When it is your job
Back to the kitchen ceiling. This one is yours.
The agent now needs four things and nothing else: what, where, who, and how bad. The temptation is to collect more, because more fields make a better CRM record. Resist it. Every extra question at 23:12 is a chance for her to give up and ring the next firm on the list.
What is happening, in her words. The postcode and the door number. Her name and the number to ring back on, read back to her digit by digit. And one severity question that actually changes the dispatch decision, which for water is nearly always some version of "is it still running, and can you get to the stopcock?"
That last one earns its place twice over. It tells you whether this is a 40-minute job or a ceiling replacement, and it gives her something to do while she waits, which is the difference between a customer who feels handled and one who rings someone else.
Who gets woken up
Here is where most out-of-hours setups quietly fail, and it has nothing to do with AI.
"Escalate to the on-call engineer" is not a rule. It has no owner and no fallback, so at 23:12 it resolves to a phone ringing out. A usable rule has four parts, which we set out in full in the transfer guide:
- Trigger. An emergency keyword between 18:00 and 08:00.
- Action. Take the four fields, do not qualify further, SMS the on-call engineer, tell the caller they have been notified and will ring back.
- Owner. A named person for this week, not "the on-call phone".
- Fallback. What happens when that person does not answer.
The owner line matters more than it looks. A rota that lives in someone's head cannot be given to an agent. Before any of this works you need a rota that exists as a thing the agent can read, with a name against each week, and someone whose job it is to update it. That is a management task, not a software one, and it is the actual prerequisite for out-of-hours cover.
When the on-call doesn't answer
They will not answer. Not always, but often enough that this is the common path rather than the edge case, and it is the branch most setups leave empty.
Design it as a ladder, and give each rung a time:
- SMS the on-call engineer with the four fields. Wait ten minutes.
- No acknowledgement, SMS the second name on the rota and email you.
- Still nothing, the agent rings the caller back and tells her the truth: the team has the details, someone will ring her, and here is what to do in the meantime.
That third step is the one that saves the customer. She does not need an engineer on the doorstep in twenty minutes. She needs to know a human being has her problem. A call back at 23:35 saying "we've got this, turn your stopcock off, someone will ring you before seven" keeps the job. Silence loses it.
Tell her what it costs before you send anyone
Out-of-hours callout charges cause more disputes than the work does, and the dispute is always about disclosure rather than the amount.
The agent should state the callout charge, and that it is a callout charge rather than the price of the job, before it dispatches anybody. Not after. Not in the confirmation text. Before.
"There's a £[X] out-of-hours callout charge, and that's before any parts or labour. Are you happy for me to send someone?"
Two reasons. It is fairer, and it filters. A caller who says no at 23:12 was never going to pay the invoice at 09:00, and you have just saved an engineer a wasted night. Put the number in the knowledge base rather than the prompt, because it changes and the prompt should not.
What the call should leave behind
By 23:15 the job should exist somewhere other than a text message.
Worth knowing before you ask any vendor about integration: the UK trade software market is not the one American articles describe. Tradify, ServiceM8, Joblogic and Simpro dominate here, with Commusoft strong among gas and heating firms because it holds certification and CP12 records. ServiceTitan is a US-centric assumption, and Jobber is used here but is not the default.
So ask the question we set out in the buying comparison: is the integration native, or is it Zapier? And then test that it writes back, not just reads. An agent that can read your diary but cannot create the job has handed you a text message with extra steps.
The record should carry the four fields, the recording or transcript, the time the SMS went out, and whether it was acknowledged. That last field is the one that tells you whether your rota actually works, and after a month of them you will know.
The other ninety calls
Almost none of this is what your agent spends its time on.
The burst pipe is the call that justifies the system. The calls that pay for it are dull: do you cover this postcode, how much for a boiler service, can someone look at a dripping tap next week, I'm chasing an invoice, are you Gas Safe registered. They arrive during the day, while you are under a sink with your phone in the van.
If those are handled well, out-of-hours cover is a bonus rather than the whole business case. Judge any agent on the dull calls first, because that is where the volume is, and only then on the 11pm one.
Before you let it answer a real call
Six calls, placed by you, before it goes near a customer.
Say "I can smell gas" and check it refuses to book and gives 0800 111 999. Say a postcode you do not cover and check it says so plainly. Ring from a van with the engine running and check it recovers instead of looping. Trigger an out-of-hours emergency and then deliberately ignore the SMS for fifteen minutes to see whether the fallback fires, because almost nothing passes that one. Ask for a person on the first turn. And ask something it cannot know, to confirm it says so instead of inventing an answer.
The full version of that battery, with what a pass looks like for each, is in the 12 test calls checklist.
Get the gas branch and the fallback right and the rest is detail. Get them wrong and the 11pm call is worse than a phone that simply rang out, because now she has been told someone is coming.