e911, Kari's Law, and RAY BAUM Compliance for AI Voice in 2026

An AI receptionist sits in front of an MLTS by definition. If the caller dials 911 from the office and the call routes through your AI first, you may have just blocked a 911 call. Kari's Law and RAY BAUM say you cannot, and the FCC has been enforcing both since 2020 and 2021 respectively.

What the rule says

flowchart LR
  UA[SIP UA] -- REGISTER --> Reg[Registrar]
  UA -- INVITE --> Proxy[SIP Proxy]
  Proxy --> Dispatcher[Kamailio dispatcher]
  Dispatcher --> Worker1[FreeSWITCH worker]
  Dispatcher --> Worker2[FreeSWITCH worker]
  Worker1 --> AI[(AI agent)]
  Worker2 --> AI

Kari's Law (Pub. L. 115-127, codified at 47 U.S.C. § 623), effective for MLTS manufactured, imported, sold, leased, or installed after February 16, 2020, requires multi-line telephone systems to enable direct 911 dialing without prefix or access code, and to send a notification (audible or visual) to a central on-site or off-site location when 911 is dialed. Section 506 of the RAY BAUM'S Act (Pub. L. 115-141), implemented by FCC rules effective January 6, 2021 (fixed) and January 6, 2022 (non-fixed/dispersed), requires that 911 calls from MLTS automatically convey a "dispatchable location" to the public safety answering point: street address, building, floor, suite, room, or other useful detail. The FCC's MLTS rules apply to enterprise systems serving office buildings, hotels, schools, and increasingly cloud-hosted PBX or AI-receptionist platforms that act as the front door.

What it means for AI voice agent operators

Three things matter for AI receptionists in 2026:

First, an AI receptionist must let 911 through, immediately and unconditionally. If a caller's first utterance is "I need 911" or the caller dials 911 from an internal extension, your routing must skip the AI and connect to PSAP. The FCC has not formally enforced against AI receptionists yet, but the underlying legal duty applies the moment your system is the MLTS.

Second, dispatchable location must travel with the call. For office deployments, this typically means each extension has a registered location (street address + suite/floor) in your carrier's e911 database, and the call carries the right ELIN (Emergency Location Identification Number) so the PSAP gets the precise address.

Third, notifications must fire when 911 is dialed. Kari's Law requires a notification (email, SMS, dashboard alert, console light) to a central location so on-site staff know help has been called and can guide first responders to the exact spot.

For AI voice agents specifically, the standard pattern is: detect 911 intent or dialed digits in the first 200ms, bypass the AI, hand the call directly to the trunk for PSAP routing with the appropriate ELIN, and fire a notification webhook to the customer's emergency contact.

How CallSphere stays compliant

CallSphere's voice routing layer detects 911 dial patterns and emergency-intent utterances ("call 911", "this is an emergency") at the front door. When detected, the AI receptionist immediately bridges the call to the carrier's PSAP routing using Twilio's Emergency API, attaches the registered ELIN for the caller's location, and fires a notification webhook to the customer's emergency contacts (configurable: email, SMS, Slack, PagerDuty). Healthcare AI deployments add a HIPAA-scoped audit log: every 911 event is logged with timestamp, caller line, location ELIN, notification confirmation. The platform supports multi-location customers (e.g., a Salon AI deployment across 3 locations) with per-location ELINs. Across 50+ businesses, 4.8/5 rating, and the 14-day trial, e911 setup is a one-time onboarding step with quarterly re-verification.

Compliance checklist

1. Configure direct 911 dialing without access code or prefix on every extension.
2. Register dispatchable location for every extension in the carrier's e911 database.
3. Use a unique ELIN per logical location (per floor, per suite, per office).
4. Fire a notification on every 911 dial event to a configured central party.
5. Test 911 routing in a controlled way (use the carrier's test ELIN where available; do not call live PSAP for testing).
6. Re-verify dispatchable location quarterly and after any address change.
7. Disclose to staff during onboarding that 911 dial events are logged and notified.
8. Keep an MLTS administrator contact on file with the carrier.
9. For BYOD remote workers, register their home address and update on relocation.
10. Document the e911 architecture in your SOC 2 and HIPAA control evidence.
11. Verify Kari's Law notification reaches a person, not a black-hole inbox; use a paging path.

FAQ

Does Kari's Law apply to a single-line AI receptionist? Kari's Law specifically governs MLTS. A single-line consumer AI does not trigger MLTS rules; an enterprise deployment with extensions does.

Can the AI ask "is this an emergency?" before connecting? Best practice: do not. Detect, bridge, and notify. Asking first adds latency that can cost lives and exposes you to liability.

What is an ELIN? Emergency Location Identification Number. A telephone number associated with a specific dispatchable location that PSAPs query to retrieve the address.

What if a remote worker moves? They must update their registered location in the e911 system. Most platforms (including CallSphere) prompt at login if the IP geolocation suggests a different location than registered.

What are the penalties? FCC enforcement actions for MLTS violations have run into the hundreds of thousands of dollars; the more serious risk is wrongful-death liability if an emergency call fails.

Sources

• FCC: Multi-line Telephone Systems — Kari's Law and RAY BAUM'S Act 911 Requirements
• 911.gov: Kari's Law and RAY BAUM'S Act
• Twilio: Emergency Calling Documentation

Start a 14-day trial, see pricing, or visit /industries/healthcare.