Rules
E911 rules for small business VoIP, explained for US employers
Voice connectivity under FCC E911 rules: what US employers must do for multi-line phone systems, dispatchable location, notification, and records.
What to take away
- If your office runs more than one phone line, 47 CFR 9.16 puts E911 duties on you, not only on your carrier.
- Since February 16, 2020, the system must allow 911 dialing with no prefix and notify someone on site.
- Dispatchable location phased in from January 6, 2021street address plus suite, floor or room.
- Remote staff need a registered location they update before calling from a new place, plus a second path to 911.
- Keep the configuration, location list, notification list and test logs for at least two years.
What 47 CFR 9.16 requires of a small employer
Multi-line telephone systems sit under 47 CFR 9.16. A cloud PBX with 12 extensions counts, and so does a hosted product with 400 seats across two states. The duties fall on whoever makes the system and whoever runs it, usually the employer.
Kari's Law set the first deadline. From February 16, 2020, a system installed, upgraded or sold after that date must let users reach 911 without dialing 9 first and without a hunt group delay. The same rules require a notification to a central point on site.
Dispatchable location arrived later. The commission phased it in from January 6, 2021 for fixed systems, and a year later for non-fixed ones.
[figure 1]
Multi-line E911 compliance checks
- 911 call reaches correct PSAP with usable location
- No dial 9 first, no extension prompt
- No auto attendant department menu
- Routing works during power cut or outage
- Backup pathanalog line, cellular, alarm
The rule text sits in 47 CFR Part 9, worth reading before a vendor says the carrier handles everything.
Your provider runs the 911 call path. You supply the address, the suite, the floor and the person who gets the alert. Who holds the phone number record decides who you call when that data is wrong.
The FCC's settlement with T-Mobile over a June 2020 outage, when 911 calls failed for hours, came to roughly $19.5 million.
Example: the address fields a dispatcher can use
47 CFR 9.5 defines dispatchable location as the street address plus anything else needed to find the caller, such as a suite number. Free text fails that test. Fixed fields pass it.
Address fields
- Site
- East Campus, Building B
- Street
- 500 Main Street
- Unit
- Suite 300, third floor
- Zone
- east wing, desk row 4
- City, state, ZIP
- Austin, TX 78701
Read the block aloud. If a colleague cannot repeat it back, a dispatcher under pressure will not either. Drop nicknames, because "The Annex" tells a dispatcher nothing.
[figure 2]
Dispatchable location by site type
Single office
- Location detail
- Street, suite
- How it reaches PSAP
- Call signaling
- Update trigger
- Suite change
Multi-building campus
- Location detail
- Building, floor, zone
- How it reaches PSAP
- Call signaling or non-emergency call
- Update trigger
- Desk move or floor change
Nomadic softphone
- Location detail
- Collected at sign-in
- How it reaches PSAP
- User-provided or device location
- Update trigger
- Travel or move
Multi-building sites need one entry per zone, with every phone assigned to the right entry. How E911 matches a call to a location explains why a stale record sends responders to the wrong building.
The 911 notification duty and a template to copy
The duty exists because a 911 call from a business phone often triggers no audible alarm. Someone can dial from a closed room and nobody else knows.
The notice must reach a central point on site, usually the front desk, the security console or a named manager. What gets touched in a panic is the inventory to keep beside those settings.
911 call placed, 14:02. Extension 214, Jane Doe, Suite 300, third floor, east wing. Front desk to meet responders at the Main Street lobby with the master badge.
Keep the template short. Include the extension, the floor and suite, the caller's name where the system shows it, and the time.
Name a backup and a second backup, because front desk turnover is high. A text, a screen pop or a ring on one handset all count, as long as a named person can act on it.
Remote and nomadic workers
Nomadic VoIP works from any internet connection, and your provider may not know where the handset is when 911 is dialed. The FCC's guide to VoIP and 911 service says the user may have to supply the location.
So the employer builds the process. The registered location matches where the phone sits today, and the user knows how to change it. A second path to 911 exists, such as a mobile phone with a known billing address.
Ask the vendor one question in writing: does the softphone use device location or the registered address? Checks that fix most mobile plan faults apply when a softphone is the only path and it stops working.
Records to keep, and for how long
Records are your defense if a 911 call fails. Keep the service agreement, the location list, the notification configuration, the test logs and the incident reports.
The FCC's forfeiture window runs one year from the violation under 47 U.S.C. 503(b)(6), so a two-year floor covers it. Some state rules require longer, so check with counsel before setting a destruction date.
Records to keep
| Record | Owner | Keep for |
|---|---|---|
| Service agreement and 911 addendum | Office manager | Life of contract plus 2 years |
| Dispatchable location list, current and prior | IT | Current plus 2 years |
| Notification configuration and call list | IT or security | Current plus 2 years |
| Test logs and provider tickets | IT | 2 years |
| Incident reports | Office manager | 2 years, or as counsel advises |
Testing without dialing 911
- Ask the PSAP for a test window on its non-emergency line before you change anything.
- Confirm the address the dispatcher sees, field by field, against the list on file.
- Trigger a notification and confirm that the named person received it.
- Repeat the test after any change to the system, the provider or the floor plan.
Never dial 911 as a test. If a real call fails, escalate to the provider in writing and keep the ticket number.
A failed test usually means a stale address, an empty notification list or a route aimed at the wrong PSAP.
Where FCC rules end and state rules begin
FCC rules are the floor. State commissions add registration, retention and notification duties on top, and the mix changes with the service address.
California is the clearest example. The state levies its own emergency telephone surcharge on VoIP lines, and the CPUC handles intrastate service complaints. Complaints filed with a state regulator show how far that route goes when a carrier stops answering.
Some states require annual certification for certain systems, and some cities add building code rules for address posting or radio coverage. Ask your provider which rules attach to each service address.
