Emergency dispatch by phone: routing urgent calls after hours

At 11:40 on a Tuesday night, a homeowner finds water pooling under their water heater. They call the plumber whose magnet is on their fridge. What happens next decides whether that plumber gets a $900 emergency job or the homeowner calls the next number on Google. Most small shops lose this moment. They do not lose it because nobody cares. They lose it because nobody wrote down what is supposed to happen.

Emergency dispatch by phone is the whole chain between that call coming in and a technician rolling. It sounds simple. In practice it has five links, and the chain breaks at the weakest one: someone has to answer, someone has to decide how urgent the call is, someone has to reach the on-call tech, the tech has to confirm, and the caller has to hear a time they can trust. Miss any link and the caller hangs up and dials your competitor.

Start with a triage ladder, not a gut feeling

The shops that handle nights well all do the same thing first. They write down what counts as an emergency for their trade, in plain language, before the phone ever rings. Everything else hangs on this list.

A workable ladder has three rungs. The top rung is dispatch tonight: gas smell (caller told to leave the house and call 911 or the gas utility first), sewage backing into living areas, water actively flowing where it should not be, no heat when it is freezing and someone vulnerable is in the house, sparking or a burning smell from electrical equipment. The middle rung is first job tomorrow: no hot water, a leak the caller already contained, a system making a strange noise but still running. The bottom rung is the daytime queue: maintenance questions, billing, quotes for new equipment, anything that can wait for a callback during business hours.

The exact lines move by trade. An HVAC shop in a heat wave treats no cooling differently than one in mild weather. A plumber treats a burst pipe differently than a slow drain. What matters is that the lines exist in writing, because the person answering at midnight cannot reconstruct your judgment from scratch. They can only follow the ladder.

Build an on-call rotation that survives contact with reality

The most common failure in after-hours dispatch is the plan that assumes the on-call tech hears their phone. Phones go on silent. Techs fall asleep. Nobody checks the rotation and the same person gets three nights in a row and stops answering on the fourth.

A rotation that works has a primary and a backup, and a rule for what happens when neither answers within a set number of minutes. Write the minutes down. Five is common. The escalation after that should be the owner or a dispatcher, and the caller should never be told to wait indefinitely. If nobody can be reached, the honest answer is a callback window first thing in the morning, delivered with the caller’s details already logged so they do not have to repeat the story.

The intake details matter as much as the routing. At minimum, every after-hours call should capture a name, a callback number (taken first, in case the call drops), the service address, what is happening, and any safety notes. “Gas smell, caller advised to leave and call 911” is the kind of note that protects everyone the next morning.

What the caller should hear

People calling at midnight are stressed. The opening seconds set the tone. A good after-hours greeting names the company, acknowledges it is after hours, and asks for the callback number before anything else. Then come two or three triage questions, then a clear statement of what happens next: “I am paging the on-call technician now. You will hear back within fifteen minutes,” or “This sounds like it can wait until morning. I have you down for our first slot at eight.”

The promise has to be one the shop can keep. Overpromising at midnight is how a shop earns a one-star review by 8 a.m. If the policy is that non-emergencies get a morning callback, say so plainly. Callers accept a straight answer. They do not accept silence.

Where an AI receptionist fits

This is the kind of process an AI receptionist was built for. It answers every call, which removes the first failure point entirely. It runs the triage ladder the same way on the hundredth call as on the first, because it does not get tired or improvise. It captures the callback number first, asks the triage questions, and pages the on-call tech with the full intake notes attached. If the tech does not confirm within the set window, it escalates to the backup automatically.

It also does something humans rarely do consistently at midnight: it logs everything. The morning crew gets a written record of who called, what was wrong, what was promised, and what was dispatched. Nobody reconstructs the night from a missed call notification and a vague voicemail.

For a deeper look at how urgency gets sorted on a live call, see our guide to emergency call triage, and for the broader picture of night versus day rules, read after-hours vs business-hours call handling. If you run an HVAC shop, never missing an emergency HVAC call walks through a trade-specific version of this setup.

Write it down this week

You do not need software to start. You need a one-page document: the triage ladder for your trade, the rotation with primary and backup, the escalation minutes, the intake checklist, and the scripts for the two or three most common night calls. Test it by calling your own number after hours and running through the scenarios. Fix whatever breaks before a real caller finds it.

Then, when the whiteboard version is working, automate the parts that depend on a human being awake and sharp at 2 a.m. That is the part machines do better. The judgment about what counts as an emergency stays yours. The phone answering, the questions, the paging, the logging: that is dispatch, and dispatch is a process. Processes can run while you sleep.