How to triage emergency calls without a night dispatcher

For trades and practices where calls happen 24/7 — HVAC, plumbing, electrical, locksmith, dental, veterinary, septic, garage door — emergency triage is the highest-leverage capability of any phone system. Done well, it captures the high-value emergency calls that competitors miss while protecting your team from getting woken up for non-urgent issues. Here is how to configure it.

Emergency-driven trades face two opposite failure modes. Mode 1: you have no after-hours coverage, so genuine emergencies (burst pipes, no heat in winter, lockouts at 2am) hit voicemail and book with whoever picks up. Mode 2: you have on-call rotation but no triage, so a tech gets paged at midnight for a "I have a question about my bill" call. Both fail; the first costs you revenue, the second burns out your team.

AI triage solves this by recognizing what is genuinely an emergency from the caller's opening words and routing accordingly. Real emergencies dispatch immediately; routine calls schedule into the next-available business-hours slot.

During onboarding, you define what counts as an emergency for your specific business. The AI uses these rules to triage every inbound call in real time. Examples by trade:

• HVAC: "no cool" with house temperature over 80°F + occupants present, "no heat" with house temperature under 50°F or vulnerable occupants (elderly, infants), CO alarm sounding, gas smell, electrical burning smell from a unit.
• Plumbing: active flooding or sewage backup, no water (whole-house or critical fixture), gas leak suspected, broken sewer line, water heater leak with no shutoff.
• Electrical: burning smell from outlet or panel, sparking, smoke from electrical, tripped breaker that will not reset, partial loss of power affecting critical systems (medical equipment, refrigeration, well pump).
• Locksmith: stranded with kids or pets inside, locked out in extreme weather, after-hours business lock change required for security (employee fired today, etc.), keys lost late at night with safety concern.
• Dental: severe tooth pain with swelling, knocked-out tooth (90-minute reimplantation window), broken tooth with sharp edge causing oral injury, post-op bleeding that will not stop.
• Veterinary: pet not breathing or unconscious, suspected toxin ingestion, severe vomiting / lethargy with other symptoms, hit by car, post-surgical complications, severe difficulty breathing.
• Septic & sewer: active sewage backup in living spaces, drain field overflow, sewage in yard, multiple drains backing up at once.
• Garage door: stuck door with car inside (customer needs to leave for work), door stuck open at end of day (security concern), broken spring with car blocked.

Every inbound call goes through this flow on platforms with proper emergency triage:

1. 1Caller speaks. AI listens to the opening message and qualifying answers.
2. 2AI asks clarifying questions if needed. For ambiguous calls ("there's water on the floor"), the AI asks the right qualifying question ("is the water still actively flowing?") to determine emergency status.
3. 3Triage decision. If the call matches an emergency rule for your business, route to emergency dispatch. If routine, route to normal scheduling. If genuinely ambiguous, route per your fallback rule (default: treat as emergency to be safe).
4. 4Emergency calls are dispatched. Configurable: text/page your on-call tech with full caller context (address, issue, urgency cues), book a same-day emergency appointment, or transfer to a designated on-call number.
5. 5Routine calls are scheduled. Booked into the next-available business-hours slot using your normal scheduling rules. Customer hangs up with a confirmation text.

When the AI dispatches an emergency, the alert your tech receives should include enough context that they can roll without a follow-up call. Configure your alert template to include:

• Caller name and callback number.
• Address (street + city; flag if outside service area).
• Issue description in the caller's own words.
• Severity / qualifying detail captured during the call (system age, symptoms, duration of issue).
• Whether the AI gave the caller any pre-arrival guidance (e.g. "walk them through finding the main shutoff" for plumbing).
• ETA window the AI told the caller — your tech needs to honor this or call back if they cannot.

Triage rules can be different at night vs during the day. Some businesses configure them this way:

• Business hours: most calls handled normally; only true emergencies (active flooding, fire risk, life safety) trigger emergency dispatch.
• After hours: tighter rules — only "we cannot wait until morning" emergencies (burst pipe, no heat in winter, locked out with kids inside) get on-call paging. Other calls schedule for first thing in the morning.

This protects your team from after-hours pages for issues that genuinely can wait until 7am while still capturing the true emergencies.