Feature 2: ERT Emergency Queue¶
Purpose¶
The ERT Emergency Queue defines how calls to the campus emergency number are received by the Quick Emergency Response Team.
This feature ensures that emergency calls are handled in a controlled, trackable, and reliable way instead of simply ringing random phones.
Linked Feature¶
This feature depends on the finalized Campus Emergency Hotline.
Final Decision¶
Use an Asterisk Queue for emergency calls.
Do not use a basic ring group as the primary receiving model.
Reasoning¶
A ring group is simple, but it is not ideal for disaster response because it does not properly manage responder availability, simultaneous calls, call distribution, missed calls, or accountability.
An emergency queue is better because it supports:
Responder availability
Multiple simultaneous emergency calls
Call answer tracking
Missed call tracking
Escalation
Queue statistics
Operational accountability
Call Flow¶
Caller dials 111
↓
Asterisk receives the call
↓
Call enters the Emergency Response Queue
↓
Asterisk rings available ERT agents
↓
First available ERT agent answers
↓
Call is recorded and logged
↓
ERT handles triage and dispatch
ERT Queue Members¶
Example queue agents:
These members are not random departments. They are trained emergency response contacts.
Agent States¶
ERT members can have operational states such as:
The queue should prefer available responders and avoid repeatedly sending calls to unavailable agents.
Queue Behavior¶
When a user dials 111:
1. Call enters the emergency queue.
2. Available ERT agents are called.
3. First available responder answers.
4. If no one answers within the timeout, escalation starts.
5. If all responders are busy, the caller hears a short emergency hold message.
Maximum Wait Time¶
Emergency callers should not wait for a long time.
Recommended maximum waiting time before escalation:
After this, the call should move to the fallback/escalation path.
Hold Message¶
If the caller has to wait briefly, the system should play a short message:
Rejected Design¶
The following design is rejected:
Reason for rejection:
Weak tracking
Poor simultaneous call handling
No proper agent availability
Less operational accountability
Harder disaster-response management