Overview#
Outbound Calls and Callback Recovery helps an emergency communications centre get back in touch with callers whose calls dropped, were abandoned or need a follow-up, and lets dispatchers place verified outbound calls from the call handling console. It turns callbacks from an informal list into a durable, shared queue where each callback is owned by one dispatcher at a time and every outcome is recorded.
Outbound calls are placed through the centre's carrier connection with checks at each step, so a call that has been requested is placed once, its progress is tied to the right call record, and any call the carrier reports in an unexpected state is reconciled. When a caller needs to be re-engaged in another language or by text, the dispatcher reviews a translated message before it is sent.
For buyers, the module closes a well-known gap in emergency call handling: callers who hang up before help is arranged. For operators, it prevents two dispatchers from calling the same person, keeps callbacks from being lost at shift change or after a browser crash, and gives supervisors an honest record of every attempt.
Last Reviewed: 2026-10-28 Last Updated: 2026-10-28
Key Features#
- Durable Callback Queue: Callbacks are stored on the server with their priority, due time and state. They survive browser restarts and shift changes, and open callbacks include claims that have expired and can be recovered.
- One Owner at a Time: A dispatcher claims the next due callback in a single step. The claim is time-limited, so if the dispatcher is called away it returns to the queue, and if it has expired the console asks them to refresh and reclaim before recording an outcome.
- Guarded Outcomes: Completing, cancelling or recording a busy or no-answer outcome is only accepted from the current owner and for the current version of the callback. Busy and no-answer outcomes reschedule the callback or mark it failed.
- End the Line First: The console asks the dispatcher to end the active line before recording an outcome, so the record matches what actually happened on the call.
- Link to the Incident: The active callback can be linked to the selected incident, and the console confirms whether the link succeeded.
- Verified Outbound Calls: Outbound calls are prepared on the server before dialling, sent with a single-use request key so a retry never places a second call, and tied to the call record through authenticated carrier status updates and a secured media hand-off.
- Carrier Reconciliation: Calls the carrier reports as stuck, or that never report back, are reconciled against the call record, so an outbound call never silently disappears.
- Call-Bound Caller Re-Engagement: For a caller who needs follow-up in another language, the dispatcher reviews a translated message tied to that call before it is delivered by the voice assistant. Caller video and media requests sit in the same on-demand engagement pane.
- Read-Only Pop-Out Views: Callback actions stay in the main console window. Pop-out views show the queue read-only, so an action cannot be taken twice from two windows.
- Callback Metrics: Supervisors see callback volumes and outcomes calculated from the stored callbacks.
Use Cases#
Abandoned Emergency Call#
A caller hangs up before giving an address. A callback appears in the queue, a dispatcher claims it, calls back, reaches the caller, links the call to the new incident and records the outcome.
Busy Evening Shift#
Several dispatchers work the callback queue at once. Each claim belongs to one person, so nobody calls the same person twice, and a callback left by a dispatcher who went to a priority call returns to the queue automatically.
Re-Engaging a Caller in Their Language#
A tourist's call drops. The dispatcher reviews a translated text bound to the call, and sends it through the voice assistant.
Audiences#
- Dispatchers and call takers working callbacks.
- Supervisors monitoring callback performance.
- Centre managers responsible for abandoned call policy.
Integration#
The module is part of the emergency call handling console and uses the centre's telephony connection, the AI voice assistant for translated re-engagement, and the incident records used by dispatch. Callback history is kept with the call record for quality review.
Open Standards#
- NENA i3: calls are handled within the platform's standards-based call handling, with caller number and location carried from the network.
- SIP (RFC 3261): outbound calls are placed over standard session signalling through the carrier connection.
- ISO 8601: due times, claim expiry and outcome times use a standard date-time representation.