Emergency escalation rules for AI answering

Why escalation design comes first

An AI system that books routine calls perfectly but mishandles one carbon monoxide call is a failure. The stakes are real: each year more than 400 Americans die from unintentional carbon monoxide poisoning not linked to fires and more than 100,000 visit an emergency department, with gas and oil furnaces among the sources^[1]. The US Fire Administration estimates there were 344,600 residential building fires in 2023, with 2,890 deaths^[2]. Water is one of the most common emergencies: from 2018 to 2022, water damage and freezing caused claims at about 1.6% of insured homes each year, second only to wind and hail^[3].

Escalation is also how your on-call technicians experience the system. BLS notes that HVAC technicians may be on call for emergencies^[4], that electricians' schedules can include evenings and weekends^[5] and that general maintenance and repair workers may be on call outside business hours for emergency repairs^[6]. If alerts are vague, late or wrong, technicians will stop trusting them, and the whole system fails quietly.

Four severity tiers

The tier rules are yours to write, and they should reflect your trade, your climate and your capacity. A heating company in Minnesota treats no heat in January as tier two; a cleaning company may have no tier-two calls at all. Write the rules with the person who runs your on-call rota, and keep them on one page.

Trigger phrases callers actually use

Callers rarely say I have a carbon monoxide emergency. They describe what they notice. Build your trigger list from your own call recordings and include everyday language. Triggers must interrupt the conversation at any point, not only when the caller first explains the problem.

• Gas: smells like gas, rotten eggs, sulfur smell, hissing near the stove or water heater, the gas company tag.
• Carbon monoxide: CO alarm, detector beeping and it says CO, headache and dizzy when the furnace runs, everyone feels sick.
• Electrical: outlet sparked, burning plastic smell, outlet or switch is hot, buzzing panel, lights flickered and there is smoke, someone got shocked.
• Water: water coming through the ceiling, ceiling is bulging, basement is flooding, water near the panel or an outlet.
• Fire or smoke: anything smoking, flames, smoke from vents, burning smell from the furnace.
• Security and entrapment: garage door will not close at night, door came down on something and did not go back up.

Approved safety scripts

Write each script yourself, check it against guidance from your local gas utility and fire department, and have the system read it word for word. Do not let any AI tool improvise safety advice. Keep each script short enough to be heard and remembered by a frightened caller.

1. 01

   Gas smell

   Please leave the home now with everyone in it. Do not switch lights or appliances on or off. Once you are outside, call the gas utility emergency line or 911. I am alerting our on-call technician now.

2. 02

   Carbon monoxide alarm or symptoms

   Please get everyone out into fresh air now and call 911. Do not go back inside until emergency services say it is safe. I am alerting our on-call technician.

3. 03

   Smoke, fire or burning smell

   If you see smoke or fire, leave the home and call 911 now. I am alerting our on-call team.

4. 04

   Sparking or hot outlet

   Please do not touch the outlet or anything plugged into it. If there is smoke or fire, leave and call 911. If it is safe, switch off that circuit at the breaker. I am alerting our on-call electrician.

5. 05

   Water near electrical

   Please stay away from water near outlets, lights or the electrical panel. If you can safely reach your main water shut-off, turn it off. I am alerting our on-call technician.

Warm transfer or paging?

There are two ways to get an urgent call to a person. In a warm transfer, the system calls the on-call technician, briefs them with the summary and then connects the caller. In paging, the system sends the technician an alert with the summary and the technician calls the customer back. Many companies use warm transfer for tier one and two calls during evening hours and paging overnight, when technicians need a moment to wake up and read the details.

Whichever you use, tell the caller which number the technician will call from. Many people do not answer unknown numbers, and a missed callback on an emergency is the worst outcome.

Designing the on-call tree

1. Primary technician: alert by call and text with the summary. Wait a set time for acknowledgement.
2. Backup technician: if the primary does not acknowledge in time, alert the backup the same way.
3. Manager or owner: if neither responds, alert the person responsible for the rota.
4. Honest final message: if nobody responds, tell the caller the truth, repeat the safety instruction where relevant and give a firm callback expectation.
5. Log every step with timestamps: when the call arrived, when each alert went out and when someone acknowledged.

Ava follows this pattern for urgent calls, using your on-call path of primary technician, backup and then an honest callback request, after giving your approved safety instruction. Whatever system you use, test the full tree at night before going live, including what happens when every phone is switched off.

What the on-call alert must contain

An alert that says urgent call, please ring back wastes the technician's first five minutes. Agree a fixed format so every alert can be read at a glance, on a phone, half awake.

• Tier and trigger: for example, tier one, gas smell reported, safety instruction given.
• Caller name and callback number, with the number read back and confirmed on the call.
• Full service address with ZIP code, unit number and any gate or access notes.
• What the caller said, in their own words, in one or two short lines.
• Whether anyone vulnerable is in the home: young children, elderly, someone unwell.
• What the caller was told, including the safety instruction and any callback promise.
• Existing customer or new, and any open job or warranty on file.

Ask your technicians to rate a sample of alerts each month. If they keep calling customers to ask the same question, add it to the intake for that tier.

Example: a stormy Saturday night

Example: at 11:40 p.m. a caller tells a fictional roofing and electrical company that water is dripping from a ceiling light in the hallway. The system recognizes the water-near-electrical trigger, gives the approved instruction to stay away from the fixture and switch off that circuit only if it is safe, and alerts the on-call technician with the address, the symptoms and the caller's number. The primary technician does not acknowledge within ten minutes, so the backup is alerted and calls the customer six minutes later. The log shows the whole sequence, and on Monday the manager finds that the primary's phone was on silent. The rota now requires an acknowledgement test call at the start of each on-call shift.

Review every escalation

Each week, read every tier one and tier two call. Check that the trigger fired, the instruction was given first, the alert went out within target and someone acknowledged. Look for near misses too, such as calls where the danger was mentioned but the trigger did not fire. Add those phrases to the list and retest. Our guide to testing AI phone agents with real call scenarios includes scripts you can reuse for these regression tests, and modeling the payback of after-hours coverage helps you decide how much on-call capacity to fund.