A 911 call from a classroom, hotel room, patient care area, or office should reach emergency services immediately, without requiring an outside-line prefix or operator assistance. That basic expectation is why organizations asking who needs Kari law compliance need to look beyond their phone carrier and examine how every calling endpoint is configured.
Kari’s Law is not limited to one industry or one kind of phone system. It affects multi-line telephone systems used across commercial, educational, hospitality, healthcare, and public-sector environments. For IT and facilities leaders, the practical issue is straightforward: if people can place calls through a shared organizational phone system, emergency calling must work as intended, and the people responsible for the system must be able to support that outcome.
Who Needs Kari Law Compliance?
Kari’s Law applies to multi-line telephone systems, commonly called MLTS. An MLTS is a phone system that serves multiple users and can route calls across more than one line, extension, device, or location. Traditional PBXs, key telephone systems, hosted VoIP platforms, cloud calling environments, and certain hybrid systems can all fall within this category.
The law places obligations on the parties that manufacture, import, sell, lease, or install MLTS equipment or services. In practice, responsibility is shared. The provider or installer must offer a system capable of compliant emergency calling, while the organization operating the system must ensure it is correctly deployed, configured, maintained, and tested.
That means compliance should be a concern for businesses of every size, school districts and higher education institutions, hotels and lodging properties, healthcare organizations, government entities, property managers, and organizations with distributed offices. A small business with a cloud phone system may have a simpler configuration than a hospital campus, but both need a reliable path for emergency calls.
Organizations with on-site staff, visitors, or residents
Any organization responsible for people in a physical facility should treat Kari’s Law as an operational requirement, not just a telecommunications requirement. Employees may know how to dial an outside line. Visitors, students, patients, guests, contractors, and new hires may not.
Hotels are a clear example. A guest facing an emergency should be able to dial 911 directly from a room telephone. The same principle applies to schools where students or staff may call from classroom phones, medical facilities with phones in patient areas, and office buildings with shared workspaces.
Multi-site and hybrid organizations
Compliance becomes more complex when an organization has multiple locations, remote workers, softphones, mobile clients, or a mix of legacy and cloud systems. A user may place a call from a desk phone one day and from a laptop application the next. The emergency response process needs to account for both scenarios.
For fixed endpoints, the organization should be able to associate the phone with a sufficiently specific location. For non-fixed devices, policies and technical capabilities must support current location information when emergency calls are placed. This is closely connected to the FCC’s rules under RAY BAUM’s Act, which address dispatchable location requirements.
Organizations replacing legacy phone services
A migration from PRI, analog lines, or an on-premises PBX to cloud voice is an ideal time to evaluate emergency calling. It is also a common point of failure. A new platform may support direct 911 dialing, but extensions, call routing, location records, alert recipients, and site-specific settings can still be incomplete after cutover.
POTS replacement projects deserve the same attention. Elevator phones, security panels, emergency call boxes, lobby phones, and other analog-dependent devices may have separate dialing behavior and location requirements. Treating them as an afterthought can leave a gap in an otherwise modern communications environment.
What Kari’s Law Requires From an MLTS
The core requirement is direct 911 dialing. A person using an MLTS must be able to reach 911 without first dialing a prefix, code, digit, or other number to access an outside line. If a system still requires users to dial 9 before outside calls, 911 must remain an exception.
Kari’s Law also requires a notification when a 911 call is made from an MLTS. The notification must be sent to an appropriate on-site or third-party location, such as security, a front desk, facilities operations, or a monitoring center. It should include the fact that a 911 call was placed and, when technically feasible, the caller’s location and callback number.
The purpose is practical. Emergency responders are on the way, but internal personnel can direct them to the correct building entrance, floor, room, or department. They can also provide immediate assistance before responders arrive.
Notification procedures should be designed around the organization, not treated as a generic feature. A small office may send alerts to a designated manager and an external monitoring service. A university may require campus police, dispatch, building security, and residence life staff to receive alerts based on the originating location. A hospital may need alerts routed to a security operations center that is staffed around the clock.
Kari’s Law Compliance Is More Than a Phone System Feature
A vendor can confirm that its platform supports 911 dialing and emergency notifications. That is necessary, but it is not the same as confirming your environment is compliant. Compliance depends on the entire implementation.
Start by identifying every system that can place a call. This includes desk phones, conference room phones, cordless handsets, lobby phones, elevator and emergency devices, softphone applications, contact center stations, and retained analog lines. Organizations often discover that an acquired office, a temporary trailer, or a facilities device was excluded from the original inventory.
Next, document how emergency calls leave each system. Determine whether calls route through a local carrier, SIP trunk, cloud provider, or separate analog line. Then confirm that direct 911 dialing works from each endpoint type. Testing should be coordinated carefully with the appropriate carrier, provider, or public safety answering point procedures. An unplanned test call can tie up emergency resources.
Location data deserves equal attention. A street address alone may not be enough for a large campus, high-rise building, warehouse, or multi-tenant property. Dispatchable location information should help responders identify where the caller can be found, such as a building, floor, suite, room, wing, or similar detail. The level of specificity that is appropriate depends on the site layout and applicable requirements.
Finally, verify notification routing and response ownership. An alert that goes to an unattended email inbox does little to support an emergency response. Identify who receives the notification during business hours, after hours, and during holidays. If the primary recipient is unavailable, there should be a defined escalation path.
Common Compliance Gaps to Watch For
The most persistent gaps are often caused by change, not neglect. A phone system may have been configured correctly when installed, then office moves, staffing changes, renovations, or software updates altered the environment.
Common issues include stale address records after a move, extensions assigned to the wrong suite or floor, notifications sent only to former employees, and softphone users without a process for updating their location. Another frequent issue is assuming that a new cloud phone deployment automatically covers all emergency devices. It may not, particularly where legacy analog equipment remains in service.
Organizations operating in regulated environments should also account for governance. Emergency calling configuration should have an owner, a documented review process, and evidence of testing. For government agencies, contractors, and other organizations with formal security controls, emergency communications documentation can support broader continuity, risk management, and compliance efforts.
A Practical Path to Ongoing Compliance
Kari’s Law compliance is not a one-time project. It is a lifecycle responsibility tied to facilities, workforce changes, and communications architecture. The strongest approach brings IT, facilities, security, operations, and the voice provider into the same planning process.
Before renewing a voice contract or beginning a migration, ask providers direct questions: Can every endpoint dial 911 without a prefix? How are emergency notifications configured? Can the system maintain detailed location information? How are remote and hybrid users handled? Who assists with testing, documentation, and changes after deployment?
For organizations with a mix of cloud, SIP, analog, and legacy services, a single accountable communications partner can simplify the work. Intuity helps organizations assess voice environments, replace aging services, and build calling configurations around reliability, compliance, and operational continuity.
The right outcome is not merely checking a compliance box. It is giving every person in your facility a clear, dependable way to call for help, while ensuring the people responsible for the building know exactly how to respond.