WebRTC + AI for 911 Dispatch in 2026: Augmenting Telecommunicators, Not Replacing Them

AI in 911 in 2026 augments understaffed PSAPs (Public Safety Answering Points), it does not replace dispatchers. Oneida County (NY), Snohomish County (WA), and Tri-Cities (WA) all deployed AI co-pilots in 2026; Prepared and Aurelian are the leading vendors. WebRTC enables the missing piece: livestream video from the caller's phone.

Why this matters

PSAPs are losing dispatchers faster than they can hire. The national dispatcher vacancy rate hit 33% in 2025. AI absorbs the non-emergency call volume — outage reports, parking complaints, "is the road closed" — that is roughly 40% of total 911 traffic in suburban PSAPs. The remaining time goes to humans on the actual emergencies.

The WebRTC layer is the under-told story. Prepared and Aurelian both push a secure WebRTC livestream link to the caller's phone (over SMS) so the dispatcher can see what the caller sees. That changes triage entirely: cardiac vs. seizure, structure fire vs. brush, single vs. multi-victim — all visible in 5 seconds.

Architecture

```mermaid flowchart LR Caller[Caller Phone] -- voice 911 --> PSAP[PSAP CAD] PSAP -- SMS link --> Caller Caller -- WebRTC video --> Gateway[Pion Go gateway 1.23] Gateway --> Disp[Dispatcher Console] Gateway -- audio --> ASR[Realtime ASR] ASR --> Sum[Incident Summary LLM] Sum --> CAD[CAD Auto-Populate] Disp --> Resp[Police / Fire / EMS] ```

CallSphere implementation

CallSphere does not directly serve PSAPs but mirrors the same architecture for adjacent verticals where a human-in-the-loop must triage incoming voice with structured data:

• Behavioral health crisis — Crisis-line operators get the same Prepared-style screen: a real-time transcript, an LLM-drafted incident summary, and an optional WebRTC video link if the caller consents. The 6-container pod (CRM, MLS-equivalent, calendar, SMS, audit, transcript) carries the same state. See /lp/behavioral-health.
• Healthcare urgent intake — A symptom-triage workflow with the same Pion Go gateway 1.23 + NATS pipeline; the transcript is HIPAA-logged into 1 of 115+ tables.
• /demo — The browser demo includes a "share my video" toggle modeled directly on Prepared's UX. Try it at /demo.

Explore a live demo and compare current plans to find the right fit for your business.

Build steps with code

```typescript // 1. SMS the caller a one-click WebRTC livestream link async function sendStreamInvite(phone: string, incidentId: string) { const token = await jwt.sign({ incidentId, exp: Date.now() + 30 * 60_000 }); const url = https://stream.callsphere.ai/i/${token}; await sms.send(phone, Open this to share your camera: ${url}); }

// 2. Caller browser: opt-in camera, ICE-restricted to PSAP relay const pc = new RTCPeerConnection({ iceServers: [{ urls: "turn:turn.psap.example.gov", username, credential }], }); const stream = await navigator.mediaDevices.getUserMedia({ video: { facingMode: "environment" }, audio: false, }); stream.getTracks().forEach(t => pc.addTrack(t, stream));

// 3. Dispatcher console: subscribe to the SFU, render with overlays const remote = await sfu.subscribe(incidentId); videoEl.srcObject = remote; remote.onAudioTranscript((line) => updateTranscriptPanel(line));

// 4. Auto-populate CAD with incident summary nats.subscribe("incident.summary." + incidentId, (msg) => { const { type, location, victims, severity } = JSON.parse(msg.data); cad.update(incidentId, { type, location, victims, severity }); }); ```

Pitfalls

• Sending links to non-consenting callers — every PSAP deploying livestream needs a callee-consent script and audit trail.
• Streaming over commodity TURN — PSAPs need a private TURN cluster, ideally on FedRAMP-Moderate infrastructure.
• AI summarizing wrong — never let the CAD auto-dispatch on AI alone; the dispatcher must confirm.
• Latency over LTE — set very low video bitrate (250 kbps) and prefer audio if the link degrades.
• PII leakage in transcripts — redact addresses and SSNs at the ASR layer before they hit the LLM summarizer.

FAQ

Is AI replacing dispatchers? No — it absorbs non-emergency volume so humans focus on real emergencies.

What about consent and recording laws? All 50 states allow PSAP recording; livestream consent is treated like any video share — opt-in.

How accurate is the auto-populated CAD? ~85-90% on incident type and location; the dispatcher always confirms.

FedRAMP/CJIS compliance? Must be in the deployment plan from day one for any PSAP that touches CJIS data.

What about cellular dead zones? Fall back to SMS-only; the AI assists from the call transcript alone.

Sources

• https://www.wrvo.org/2026-03-13/oneida-county-uses-ai-to-enhance-911-operations
• https://oneidacountyny.gov/news/oneida-county-enhances-911-operations-with-two-new-public-safety-technology-systems/
• https://www.govtech.com/em/preparedness/tri-cities-in-wash-turn-to-ai-for-understaffed-911-dispatch
• https://www.police1.com/911-and-dispatch/smarter-faster-safer-how-ai-is-reinventing-the-emergency-call
• https://aibusiness.com/automation/ai-isn-t-replacing-emergency-dispatchers-it-s-helping-them

Explore a live demo and compare current plans to find the right fit for your business.