Business VoIP E911: The Location Checklist Every Office Needs

Published October 25, 2026 · Last updated October 25, 2026

Every business VoIP E911 plan has to answer three questions. Can an employee reach 911 by dialing three digits and nothing else? What location goes to the 911 center when they do? And who fixes that location the day someone moves to a different desk? If your office cannot answer all three from a document rather than from memory, this checklist is for you.

Local Business VoIP is the small-business site of Carolina Digital Phone, Inc. We hold a NENA Company Identifier, we deliver room-level location with every 911 call on our platform, and we still find that most of the E911 work on a new system is not technical. It is keeping a list accurate. This guide is written for the office manager, practice administrator or town clerk who ends up owning that list, with the legal background kept short and the working steps kept long. A companion piece on the company site, Business VoIP Emergency Calling: E911 Setup and Location Planning, covers the same ground from the IT director's seat.

Which E911 rules apply to which part of your phone system?

Two sets, and they land on different parties. Interconnected VoIP service is the part that connects internet calling to ordinary telephone numbers, and its emergency-calling obligations fall on the service provider. Multi-line telephone system rules, the ones people call Kari's Law and RAY BAUM'S Act, address the manufacturers, sellers, installers, managers and operators of the system, which means they land on your organization. A hosted deployment involves both. Buying the service does not settle every configuration question, and that is the mistake most offices make.

The MLTS provisions apply to systems manufactured, imported, first sold or leased, or installed after February 16, 2020. Establish your system's installation history instead of assuming the oldest handset on a desk decides it. A 2017 phone plugged into a system installed in 2024 is covered.

Kari's Law and RAY BAUM'S Act solve two different problems. Kari's Law is about reaching dispatch: 911 must work with no outside-line prefix, and someone on site must be notified. RAY BAUM'S Act is about being found: a dispatchable location has to travel with the call. The National 911 Program's overview of both laws is the plain-language reference, and the FCC's MLTS 911 requirements page carries the rule text.

What are the six steps to an E911 plan that stays accurate?

1. Sort out which rules apply to which part of your phonesYour hosted provider carries the interconnected VoIP obligations. Your organization carries the multi-line telephone system (MLTS) obligations for any system installed after February 16, 2020. Write down the installation date and which rules each party owns before anything else.
2. Walk the building and name every emergency-calling locationWith facilities staff, agree on building, floor and room names that match the signs a responder can see. Ask of every spot: could someone find this caller without first finding our receptionist?
3. Build the location registerOne row per distinct location: validated street address, building, floor, suite or room, the devices and app logins tied to it, the callback number, the administrator responsible and the date of the last confirmed review. Keep it separate from the billing address and the extension list.
4. Assign the handoff before you change serviceName who enters locations, who maps extensions and app users to them, who approves changes and what evidence closes a change. Before signing, have the provider demonstrate the emergency-calling path for one desk phone, one shared phone and one remote user.
5. Treat every move as a location-change ticketRecord the endpoint, old location, new location and move time; submit the new location through the provider's method; record acceptance and activation timing; verify the mapping after the move and close the ticket with the result. Reconcile the whole register quarterly.
6. Test dialing, notification and callback together, safelyConfirm 911 dials without a prefix, the on-site alert reaches a named recipient and backup for every site and shift, and the callback number works. Arrange live tests through the 911 center's non-emergency number, never by dialing 911 to see what happens.

How do you build E911 records around physical locations instead of phone numbers?

You start from the building, not from the extension list. For fixed interconnected VoIP service, automated dispatchable location is required. For non-fixed service, such as a softphone on a laptop, it is required when technically feasible, with specified alternatives otherwise: registered-location procedures, alternative location information or routing to a national emergency call center. Ask your provider which method its service actually uses for each kind of device you have, and write the answer down.

Then create the location register. One entry per distinct emergency-calling location, with these fields: validated street address, building, floor, suite or room, the devices and app logins tied to it, the callback number a dispatcher would reach, the administrator responsible and the date of the last confirmed review. Keep the billing address out of it. Keep the general extension list out of it too. The register is its own deliverable, and the moment it gets buried in a spreadsheet of extensions it stops being maintained.

The test for enough detail is a practical one: could a responder find this caller without first locating your receptionist? A campus address alone leaves several buildings to search. "Building C" means nothing if the sign on the door says "Annex." Walk the site with facilities staff and agree on building and room names that match what people can read on the wall. Our hands-on guide to assigning dispatchable E911 locations walks the property with you, and the schools E911 guide shows what the register looks like for a campus.

Do not assume every extension needs its own public number. Ask the provider to explain how each endpoint maps to the location sent with an emergency call and how a dispatcher calls back. A shared phone in a break room or a conference room behaves differently from an employee's own extension; document the shared-device behavior separately.

Who hands off E911 responsibility when you change phone service?

Whoever you name before the contract is signed, and nobody if you do not. If your organization keeps its own PBX and buys SIP trunks, separate carrier routing from PBX configuration in the project plan and ask three questions: who enters locations, who maps extensions to them and who approves changes. If you are moving to a fully hosted system, the same three questions apply; the answers just shift more toward the provider.

Put a named business owner beside each task, even when a contractor does the work. A useful handoff identifies the requested change, the person making it and the evidence needed to close it. Before signing a proposal, request a walkthrough of one desk phone, one shared phone and one remote user's emergency-calling path. Ask what happens when location is unavailable, how updates become active and how failed address submissions are surfaced to you. Those questions turn E911 planning into a deployment specification rather than a line in a brochure. Our office phone onboarding checklist has a place for every one of these names, and the migration guide shows where E911 sits in the larger project.

What should happen to E911 data when people move?

Treat every phone move as a location-change ticket, even when the extension stays the same. The National 911 Program's VoIP guidance tells owners to update the provider when a VoIP phone moves. Build that handoff into office relocations, classroom changes and temporary work areas, because those are exactly the moments when nobody is thinking about 911.

For home workers and employees who travel between branches, request a demonstration of location detection, the prompts the user sees on a new network and how manual updates work in the proposed app. Ask what happens through a VPN, which can make a laptop in Asheboro look like it is in the Greensboro office. Keep a user's home address visible only to staff who need it for administration. The remote and hybrid phone checklist covers the rest of the remote-user setup.

Two dates are worth knowing so you do not mistake them for upcoming milestones. Covered fixed on-premises devices had a January 6, 2021 dispatchable-location deadline. Non-fixed on-premises and off-premises devices had a January 6, 2022 deadline, with permitted alternatives where automation is not technically feasible. Those are past requirements. If your system is covered and not yet compliant, you are catching up, not planning ahead.

How much administrative work is this, really?

Less than most offices fear, if you size it honestly. Count endpoints and user setups, not legal locations; several phones can share one location while a single roaming laptop needs its own movement process. A business with three branches, 24 desk phones each and 18 remote-user setups has 72 desk phones plus 18 app users, so 90 endpoint or user records to review. If six phones move this month, that is six change tickets this month, not a note to deal with it at the next quarterly review.

How do you test E911 dialing, notification and callback without causing a problem?

You test all three at once, through the 911 center's front door rather than its emergency line. For a covered system, direct dialing must work without a prefix. Notification is required when it can be configured without a hardware or software upgrade; it must not delay the call, and it must go somewhere a person is likely to notice. Contemporaneous notification, at the same moment as the call, is required where technically feasible.

Assign an alert recipient and a backup for each site and each shift. Have them show you how they would read the caller's location from the alert and meet arriving responders at the right door. Keep alert handling separate from permission to call: no employee should wait for a supervisor's approval to dial 911, and no greeting or dial plan should ever get in the way.

Schedule live test calls through the local emergency communications center's non-emergency number, following its instructions. Never dial 911 just to see what happens. For an approved session, record the location the center received, the callback number it saw, whether direct dialing worked and whether the on-site alert fired. Ask the provider which non-emergency test tools it offers and what each one actually proves. Repeat the affected checks after any routing or location change. And include internet and power failure behavior in staff instructions, using the service's actual emergency-calling disclosures rather than a general assurance; our power outage guide explains what fails in which order.

North Carolina has an advantage here. All of the state's 911 centers now run on Next Generation 911, which can accept the richer location data a modern phone system sends. We explain what that means for a business caller in What Is Next Generation 911?, and the NC 911 Board publishes the contact information for each county center.

What does a local provider do differently with E911?

We walk the building with you. A national carrier gives you a portal where you can type an address. Carolina Digital Phone's onboarding engineers inventory every phone and app on site, help you name the locations the way the signs read, load the register, and come back when you expand onto another floor. Our platform sends the exact room, not just the street, backed by NENA Company Identifier "CDP" through our carrier partners, and our government and education team at (336) 543-0000 has done this for school districts and county offices across the state. That is the difference between an E911 feature and an E911 plan, and it is the reason the business owners on why Carolina Digital Phone and in our company history stay with us. Read a trusted business communications partner for how the rest of the relationship works.

Frequently asked questions about business VoIP E911