Why We Won't Publish a Price
We're a founding cohort. There's no public price because a price before a conversation locks you into a number before we understand your business. Here's why that's actually better for you.
July 8, 2026·3 min read
Read →How to Fire-Drill Your After-Hours Emergency Line: a 4-Scenario Test Any HVAC Owner Can Run This Week
You test every furnace you install. You pressure-test gas lines. You verify airflow before you leave the job. But there's one system in your business that almost certainly has never been tested: whatever answers your phone at 11 PM.
Most owners assume their after-hours setup works — the answering service, the voicemail tree, the forward-to-on-call rule — because nobody has complained. That's the trap. The callers your after-hours line fails don't complain. They call your competitor, and you never find out.
We've already published a full framework for building emergency call routing. This article is the companion piece: the drill. Four scripted test calls, what a pass looks like for each, and a scorecard you can fill out this week.
>Key Takeaways
- Your after-hours line is an untested system until you place test calls against it. Assumed-working is not tested.
- Four scenarios cover the failure modes that matter: gas smell, winter no-heat, CO alarm, and a routine call that must not wake anyone.
- For gas and CO calls, the correct first response is evacuate and call 911. A tech is secondary. Handling that skips the safety instruction is a fail.
- When a call is ambiguous, the safe default is to treat it as an emergency: false positives cost sleep, false negatives cost safety.
- Score all four scenarios, fix the failures, and re-run the drill quarterly — seasonal shifts change what counts as urgent.
Before You Start: Drill Ground Rules
Keep the drill honest with six rules:
- Call from a number your system doesn't know. A spouse's or friend's phone. If your setup recognizes your cell, you're testing the VIP path, not the customer path.
- Call at a realistic time. Run the calls when the scenario says.
- Warn your on-call tech that a drill is coming this week — but not when. You want to test the alert path, not ambush anyone.
- Play the caller straight. Use the scripts as written. Real callers are stressed and vague; don't feed the system hints.
- End every drill call by identifying it as a test, and for gas or CO scripts, state clearly there is no real hazard — you don't want a real truck rolling or a real 911 report.
- If at any point the person or system on the line moves to contact 911, the gas utility, or emergency dispatch on your behalf, break character immediately and identify the call as a test. A drill must never trigger a real emergency response.
Scenario 1 — Gas Smell at 11 PM
The script: "Hi, um — I think I smell gas in my house? Like near the furnace closet. It's kind of strong. You guys installed our system a couple years ago."
What a pass looks like:
- The very first substantive response addresses safety, not scheduling: the caller is told to leave the house and call 911 (or the gas utility's emergency line) from outside.
- Only after the safety instruction does anything else happen — connecting or alerting the on-call tech, capturing callback details.
- No message-taking, no "someone will call you back in the morning," no hold queue.
Scenario 2 — No Heat at 2 AM in January
The script: "Our heat just quit. It's the middle of the night and it's freezing outside. The house is already getting cold and we've got a baby."
(If you're running this drill in July, say the line anyway — a good system responds to the stated conditions, and you'll learn whether it's listening to context or just matching the clock.)
What a pass looks like:
- The call is treated as urgent, not routine: dangerous cold plus a vulnerable occupant is a same-night response situation, not a next-day booking.
- The on-call tech is actually alerted — verify this from the tech's side. Did the alert arrive, and how many minutes after the call? A triage decision that never reaches a human is a fail dressed up as a pass.
- Before hanging up, the caller is told what happens next and roughly when to expect contact. "We got your message" is not a plan.
Scenario 3 — CO Alarm Sounding
The script: "Our carbon monoxide detector keeps going off and I don't know why. Everyone feels fine, I think. Should somebody come look at the furnace?"
This is the sharpest test in the set, because the caller is downplaying it. CO is odorless; a sounding detector with no obvious cause is a leave-now situation, not a diagnostic conversation.
What a pass looks like:
- The response treats a sounding CO alarm as life safety, full stop: get everyone (including pets) out of the house and call 911 from outside. This is the standard public-safety guidance for a CO alarm from fire departments and health agencies alike — fresh air first, investigation second.
- No troubleshooting on the phone ("is it maybe the battery?"), no scheduling a next-day inspection as the primary response.
- The tech dispatch happens after the safety instruction, as the secondary track.
Scenario 4 — The 10 PM Tune-Up Request That Must NOT Page Anyone
The script: "Hey, no rush at all — I just keep forgetting to call during the day. I want to get a tune-up scheduled sometime in the next couple weeks."
This scenario tests the opposite edge, and skipping it is the most common drill mistake. A system that escalates everything passes scenarios 1–3 by accident and then burns out your on-call rotation in a month.
What a pass looks like:
- The caller gets a real outcome — an appointment scheduled, or complete details captured with a clear promise of a morning callback.
- Your on-call tech's phone stays silent. Verify from the tech's side, same as scenario 2. A pass isn't "the caller was handled"; it's "the caller was handled and nobody was woken up."
The Fail-Toward-Emergency Principle
Somewhere between scenario 3 and scenario 4 lives the ambiguous call: "the furnace is making a weird smell, I'm not sure what it is." No triage system — human or AI — classifies every ambiguous call perfectly. So the design question isn't whether your system will get an edge case wrong. It's which direction it errs.
The safe default is simple: when a call is genuinely ambiguous, treat it as an emergency. The costs are asymmetric. A false positive means your on-call tech takes a call that could have waited — annoying, cheap, recoverable. A false negative means a caller with a real gas leak or CO event gets a morning-callback promise — a safety event and a liability event. False positives cost sleep. False negatives cost safety.
When you score your drill, apply this principle to borderline handling: an unnecessary escalation is a soft deduction. A missed escalation is a hard fail.
The Scorecard
Run all four calls in one week, then fill this in:
| # | Scenario | Pass criteria | Result |
|---|---|---|---|
| 1 | Gas smell, 11 PM | Evacuate + 911 instructed FIRST; tech alert secondary; no message-taking | ☐ Pass ☐ Fail |
| 2 | No heat, 2 AM, January, infant | Treated as urgent; on-call tech alert VERIFIED received; caller told what happens next | ☐ Pass ☐ Fail |
| 3 | CO alarm sounding | Life-safety handling; evacuate + 911 stated explicitly; no phone troubleshooting | ☐ Pass ☐ Fail |
| 4 | Routine 10 PM tune-up | Caller booked or captured for morning; on-call tech NOT paged (verified) | ☐ Pass ☐ Fail |
- 4/4 — your after-hours line is doing its job. Put a repeat drill on the calendar for the start of the next heating or cooling season.
- 3/4 — fix the failing scenario and re-test it within seven days. If the failure was scenario 1 or 3, treat it as urgent: those are the safety lanes.
- 2/4 or worse — your after-hours handling needs a rebuild, not a patch. Start with the triage framework in our routing guide, define your tiers and escalation path on paper, then re-implement and re-drill.
If you get to the rebuild stage and want after-hours calls answered and triaged without adding headcount, that's the problem Vectrion AI builds for — Asher, your 24/7 receptionist, is built to separate the 2 AM emergency from the 10 PM tune-up request. But run the drill first, whatever system you use. You can't fix a phone line you've never heard fail.
Frequently Asked Questions
How often should I run this drill? Quarterly at minimum, and always at the start of heating season and cooling season — the seasonal shift changes what counts as urgent (a no-cool call means something different in a heat wave than in October). Also re-drill after any change to your answering setup, on-call roster, or phone provider.
Should I tell my answering service or on-call tech before I run test calls? Tell them a drill is coming during a given week, but not the day or scenario — honest system behavior, no ambush. Always end each call by identifying it as a test, and for gas/CO scripts, state clearly that there is no real hazard.
What if my current setup is just voicemail — should I still run the drill? Yes. Listen to your own after-hours greeting the way a panicked 2 AM caller would. If the honest answer is "I'd hang up and call someone else," you've learned exactly what the drill is designed to teach.
Why shouldn't the gas-smell caller just wait for my tech instead of calling 911? Because your tech might be 40 minutes out, and a gas leak is a fire-and-explosion risk now. Emergency services and the gas utility can respond immediately and make the scene safe; your tech's job is the repair that comes after. Any phone handling that positions the tech as the first responder to gas or CO has the order backwards.
Isn't treating ambiguous calls as emergencies going to burn out my on-call tech? Not if scenario 4 also passes. Fail-toward-emergency applies to genuinely ambiguous calls, a small slice of after-hours volume. The tune-up-at-10-PM test exists precisely to confirm that routine calls stay routine.
Related reading:
More Articles
The Holdout, Explained Simply
When you miss a call, we don't call back in three seconds. There's a short delay built in — and it's there for a reason. Here's what the holdout is, why it exists, and why it makes callbacks work better.
July 8, 2026·3 min read
Read →How We Measured Our Own Callback Speed
We ran a 1,000-call measurement rig to verify our callback speed. Here's what the clocks actually measure, what we refused to publish, and why honesty about the limits of our data matters.
July 8, 2026·4 min read
Read →Ready to stop losing leads?
Takes 60 seconds to fill out. We'll email your full revenue leak report in under 2 minutes.
No obligation. No credit card. Your Revenue Leak Report arrives in under 2 minutes.