Hotels get discussed as the standard example of a multi-line telephone system, and the compliance conversation usually stops at the phone system as a result. Whether the PBX passes 911 through without a prefix is the easiest part of the obligation to check and the least likely to be the actual gap.
The parts that are more often unmet involve people and property records rather than telephony.
They are separate obligations, usually discussed as one, and a property can satisfy either while failing the other.
Kari's Lawis named for Kari Hunt, who was killed in a motel room in Marshall, Texas in 2013. Her nine-year-old daughter tried four times to call 911 from the room phone. No call connected, because the motel's system required dialing 9 for an outside line first. Congress enacted Kari's Law in 2018 and the requirements took effect on February 16, 2020. It imposes two obligations: a user must be able to dial 911 directly with no prefix or access code, and when that call is placed the system must notify a central location, on-site or off-site, where someone is likely to see or hear it.
Section 506 of RAY BAUM'S Act requires that a dispatchable location be conveyed with the call — a validated street address plus whatever additional detail is needed to actually find the caller, which in a hotel means room and floor. Fixed on-premises devices had to meet this by January 6, 2021; devices a user can move, such as cordless and conference units, by January 6, 2022.
Both statutes are forward-looking. They apply to systems manufactured, imported, offered for first sale or lease, first sold or leased, or installed after February 16, 2020. A property running genuinely untouched pre-2020 equipment sits differently under the rule — which is a narrower exemption than it sounds, because most properties have replaced or reconfigured something since. If that is your situation, whether the rule applies to you is worth establishing before anything else, and what each statute requires covers the distinction in more depth.
Most MLTS compliance guidance is written for offices. An office caller is an employee who knows the building, can describe where they are, and appears in a directory that maps to a desk.
None of that holds in a guest room.
A guest who dials 911 may have arrived hours earlier. They frequently cannot name the property, the street, or which building of a multi-building resort they are in. The dispatchable location transmitted with the call is not a convenience in this context — it is the only location information the call carries.
Room 412 is meaningful to your staff and meaningless to a Public Safety Answering Point unless the location database maps it to a civic address with floor and unit detail. That mapping is a data exercise, not a telephony one, and it is the piece most often either missing or stale.
In a franchised or managed-portfolio structure, the entity operating the telephone system holds the obligation — which is not always the entity whose name is on the building. This is worth establishing property by property in writing, because the assumption at corporate is usually that the franchisee handles it and the assumption at the property is usually the reverse.
Cisco at some properties, Avaya at others, a cloud platform at the newest builds. Each handles location differently. Reaching one compliance position across a mixed estate does not require unifying the platforms, and treating it as though it does turns a compliance program into a migration project.
Across a portfolio these compound, which is why property-by-property remediation never converges into a portfolio-level answer.
Direct dialing gets tested because it is easy to test. Anyone can pick up a room phone and check whether 911 connects without a 9.
The notification half of Kari's Law is different. It requires that someone be alerted, at a location where they will actually see or hear it, when a 911 call is placed from the property. In practice this means the front desk, security, or the duty manager — and it means a real, configured destination, not a capability the system theoretically supports.
Three failure modes recur:
Night audit is the shift where this matters and the shift with the fewest people to notice it is broken.
A property that was compliant at deployment does not stay compliant by default. Compliance decays through moves, adds and changes, and hotels generate more of those than most environments:
The pattern is consistent: the telephony work gets done and the location data work does not, because they usually sit with different people and only one of them appears on the project plan.
Work through this per property. It is deliberately answerable without specialist tooling — if you cannot answer one of these, that is the finding.
Item eight is the one that separates a property that believes it is compliant from a property that can demonstrate it.
Four questions, usually answered at corporate rather than at a property, tend to establish whether this is a compliance problem, an inventory problem, or an ownership problem — three engagements that look identical from a head office.
Does anyone hold a current inventory of which telephone system is deployed at which property? If not, the first phase is inventory, and scoping it as compliance work will not go well.
Which properties have changed or upgraded a phone system in the last five years, and did anyone re-verify location data afterwards? The second half of that question is where the gaps cluster.
For each franchised property, where does the obligation sit, and is that written down anywhere? Verbal understanding is common and does not survive an incident.
When a guest dials 911 from a room, who at the property is notified — and has that been tested this year? Not “can the system notify.” Who was notified, and when was it last verified.
An organization that can answer all four precisely usually needs a narrower engagement than it expected. An organization that cannot answer the first one is not behind — it is at a normal starting position, and discovering it during a deployment is the expensive version of finding out.
The multi-site assessment reviews every property under both statutes and produces per-property findings, including the location-data and notification gaps that a direct-dial test will not surface. It is free and there is no scoped project attached to it.
If you already know the gap and want it closed, E911 Compliance & Governance covers assessment, deployment, PSAP testing and the annual governance cycle across a portfolio under a single contract.
Regulatory detail in this article is drawn from the FCC's Multi-line Telephone Systems — Kari's Law and RAY BAUM'S Act requirements guidance. Statutory citations: Kari's Law Act of 2017; RAY BAUM'S Act §506; 47 C.F.R. Part 9, Subpart F.
Related
Why property-by-property remediation never converges, and what corporate-level scoping looks like.
E911 & MLTSWhat each statute requires, how they differ, and why dispatchable location is the obligation most organizations fail.
Professional & ManagedAssessed, deployed, PSAP-tested and governed annually across every site.
The multi-site assessment reviews every property under both statutes and produces per-property findings. It is free, with no scoped project attached.