Published October 27, 2026.

The hardest part of an emergency dispatch is not paging a technician. It is deciding, in under a minute, whether the caller needs emergency services, an after-hours visit, or a morning appointment. A dispatcher who defaults to "we will send someone" creates unsafe promises and unnecessary overtime. A dispatcher who defaults to "call back tomorrow" loses the customer. An escalation tree gives both the dispatcher and the client a defensible middle path.

Separate life safety from property damage

The first branch is always life safety. Gas odor, a carbon monoxide alarm, smoke, sparks, a downed power line, or a person trapped or injured goes to the local emergency number before any dispatch discussion. The dispatcher should say the words the client approved, stay on the line if the protocol requires it, and record the time of referral.

Property damage comes next: active water intrusion, sewage backup, no heat below a stated temperature, or a failed sump pump during a storm. These may justify after-hours dispatch depending on the client's contract and the technician's availability. The tree should name the conditions, not rely on the dispatcher's judgment about whether the caller sounds panicked.

Give each trade its own first question

Plumbing: "Is water actively flowing, and can you shut off the supply?" If the caller can close the valve and the leak is contained, a morning visit may be appropriate. If water is near electrical outlets or the shutoff will not close, escalate.

HVAC: "Is anyone in the home elderly, an infant, or medically vulnerable, and what is the indoor temperature?" A no-heat call at 20 degrees with an infant is different from a no-heat call at 55 degrees with a second working zone. Follow the client's written temperature threshold.

Electrical: "Is there burning smell, smoke, or a hot panel?" Burning smell or sparks means emergency services or an immediate dispatch by a licensed electrician, not a routine appointment. A single dead outlet is a next-day call.

Restoration: "Is the water category known, and has the source been stopped?" Category 3 water or an ongoing source changes the response. Do not let the desk classify the category clinically; record what the caller reports and route it.

Define the paging ladder

Name the primary on-call technician, the backup, and the service manager. State the page method, the acknowledgment window, and what happens when no one acknowledges. A typical ladder is: page primary, wait five minutes, page backup, wait five minutes, call the service manager. If no one acknowledges within 15 minutes, the dispatcher tells the caller the truth and offers the first available morning window or a referral.

Do not page every technician at once. A broadcast page creates confusion about who owns the call and wakes people who are not scheduled. One owner at a time, with a visible timer, is easier to audit.

Write the caller promise carefully

Say what the desk controls. "I have paged the on-call technician; they will call you within 20 minutes" is a promise the desk can keep if the ladder works. "Someone will be there in an hour" is a promise about travel, traffic, and the technician's current job. Avoid it unless the client has authorized that language and the technician has confirmed.

If the caller declines the after-hours visit because of the cost, record the decision and offer the morning slot. Do not pressure a frightened caller into a service they cannot afford. The record should show that the option was offered and the caller chose.

Build a client-specific override sheet

Every client has quirks: a landlord who authorizes dispatch for any leak, a property manager who requires a purchase order first, a restaurant that cannot close during dinner service. Put those overrides on one page with the client's name, the approver, the effective date, and the maximum dollar amount the desk may commit. Review the sheet monthly.

The override sheet should not live only in a dispatcher's memory. If the approver is on vacation, the sheet should name an alternate. If the client changes the policy, replace the sheet and archive the prior version.

Close the loop with the technician

The record is not complete when the page is sent. It is complete when the technician acknowledges, when the caller is told the technician's name and callback, and when the outcome is recorded. If the technician cannot respond, the dispatcher should return to the caller before the promise window expires, not after the caller calls again.

Capture the technician's arrival time and the disposition: repaired, temporary fix, parts needed, or referred. Those fields make the next dispatch faster and give the client a factual after-hours report.

Review escalations weekly

Sample every life-safety referral and a portion of after-hours dispatches. Check the first question, the branch chosen, the page timing, the promise made, and the outcome. Look for patterns: a trade that consistently over-dispatches, a client whose approval path is unclear, or a technician who acknowledges late.

Feed the findings into the tree. If three dispatchers misclassify the same HVAC scenario, the question is ambiguous, not the people. Revise the wording and retrain on the changed branch.

Implementation checklist

  1. Put life-safety referrals before any dispatch decision.
  2. Write a first question and branch for each trade.
  3. Publish the paging ladder with timers and named alternates.
  4. Script the caller promise and the cost-decline path.
  5. Keep a client override sheet with approval limits.
  6. Record acknowledgment, arrival, and disposition.
  7. Review escalations weekly and revise ambiguous branches.