If you run a UCaaS platform or provide a hosted PBX service, E911 compliance is not optional. It is a federal requirement, and failing to comply can lead to serious legal and financial consequences. However, many VoIP operators still assume that because they route calls through carriers, E911 compliance is handled by someone else. 

That assumption is incorrect. Regulators have made it clear that UCaaS providers, hosted PBX operators, MSPs, and other VoIP service providers have their own compliance responsibilities, regardless of the carriers they use. Since Kari’s Law became effective in 2018 and RAY BAUM’S Act introduced dispatchable location requirements in 2021, the compliance requirements for VoIP services have become much stricter. 

Did You Know? Every year, over 10,000 lives are lost due to delays and failures in 911 response, often because emergency dispatchers cannot quickly access accurate caller location information from mobile and VoIP calls. 

This blog explains what the regulations require, where providers commonly fall short, and what a compliant E911 for UCaaS platforms and hosted PBX 911 compliance strategy looks like in practice. 

What Is E911 and How It Differs from Basic 911

Standard 911 simply routes an emergency call to the nearest Public Safety Answering Point (PSAP). While the call reaches emergency services, it may not automatically provide the caller’s location or a reliable callback number. 

Enhanced 911 (E911) improves emergency response by delivering two critical pieces of information along with the call: the caller’s callback number, known as Automatic Number Identification (ANI), and the caller’s physical location, known as Automatic Location Identification (ALI). This information helps dispatchers quickly identify where help is needed and contact the caller if the call is disconnected. 

For traditional landline systems, maintaining accurate location information was relatively simple because phone numbers were tied to fixed addresses. However, VoIP, UCaaS, and hosted PBX environments are far more dynamic. An employee may use the same extension from an office, a home workspace, or a temporary location while traveling. As a result, emergency calling for hosted PBX and UCaaS platforms requires mechanisms that can accurately track, update, and transmit location information for every 911 call, regardless of where the user is connected. 

The FCC’s current standard requires dispatchable location, which means providing a caller’s physical address along with additional details such as the floor, suite, apartment, or room number when applicable. For businesses operating in multi-story or multi-tenant buildings, a street address alone is not sufficient. Emergency responders must be able to identify the caller’s precise location within the building to meet compliance requirements and ensure a faster response. 

The Regulatory Framework: RAY BAUM’S Act and Kari’s Law

For VoIP providers, UCaaS operators, and hosted PBX service providers, E911 compliance is primarily defined by two federal laws: Kari’s Law and RAY BAUM’S Act. Together, these regulations establish the minimum requirements for emergency calling in modern business communication systems. 

Kari’s Law (Effective 2018)

Kari’s Law was enacted following the tragic death of Kari Hunt in a Texas hotel. During the incident, her daughter attempted to call 911 from a hotel phone but was unable to connect because the system required dialing “9” to access an outside line. The delay prevented the emergency call from reaching responders. 

To prevent similar incidents, Kari’s Law requires: 

  • Direct 911 dialing without any prefix or access code from any Multi-Line Telephone System (MLTS). 
  • On-site notifications to designated personnel, such as security staff, receptionists, or front desk operators, whenever a 911 call is placed. 
  • Compliance for systems with two or more lines, which includes virtually all hosted PBX and UCaaS platform deployments. 

RAY BAUM’S Act (Phase II Effective 2021)

While Kari’s Law focuses on call accessibility, RAY BAUM’S Act focuses on caller location accuracy. The law requires providers to transmit a dispatchable location with every 911 call, enabling emergency responders to locate the caller quickly and accurately. 

Phase II requirements include: 

  • Fixed devices: The installed or assigned location must be provided. 
  • Non-fixed devices: Softphones, mobile apps, and other portable endpoints must provide either dynamically determined location information or a manually validated address. 
  • Remote and off-premises users: Providers must support accurate location reporting for employees working from home, temporary offices, or other remote locations. 

This requirement presents one of the biggest compliance challenges for providers implementing E911 for remote workers, as users can move between locations while retaining the same extension or device. 

Together, Kari’s Law and RAY BAUM’S Act make it clear that simply routing a 911 call is no longer enough. Providers must ensure that emergency calls can be placed easily and that accurate, dispatchable location information accompanies every call to emergency services. 

E911 Compliance Requirements for UCaaS Platforms

E911 for UCaaS platforms is more complex than traditional phone systems because users are mobile and may work from multiple locations. 

At the platform level, UCaaS operators must address the following: 

Dynamic Location Capture

When a user logs in or registers a device, the platform must capture or update their physical location. This can be done through: 

  • Network-based location using the user’s IP address and mapping it to a physical location through emergency location databases. 
  • User-confirmed location, asking users to confirm or enter their current address when logging in from a new location. 
  • Integration with an Emergency Location Identification Number (ELIN) database. 

Routing to the Correct PSAP

A 911 call must be routed to the PSAP serving the caller’s current location, not their billing address or home office. This requires integration with a 911 routing provider (such as Bandwidth, West Safety Services, or Intrado) that maintains PSAP routing tables based on location. 

Dispatchable Location Transmission

The location data sent to the PSAP must be dispatchable: 

  • For a corporate office: building address, floor, and room number. 
  • For a home worker: full residential address. 

On-Site Notification

UCaaS platforms serving multi-tenant or enterprise clients must support on-site notifications as required by Kari’s Law. Notifications are typically sent through a desk phone, intercom, or a separate alert system connected to the platform. 

Running a UCaaS or hosted PBX platform? 

 iCallify supports E911 and STIR/SHAKEN at the operator level. 

Book a platform demo to see how compliance is built into the operator dashboard. 

Hosted PBX 911 Compliance: What Changes at the Operator Level 

Hosted PBX 911 compliance differs from UCaaS because most users are based in fixed office locations. Businesses typically use hosted PBX to replace on-site phone systems, with employees making calls from office desks. 

However, compliance is not necessarily simpler. Multi-floor buildings, co-working spaces, and hybrid work arrangements can create location challenges that operators must address. 

For hosted PBX operators, compliance requirements include: 

Registered Address Accuracy

Each extension must have a validated emergency service address on file. The address must route to the correct PSAP and cannot simply be the billing address. 

Extension-Level Location Granularity

In buildings with multiple floors, suites, or departments, each extension or user group may require its own location record to ensure accurate emergency response. 

Remote Worker Handling

If employees work from home or travel frequently, the platform must provide a way to update their emergency locations and keep records current. 

Carrier Integration

Operators must ensure their carrier or 911 routing provider maintains accurate ALI records for all registered locations. This requires ongoing data management and synchronization between systems. 

How VoIP Providers Implement E911 for Business Clients

The question operators ask most often is: who owns the E911 implementation? Is it the carrier, the platform vendor, or the operator? 

In most cases, the operator is responsible. FCC obligations apply to the organization providing the MLTS service to the end user. If you offer hosted PBX or UCaaS services to businesses, compliance responsibility falls on you. 

Here’s how VoIP providers implement E911 for business clients: 

Step 1: Choose a 911 Routing Provider

Operators need a dedicated 911 routing provider, which may be separate from the voice carrier. Providers such as Bandwidth, Intrado, and West Safety Services maintain PSAP routing databases based on location.

When a 911 call is placed, the platform sends the caller’s number and location to the routing provider, which directs the call to the correct PSAP. 

Step 2: Build or Configure Location Data Capture

The platform must have a process for collecting and storing valid emergency locations for each user or extension. 

  • For fixed devices, location setup is usually completed once per site. 
  • For non-fixed devices such as softphones and mobile apps, users should be prompted to update their location when needed. 

Step 3: Provision ALI Records

Automatic Location Identification (ALI) records must be provisioned in the 911 routing provider’s database. 

When a 911 call is made, the provider retrieves the caller’s ALI record and sends it to the PSAP. Outdated or inaccurate ALI records are among the most common E911 compliance issues. 

Step 4: Test End-to-End

Operators should regularly test their E911 implementation to ensure calls route correctly and location information is delivered properly. 

Testing is often done through tools and frameworks provided by the 911 routing provider, without requiring a live PSAP connection. 

Step 5: Document and Maintain

E911 compliance is an ongoing process, not a one-time setup. 

As customers add users, relocate offices, or change configurations, ALI records and emergency location data must be updated. Operators should maintain clear internal procedures to keep records accurate and compliant. 

Common Gaps That Create Compliance Risk

Most E911 compliance VoIP operators problems aren’t about intent. Operators generally want to comply with regulations, but gaps often arise from operational processes or platform design.

The most common compliance risks include: 

  • Stale ALI records: When a client moves offices or a remote employee changes location, the ALI record may not be updated. As a result, a 911 call could be routed to the wrong PSAP or fail to reach the correct emergency services. 
  • Softphone and app coverage gaps: Many operators configure E911 for desk phones but overlook mobile softphones and communication apps. Since these tools are often the primary calling method for users, they must also be covered by E911 processes. 
  • No on-site notification: Kari’s Law requires on-site notification when a 911 call is made. This requirement is sometimes missed, especially in multi-tenant environments where the business client manages the office location. 
  • Incorrect PSAP routing for non-US locations: Operators with international customers may assume that US E911 compliance applies globally. However, emergency calling requirements vary by country, and each region may have different routing and location requirements. 
  • Missing compliance documentation: During FCC audits, operators must demonstrate their E911 compliance procedures. Even if the technical implementation is correct, a lack of documented processes can result in compliance issues or penalties.

How iCallify Supports E911 and STIR/SHAKEN Compliance

iCallify is designed for operators running UCaaS and hosted PBX services at scale. E911 compliance is built into the platform and managed through an operator-level configuration framework. 

At the operator level, iCallify supports: 

E911 Carrier Integration

iCallify integrates with major US 911 routing providers, allowing operators to configure emergency call routing directly from the operator dashboard instead of managing it solely through the carrier. 

Per-Tenant Location Management

Each tenant within the multi-tenant platform can maintain its own emergency service addresses. The platform also supports extension-level granularity for organizations with multiple floors, suites, or departments. 

STIR/SHAKEN Support

iCallify includes built-in STIR/SHAKEN support for call authentication. This helps operators meet FCC requirements related to caller identity verification while supporting broader VoIP compliance efforts. 

Also Read: What Is STIR/SHAKEN? How It Works and Why It Matters 

SMS Provider Support

The platform supports integration with standard SMS providers, enabling compliance-related services such as 911 text messaging where available and supported by local emergency systems. 

Simplified Compliance Management

Operators using iCallify do not need to build their E911 compliance for VoIP setup from scratch. The platform provides the necessary configuration tools through the operator dashboard, and the consulting team can assist with deployments, market expansion, and migration from non-compliant legacy systems.

Conclusion:

E911 compliance is a critical responsibility for any operator offering hosted PBX service, UCaaS platform, or other MLTS services. Regulations such as Kari’s Law and RAY BAUM’s Act have made it clear that operators must ensure 911 calls are routed correctly, provide accurate dispatchable location information, and support required notification processes. 

While the technical requirements such as PSAP routing, ALI record management, and location tracking are well established, compliance is an ongoing process. Changes in office locations, remote work arrangements, and device usage can quickly create gaps if emergency location data is not actively maintained. 

The most successful operators treat E911 compliance as part of their day-to-day operations rather than a one-time deployment task. With the right platform, processes, and carrier integrations in place, meeting compliance requirements becomes far more manageable while helping ensure emergency calls reach the right responders when they matter most.

If you’re evaluating your current E911 strategy or planning to scale your UCaaS or hosted PBX business, now is a good time to review your compliance framework and identify any gaps before they become operational or regulatory risks.