If an employee in your office dialed 911 right now, what would the dispatcher see on screen? Your validated street address plus the caller's floor and room — or just your company's main number with no usable location at all? If you are not certain, you have a problem that is both a safety risk and a federal compliance violation. Since 2022, every business phone system in the United States has been required to send a pinpoint location with each 911 call, and the FCC is actively enforcing the rules.
Two federal laws set these obligations: Kari's Law and Section 506 of the RAY BAUM'S Act. They apply to multi-line telephone systems of every size, including the cloud VoIP setup a ten-person company buys in an afternoon. Here is what each law requires, how the remote-work era complicated compliance, and an eight-step checklist to get your system in order.
Why These Laws Exist
In 2013, a nine-year-old girl in a Texas motel room tried four times to call 911 while her mother was attacked in the next room. Every call failed, because the motel's phone system required dialing 9 for an outside line — something a panicked child could not know. Congress named the resulting federal law for the mother. The lesson for your business is blunt: any phone system that puts extra digits, codes, or steps between a caller and 911 can cost lives, and it is now illegal to install or operate one that does.
Does This Apply to Your Business?
Probably yes. Both laws apply to a multi-line telephone system, or MLTS, which the FCC defines broadly: common control units, telephone sets, control hardware and software, and adjunct systems — including network- and premises-based systems such as Centrex and VoIP, as well as PBX, hybrid, and key telephone systems. The definition expressly covers systems owned or leased by for-profit businesses, nonprofits, and government agencies alike.
In practical terms, you operate an MLTS if your business uses any of the following:
- A cloud VoIP service with multiple extensions (RingCentral, Nextiva, Dialpad, and similar)
- A hosted or on-premises PBX (3CX, FreePBX, Asterisk, Mitel, Cisco)
- A unified-communications platform carrying voice calls (Microsoft Teams Phone, Zoom Phone)
- An older key system or Centrex lines still hanging on in the back room
There is no small-business exemption. A common misconception among small companies is that these rules target hotels, hospitals, and campuses. They do cover those — but they also cover your twelve-desk office, because from the dispatcher's perspective a 911 call with no location is equally useless wherever it originates.
One nuance: Kari's Law obligations attach to systems manufactured, imported, sold, leased, or installed after February 16, 2020. But any upgrade, alteration, or new software on an older system pulls it into compliance, so a legacy system you have touched in the last several years is almost certainly covered.
What Kari's Law Requires
Kari's Law took effect for covered systems on February 16, 2020, and has three core requirements.
1. Direct 911 dialing with no prefix
Every phone on the system must be able to reach 911 by dialing 911 — no 9 prefix, no 8 prefix, no access code. Even if your system normally requires dialing 9 for an outside line, 911 must work both ways: callers who dial 9-911 out of habit should still get through, and callers who dial plain 911 must never hit a fast busy or an error. Test both patterns.
2. On-site notification when 911 is dialed
The system must send a notification to a central point your business designates — a front desk, a security office, or in a small company, the owner or office manager's email and mobile phone. The point is to let someone on site meet responders at the door and guide them to the caller. The notification must go out without delaying the 911 call itself, and the FCC has made clear it cannot be used to intercept or screen emergency calls.
3. No blocking or extra steps
911 calls cannot be blocked, and the system cannot demand anything extra — no account codes, no login, no dialing sequence beyond the three digits. If any phone in your building needs any of that to complete an emergency call, the configuration is noncompliant.
What the RAY BAUM'S Act Adds: Dispatchable Location
Kari's Law gets the call out the door. Section 506 of the RAY BAUM'S Act — the Repack Airwaves Yielding Better Access for Users of Modern Services Act — makes sure responders know where to go. Every 911 call from your system must carry a dispatchable location: the validated street address of the caller plus additional information such as suite, floor, room, or building number sufficient to identify the caller's location.
How granular that must be depends on your premises. A single-floor donut shop may satisfy the rule with just its street address, because responders arriving at the door can see the whole space. A three-floor office, a warehouse with a mezzanine, or a multi-suite floor needs floor and room or suite detail — otherwise dispatchers send crews to a street address and leave them searching.
Compliance deadlines have all passed, so these are live obligations today:
| Device type | Example | Deadline |
|---|---|---|
| On-premises fixed phones | Desk sets, wall phones, conference-room phones | January 6, 2021 |
| On-premises non-fixed devices | Softphones on laptops, Wi-Fi handsets that roam the building | January 6, 2022 |
| Off-premises devices | Home-office desk phones, softphones used anywhere | January 6, 2022 |
For non-fixed and off-premises devices, the rule applies where technically feasible; where it is not, the business must provide either an end-user-manually-updated dispatchable location or alternative location information, such as coordinate-based data sufficient to identify the civic address and approximate in-building location. In plain terms: automatic per-device location is the standard, a disciplined manual-update process is the fallback, and having nothing is not an option.
The Remote-Worker Wrinkle
The hardest part of compliance in 2026 is not the office — it is the employee working from a kitchen table two states away. VoIP numbers are portable by design: a softphone registered to your Chicago office works identically from an apartment in Austin, and without nomadic 911 handling, a 911 call from that softphone routes to a Chicago dispatcher who sees a Chicago address. That misroute can delay help by many minutes.
Handle it with a combination of technology and policy:
- Turn on your provider's nomadic or dynamic E911 features. Most business VoIP platforms can prompt softphone users to confirm or enter their current address, detect network changes, and update the registered location automatically. If your plan or provider lacks this, that is a reason to switch, not a reason to skip it.
- Require address updates as a condition of remote work. Your remote-work policy should obligate employees to keep their 911 address current in the phone app or portal and to update it before working from a new location.
- Cover take-home desk phones. A physical IP phone an employee carries home is an off-premises device the moment it plugs into a residential router. Either register its new address or restrict those phones to office use.
- Mind the callback number. The FCC requires a callback number with 911 calls so a dispatcher who gets disconnected can ring the caller back directly. Make sure yours routes to the person who called, not to an auto-attendant or a general voicemail box.
What Noncompliance Costs
The FCC enforces both laws under the forfeiture provisions of the Communications Act, with penalties of up to $10,000 per violation — and each day a violation continues can count separately. Industry attorneys describe enforcement as ramping up now that every deadline is years in the rearview mirror; the grace-period mindset is over.
FCC fines are only the first layer of exposure. If a 911 call fails or misroutes because your system was noncompliant and someone is harmed, your business faces civil litigation over injuries a compliant system might have prevented. And the federal rules are a floor, not a ceiling: many states have their own MLTS 911 statutes and administrative codes, some predating the federal laws, which can add registration, testing, or recordkeeping duties. Check your state's public-utility commission or 911 administrator for overlays that apply to you.
Set against that exposure, compliance is cheap. Business E911 service typically costs a few dollars per number per month, direct-dial configuration is a setting rather than a purchase, and notification is usually a built-in feature waiting to be pointed at an email address.
Your 8-Step Compliance Checklist
Work through these in order. Most small businesses can finish in an afternoon with their VoIP provider's support team on the line.
1. Inventory every voice endpoint
List every desk phone, softphone seat, conference phone, and take-home device, where it physically sits, and which extension or direct number it uses. Note which ones ever leave the office. This inventory is the foundation everything else builds on.
2. Confirm direct 911 dialing in your dial plan
Verify in your PBX or provider portal that 911 routes to emergency services with no prefix, and that 9-911 still completes for callers who dial it from habit. Do this by inspecting the configuration — never by placing live 911 test calls.
3. Configure on-site notification
Point 911 notifications at a monitored destination: the front desk during business hours plus the owner or manager's email and SMS as backup. Place a test call to your provider's test facility or coordinate with your local dispatch center's non-emergency line to confirm the alert fires.
4. Register dispatchable locations per zone
In your provider's E911 portal, register the validated street address for each location, then add floor, suite, or room detail per zone as your building size requires. Larger offices typically assign one emergency location number per floor or wing so each phone's 911 calls carry the right zone.
5. Set up nomadic 911 for remote users
Enable address-prompt and dynamic-location features for every softphone and take-home phone. Send every remote employee a one-page instruction for updating their 911 address, and add the update step to your onboarding and move checklists.
6. Verify callback numbers
Confirm that the callback number transmitted with each 911 call reaches the actual caller. Ring each one during your testing window and fix any that land on attendants, queues, or dead extensions.
7. Test safely — dial 933, not 911
Most E911 providers support dialing 933, which connects to an automated test line that plays back your registered address without involving dispatchers. Dial 933 from each zone, confirm the playback matches the phone's real location, and verify routing to the correct dispatch center. For full end-to-end verification, call your local dispatch center's non-emergency number, explain you are testing business E911, and schedule a supervised test. Never dial 911 casually to test — it ties up emergency resources and can be illegal.
8. Document and retest on a schedule
Save your endpoint inventory, registered addresses, notification settings, and dated test results with your compliance records. Then retest quarterly and after every office move, renovation, provider change, or phone-system upgrade — moves and upgrades are the two events most likely to silently break a working configuration.
Keep Compliance Costs Visible in Your Books
E911 fees, per-number surcharges, provider upgrades, and the afternoon you spend testing are all ordinary costs of running a compliant business — which means they belong in your books as deliberately tracked compliance expenses, not buried in a generic phone bill. Break them out in your chart of accounts so you can see what each location costs to keep compliant, and file your location inventory and dated 933 test logs alongside your other compliance records. If the FCC or a state regulator ever asks questions, a tidy paper trail showing registered addresses, notification settings, and quarterly test dates is the difference between a quick resolution and a painful one.
Simplify Your Financial Management
As you work through 911 compliance for your phone system, maintaining clear financial records for every location is essential. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
