The emergency call playbook: what should happen when it's an actual emergency

Every home-services business gets two very different kinds of call, and the difference decides how much money is on the line. One is *"can someone come look at this next week and give me a price?"* The other is *"there's water coming through my kitchen ceiling right now."* Both are worth answering. Only one of them is going to hire whoever picks up the phone first and stops asking questions.

The trouble is that most phone setups treat both identically — same greeting, same voicemail box, same "we'll get back to you." That's how you end up losing the highest-value job of the week to a company that simply reacted faster.

Step 1 — Decide what actually counts as an emergency

Before anyone can triage, you have to define the line. It's different by trade, and it should be written down rather than left to whoever answers. Roughly:

• Plumbing: active leak or burst pipe, sewage backing up, no water in the house, water near electrical. A dripping faucet is not an emergency, however annoying.
• HVAC: no heat in freezing weather or no cooling in dangerous heat — especially with infants, elderly residents, or medical needs in the house. A noisy unit can wait until morning.
• Electrical: burning smell, sparking, scorched outlet, panel issues, total power loss. This is the trade where "can it wait?" is most often *no*, because the failure mode is a fire.
• Roofing: active water intrusion during a storm, structural damage, exposed interior. A missing shingle spotted from the driveway can wait for a scheduled look.

Write your version down. Everything not on the list is a booking, not an emergency — and that clarity is what makes fast triage possible instead of a judgment call made under pressure.

Step 2 — The first sixty seconds

Whoever (or whatever) answers should get through four things quickly, in this order. The order matters — you want to know if it's dangerous before you start collecting an address.

1. 1Is anyone in danger, and is damage actively happening right now? This single question separates the emergency from the urgent-but-fine.
2. 2Can they stop it getting worse? Where's the water shut-off, can they kill the breaker, can they move what's under the leak. This is the most valuable thirty seconds of the call — it protects the customer's property before you've even left the shop, and it is the thing customers remember.
3. 3Where are they, and are they inside your service area? No point dispatching to a job you can't take.
4. 4Get a callback number before anything else. Phones die, calls drop, storms cut signal. If you have the number, the job survives a dropped call.

Step 3 — The promise you must NOT make

Here is where most emergency calls go wrong, and it isn't by being too slow. It's by over-promising to make the caller feel better. Someone answers the phone, hears panic, and says "we'll have someone there within the hour" or "that'll be about three hundred dollars" — without knowing the traffic, the crew's status, or what's actually behind the wall.

Then you arrive ninety minutes later and the job costs more. Now you're not the company that came out at midnight; you're the company that lied. That customer leaves the review, and they tell the neighbour.

The rule is simple: whoever answers the phone should never commit to a price or an arrival window they can't personally guarantee. They should commit to what's actually true — that you've got the details, that a real person is being contacted right now, and when the customer will hear back with a firm time. Certainty about the *process* reassures people just as much as a made-up number, and it doesn't blow up in your face.

Step 4 — Route it like it matters

A genuine emergency should not sit in the same queue as a quote request. It should reach a human who can act — a call, a text with the details, something that cuts through. And the routing should be explicit about time of day: what happens at 2pm is not what should happen at 2am. Decide in advance who gets woken up, for which trades, and at what threshold. Then the decision is already made when it's actually 2am.

The routine calls, meanwhile, should just get booked — on the calendar, confirmed by text, done — so they never compete for your attention with the emergency. Most businesses have this backwards: they let routine calls interrupt them all day and let emergencies go to voicemail at night.

Questions to ask whoever answers your phone

Whether it's a family member, an answering service, or an AI receptionist, these are the questions that reveal whether emergencies are actually handled:

• How do you tell an emergency from a routine call — is there a written rule, or is it a guess?
• What happens differently when it IS an emergency? Be specific.
• Will you ever quote a price or an arrival time? *(The right answer is no.)*
• How fast do I personally find out, and by what channel?
• What happens at 2am on a Sunday, specifically?

How June handles it

June answers your line live, 24/7, in your business's name. She works out whether it's a genuine emergency or a routine booking, gathers what's happening and where, gets a callback number, and books the routine jobs straight onto your calendar. For a real emergency she flags you immediately rather than letting it wait. And she is built not to promise a price or an arrival window she can't honor — because the fastest way to lose a customer you just won at midnight is to tell them something that turns out not to be true.

Related: the jobs you lose in your sleep, why a fast response wins the job, and what to look for in an AI answering service.