You've seen the term on a carrier invoice, in a Teams admin center setting, or in a compliance email from legal: E911. It sounds like 911 with a marketing letter attached. It isn't. The "E" changes what happens in the seconds after someone in your building dials for help and if you operate a business phone system, federal law almost certainly requires you to get it right.
This guide explains what E911 actually is, how it differs from basic 911 and Next Generation 911 (NG911), and what it means in practice for the person responsible for an enterprise phone system.
E911, defined
E911 Enhanced 911 is the system that automatically delivers a caller's location and callback number to the emergency call center (the PSAP, or Public Safety Answering Point) along with the call itself. Basic 911 connects a voice call and nothing more. Enhanced 911 connects the call and tells the dispatcher who is calling and where they are, even if the caller never says a word.
That distinction sounds small until you picture the calls where it matters: a caller who is choking, unconscious mid-call, hiding from a threat, or simply doesn't know the address of the building they work in. E911 exists because dispatchers can't send help to a location they don't have.
How E911 works behind the scenes
When a 911 call leaves your phone system, three things have to happen for the dispatcher to see accurate information on their screen:
- Routing. The call must reach the correct PSAP for the caller's physical location not the PSAP near your headquarters, your carrier's data center, or wherever your SIP trunk happens to terminate.
- Callback number. The call must present a number the dispatcher can dial back if the call drops a real, routable number, not an internal four-digit extension.
- Location delivery. The caller's location must be available to the dispatcher, historically via a lookup in the ALI (Automatic Location Identification) database keyed to the calling number, and increasingly delivered with the call itself.
For a home landline, all of this is trivial one number, one address. For a multi-line telephone system (MLTS) serving hundreds or thousands of phones across buildings, floors, and remote workers, none of it is automatic. The phone system knows a device's extension; it does not inherently know which floor of which building that device sits on today. Making the system location-aware is what enterprise E911 solutions do.
E911 vs. basic 911: what the dispatcher sees
With basic 911, the dispatcher gets a voice call and must ask: "911, what's the address of your emergency?" Everything depends on the caller's ability to answer. With E911, the dispatcher's screen already shows a location and callback number when they pick up. They verify instead of interrogate and if the caller can't speak, help still has somewhere to go.
Inside an enterprise, the quality of that location is where organizations differ. "1200 Corporate Parkway" is technically a location. "1200 Corporate Parkway, Building C, 3rd Floor, Room 312" is a dispatchable one. Federal law now cares about the difference, which brings us to the regulations.
The laws that make E911 mandatory for businesses
Two federal laws turned enterprise E911 from a best practice into a legal requirement for MLTS operators:
- Kari's Law (effective February 16, 2020) requires direct 911 dialing no "9" prefix, no access code and simultaneous on-site notification to a designated location or person whenever 911 is dialed.
- RAY BAUM's Act, Section 506 (phased in January 2021 for fixed devices and January 2022 for non-fixed and off-premises devices) requires that a dispatchable location the street address plus floor, suite, room, or similar detail be conveyed to the PSAP with every 911 call, including calls from softphones and remote workers.
Non-compliance carries FCC penalties that start at $10,000 per violation plus ongoing daily fines, alongside the civil liability that follows any emergency where help was delayed. If your organization runs Cisco Unified Call Manager, Microsoft Teams, or a hosted platform, these obligations belong to you as the MLTS operator not solely to your carrier or platform vendor.
E911 vs. NG911: don't confuse the two
NG911 (Next Generation 911) is often used interchangeably with E911, but they describe different things. E911 describes the capability location and callback delivered with the call. NG911 describes the infrastructure modernization happening on the public safety side: replacing decades-old analog and TDM networks with IP-based systems that can carry richer data, text, and eventually multimedia between callers and dispatchers.
For an enterprise, the practical takeaway is this: NG911 raises the ceiling on what information can travel with a 911 call, but it doesn't change your legal obligations and it doesn't populate your location data for you. An organization that hasn't solved E911 fundamentals won't be rescued by NG911; an organization that has is positioned to take advantage of everything the new infrastructure enables.
What E911 looks like in a modern enterprise
A complete enterprise E911 deployment typically includes location mapping for every device and network segment, automatic location updates as softphone users move, correct PSAP routing for every site including home offices, valid callback numbers on every call, and on-site notifications that reach the right people the moment 911 is dialed.
That last piece is evolving fastest. A notification that says only "someone dialed 911" satisfies Kari's Law but leaves your response team guessing. Newer capabilities like 9Line's Echo, which transcribes the 911 call in real time and alerts your team to what's actually happening are turning the compliance-mandated alert into genuine situational awareness. Compliance is the floor. What you build on top of it is what changes outcomes.
Common E911 questions
Does E911 apply to VoIP and Microsoft Teams? Yes. The obligations attach to the multi-line telephone system regardless of the underlying technology. A Teams Phone deployment, a Cisco Call Manager cluster, and a hosted BroadWorks seat all count and softphones on laptops are explicitly covered by the non-fixed device rules.
Isn't this my carrier's problem? Only partially. Carriers handle transport, but the location data, on-site notification, and dial-plan behavior live inside your phone system. The FCC's MLTS rules apply to those who manage and operate the system and in practice, the organization that configured the phones is the one answering the questions after a failure.
How do I test E911 without calling 911? Use 933 test calls where supported. Dialing 933 reads back the location and callback number your system would deliver on a real 911 call, letting you verify every site and every remote worker without touching a live dispatcher.
What's the penalty for getting it wrong? FCC forfeitures start at $10,000 per violation with additional daily penalties, and that's before civil liability. But the real cost of an E911 failure is measured in response time during an actual emergency which is why the law exists at all.
The bottom line
E911 is the difference between a 911 call that merely connects and one that arrives with the information dispatchers and on-site responders need to act. For enterprises, it's also federal law. If you can't say with confidence where every phone, softphone, and remote worker in your environment would appear on a dispatcher's screen right now, that's the gap to close before an emergency or an FCC inquiry closes it for you.
9Line makes E911 compliance simple: a cloud-based platform, no software installed on your machines, and pricing that doesn't punish you for taking safety seriously. Talk to us about where your environment stands.
