The "Is This an Emergency?" Customer Decision Tree

It's 11:40pm. Your phone rings: a customer whose AC is "making a weird noise." Not broken — noisy. They're anxious, it's late, and in their mind this might be an emergency. You now have two bad options: roll a truck at midnight overtime rates for a noise, or tell an anxious customer to wait until morning and hope you're right. The decision tree eliminates this dilemma — by teaching the customer to triage themselves before they ever call you.

This is part of Pillar A: Capture Every Lead — the triage companion to the complete missed-call text-back setup guide. System 6's after-hours triage works best when customers arrive pre-sorted.

Why customers can't triage (and why that's your problem)

To you, "no heat at 20°F" vs. "furnace making a clicking sound" is an obvious sort. To the customer, both are "something's wrong with my furnace and it's nighttime." They lack three things you have: the technical knowledge to assess severity, the experience of what's happened before, and the calm that comes from it not being their house. So they call — and every call costs you sleep, attention, or an unnecessary dispatch. The decision tree gives them your judgment in a form they can use at midnight.

The tree: what waits vs. what doesn't

Build one tree per trade you serve. The structure is the same; the branches differ. Here's the template:

Branch 1: dispatch NOW (true emergencies)

• Safety threats: gas smell, sparking/burning smell from electrical, active flooding, sewage backup into living space, no heat when it's below freezing (with vulnerable occupants — elderly, infants, medical needs).
• Active damage in progress: burst pipe actively flooding, roof actively leaking into the house during rain, electrical panel arcing.
• Total loss of critical system in extreme conditions: no AC during a heat wave with health risk, no heat in deep cold, complete power loss not caused by the utility.

The test: is someone unsafe, or is damage actively getting worse by the hour? Yes to either = dispatch now.

Branch 2: first call in the morning (urgent but stable)

• System down in mild weather: no AC on a 75° night, no heat when it's 55° outside. Uncomfortable, not dangerous.
• Contained problems: leak stopped with the shutoff valve, tripped breaker that reset and holds, slow drain, single outlet dead.
• Noises, smells (non-burning), and performance issues: the weird noise, the lukewarm water, the room that's always cold. Annoying, diagnosable, not time-critical.
• Anything the customer already stabilized: if they turned off the water, reset the breaker, or otherwise stopped the problem's progress, it's a morning job.

The test: can this safely wait 8 hours without getting worse? Yes = morning.

Branch 3: schedule at convenience (not urgent at all)

• Maintenance reminders, tune-up requests, estimates for planned work.
• Minor cosmetic issues, questions about past work, billing questions.

These callers just need to know they'll be heard — the after-hours text-back captures them for the morning queue.

The text version (what the customer actually sees)

Nobody reads a flowchart at midnight. The tree ships as a text-back script — the after-hours auto-reply that sorts callers:

The two-question sort does the triage: "anyone unsafe / damage in progress" splits Branch 1 from everything else, and the morning-callback promise (with a specific time) defuses the anxiety that drives non-emergency midnight calls. Most Branch 2 and 3 callers, given a credible morning promise, happily wait.

The web version (the permanent asset)

Turn the tree into a page on your website: "Is This an Emergency? How to Tell." It serves three purposes:

• SEO: "is this an emergency" + your trade is a real search query from anxious homeowners at midnight. The page captures them.
• Pre-call triage: customers who find the page sort themselves before dialing.
• The link in your text-back: append "Not sure? See our emergency guide: https://leveragedowner.com/blog/is-this-an-emergency-decision-tree/" to the after-hours text. The callers who need convincing get the full tree.

Write it in the customer's language, not yours: "Water coming through the ceiling right now" beats "active intrusion event." Include the shutoff-valve and breaker-box basics — the customer who can stabilize their own problem becomes a morning job instead of a midnight dispatch, and they'll remember you taught them how.

Training your team on the tree

The tree isn't just customer-facing — it's your on-call tech's dispatch criteria:

• Write the dispatch rules down. "URGENT replies get a callback within [X] minutes; the tech dispatches if Branch 1 criteria are met on the callback." No judgment calls at 2am — the tree decides.
• Give the on-call tech an out. "If the callback reveals it's not Branch 1, schedule for morning — you're authorized to make that call." Techs who fear second-guessing dispatch everything; techs with clear criteria dispatch correctly.
• Review the URGENT log monthly. How many after-hours dispatches were true Branch 1? If half weren't, the tree's wording needs tightening — the sort is leaking.

Worked example: the 11:40pm noise call

Example: the customer with the noisy AC at 11:40pm. Under the old system: anxious call, groggy owner, 50/50 guess, possible wasted midnight trip. Under the tree system:

• Customer calls, gets the after-hours text-back with the two-question sort.
• They read it: nobody unsafe, no active damage — just a noise. They reply with name, address, and "AC making rattling noise, still cooling."
• Morning: the callback list shows them first. Your CSR calls at 7:30am, books a diagnostic for that afternoon.
• The customer later says the text "was actually reassuring" — the specific morning promise turned anxiety into patience.

No midnight dispatch, no anxious standoff, no lost customer. The tree did the triage; the morning system did the rest.

Compliance note

The after-hours text-back is an automated text: 10DLC business-texting registration (the carriers' registration for texts sent by software from standard numbers; 1–7 day approval, ~$15–$20 in fees) must be in place, with opt-out language in the message. Keep the after-hours reply about their inquiry — no marketing content appended. Emergency dispatch callbacks are transactional. This is general information, not legal advice.

Related guides in this series

The triage layer of Pillar A: Capture Every Lead — System 6's after-hours system. Pair with the after-hours emergency-call handling guide and the on-call rotation system for the staffing side.

The done-for-you version

This post is System 6 from the Leveraged Owner Starter Pack — the done-for-you version with the full after-hours setup guide, the triage scripts per trade, the decision-tree templates, and complete setup guides for all 8 systems.

No industry statistics were used in this post.

Keep building your systems

Related guides from the Leveraged Owner blog: