Ask a nonprofit operations director about phone compliance and you will probably hear about call recording consent or TCPA texting rules. Almost no one mentions 911. That is a problem, because two federal laws have quietly reshaped what every multi-line phone system has to do when someone dials those three digits. If your organization runs a cloud phone system across an office, a satellite location, a shelter, a thrift store, or a remote staff base, you are on the hook.
The good news: compliance is mostly a configuration project, not a budget line. The bad news: most nonprofits we audit have at least one gap.
The Two Laws You Need to Know
Kari's Law took effect in February 2020. It requires that any multi-line telephone system (MLTS) allow users to dial 911 directly, without pressing 9 or any other prefix first. It also requires that the system send a notification to a central point (front desk, security, an on-call manager) whenever a 911 call is placed, so someone onsite can meet first responders at the door.
RAY BAUM's Act, Section 506 went into force in stages through 2021 and 2022. It requires that 911 calls deliver a "dispatchable location" to the emergency call center. That means more than just a street address. For larger buildings it means the floor, suite, or room number. The rule applies to fixed phones, softphones on laptops, and mobile clients used over wifi or cellular data.
Both rules apply regardless of organization size or tax status. Nonprofits are not exempt.
Where Nonprofits Typically Fall Short
The most common gaps we see in nonprofit phone audits:
- The "dial 9 first" habit. Older systems trained staff to dial 9 for an outside line. If your system still requires that prefix to reach 911, you are out of compliance.
- One address for every location. The headquarters address is registered with the carrier, but the satellite office across town shows the same record. A 911 call from the satellite sends responders to the wrong building.
- Softphones with no location data. A volunteer coordinator working from home uses the desktop app to dial 911 in a medical emergency. The call routes to a dispatcher in the office's city, not theirs.
- No internal notification configured. A 911 call happens after hours from the children's program wing. No one at the front desk gets pinged, no email goes out, no SMS alert fires.
- Stale location records. The org moved suites two years ago. The 911 database still lists the old one.
Each of these is fixable in an afternoon. Each of them, left alone, is a real risk to someone's life and to your organization's liability posture.
A Practical Compliance Checklist
- Confirm 911 can be dialed directly from every desk phone, softphone, and conference room device, with no prefix.
- Register a unique dispatchable address for every physical location, including remote staff home offices if they use the phone system for work.
- For buildings larger than a single suite, add floor, wing, or room-level detail to the location record.
- Configure a 911 notification rule that sends an alert (email, SMS, Teams or Slack message) to at least two people whenever an emergency call is placed.
- Test the notification quarterly. Use your provider's test number, not a live 911 call.
- Document the process for updating location data when someone moves desks or a new site opens. Assign one owner.
- Brief new hires during onboarding: where they are working from, and how their phone treats 911.
The Remote Worker Question
Hybrid and remote staff create the trickiest piece of this puzzle. A development associate who travels between three program sites and works from home two days a week could place a 911 call from four different addresses in a single week. Most cloud phone platforms now support per-session location updates: the softphone prompts the user to confirm their current address on login, or detects it from the network.
Whatever tool you use, the policy needs to be explicit. Tell staff who use softphones that they are responsible for confirming their location whenever they change work sites, and that placing a 911 call from a phone with a stale address could send responders dozens of miles away.
Why This Matters Beyond the Rule
Federal penalties for noncompliance can reach into the tens of thousands of dollars per violation, but that is not the real argument. Nonprofits serve vulnerable people. Shelters, food banks, after-school programs, recovery houses, senior centers: these are exactly the environments where a medical event or a safety incident is more likely than in a typical office. The seconds saved by accurate location data are the seconds that matter.
This is also one of the rare compliance topics where doing the right thing costs almost nothing. Most modern cloud phone platforms include the tools required. Someone just has to turn them on and keep the records current.
Closing the Gap
If you are not sure where your organization stands, a 30-minute review with your phone provider should answer it. Ask three questions: Can every device dial 911 directly? Does every location have a dispatchable address registered? Who gets notified when a 911 call is placed? If any answer is fuzzy, you have work to do.
NonprofitVOIP runs E911 readiness checks as part of every new client onboarding, and we are glad to walk existing systems through the same review. It is the kind of project no one celebrates finishing, and the kind everyone is grateful for when it matters.
