The Emergency Call Triage Decision Tree

Why this matters

When a customer calls and says "emergency," the office has seconds to decide what it really is. Treat a genuine safety hazard as a routine booking and you put a household at risk and expose the company to liability. Treat every minor inconvenience as a drop-everything crisis and you wreck the day's schedule and exhaust your crew. Triage is the skill of sorting fast and right: protect life first, prevent property damage second, and book the rest in order. Whoever answers the phone needs this tree in their head.

Start here: is anyone in danger right now?

The first question is always safety, before scheduling, before price, before anything.

If the caller describes a smell of gas, sparking or burning electrical, smoke, a fire, or anyone feeling sick or dizzy in the building, this is not a service call yet. Tell them to leave the building and call emergency services or the utility's emergency line first. Your tech is not the first responder for a life hazard. Get them safe, then talk about the repair. Stay calm, give clear short instructions, and do not minimize what they are describing.

If no one is in immediate danger, move to the property-risk branch.

Branch one: is property actively being damaged?

If yes (water actively flooding, sewage backing up, a system failure threatening the structure or other systems), this is a true same-day emergency. The clock is running and every hour adds damage. Before you dispatch, give the caller the one action that stops the bleeding: where the main shutoff is, how to kill power to the affected area, how to contain the spread. A customer who can shut a valve buys you time and saves their home. Then get a tech moving.

If damage is contained or only threatened, drop to the next branch. A leak caught in a bucket is urgent but not the same as a flooding basement.

Branch two: has the customer lost an essential service?

If they have no heat in dangerous cold, no cooling in dangerous heat, no working water, or no power to critical needs, weigh who is affected. A household with an infant, an elderly person, or someone with a medical condition moves up the priority list. Loss of an essential in extreme conditions is a real emergency even without active damage, because the next stage is a health risk.

If the service is degraded but not gone (one zone out, a slow drain, a minor performance drop), it is urgent-soon, not now. Book it for the earliest realistic slot and tell the customer plainly when to expect a tech.

Branch three: is it inconvenience dressed as emergency?

Many "emergencies" are genuinely frustrating but carry no danger and no damage: a unit that quit on a mild day, a fixture that works but annoyingly, a cosmetic failure. The customer is upset, and that is real, but it is not a triage emergency.

Handle the emotion without breaking the schedule. Acknowledge the frustration, do not argue about whether it counts as an emergency, and offer the soonest honest slot. "I completely understand that's frustrating, the earliest I can get someone out is tomorrow morning, let me lock that in for you." You are validating the person while protecting the day.

When everything is an emergency at once

On a heat wave or a freeze, every call is urgent and you cannot do them all today. Triage within the urgent pile by the same order: active danger over active damage, active damage over lost-essential, lost-essential over degraded. The household with a vulnerable person and no heat in a freeze outranks the household with a comfort problem. Be honest about wait times rather than promising same-day to everyone and failing them all.

Quick reference

References

• OSHA general-duty guidance on hazard recognition and evacuation.
• Trade-standard emergency-dispatch and call-triage practice for service businesses.
• See related: The Running Late Customer Call Script.