Call-intake checklist · Escalate by your written safety policy
Safety-sensitive call escalation checklist
A caller mentions a gas odor, a carbon monoxide alarm, a burning smell or smoke. This page is about designing the office's escalation path. It is not safety advice, and it deliberately contains no instructions to give callers.
What this call usually looks like
Safety-sensitive calls are rare compared with routine service calls, which is exactly why they are dangerous to handle informally. A call-taker who has never had one improvises; an answering service reads whatever generic line it was given; software follows whatever it was configured to do. The only reliable approach is a written company policy — ideally reviewed by whoever is responsible for safety in your business and consistent with guidance from your local utility and authorities — that every answering path follows word for word.
Vendors in this market describe routing these calls to people. Avoca's HVAC pages show a 'gas smell from furnace' call routed to a technician rather than booked, and its busy-season post describes configuring specific instructions for edge cases such as a gas smell. Goodcall's HVAC buyer article calls this 'safety-grade call triage'. None of that replaces your own policy.
Rules to decide before the phone rings
These decisions belong to the owner or safety lead, in writing. Nobody answering the phone — employee, service or software — should invent any part of them.
- The exact wording, if any, the call-taker reads to a caller who reports a gas odor, carbon monoxide alarm, burning smell or smoke. Your company writes and approves it; it should be consistent with the guidance your local gas utility and emergency services publish.
- Who is contacted immediately, by what channel, and who is the backup if they do not answer within a set time.
- Whether the call-taker stays on the line, ends the call, or transfers, and to whom.
- What is recorded, and how quickly a manager reviews every safety-sensitive call afterwards.
- Which words or situations trigger this procedure. Keep the trigger list broad; a false alarm costs little.
- What the call-taker must never say — for example, reassurance that something is probably fine.
What to capture on every safety-sensitive call
| Capture | Why it matters |
|---|---|
| Callback number, confirmed | The single most important field if the call drops. |
| Service address | Needed for any response. |
| What the caller reported, in their exact words | Recorded verbatim; no interpretation. |
| Time of the call | Needed for follow-up and review. |
| Which script lines were read | Shows the policy was followed. |
| Who was notified, when, and whether they acknowledged | Closes the loop. |
Sample questions (adapt to your own script)
Ask: Read your company's approved safety wording exactly as written.
Ask: "Can I confirm the best number to reach you right now?"
Ask: "What is the address?"
What not to promise on this call
- Any diagnosis, reassurance or guess ("it's probably the pilot light").
- Any instruction not in your company's approved script.
- Continuing the normal booking flow or asking about scheduling preferences.
- Treating the call as routine because the caller sounds calm.
Where the call goes next
The call goes immediately to the person your policy names — often a manager or on-call technician — with the caller's exact words, address, confirmed number, time and the script lines read. The receiving person acknowledges; if they do not within your set time, the backup is contacted. Every such call is reviewed afterwards.
Handoff templates: On-call technician handoff template · Warm transfer to a live CSR
After hours
Safety-sensitive calls do not follow business hours. The escalation chain must work at 3 a.m. on a holiday, which means named people, working numbers and a tested backup. Test the chain before the heating season starts.
How the HVAC Reception concept would handle it
Proposed · not available
The proposed HVAC Reception design treats these calls as outside the software's job: it would recognise trigger words broadly, read only the wording your company approves, confirm the callback number and address, and hand the call to the person your policy names. It would not diagnose or improvise. This is a design proposal; no product exists.
Common ways this call goes wrong
| What goes wrong | What prevents it |
|---|---|
| Call-taker improvises reassurance | Approved wording only; train and review. |
| Trigger list too narrow (only "gas leak") | Include odor, alarm, burning, smoke and similar words. |
| On-call contact unreachable | Named backup with a timed fallback. |
| No record of what was said | Log script lines read and notifications sent. |
Frequently asked questions
What should a receptionist tell a caller who smells gas?
Whatever your company's written safety policy says, read exactly. We do not provide that wording because it must come from your company and be consistent with guidance from your local gas utility and emergency services. The receptionist's job is to follow the policy, confirm contact details, and escalate — not to diagnose or advise.
Should an AI receptionist handle gas-smell calls?
In the design this concept proposes, software would only recognise the situation, read your approved wording, confirm the number and address, and hand the call to a person you name. It would not decide what is safe. The product does not exist; this describes how we think it should be designed.
Which words should trigger the safety procedure?
Keep the list broad: gas odor or smell, rotten-egg smell, carbon monoxide or CO alarm, burning smell, smoke, sparks, and anything the caller describes as a safety worry. A false alarm costs a few minutes; a missed one can cost far more.
How do we know the procedure works?
Test it. Call your own line after hours, use a trigger phrase, and check that the right person is notified, the backup triggers when they do not respond, and the record shows what was said. Repeat after any staffing or phone change.