Blog

Picture this: an employee collapses in the break room. A coworker grabs the nearest desk phone and dials 911. But instead of sending help to the right floor, in the right building, on the right street, the emergency dispatcher sees an address from company headquarters three states away. Those lost minutes could mean the difference between life and death.

This isn’t a hypothetical. It’s a real risk for any business running a VoIP or cloud-based phone system without properly tested E911 configuration. The good news? A little proactive E911 testing can close that gap entirely — and it’s a lot simpler than most business owners assume.

In this guide, we’ll break down exactly how to test E911, walk through the steps of testing your business phone system, cover what E911 compliance actually requires, and share practical tips for a successful 911 test call. By the end, you’ll know exactly how to protect your team and keep your business on the right side of the law.

Why E911 Testing Isn’t Optional

Traditional landlines had one job: connect a phone number to a fixed address. Simple. But VoIP changed everything. Employees now call from desk phones, softphones, mobile apps, and laptops — sometimes from a different floor, a different building, or a different city than where the phone system is registered.

That flexibility is fantastic for productivity. It’s dangerous for emergency response if location data isn’t accurate. A misrouted 911 call doesn’t just delay help — it can send responders to the wrong place entirely while precious minutes tick by.

That’s exactly why Kari’s Law and the RAY BAUM’s Act exist. Kari’s Law requires that any multi-line telephone system allow employees to dial 911 directly, without needing to dial a prefix like “9” first, and that it automatically notify a designated person on-site (like security or the front desk) when a 911 call is placed. RAY BAUM’s Act goes a step further, requiring that the dispatch center receive a “dispatchable location” — meaning specific enough detail (floor, suite, room number) to send help to the exact spot, not just the building’s general address.

Together, these laws aren’t just red tape. They’re the reason E911 compliance matters for every business, regardless of size or industry. And compliance isn’t a “set it and forget it” checkbox — it requires ongoing verification, which is where testing comes in.

What Happens If You Skip Testing?

Skipping E911 testing is a gamble most businesses can’t afford to lose. Here’s what’s on the line:

• Delayed emergency response. Inaccurate location data means dispatchers waste critical time trying to figure out where to send help.
• Legal and regulatory penalties. Non-compliance with Kari’s Law or RAY BAUM’s Act can result in fines and legal liability, especially if an incident occurs and the system failed to perform as required.
• Reputational damage. Beyond the legal risk, failing to protect employees during an emergency erodes trust — both internally and publicly.
• False confidence. Perhaps the biggest danger is assuming your system works simply because it was configured correctly at setup. Phone systems change. Employees move desks. New locations get added. Without testing, you won’t know something’s broken until it’s too late.

How to Test E911: Step-by-Step

Ready to verify your system actually does what it’s supposed to? Here’s how to test E911 on your business phone system the right way.

Step 1: Notify Your Local PSAP Before Testing

Never place a live test call to 911 without warning. Contact your local Public Safety Answering Point (PSAP) ahead of time to let them know you’re conducting a scheduled test. Many providers, including Cebod Telecom, also offer dedicated E911 test call numbers that simulate the process without tying up emergency dispatch lines — always check if this option is available first.

Step 2: Verify Registered Addresses for Every Endpoint

Before you even pick up the phone, confirm that every device — desk phones, softphones, mobile extensions, remote workers’ setups — has an accurate, up-to-date registered address in your system. This is especially critical for multi-floor offices, satellite locations, and remote or hybrid teams.

Step 3: Place a Test Call from Each Location Type

Don’t just test one device and call it done. Test from:

• A standard desk phone in the main office
• A softphone or desktop app
• A mobile extension
• Any remote or work-from-home setups

Each connection type can pull location data differently, so testing broadly ensures nothing slips through the cracks.

Step 4: Confirm the Dispatchable Location Received

During the test, verify that the address transmitted to the PSAP includes the specific floor, suite, or room number — not just the building’s street address. This is the core requirement of RAY BAUM’s Act, and it’s the detail most likely to be wrong if your system hasn’t been configured carefully.

Step 5: Check On-Site Notification Alerts

Kari’s Law requires an automatic internal alert whenever a 911 call is placed — typically to front desk staff, security, or a facilities manager. During your test, confirm this notification actually fires and reaches the right person in real time.

Step 6: Document Everything

Keep a record of each test: the date, the device tested, the location transmitted, and whether the on-site notification worked correctly. This documentation isn’t just good practice — it’s often required for compliance audits.

Step 7: Repeat Regularly

E911 testing isn’t a one-and-done task. Test after any office move, phone system update, new hire onboarding for remote staff, or expansion to a new location. A good rule of thumb: schedule a full system test at least twice a year, with spot checks after any major change.

Tips for a Successful 911 Test Call

Want your testing process to go off without a hitch? Keep these tips in mind:

Always use a dedicated test line when possible. Providers like Cebod Telecom often offer specific numbers designed to simulate the 911 process without alerting live dispatchers, saving everyone time and avoiding unnecessary strain on emergency resources.

Loop in IT and facilities teams together. Location accuracy depends on both the technical configuration and the physical reality of your office layout. Cross-checking between departments catches errors that either team might miss alone.

Test after every office change. New desks, new floors, new remote hires — any change to where people physically work should trigger a fresh round of testing.

Set calendar reminders. E911 testing is easy to forget when nothing’s gone wrong. Build it into your routine IT maintenance schedule so it doesn’t fall through the cracks.

Train employees on what to expect. Make sure staff know that dialing 911 will trigger an internal alert, so they’re not caught off guard, and so designated responders know to act quickly when that notification comes through.

Partner with a provider that prioritizes E911 compliance. Not all VoIP providers handle E911 configuration and testing support the same way. Choosing a partner who builds compliance into the system from day one takes a huge burden off your internal team.

Stay Protected, Stay Compliant

E911 testing might not be the most glamorous item on your IT checklist, but it’s one of the most important. A phone system that looks fully functional on paper can still fail when it matters most if it hasn’t been properly tested. By following these steps and building routine testing into your operations, you’re not just checking a compliance box — you’re protecting the people who count on your business every day.

At Cebod Telecom, we build E911compliance and dispatchable location accuracy directly into our business phone systems, so you can test with confidence and respond when it counts. Ready to make sure your system is truly emergency-ready? Reach out to our team to schedule a compliance review today.