Emergency Call Triage: How to Set Rules for an AI Receptionist
By AetherFlow Automation · Published · 3 min read
Key takeaways
- Triage means sorting calls into safety situations, urgent jobs and routine work, and deciding what happens next for each.
- The rules should come from you, not from the vendor. Write them as a short table: condition, class, action.
- Test the rules with realistic calls, review real calls regularly, and never rely on a business phone system as a substitute for emergency services.
What triage means on the phone
Triage is a simple idea borrowed from medicine: decide quickly who needs attention first. For a service business, it means every incoming call is classified within a minute or two and routed accordingly. A leaking tap and a burst pipe need different responses. A customer wanting a quote and a customer with no heat in freezing weather need different responses.
An AI receptionist can apply the same rules to every call, at any hour, which is its strength. It can only apply rules that exist, which is why writing them is your job.
Three classes are usually enough
| Class | What it means | What should happen |
|---|---|---|
| Safety | Possible danger to people: gas smell, carbon monoxide alarm, smoke, sparks, a person in distress | Tell the caller to leave the building and contact emergency services or the gas utility. Alert the owner or on-call person as well. |
| Urgent | Serious damage or hardship is likely if nothing is done soon | Alert the on-call person immediately; promise nothing you cannot deliver |
| Routine | Everything else | Capture details and book into the normal calendar, or queue for a morning callback |
Example rules for HVAC
| Condition | Class | Action |
|---|---|---|
| Gas smell, carbon monoxide alarm sounding, smoke or burning from equipment | Safety | Safety script; alert on-call |
| No heat in freezing weather | Urgent | Alert on-call; capture vulnerable occupants |
| No cooling in extreme heat with an elderly person, infant or medical need | Urgent | Alert on-call |
| Cooling not working, no vulnerable occupant | Routine (priority) | Book next available visit; confirm by email |
| Noise, intermittent fault, maintenance, quote | Routine | Book or queue for callback |
Example rules for plumbing
| Condition | Class | Action |
|---|---|---|
| Gas smell | Safety | Safety script; alert on-call |
| Burst pipe or active flooding | Urgent | Alert on-call; coach on shut-off if approved |
| Sewage backing up | Urgent | Alert on-call |
| No water at all | Urgent | Gather details; same-day dispatch if possible |
| Slow drain, dripping tap, running toilet, quote | Routine | Book or queue for callback |
These examples show the format. Your thresholds should reflect your service area, crew, pricing and legal obligations. If you are unsure about safety scripts, ask your local gas utility or trade association what wording they recommend.
Writing rules a machine can follow
- Be specific. “Serious leak” is vague; “water is flowing and cannot be stopped” is clear.
- Cover the grey areas. What happens if the caller is not sure? A sensible default is to treat uncertainty as urgent and alert a person.
- State what the receptionist must not say. For example, never promise an arrival time; never quote a price you did not approve.
- Decide who is alerted and how. Name the person or role, the channel and what they should do if they do not respond.
- Plan the fallback. If the first on-call person does not respond within a set time, who is next?
Keep it honest with callers
In an emergency, a caller needs clear information, not reassurance that cannot be backed up. A good script says what is happening (“I’ve flagged this as urgent and alerted our on-call technician”), does not promise a specific arrival time unless the company has agreed to it, and gives the safety instruction first where relevant.
How to test your triage
- Write ten to twenty realistic call descriptions, mixing clear and vague, calm and panicked.
- Call and role-play each one. Include at least a few borderline cases.
- Check the classification, the safety message where relevant and the alert that reached the on-call person.
- Fix the rules, then retest the same calls.
- After launch, review a sample of real calls each week for the first month, then monthly.
On the Professional plan, AetherFlow supports emergency-versus-routine dispatch logic, and the exact escalation method is agreed with you during setup. To compare coverage options, see HVAC answering service: what to look for and plumbing answering service.
Frequently asked questions
Can an AI receptionist decide what is an emergency?
It can apply the rules you give it, consistently, at any hour. It should not invent its own definition. For uncertain cases, the safest design treats uncertainty as urgent and alerts a person.
What if the system misclassifies a call?
It can happen. That is why transcripts and audio matter: review real calls, correct the rules and retest. Do not assume the first configuration is final.
Does it call emergency services for the caller?
No. It should instruct the caller to contact emergency services themselves in a safety situation.