Triage after-hours emergency calls and page the right person
A voice agent answers calls outside office hours, asks the questions your emergency rules require and decides whether to page the on-call manager, dispatch an approved vendor or log the request for morning. Residents reach someone quickly and the on-call person stops being woken for dripping taps.
Function: Operations · Industry: Property management
Triage after-hours emergency calls and page the right person
6 steps
At a glance
- Trigger
- A resident calls the maintenance line outside business hours.
- Typical inputs
- Inbound calls and caller phone numbers
- Your emergency definitions and scripts
- On-call schedule and escalation chain
- Approved emergency vendor list
- Systems it usually connects to
- AppFolio
- Twilio
- Slack
- PagerDuty
- How the work splits
4 rules, 1 model, 1 person steps
How it runs, step by step
6 steps, each tagged by what does the work. Rules are fixed logic, a model reads or drafts, and a person decides.
- Rules Fixed logic in code
- Model AI reads or drafts, with a confidence score
- Person A named person decides
- 1
Answer and identify
RulesThe agent answers on the first ring, states that it is an automated assistant and matches the caller's number to a unit.
- 2
Ask the classification questions
ModelThe agent asks the questions from your script and a model maps the answers to your emergency categories.
- 3
Apply the escalation rules
RulesCode decides the route: page on-call, dispatch the emergency vendor, give safety instructions or log for the morning.
- 4
Page with a summary
RulesThe on-call manager receives the unit, the caller's details and a short summary, and a failed page rolls to the next person.
- 5
Take the call forward
PersonThe on-call manager confirms the dispatch, speaks to the resident where needed and decides on anything not covered by the rules.
- 6
Log the work order
RulesThe call recording, transcript and classification are attached to a work order for the day team.
Where people approve
The decisions that stay with your team, whatever the confidence score says.
- The on-call manager approves any vendor dispatch outside your pre-approved list.
- Residents are told to call emergency services where your script says so.
- The emergency rules are signed off by management before launch.
KPIs to track
What to measure, before and after. Targets come from your own baseline.
- 01Time from call to page for true emergencies
- 02Pages sent for non-emergencies
- 03Calls that needed a person to repeat questions
- 04Emergency calls that were first classified as routine
Questions about this workflow
What if the agent is unsure?
It treats the call as urgent. An unnecessary page is a nuisance. A missed emergency is not. We test the rules on scripted and recorded calls and review misclassifications every week after launch.
Does it give safety advice?
Only the exact instructions you approve, such as shutting off a water valve or leaving the building. It does not improvise advice on gas, electrical or fire hazards, and it tells the caller to contact emergency services where your script requires it.
Which steps use rules, a model and a person?
Rules: answer and identify; apply the escalation rules; page with a summary; log the work order. Model: ask the classification questions. Person: take the call forward. Rules are fixed logic in code. A model reads or drafts and reports its confidence. A named person decides.
What do we need to start?
Typically: inbound calls and caller phone numbers; your emergency definitions and scripts; on-call schedule and escalation chain; approved emergency vendor list. You also need read access to AppFolio, Twilio, Slack and PagerDuty, or the equivalents you use. A workflow audit measures your volumes and past cases first, then gives a fixed price for the build, so you can decide with real numbers.