Summarize with
Share

It is 6:40 on a cold Sunday morning. A woman calls your plumbing and heating number because the furnace kicked on and now the basement smells like rotten eggs. Nobody at your shop is awake yet, so the call rolls to whatever answers when you can’t. What happens in the next thirty seconds matters more than any booking you will take that week. A phone system that cheerfully asks for her address, her preferred time and how she heard about you is doing exactly the wrong thing. She should be outside. This post is about what the right thing looks like, and why the best answer to a gas call is a short one.

01The call that is not a booking

Most calls to a plumbing or HVAC shop are some version of the same thing. Something is broken or about to be, and the customer wants someone to come look. A good answering setup takes the details, sends them to you and lets you decide what happens next.

A gas call is different. The customer thinks they want an appointment, but the thing they need first is to leave the building. Everything that makes an answering system good on a normal call (asking follow up questions, getting a clear description, collecting an address and a callback number) slows down a person who should be standing in the driveway.

I don’t have a number for how often these calls come in, but they tend to cluster around predictable moments. The first cold morning when furnaces fire up after sitting all summer. A water heater swap that left a fitting not quite right. A new range hooked up over the weekend by a brother-in-law. Most of them turn out to be nothing serious. Some of them do not, and the person answering the phone has no way of knowing which kind it is.

That last sentence is the whole post, really. Nobody on the phone can tell a minor smell from a dangerous one. Not a receptionist, not you on your day off, and definitely not an AI. So the system should not try.

02What the gas company and the safety agency tell people

You do not have to invent the rules here. The industry already wrote them.

An open front door of a house seen from the driveway with a phone resting on the porch step

The American Gas Association and the federal pipeline safety agency (PHMSA, the part of the Department of Transportation that oversees gas pipelines) give the public the same basic instructions. If you smell gas, leave the building right away. Do not flip light switches on or off. Do not use phones near the smell. Do not start a car near it. Once you are a safe distance outside, call 911 or your gas utility.

Read that list again with your phone line in mind. “Do not use phones near the smell.” The customer is on the phone with you, inside the house, possibly standing next to the furnace. Every extra question your answering system asks keeps them there longer.

That flips the usual goal of a phone call. On a normal call, a longer conversation means better information for you. On a gas call, a longer conversation is the risk. The right system gets off the phone quickly, and it gets the customer moving before it does.

It also changes who the customer should be talking to. Your shop is not the first call after a gas smell. The gas utility runs emergency lines for exactly this, and 911 is there for it too. Your plumber can repair the fitting tomorrow. The utility is the one that comes out tonight and checks whether the house is safe to go back into.

03Why a phone system should say less, not more

When people picture an AI handling an emergency, they tend to imagine something clever. It listens to the symptoms, asks smart questions, works out how bad it is and tells the caller what to do. That sounds helpful. I think it is the most dangerous version you could build.

Diagnosis over the phone is a bad idea for a human with twenty years in the trade. It is a worse idea for software. A caller who says “it’s faint, I think it’s fine” might be right, or might have been breathing it for an hour and stopped noticing. A phone system that agrees with them (“sounds minor, we can come Tuesday”) has just made a safety call it had no business making, in your company’s name.

So the rule I would hold any phone system to is simple. It never diagnoses a gas, medical or electrical problem. It does not decide whether a smell is serious. It does not suggest the caller check the pilot light, turn a valve, or open a window and wait. It does not book a routine visit for a gas smell as if it were a dripping tap. Those are all judgment calls, and on a gas call the only safe judgment is the one the gas company already made: get out and call from outside.

I made a similar argument about bookings in why an AI should never book a job without confirming it first. The principle is the same, just with higher stakes. Software should do the parts that are routine and hand everything else to a person. A gas smell is never routine.

04What the call should sound like

Here is roughly what a good answering system says when a caller mentions gas, a rotten egg smell, or a hissing sound near a gas appliance. Not word for word, because callers phrase it a dozen different ways, but this is the shape of it.

A phone screen showing an urgent alert notification with a caller number and a play button for a recording

First, it stops the normal script. No more questions about scheduling. Then it says something close to this: “If you smell gas, please leave the house now. Don’t switch any lights or appliances on or off on your way out. Once you’re outside and away from the house, call 911 or your gas company. I’m letting our team know right now.”

That is it. Short enough that the caller can hear it once and act on it. It does not ask them to stay on the line. It does not ask them to describe the smell. If the caller wants to keep talking, it repeats the instruction to go outside first.

After the call, the system does the part it is good at. It sends an urgent alert to the human number you named, with the caller’s number and whatever they said before the script stopped, plus a link to the recording. Your person can call them back once they are outside, check that they reached the utility, and arrange the repair visit for after the gas company has been out.

A few details that matter more than they look:

The same thinking runs through the after-hours call you should not quote over the phone, which covers the electrical version: sparks, burning smells and panels that are hot to the touch. Different trade, same rule. The phone system’s job is to get people safe and get a human involved, not to play technician.

05Who on your team gets that call

The weak point in most setups is not the AI. It is the handoff. An urgent alert at 6:40 on a Sunday morning is only useful if it reaches someone who will look at it.

Before you turn anything on, decide who owns these alerts. For a lot of small shops that is the owner, and that is fine, as long as everyone knows it. If you run an on-call rotation, the alert should follow the rotation, not go to whoever set up the system two years ago. Write down a backup. People sleep through texts, leave phones in trucks and go on holiday.

Then decide what that person does with it. A sensible callback goes something like: “Are you outside? Did you reach the gas company? Okay, once they’ve been out and it’s safe, here’s when we can come look at the furnace.” Your person is not diagnosing either. They are confirming the customer is safe and taking over from there.

This is also where a human beats software, and I am happy to say so. A calm voice from the actual company, five minutes after a scary phone call, does a lot for that customer. They will remember who called them back. The AI’s job was to get them outside and get your person on it fast. The relationship part belongs to you.

One more thing worth deciding ahead of time: what happens to the original appointment the customer may have been calling about. Sometimes the gas smell came from the furnace they already wanted serviced. The urgent alert should include anything they said about that, so your callback can pick it up once the emergency is over and you are not starting from zero.

06Test it before the first cold morning

You should not find out how your phone handles a gas call by getting one. Test it yourself.

A basement furnace and water heater beside a wall-mounted carbon monoxide alarm

Call your own business number from a phone the system does not recognize, at a time when your team would not pick up. Say you smell gas in the basement. Then listen. Does the safety instruction come first? Does it try to keep you talking or ask for your address before telling you to leave? Does your on-call person actually get an alert, and how long does it take to arrive? Try it again with different wording: “it smells like rotten eggs by the water heater.” Try a carbon monoxide alarm. A setup that only reacts to the exact word “gas” is not good enough.

Then listen back to the recordings. I wrote about why that habit matters for every call, not just emergencies, in listening back to every call your business takes. If your system records calls, make sure it announces that at the start. About a dozen states require everyone on a call to consent before it is recorded. The Digital Media Law Project lists California, Connecticut, Florida, Illinois, Maryland, Massachusetts, Montana, New Hampshire, Pennsylvania and Washington, and other surveys add Nevada and Delaware. A short notice at the start of the call is the simple version that works everywhere, but check your own state’s rule. I am not your lawyer.

If you are comparing vendors, put the gas test on your list of questions. Ask them directly: what does your system say when a caller mentions a gas smell, and can I hear it? A vendor that cannot answer clearly, or that brags its AI can “assess the situation,” has told you what you need to know. There are more questions worth asking in what to ask an AI phone vendor before you pay them anything.

Frequently asked questions

Can the AI tell whether a gas smell is dangerous?

No, and it should never try. Nobody can judge that over the phone, including experienced technicians. The system’s only job on a gas call is to tell the caller to leave the building and call 911 or the gas utility from outside, then alert a person on your team.

Why doesn’t it just transfer the caller to me?

Because a transfer keeps the caller on the phone, inside the house, while it rings. The safety guidance from the gas industry is to leave first and call from outside. Sending you an urgent alert lets you call them back once they are out, which is safer than keeping them on hold.

What if the caller is not actually in danger and just wants a gas line installed?

Then they hear a safety message they did not need, and your person calls them back to sort out the real request. That costs a little awkwardness. Missing a real leak because the system guessed wrong costs far more. I would rather the trigger be too sensitive than not sensitive enough.

Will it ever book a visit for a gas smell?

Not on its own. Appointments wait for your team to confirm them, and on a gas call the first step is the gas company, not your van. Your person arranges the repair visit after the customer is safe and the utility has been out.

Does this work the same for electrical and medical emergencies?

The principle is the same. The system does not diagnose sparks, burning smells, injuries or anything that sounds like an emergency. It tells the caller to call 911 when that is the right step, and it gets a person on your side involved straight away.

The bottom line

A gas call is the one call where the best thing your phone system can do is say very little. Tell the caller to get out. Tell them to call 911 or the gas company from outside. Get a real person on your team moving. Everything else, the diagnosis, the repair and the booking, can wait until everyone is safe, and none of it should be left to software.

These days we book appointments for roofing companies: we find homeowners looking for roof repair or replacement, answer their replies and book them into your system. If you run a roofing company, see how it works at rushdial.com/roofing.