E911 on a Cloud Phone System: The Obligations Most Businesses Miss
Emergency calling is the part of a phone system nobody tests and everybody assumes works. On a cloud platform, where a handset can be anywhere, several assumptions that held for a traditional system no longer do.
Two US laws set the requirements for multi-line telephone systems, and both apply to ordinary business installations.
Kari's Law: dial 911 directly, and tell someone
Named after a woman who died when repeated 911 calls from a hotel room failed because the system required a 9 prefix, Kari's Law requires that a multi-line phone system:
1. Allows 911 to be dialled directly — no prefix, no access code. If your system requires 9 for
an outside line, 911 must still reach emergency services on its own.
2. Sends a notification when 911 is dialled, to a location where someone is likely to see it — a front desk, a security office, a monitored email address or group chat. The notification must identify that a 911 call was made and where it came from.
The second requirement is the one most commonly missing. It exists so that someone on site knows to unlock a door, direct responders to the right floor, or begin first aid.
RAY BAUM'S Act: dispatchable location
Where Kari's Law governs how the call is placed, RAY BAUM'S Act governs what the emergency call centre receives. It requires a dispatchable location — enough information to actually find the caller.
In practice that means a street address plus the detail needed within a building: floor, suite, wing, room number. "1234 Market Street" is not dispatchable in a twelve-storey building.
This is where cloud systems get difficult, because the thing that made them attractive — a handset or app that works anywhere — breaks the assumption that a phone number maps to a fixed address.
The three hard cases
Fixed desk phones
The straightforward case. Each device is registered to a location, including the within-building detail, and that is what gets delivered. The failure mode is stale data: phones get moved between desks, floors and offices, and nobody updates the record.
Control: a documented process that updates the emergency location whenever a device moves, and a periodic audit comparing registered locations against reality.
Softphones and mobile apps
An app on a laptop can be at the office, at home, or in another state. Approaches vary by platform:
- prompting the user to confirm or set their current location
- detecting network location — a known office network maps to a known address
- using device location services where available and permitted
- defaulting to a registered home-office address for remote workers
Whatever the mechanism, the obligation does not disappear because the user is mobile. The practical requirement is that every user who can dial 911 from the system has a current, specific location associated with them.
Control: make location confirmation part of onboarding and of any change of work location. For permanently remote staff, record their home address as their emergency location and re-confirm periodically.
Remote and hybrid workers
The group most often overlooked, because they are not in a building anyone manages. If a remote employee dials 911 from the company softphone and the system delivers the head-office address, responders go to the wrong city.
Some organisations address this by disabling emergency calling on softphones and instructing staff to use their mobile — a defensible choice, provided it is a decision that is documented and communicated, not an accident.
What to actually verify
Do not take the platform's compliance page as evidence that your configuration is right. Check:
- Dial 911 from a test device — in coordination with your local emergency authority, or using a test number the provider offers for this purpose. Never dial 911 casually to test.
- Confirm the location delivered is the specific one, including floor and suite.
- Confirm the notification fires and reaches somewhere a person will see it, including out of hours.
- Walk the softphone path for an office worker, a home worker and a travelling worker.
- Check what happens when the internet is down. A cloud phone with no connectivity cannot place any call. Staff need to know the fallback is a mobile phone — and that expectation should be explicit, not assumed.
The administrative side
- Keep a location register. Device, user, address, within-building detail, last verified.
- Tie it to onboarding and offboarding. New device, new location, confirmed. Office move, bulk update.
- Review after any physical change — a new floor, a reorganised suite, a second site.
- Document the notification destination and who monitors it.
- Record your decisions about softphones, including any deliberate choice to disable emergency calling.
Why this deserves attention it usually does not get
Emergency calling has no normal failure mode. It works until the one occasion it matters, and the cost of it being wrong is measured in minutes of response time in a situation where minutes decide outcomes.
It is also one of the cheapest things on any compliance list to get right. The platform features exist; what is usually missing is the location register, the notification destination, and anyone having tested it end to end.
If you do nothing else after reading this: find out where a 911 notification from your phone system currently goes, and confirm that somebody is watching it.
