E911 for AI Receptionists: Dynamic Location and 2026 Compliance

If a caller dials 911 from a phone served by your AI receptionist, the call must reach the right Public Safety Answering Point with an accurate dispatchable location. In 2026, that is non-negotiable: Kari's Law and RAY BAUM'S Act apply to virtually every business phone system.

Background: the legal floor in 2026

flowchart TD
 Out[Outbound campaign] --> Twilio[Twilio Voice API]
 Twilio --> STIR[STIR/SHAKEN attestation]
 STIR --> Carrier[Originating carrier]
 Carrier --> Term[Terminating carrier]
 Term --> Recipient[Recipient phone]
 Recipient --> Webhook[/voice webhook/]
 Webhook --> Agent[AI sales agent]

Two federal laws govern emergency calls from business phone systems in the US:

• Kari's Law (effective Feb 16, 2020). Direct dial of 911 with no prefix. Notification to a central location (front desk, security) when 911 is dialed.
• RAY BAUM'S Act, Section 506 (effective Jan 6, 2021 for fixed and Jan 6, 2022 for non-fixed). Dispatchable location must be sent with every 911 call. Dispatchable location means street address plus enough information to find the caller — floor, suite, room, or other identifier.

Both laws apply to the multi-line telephone system (MLTS), which is exactly what an AI receptionist plus business phone system is. Compliance is the obligation of the platform provider, the reseller, and the on-site operator together. The FCC has begun enforcement; consent decrees in 2024 and 2025 hit several providers for failures.

By 2026, the operational picture has matured: every line must deliver Automatic Number Identification (ANI) and Automatic Location Identification (ALI) accurately to the appropriate PSAP. Dynamic E911 — where the location follows the user rather than the number — is widely deployed at large enterprises but still rare at small businesses, which is exactly where AI receptionists thrive.

How VoIP and SIP work for this use case

A 911 call from a SIP phone takes a different path than a normal call:

1. The phone or AI agent recognizes the dialed string as 911.
2. The originating SBC routes the call to a 911 Service Provider (Bandwidth, Intrado/West, Comtech, Telnyx 911) instead of a regular trunk.
3. The 911 Service Provider looks up the caller's registered or transmitted location and selects the correct PSAP.
4. Location data is delivered either as an ALI lookup keyed by the calling number (legacy) or as a PIDF-LO XML payload embedded in the SIP INVITE (modern, dynamic).
5. The PSAP receives the call and dispatches.

For dynamic E911, the multi-line telephone system has to know where each user is when they dial. Software clients can supply this from network location, GPS, or a manual address. Hardware phones must be associated with an installed location.

For an AI receptionist, the relevant lines are typically the business's main number (a fixed location) and any extensions or DID numbers assigned to staff. Each must have a registered address.

CallSphere implementation

CallSphere uses Twilio for all voice. Twilio offers Emergency Calling for Programmable Voice with explicit address registration on every number. CallSphere's onboarding requires the tenant to register a service address for each number they purchase. The Healthcare AI receptionist on FastAPI:8084 is for inbound and outbound business calls, not for on-site emergency calls — but if a caller reaches the AI and asks for emergency services, the AI is trained to immediately suggest hanging up and dialing 911 directly rather than transferring.

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

Build and integration steps

1. Identify every line, DID, extension, or virtual user that can dial 911.
2. Register a service address for each line with your carrier's emergency calling product.
3. For mobile or remote agents, implement a session-start prompt to confirm or update location.
4. Test 911 by calling 933 (Twilio) or your carrier's test ANI/ALI service to confirm correct delivery.
5. Implement the Kari's Law notification — typically a Slack message, email, or page to a central staff member when 911 is dialed.
6. Document the location-update process for staff who relocate.
7. Train your AI receptionist to escalate to "please hang up and dial 911" if a caller describes a life-threatening emergency.
8. Annually audit the address-of-record for every line in your inventory.

Code or config snippet

<!-- TwiML: route 911 to Twilio Emergency Calling and notify on-call contact -->
<Response>
 <Dial
 callerId="{{ from }}"
 answerOnBridge="true">
 <Sim>911</Sim>
 </Dial>
 <Sms
 to="+15555559911"
 action="https://api.callsphere.ai/twilio/karis-law-ack">
 EMERGENCY: 911 dialed from {{ from }} at {{ timestamp }}.
 </Sms>
</Response>

FAQ

Does the AI agent itself need an emergency address? The number the AI answers on does. The AI is software; it does not need a physical address, but the public-facing number tied to it does.

What if a caller mentions an emergency to the AI? Train the agent to instruct the caller to hang up and dial 911. Do not have the AI dial 911 on the caller's behalf — it confuses ANI/ALI and may not reach the correct PSAP.

Are virtual numbers (Google Voice, etc.) E911-compliant? Some are, some are not. Check the provider's emergency calling documentation explicitly.

Does Kari's Law require notification by SMS? The law requires notification to a "central location" when reachable; SMS, email, page, or a console alert all qualify.

Is E911 different in Canada or the EU? Yes. Canada has its own NG911 transition; the EU uses 112 with country-specific rules. International deployments must build per-country.

Sources

• Genesys Documentation: E911 Emergency Dialing Solution Guide
• Telnyx: E911 Requirements for VoIP
• Pure IP: E911 Compliance Explained for Enterprise VoIP
• Mitel: Dynamic E911

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