Overview#
The Crisis Line Handoff module enables emergency dispatchers to perform warm transfers from an active emergency call to specialist mental health crisis lines without dropping the caller or requiring them to redial. When the AI dispatcher or a human operator determines that a caller requires mental health crisis support rather than, or in addition to, an emergency response, the module constructs a proper call transfer signal and routes the caller directly to the 988 Suicide and Crisis Lifeline (US), Samaritans (Ireland and UK), or Lifeline (Australia), preserving call continuity and generating an auditable handoff record for post-incident review.
The module is designed to close the operational gap between emergency dispatch and crisis care: callers in mental health emergencies frequently call 999, 911, or 112 rather than specialist lines, and the warm-transfer capability ensures they reach the right service without the interruption of a disconnected call.
Key Features#
- Multi-Line Support: Supports warm transfer to the 988 Suicide and Crisis Lifeline (US), Samaritans (Ireland and the United Kingdom), and Lifeline Australia, with the correct routing target selected by the dispatcher or automatically based on the tenant's country configuration
- SIP REFER Transfer: Transfers are executed using standard SIP REFER signalling, which instructs the telephony infrastructure to route the caller to the crisis line while maintaining proper call session management and enabling the receiving line to identify the transfer origin
- Session Continuity: The Replaces header in the SIP REFER message ties the transferred call to the original emergency session, ensuring the crisis line receives a seamless continuation of the call rather than a cold inbound ring
- Handoff Audit Record: Every transfer generates a handoff record with a unique handoff identifier, correlation identifier, originating session identifier, timestamp, crisis line selected, and reason for transfer, providing a complete audit trail for safeguarding reviews and quality assurance
- Correlation IDs for Post-Incident Review: The correlation_id linking the emergency session to the crisis handoff enables supervisors to reconstruct the full call journey across both services for any post-incident review
- Dispatcher-Initiated Transfer: Dispatchers can initiate the transfer at any point during the call through the operations dashboard, with the selected crisis line and a required handoff reason recorded before transfer proceeds
- Dry-Run Mode: In development and staging environments, the full transfer message is constructed and logged but not transmitted, allowing end-to-end testing of the handoff workflow without placing live calls to crisis lines
Use Cases#
Mental Health Crisis During Emergency Call#
A caller contacts emergency services reporting suicidal ideation. The AI dispatcher follows the mental health crisis protocol, provides immediate safety acknowledgement, and determines the caller would be better served by a specialist crisis counsellor. The dispatcher initiates a warm transfer to 988 (or Samaritans/Lifeline based on jurisdiction). The caller is connected to the specialist line without interruption and without having to re-explain their situation from scratch.
Escalation from Non-Emergency Contact#
A caller initially contacts emergency services about a seemingly minor matter but discloses self-harm during the conversation. The dispatcher reassesses, logs the reason for transfer, and routes the caller to the appropriate crisis line, with the original call session preserved as context in the handoff record.
Post-Incident Review#
A safeguarding team reviewing a critical incident can retrieve the handoff record by correlation ID, see exactly when the transfer was initiated, which dispatcher authorised it, which crisis line received the call, and the stated reason, providing a complete accountability trail without requiring manual log reconstruction.
Multi-Jurisdiction Deployments#
An organisation operating across Ireland and the United Kingdom has both Samaritans and 988 configured. The dispatcher selects the appropriate line based on the caller's stated location or the tenant's default, and the system routes accordingly without any configuration change required at the point of transfer.
How It Works#
Integration#
The Crisis Line Handoff module integrates with the Voice AI session layer to access the active call session identifier, and with the Operations Dashboard to expose the dispatcher-facing transfer control. Handoff records are written to the crisis_handoffs table, scoped to the tenant and linked to the originating incident. The correlation_id is also recorded on the incident record, enabling case management teams to see that a crisis handoff occurred without needing direct access to the call detail record. Crisis line targets and gateway configuration are set at the organisation level and require explicit activation of live transfer mode before any real calls are placed.
Open Standards#
- SIP (RFC 3261): All warm-transfer signalling uses Session Initiation Protocol version 2.0, with standard SIP message structure including Via, To, From, Call-ID, and CSeq headers to establish and manage the transferred call session.
- SIP REFER Method (RFC 3515): The crisis line transfer is executed using the SIP REFER method, with Refer-To and Referred-By headers instructing the telephony gateway to route the caller to the target crisis line without dropping the call.
- SIP Replaces Header (RFC 3891): The Replaces header in the REFER message binds the outbound crisis call to the originating emergency session identifier, ensuring the receiving crisis line receives a seamless session continuation rather than a disconnected inbound ring.
- SIP over TLS (RFC 5630): Transfer messages are carried over TLS transport, specified in the Via header as SIP/2.0/TLS, protecting call signalling in transit between the Argus proxy and the crisis line gateway.
- ITU-T E.164: All crisis line destinations (988 Lifeline, Samaritans, Lifeline Australia) and caller identifiers are stored and dialled using the international E.164 telephone numbering format, ensuring interoperability with any PSTN or SIP gateway.
- ISO 8601: Handoff timestamps (transfer initiation time, audit record creation) are stored and returned as UTC ISO 8601 datetime strings, providing unambiguous timestamps for post-incident safeguarding review.
- JSON Web Signature (RFC 7515) / JSON Web Token (RFC 7519): The associated handoff envelope carries an ES256 JWS compact serialisation as the chain-of-custody signature, guaranteeing the integrity and non-repudiation of the handoff audit record.
Compliance#
- All crisis handoffs are recorded with dispatcher identity, timestamp, reason, and crisis line selected, meeting safeguarding audit trail requirements
- Dry-run mode is enabled by default; live transfers require explicit environment-level activation to prevent accidental calls to crisis services during testing
- Correlation identifiers link emergency and crisis records for the full lifecycle of the intervention, supporting post-incident review under mental health and safeguarding frameworks
- Transfer reason is a mandatory field, ensuring dispatchers document clinical or operational rationale for every transfer that is committed to the audit record
Last Reviewed: 2026-04-14 Last Updated: 2026-04-14