2026-07-01 · 6 min read

What Should Your After-Hours Emergency Call Protocol Include? (Free Template)

It's 9:40 on a Saturday night. A homeowner with water pouring through their kitchen ceiling calls your number. What happens next?

If your honest answer is "depends who picks up," you don't have an after-hours protocol. You have a coin flip. And every coin flip at 9:40 pm is a coin flip with a real job — sometimes a very big one — on the other side.

This post gives you a written protocol you can copy, adapt to your trade, and hand to whoever (or whatever) answers your phone tonight.

Why does "we'll call you back tomorrow" lose the job?

A homeowner standing in two inches of water is not going to wait until tomorrow. Neither is the family whose AC died in a July heat wave, or the one staring at a breaker panel that smells like burning plastic.

They do the obvious thing: they hang up and call the next company on Google. The first shop that answers like a professional — calm, structured, with a clear promise — usually gets the job.

And these aren't small jobs. After-hours calls skew toward real problems: burst pipes, dead systems, no-heat and no-cool emergencies. Say your average emergency ticket is $600, and one in ten turns into a system replacement worth five figures. Missing even two of those calls a month is real money — far more than any answering solution costs.

The fix isn't heroics. It's a boring, written protocol that gets followed the same way every single time.

The three-bucket triage template (copy this)

Every after-hours call fits one of three buckets. Write these down with examples from your trade, and make the classification rules explicit — no judgment calls at 2 am.

EMERGENCY — callback within 30 minutes, dispatch tonight if confirmed:

• HVAC: no heat with outside temps near or below freezing; no cooling in dangerous heat, especially with infants, elderly, or medically vulnerable people in the home; burning smell from the furnace or air handler.
• Plumbing: burst pipe or active flooding; sewage backing up into the home; no water to the entire house; water heater leaking near electrical.
• Electrical: burning smell or sparking from the panel or an outlet; exposed live wires; a panel or outlet that's hot to the touch; whole-home outage when the utility confirms it's not them.
• Any trade: gas smell or CO alarm — this one has its own rules. See the next section.

• HVAC: AC not keeping up in mild weather; system short-cycling; frozen coil with the system off.
• Plumbing: one fixture out of commission; a slow drain that's getting worse; a toilet that won't stop running.
• Electrical: one dead circuit; a breaker that trips occasionally; dead outlets confined to one room.

Maintenance, tune-ups, estimates, upgrades, "it makes a noise sometimes." Take the details, book the appointment, done.

The point of writing this down isn't that the categories are clever. It's that whoever answers your phone at midnight shouldn't have to invent them under pressure.

What safety rules should override everything?

Two situations where the script changes completely — and these belong at the top of your protocol sheet, not buried in the middle.

Gas smell or CO alarm. The order is non-negotiable:

• Tell the caller to get everyone out of the house now.
• Tell them to call 911 and the gas utility from outside.
• Only then capture their callback info and promise a follow-up.

A breaker that keeps tripping or anything electrical that smells hot. Tell the caller to switch the breaker off and leave it off. Repeatedly resetting a tripping breaker on a faulted circuit is how house fires start. Same family of rule: if there's standing water near anything electrical, nobody wades in.

If you take one thing from this article, take this section. A protocol that books jobs but skips the safety script is a liability, not an asset.

What should you capture on every emergency call?

An emergency call your tech can't act on is a lost call with extra steps. Every emergency intake must capture:

• Name.
• Callback number — read back digit by digit. One transposed digit and your tech is driving to a job with no way to call ahead, confirm, or find the house. This is the single most common intake failure, and reading the number back costs ten seconds.
• Full service address, including unit number and gate code if there is one.
• The symptom in the caller's own words, plus when it started. "Water heater leaking since about 8 pm" beats "plumbing issue."
• Access notes: dogs on the property, lockbox, whether anyone will be home, and — if they know it — where the main shutoff is.
• What they've already tried. Saves your tech twenty minutes of re-diagnosis.

Design your dispatch promise: the 30-minute callback window

Here's where most shops overpromise. Don't tell a panicked caller "we'll have someone there in an hour" unless you can guarantee it — a broken arrival promise turns an emergency customer into a one-star review.

Promise something you fully control instead: "A technician will call you back within 30 minutes."

It works because it's achievable, it's verifiable, and it immediately lowers the caller's stress — they know exactly what happens next, and they stop dialing your competitors while they wait.

Make the promise real with three rules:

• A written on-call rotation. One name per night. Not "whoever's up."
• An escalation path. If the on-call tech doesn't respond in 15 minutes, the call rolls to a backup — or to you. The 30-minute promise survives one missed page; it doesn't survive two.
• Log the promise time. Every emergency call gets a timestamp for "promised callback by." What gets logged gets kept.

Put it in writing, and give it to whoever answers

A protocol that lives in your head only works when you personally answer the phone. Write it on one page, laminate it, and make it the script for anyone who picks up after hours — you, your office manager, your spouse, an answering service.

If you use a human answering service, hold them to the same sheet. And check the math while you're at it: contractor-focused services like AnswerForce run roughly $279–699 a month on per-minute plans, and Ruby runs about $235–1,640 depending on minutes — real money for a script you still have to write yourself.

This is, as it happens, exactly the protocol we built into FieldAngel: safety-first gas and CO handling, three-bucket triage, the six-item intake with the callback number read back, and the 30-minute callback promise — on every call, at 3 am, without a per-minute meter running.

Test it: call your own line after hours

Don't assume. Tonight, after close, call your business line from your cell and grade what happens:

• How many rings before anyone — or anything — picks up? Did it go to voicemail?
• Give a routine scenario. Do you get booked, or brushed off?
• Give an urgent one: "my AC quit this afternoon." Does it get classified and scheduled?
• Now the real test: "I smell gas near my water heater." If the first response is anything other than get out of the house and call 911, your protocol failed where it matters most.
• Did anyone read your callback number back to you?