Kari's Law and RAY BAUM'S Act require business phone systems installed after February 16, 2020, including cloud VoIP, to allow direct 911 dialing, notify a designated person when 911 is called, and send a dispatchable location. Direct dialing means no prefix like "9", and a "dispatchable location" is a validated street address plus floor, suite or room. Under the FCC's multi-line telephone system rules, whoever manages the phone system is presumed responsible when those requirements are not met.
The rest of this page explains the rules as written in the FCC's regulations (47 CFR Part 9) as of October 2026, who is on the hook, how remote workers fit in, and what to configure. It is general information, not legal advice. If you run a hotel, hospital, school or a large campus, or you are in a dispute over who is responsible, talk to a telecom attorney.
What are the VoIP E911 requirements for businesses?
Two federal laws, both passed in 2018, sit behind the current rules. The FCC adopted rules implementing both of them in August 2019 (FCC 19-76), and they live in 47 CFR Part 9, Subpart F for multi-line telephone systems and 47 CFR 9.11 for interconnected VoIP providers.
| Requirement | What it means in practice | Rule | Compliance date |
|---|---|---|---|
| Direct dialing (Kari's Law) | Dialing 911 from any phone on the system reaches 911. No "9", no access code, no prefix. | 47 CFR 9.16(a)(1), (b)(1) | Systems manufactured, sold, leased or installed after Feb. 16, 2020 |
| Notification (Kari's Law) | The system alerts a front desk, security desk or designated person when someone dials 911, if the system can do it without new hardware or software. | 47 CFR 9.16(b)(2) | Same as above |
| Dispatchable location, on-premises fixed phones (RAY BAUM'S Act) | Desk phones on your premises automatically send a validated address plus floor, suite or room. | 47 CFR 9.16(b)(3)(i) | Jan. 6, 2021 |
| Dispatchable location, on-premises non-fixed devices | Softphones, Wi-Fi handsets and laptops on your premises send automated dispatchable location if technically feasible, otherwise a user-updated location or "alternative location information". | 47 CFR 9.16(b)(3)(ii) | Jan. 6, 2022 |
| Dispatchable location, off-premises devices | Remote and traveling users send automated dispatchable location if technically feasible, otherwise a user-updated location or the best available location. | 47 CFR 9.16(b)(3)(iii) | Jan. 6, 2022 |
| Interconnected VoIP provider E911 | The provider must deliver every 911 call with a callback number and location, cannot let customers opt out, and must warn customers about E911 limits. | 47 CFR 9.11(b) | Jan. 6, 2021 (fixed service), Jan. 6, 2022 (non-fixed service) |
Does Kari's Law apply to cloud VoIP phone systems?
Yes. The FCC's definition of a multi-line telephone system (MLTS) in 47 CFR 9.3 explicitly includes "network and premises based systems, such as Centrex and VoIP, as well as PBX, Hybrid, and Key Telephone Systems", and it covers systems owned or leased by businesses, government agencies and nonprofits. A hosted phone system from a UCaaS provider with 12 extensions is an MLTS just as much as an on-site PBX in a closet.
The rules are forward-looking. Under 47 CFR 9.15 and 9.17(b), they apply to any MLTS that is manufactured, imported, offered for first sale or lease, first sold or leased, or installed after February 16, 2020. A system installed on or before that date is not covered by the federal rules. If your cloud phone account was set up or moved to a new platform after that date, plan on it being covered.
What about an older system you have upgraded since? The FCC declined to set a bright line. In its 2019 order (FCC 19-76, paragraph 105) it said minor improvements do not automatically trigger the rules and that it would address the question for a specific fact pattern if one came up. If you are replacing the phone system, assume the new one must comply.
If you are still learning how cloud calling routes calls compared with a landline, our explainer on how VoIP works covers why a VoIP number has no fixed physical address, which is the root of the location problem these rules address.
What does Kari's Law require for direct 911 dialing?
Every station "equipped with dialing facilities" must be able to reach 911 without dialing any additional digit, code, prefix or post-fix, "including any trunk-access code such as the digit 9" (47 U.S.C. 623 and 47 CFR 9.16). This applies even if users must dial 9 for every other outside call.
You are allowed to keep extra dialing patterns. The FCC's definition of "pre-configured" says a system can also accept something like 9-911, but only in addition to plain 911, never instead of it. The law is named for Kari Hunt, who was killed in a Texas motel room in 2013 while her 9-year-old daughter tried to call 911 four times from the room phone, which required dialing 9 first, according to the FCC.
On a cloud system this is usually handled in the provider's dial plan or emergency calling settings. The risk is highest in custom setups: a self-managed IP PBX on SIP trunks, an old outbound route that only matches 9 followed by digits, or a phone that was provisioned by hand.
Who has to be notified when someone dials 911?
Whoever installs, manages or operates the system must configure it to notify "a central location at the facility where the system is installed or to another person or organization regardless of location", as long as the system can do so without a hardware or software improvement (47 CFR 9.16(b)(2)). Per the FCC's definition of "MLTS notification" in 47 CFR 9.3, the notice must include at minimum:
- The fact that a 911 call has been made.
- A valid callback number.
- The location information the system sent to the 911 center with the call.
The callback number and location can be left out only when including them is technically infeasible. The notice must be sent at the same time as the 911 call when technically feasible, it must not delay the call, and it must go somewhere someone is likely to see or hear it. The FCC lists examples: an on-screen alert with an audible alarm on a security desk computer, a text message to a smartphone, or an email to administrators.
Who should receive it? The FCC did not mandate a specific recipient, but in its order (paragraph 39) it called it a best practice to notify whoever "has the keys" to a building with restricted access, and whoever knows the building layout. For a 30-person office that is usually the office manager plus one backup, not a shared inbox nobody watches after 5 p.m.
What is a dispatchable location under RAY BAUM'S Act?
The FCC defines dispatchable location in 47 CFR 9.3 as "the validated street address of the calling party, plus additional information such as suite, apartment or similar information necessary to adequately identify the location of the calling party." The FCC's own summary describes it as "the street address, floor level, and room number of the 911 caller."
"Validated" matters. The address has to match what the 911 system recognizes. Platforms such as Microsoft Teams and Zoom Phone check an entered address against a mapping or validation service before it can be used, and Zoom's documentation notes that the "Address Line 2" field is where building, floor, wing and room details go.
The requirement depends on the kind of device, because a desk phone that never moves is easier to locate than a laptop that leaves the building:
| Device type | Example | What must be sent with a 911 call | Deadline |
|---|---|---|---|
| On-premises, fixed | Desk phone plugged in at your office | Automated dispatchable location | Jan. 6, 2021 |
| On-premises, non-fixed | Softphone on a laptop, Wi-Fi handset, mobile app on the office network | Automated dispatchable location if technically feasible. Otherwise dispatchable location from a manual update by the user, or alternative location information (which may be coordinate-based, but must identify the civic address and approximate in-building location, including floor in large buildings) | Jan. 6, 2022 |
| Off-premises | Softphone at home, desk phone taken to a home office, mobile app on the road | Automated dispatchable location if technically feasible. Otherwise dispatchable location from a manual update by the user, or enhanced location information (the best available location obtainable at reasonable cost, which may be coordinate-based) | Jan. 6, 2022 |
"On-premises" has a specific meaning: within the fixed property (buildings, facilities or campus) under the operational control of a single administrative authority (47 CFR 9.3). A coworking space you do not control, a client's office or an employee's apartment counts as off-premises.
What must a VoIP provider do for E911?
Separate from the MLTS rules, 47 CFR 9.11(b) puts E911 obligations on providers of interconnected VoIP service (VoIP that connects to the regular phone network). According to the rule and the FCC's consumer guide on VoIP and 911 service, the provider must:
- Provide E911 to every customer as a standard feature. Customers cannot opt out.
- Send every 911 call, the callback number and the location to the 911 center that serves the caller's location.
- For fixed service, send automated dispatchable location.
- For non-fixed service, send automated dispatchable location if technically feasible. Otherwise use a Registered Location collected before service starts, give users a way to update it from the device itself, and detect when a 911 call comes from somewhere other than the Registered Location so the user is prompted (or the location is updated automatically). Alternative location information or routing to a national emergency call center are also allowed fallbacks.
- Tell every subscriber in plain language when E911 may not work (relocated equipment, internet or power failure, non-native numbers, delays in updating location), keep a record of each subscriber's acknowledgment, and provide warning labels or another conspicuous notice.
That last point is why your provider's admin portal asks you to accept an E911 disclosure and why some desk phones arrive with a sticker. It is also a reminder that VoIP phones need power and internet to call 911. The FCC's consumer guide suggests a backup power supply, a traditional line or a mobile phone as a backup. That is advice, not a rule. The FCC's former backup-power rule (the old 47 CFR 9.20) only ever covered residential service, and the FCC removed it in its 2026 "Delete, Delete, Delete" rulemaking.
Is the VoIP provider or the business responsible for E911?
The rules assign duties by role, not by company type. One company can hold more than one role.
| Role (47 CFR 9.3) | Who it usually is | Main duties |
|---|---|---|
| Manufacturer, importer, seller or lessor | Phone system vendor, hardware maker, reseller | Ship systems pre-configured for direct 911 dialing and capable of sending dispatchable location |
| Installer | Whoever configures the system and sets the emergency dial pattern and routing | Configure direct dialing, notification and the ability to send dispatchable location |
| Manager | Whoever controls the system after installation: adds or moves lines, assigns numbers, manages configuration | Keep direct dialing and notification working and make sure dispatchable location is sent. Presumed responsible for violations |
| Operator | Whoever runs the system day to day | Same as manager |
| Interconnected VoIP provider | Your phone service carrier | E911 call delivery, location, customer warnings (47 CFR 9.11) |
The key rule is 47 CFR 9.17(a)(2): when a system fails to comply with the installer, manager and operator obligations, "the person engaged in the business of managing the multi-line telephone system shall be presumed to be responsible." That presumption can be rebutted by showing you met your obligations, and the FCC said it will look at the facts case by case, including contracts, which are relevant but not determinative.
The FCC gave a concrete example in its 2019 order (paragraph 92). When a carrier sells a hosted phone system and its service includes installation and management functions, the carrier is responsible for those functions. When a carrier only sells SIP trunks and the customer runs its own PBX, the customer is the operator and manager. The FCC also noted (paragraph 94) that customers often do part of the job themselves, such as updating user locations and choosing where notifications go.
For a typical small business on a cloud phone system, that means: the provider supplies a system that can comply, but if your admin adds users, assigns numbers and sets emergency addresses in the portal, you are doing manager work, and a missing address or a notification sent to a former employee is likely your problem. Ask your provider in writing which of these tasks it performs for you. Our guide on how to choose a VoIP provider includes E911 questions to raise before you sign.
Do remote VoIP users need an E911 address?
Remote work is where most E911 setups break. When an employee calls 911 from a softphone at home, the phone system often has no way to know where that laptop is. The FCC acknowledged this in its order (paragraph 159), citing industry comments that a user on a VPN appears to be at the company's end of the tunnel, so the location sent can be the office, not the employee's house. That is why off-premises devices have a "technically feasible" standard with fallbacks.
Your practical options, from best to weakest:
- Automatic location from the network. Map your offices' subnets, Wi-Fi access points (BSSIDs) and switch ports to addresses so the system can detect where a device is. Microsoft documents this for Teams, where the client matches in order of Wi-Fi access point, switch port, switch and subnet. This works well in offices you control and does not reach employees' homes on its own.
- User-confirmed location. Let remote users enter and confirm their address in the app, and have the app prompt them when it detects a new network. Zoom and other platforms let admins allow users to manage their own emergency addresses.
- Best available location. Where neither is possible, the rule accepts the best available location from any technology at reasonable cost, which may be coordinate-based.
Two settings to check. First, notification still applies to remote users: the FCC said notifications have value "regardless of location", for example someone at headquarters can alert people near a remote employee. Second, some clients do not support dynamic emergency calling at all. Microsoft's documentation says the Teams web client does not support dynamic emergency calling or security desk notification and recommends blocking PSTN calls from the web client. Our guide to mobile VoIP apps for business covers how the major apps handle location on phones.
How to set up VoIP E911 in practice
- Inventory every way to place a call. Desk phones, conference phones, softphones, mobile apps, fax lines and analog adapters. Note which are fixed, which move, and which leave the building.
- Check the dial plan. Confirm that 911 works with no prefix from every device type, and that any legacy 9-911 pattern exists only as an extra.
- Enter validated addresses with in-building detail. One emergency address per floor, suite or wing, not one per company. A 4-floor office needs at least 4 locations.
- Map network identifiers. For each office, map subnets, access points or switch ports to the right floor or zone so non-fixed devices pick up location automatically.
- Turn on notification. Send it to at least two people or a staffed desk, by a channel they will notice (SMS or an on-screen alert, plus email). Include after-hours coverage.
- Set up remote users. Require each remote employee to register and confirm a home address, and turn on prompts when the app detects a new network.
- Test with 933 from each device type and location (see below).
- Write it down. Keep a short record of addresses, notification recipients, test dates and results. If you ever need to rebut the manager presumption, records help.
- Repeat on every move, add or change. New hires, office moves, new floors and staff departures are when addresses and notification lists go stale.
- Tell employees. Explain that they dial 911 directly, that softphones need a correct address, and that VoIP does not work during a power or internet outage.
How do you test VoIP 911 without calling 911?
Many US emergency routing providers offer a test number, 933, that answers with an automated message reading back the caller ID and the emergency address associated with the call. Telnyx's documentation states that a 933 call "does not dispatch emergency services" and that if the address read back is wrong, the test failed and you should fix the configuration before relying on it. Microsoft says Calling Plan, Operator Connect and Teams Phone Mobile users in the US and Canada can use 933, while Direct Routing customers should ask their emergency routing provider for a test service. Zoom documents 933 for Zoom Phone in the US and Canada and says it also validates notification delivery.
933 is a provider service, not an FCC requirement, so confirm with your provider that it is supported on your account. Do not place live 911 test calls for routine checks. Telnyx says live 911 calls should only happen in a real emergency or when the appropriate authority instructs you, and the FCC's order cites the Michigan State 911 Committee's recommendation to work with the local 911 authority when testing after an installation or upgrade.
What are the penalties for violating Kari's Law?
Kari's Law is enforced under Title V of the Communications Act, "except that section 501 applies only to the extent that such section provides for the punishment of a fine" (47 U.S.C. 623(e), repeated in 47 CFR 9.17(a)(1)). In plain terms, the FCC can fine you, and the FCC's order notes that this language rules out imprisonment.
The rules themselves do not set a dollar amount. The FCC's general forfeiture rule, 47 CFR 1.80, sets inflation-adjusted maximums. For a party that is not a common carrier, broadcaster or cable operator, the catch-all cap in 47 CFR 1.80(b)(10) is $25,132 per violation or per day of a continuing violation, up to $188,491 for a single continuing violation, according to the eCFR text current in October 2026. Common carriers face higher caps. The FCC also adjusts these numbers for inflation, so check the current figures.
There is a procedural step that many vendor articles leave out. Under 47 U.S.C. 503(b)(5), the FCC generally cannot fine a party that holds no FCC license or authorization unless it first sends that party a citation, offers an interview, and the party then repeats the violation. A typical business that only manages its own phone system usually holds no FCC license, so a first problem would normally lead to a citation, not a fine. The citation step does not apply to parties that hold an FCC license or other authorization, or have applied for one.
On enforcement history: as of October 2026, we found no published FCC fine against a business specifically for violating the MLTS 911 rules. Treat any article that describes a specific fine without linking the FCC release with suspicion. In July 2025 the FCC's Public Safety and Homeland Security Bureau announced a renewed outreach initiative to "raise awareness and improve compliance", and the FCC's MLTS page says it "will closely monitor any complaints". Anyone can file a complaint through the FCC Consumer Complaint Center, and 47 CFR 9.17(a)(3) sets out the complaint procedure.
Two more things to know. States keep their own authority over emergency communications where it does not conflict with federal law (47 U.S.C. 623(d)), so check with your state 911 office for additional rules, especially for older systems the federal rules do not cover. And in September 2026 the FCC released a draft Notice of Inquiry on modernizing its 911 framework (PS Docket No. 26-197). A notice of inquiry asks questions. It does not change the current MLTS rules.
Beyond fines, the bigger exposure is practical: a 911 call that reaches the wrong dispatch center or arrives with no floor number costs response time. That risk is the reason to do this well, regardless of how often the FCC enforces.
What are the most common VoIP E911 mistakes?
- One address for the whole company. A street address without floor or suite is not a dispatchable location for a multi-floor building.
- Notification to a dead end. An email to a former office manager, or a shared inbox nobody reads at night.
- Remote users on the office address. A softphone at an employee's home in another city that still reports headquarters.
- Assuming the provider handles everything. The provider supplies the capability. If your team adds users and sets addresses, you are performing manager functions.
- Web clients and unsupported devices. Calling from a browser client or a device without location support while dynamic location is assumed.
- Never testing. Settings drift after moves, adds and changes. A 933 test takes a minute.
VoIP E911 compliance checklist
- 911 works with no prefix from every desk phone, softphone, mobile app and conference phone.
- Any 9-911 pattern exists only in addition to 911.
- Every office location has validated emergency addresses down to floor, suite or room.
- Office subnets, Wi-Fi access points or switch ports are mapped to those locations.
- Remote users have registered and confirmed their current address, and the app prompts them when they move.
- 911 notification goes to at least two people or a staffed desk, with callback number and location included.
- Web or unsupported clients are blocked from placing outside calls, or users know not to use them for 911.
- Each device type and location has passed a 933 test, and results are recorded.
- Your contract or written confirmation says which E911 tasks the provider performs and which you do.
- Employees know that VoIP 911 needs power and internet and know the backup option.
- The setup is reviewed at every office move, reorganization and at least once a year.
E911 is one part of running a business phone system responsibly. For the security side, see our guide to VoIP security, and for how calling fits into a wider platform, see unified communications explained.
Choosing a phone system? See the main providers' current plans side by side.
Compare VoIP providers →Frequently asked questions
Does Kari's Law apply to small businesses?
Yes, if the business uses a multi-line telephone system that was manufactured, sold, leased or installed after February 16, 2020. There is no size exemption in the rule, and the FCC's definition of a multi-line telephone system includes cloud VoIP systems. A business with a handful of extensions on a hosted phone system is covered.
What is the difference between Kari's Law and RAY BAUM'S Act?
Kari's Law requires direct 911 dialing without a prefix and notification to someone when a 911 call is made. Section 506 of RAY BAUM'S Act led to FCC rules requiring 911 calls to carry a dispatchable location, meaning a validated street address plus details like floor or suite. Both are implemented in the FCC rules at 47 CFR 9.16.
Who is responsible for E911 compliance, the VoIP provider or the business?
Responsibility depends on who performs each function. Under 47 CFR 9.17, the party that manages the phone system is presumed responsible for violations, and the FCC decides case by case. If your provider installs and manages a hosted system for you, it carries those duties, but if your own admin adds users and sets emergency addresses, your business is doing manager work.
Do remote employees need an E911 address?
Yes. Since January 6, 2022, off-premises devices must send automated dispatchable location when technically feasible, and otherwise a location the user updates manually or the best available location. In practice, remote employees should register and confirm their home address in the phone app and update it when they work from somewhere else.
How can I test 911 on a VoIP phone without calling 911?
Many US emergency routing providers support 933, a test number that reads back the caller ID and emergency address for the line without dispatching anyone. Check with your provider that 933 is enabled on your account. Do not place live 911 test calls unless your local 911 authority or provider tells you to.
What is the fine for violating Kari's Law?
The rules do not set a specific amount. The FCC enforces Kari's Law with fines under the Communications Act, and its forfeiture rule (47 CFR 1.80) caps fines for non-carriers at $25,132 per violation or per day, up to $188,491 per continuing violation, as of October 2026. A business that holds no FCC license generally receives a citation before any fine.
Sources
- 47 CFR Part 9, Subpart F (9.15, 9.16, 9.17): Multi-Line Telephone Systems, eCFR
- 47 CFR 9.3: Definitions (dispatchable location, MLTS, MLTS notification, on-premises, manager, operator), eCFR
- 47 CFR 9.11: E911 service for interconnected VoIP providers, eCFR
- 47 CFR 1.80: Forfeiture proceedings and inflation-adjusted maximums, eCFR
- Federal Register, 91 FR 1400 (Jan. 14, 2026): Delete, Delete, Delete (removal of obsolete public safety rules, including the residential backup-power rule)
- 47 U.S.C. 623: Kari's Law (Cornell LII)
- 47 U.S.C. 503: Forfeitures, including the citation requirement in (b)(5) (Cornell LII)
- FCC: Multi-line Telephone Systems, Kari's Law and RAY BAUM'S Act requirements
- FCC 19-76: Report and Order implementing Kari's Law and Section 506 of RAY BAUM'S Act (August 2019)
- FCC blog: Multi-Line Telephone Systems: Can You Connect to 911? (July 28, 2025)
- FCC consumer guide: VoIP and 911 Service
- FCC fact sheet and draft Notice of Inquiry: Modernizing the 911 Framework, PS Docket No. 26-197 (September 2026)
- Microsoft Learn: Configure dynamic emergency calling in Teams
- Zoom: U.S. regulatory requirements, Kari's Law and RAY BAUM'S Act (Zoom Phone)
- Telnyx: How do I test E911 service?
