Overview#
Emergency call transfers carry the caller's full context to the receiving centre, so a transferred caller never repeats their emergency and the receiving operator answers already informed.
A caller two minutes into describing a coastal emergency should not have to start again because the call belongs with the coast guard. Traditionally, transferring an emergency call discards everything the first operator learned: the location work, the triage notes, the caller's state. The receiving centre re-interviews a caller who is frightened, injured, or losing signal, and critical minutes are spent recovering facts the platform already held.
This module makes context travel with the call. When one emergency call centre transfers a call to another centre on the platform, the transferring operator reviews and approves a continuity packet containing the caller's identity, the facts gathered so far, the transfer reason, verified location, the linked dispatch incident, the AI-generated summary, a transcript excerpt, recording status, and any caller media. Destinations come from an administrator-governed agency directory, and the receiving operator sees the incoming context before picking up. It serves call takers, dispatchers, and the administrators who govern which agencies may receive transfers.
Key Features#
- Continuity Packet: The transferring centre attaches who is calling, what has already been gathered, and the transfer reason, together with location, the linked dispatch incident, the AI summary, a transcript excerpt, recording status, and caller media. The packet can be cancelled before pickup.
- Handoff Review Step: Before the transfer completes, the operator sees exactly which core facts are attached (location, incident, AI context, continuity), a readiness count, and warnings for anything missing, so what travels with the call is a deliberate decision.
- Blind and Attended Transfers: Both transfer types are supported with an explicit confirmation step, and an operational override remains available when core facts are missing but the call must move now.
- Carrier-Confirmed Claim: The receiving centre claims the packet only after a signed confirmation from the telephony carrier matches the actual inbound call and caller number, so context can never be released to the wrong party.
- Per-Organisation Segregation: Each packet is owned by the receiving centre and strictly segregated per organisation, with record-level access rules enforced in the platform record store.
- Governed Agency Directory: Administrators curate the live directory of agencies, services, and numbers. Operators get search, best-match recommendations, mutual-aid tags, and estimated response times, and only ever see callable, in-policy destinations.
- Incoming Transfer View: The receiving operator sees the transferred context before and after connection, and call takers see it immediately on answer instead of re-interviewing the caller.
- Accountability Recording: All handoff context is recorded with the transfer, preserving a reviewable account of what the receiving centre was given and why the call moved.
Use Cases#
- Cross-Jurisdiction Transfer: A call taker transfers a 112 or 911 call to a neighbouring jurisdiction; the caller's location, gathered facts, and transfer reason arrive with the call, and the caller never repeats their emergency.
- Specialist Crisis Handoff: An operator hands a mental-health crisis call to a specialist line with the triage notes already attached, so the specialist starts from what is known rather than from zero.
- Maritime Escalation: A coastal incident reported on 112 is transferred to the coast guard with the verified location, AI summary, and transcript excerpt attached for immediate tasking.
- Directory Governance: An administrator maintains the approved list of transfer partners, mutual-aid tags, and contact numbers, so operators under pressure choose only vetted, reachable destinations.
Integration#
Context continuity builds directly on the emergency call-taking workflow: the continuity packet draws its location from caller location intelligence, its incident link from incident command, and its summary and transcript from the live AI call intelligence that runs during the call. The incoming transfer view appears inside the dispatcher console and adaptive operator workspace, the governed directory complements mutual-aid resource requests for larger multi-agency responses, and every handoff feeds the platform audit trail. For structured incident handoffs outside a live call, the agency incident handoff exchange covers the complementary case.
Open Standards#
- SIP Call Transfer (RFC 3515 and RFC 5589): Blind and attended transfers align with the semantics standardised for session-based telephony, keeping transfer behaviour predictable across carrier networks.
- ITU-T E.164: Caller and destination numbers in the transfer directory and in carrier confirmations use the international numbering format, so the confirmed inbound number is matched exactly before context is released.
- TLS 1.3: Continuity packets and carrier confirmation messages travel over encrypted, authenticated transport between call centres and the telephony carrier.
- ISO 8601: Transfer events, claims, cancellations, and accountability records carry standard date-time formatting for downstream review and compliance reporting.
Last Reviewed: 2026-07-16 Last Updated: 2026-07-16