Most businesses think about their phone system in terms of features — call quality, mobile apps, CRM integrations. Almost none of them think about it in terms of federal law. But there’s a compliance requirement built directly into how every business phone system in the country is legally required to function, and it exists because of a tragedy that could have been prevented by something as simple as a dial tone.
The Story Behind the Law
In 2013, a 9-year-old girl in a Marshall, Texas motel room tried to call 911 for help four times as her mother was being attacked. The call never went through because she didn’t know the motel’s phone system required dialing “9” for an outside line before dialing 911. Her mother, Kari Hunt, died. Congress responded by passing Kari’s Law in 2018, which the FCC then adopted rules to implement in August 2019, according to the FCC’s guidance on 911 requirements for multi-line telephone systems. What started as one family’s devastating loss became a binding federal requirement for every business phone system in the country.
What the Law Actually Requires
Kari’s Law is direct about what’s required: a business may not install, manage, or operate a multi-line telephone system in the United States unless that system is configured so a user can directly initiate a call to 911 from any station, without dialing any additional digit, code, prefix, or postfix — including a trunk-access code like the number 9 — regardless of whether that digit is otherwise required for other calls, according to the FCC’s MLTS 911 requirements. The law also requires that when a 911 call is made from within a facility, a notification goes to a central location or designated person at that facility, so someone on-site knows an emergency is happening and can help direct first responders when they arrive.
This applies to essentially any multi-line phone system used in an office, hotel, hospital, or campus setting — which means any business using a standard office phone setup with multiple extensions is subject to these requirements, whether or not anyone at that business has ever read the law itself.
Why This Got More Complicated in 2021
A second federal law added another layer to this requirement. RAY BAUM’S Act, which took effect in phases starting January 2021, requires that dispatchable location information be conveyed with every 911 call — meaning enough detail for emergency responders to find the caller’s exact location, not just the building’s general address, according to 911.gov’s overview of Kari’s Law and RAY BAUM’S Act requirements. Dispatchable location generally means the validated street address plus additional detail — a suite, floor, or room number — necessary to actually find the person calling, not just the building they’re in.
This distinction matters enormously in practice. A 911 call from a 40-person office building that only transmits the building’s street address gives first responders almost nothing to work with if they need to find someone on the fourth floor versus the first. The requirement to convey more precise location information exists specifically because “the building” isn’t a useful answer when every second matters.
Why This Compliance Gap Goes Unnoticed
Most businesses that switch phone providers, move offices, or expand to new locations focus entirely on the features and cost of their new system — call routing, mobile apps, integrations. Whether that new configuration still meets Kari’s Law and RAY BAUM’S Act requirements is rarely part of the conversation, because it’s not something most businesses know to ask about. A phone system can look and function perfectly for every normal business purpose while quietly failing to meet a federal emergency-calling requirement that nobody at the business has any reason to test until an actual emergency occurs.
This is precisely the kind of gap that a knowledgeable phone systems for business provider is expected to close automatically — configuring direct 911 dialing, setting up internal notification, and maintaining accurate location data — rather than leaving compliance entirely in the hands of a business that has no particular reason to know these requirements exist. When evaluating phone systems for business, this is one of the few features that genuinely can’t be treated as optional or something to configure “later,” since the entire point of the requirement is that it has to work correctly before it’s ever actually needed.
What This Looks Like in Practice
A few practical questions reveal whether a business phone system is actually meeting these requirements:
Can any phone on the system dial 911 directly, with no prefix required? This should work the same way regardless of whether a “9” is normally needed to reach an outside line.
Does a 911 call trigger an internal notification to a designated person or location? Front desk staff, security, or a facilities manager should know immediately when a 911 call is placed from within the building.
Does the system convey a precise enough location for emergency responders to actually find the caller? A general building address isn’t sufficient for a large office, especially across multiple floors or suites.
Has this been tested, not just assumed? A system that was compliant when installed years ago may not still meet current requirements if the business has moved, expanded, or changed configurations since.
What This Means Going Forward
Most compliance requirements businesses deal with are administrative — paperwork, filings, documentation. This one is different, because the entire purpose of the law is to make sure a system nobody thinks about in ordinary circumstances works exactly right in the one circumstance where failure has irreversible consequences. A business phone system that handles calls flawlessly every single day but fails to connect a 911 call correctly hasn’t just missed a feature — it’s failed at the one function the law specifically exists to guarantee.
That’s the real reason this compliance requirement deserves more attention than it typically gets. It’s invisible until the moment it matters most, and by then, there’s no opportunity to fix it. See More