What Triggers an FCC 911 Investigation — And How to Avoid Being Next

The FCC doesn't have the resources to audit every organization with a phone system. They're not showing up randomly to check your 911 configuration.

But they do investigate. And when they do, it's usually because something specific put your organization on their radar.

Here's what actually triggers an FCC 911 investigation — and how to avoid becoming a target.

Trigger 1: A Failed 911 Call With Serious Consequences

This is the most common trigger. Something goes wrong during a real emergency:

• A 911 call doesn't connect
• Responders are dispatched to the wrong location
• Internal notification doesn't reach anyone
• The delay contributes to injury or death

When outcomes are serious, they get reported. Local PSAPs, first responders, hospitals, or family members may file complaints. News coverage attracts attention. The FCC receives a report and opens an inquiry.

The investigation: The FCC sends a Letter of Inquiry asking for documentation about your phone system, 911 configuration, location data, and compliance processes. You have 20-30 days to respond with evidence.

How to avoid it: Test your 911 infrastructure regularly. Verify that calls connect, locations are accurate, and notifications work. Don't wait for a real emergency to discover a problem.

Trigger 2: Complaints

Anyone can file a complaint with the FCC. Employees, tenants, visitors, contractors, competitors — if someone believes your phone system doesn't meet 911 requirements, they can report it.

Common complaint scenarios:

• An employee tries to dial 911 and discovers they need a prefix
• A tenant in a multi-tenant building realizes 911 calls don't show their specific floor
• A safety officer notices that no one receives notification when 911 is dialed
• A terminated employee reports compliance issues on their way out

The investigation: The FCC is required to investigate credible complaints. They'll contact your organization, request information, and evaluate whether a violation exists.

How to avoid it: Don't give people reasons to complain. Make sure your system actually works. When employees raise concerns about 911, take them seriously and address them — don't dismiss them.

Trigger 3: Carrier or Vendor Reports

Your telecom carrier, UCaaS provider, or phone system vendor may have reporting obligations. If they become aware of 911-related issues affecting your organization, they may be required to report them.

This can happen when:

• A carrier identifies a 911 routing failure affecting your calls
• A vendor discovers a configuration issue during a support engagement
• An integration problem causes 911 data to be delivered incorrectly
• An outage affects 911 service for your organization

The investigation: Carrier reports can trigger FCC inquiries into the organizations affected, even if no specific incident occurred at your location.

How to avoid it: Stay engaged with your carriers and vendors about 911. Ask questions. Request documentation. Don't assume they're handling everything.

Trigger 4: Industry Enforcement Sweeps

Periodically, the FCC conducts targeted enforcement initiatives focused on specific compliance areas. They've done this with Kari's Law, with location accuracy requirements, and with specific industries like hospitality and healthcare.

During a sweep, the FCC may:

• Send inquiries to organizations in a target sector
• Request compliance documentation from a sample of organizations
• Follow up on previously identified issues
• Focus on requirements that have passed their implementation deadlines

The investigation: You may receive an inquiry even without a specific incident or complaint — simply because your organization fits the profile of the enforcement initiative.

How to avoid it: Stay current with FCC announcements and enforcement priorities. When the FCC signals increased focus on a requirement, make sure you're compliant before they come asking.

Trigger 5: Acquisition or Change of Control

When organizations merge, get acquired, or undergo significant structural changes, compliance obligations don't pause. The acquiring entity inherits whatever compliance gaps existed.

Due diligence processes sometimes surface 911 compliance issues. When they do, the question becomes: did the acquiring organization knowingly take on non-compliant infrastructure?

The investigation: Compliance issues discovered during M&A can trigger inquiries, especially if the new entity doesn't remediate them promptly.

How to avoid it: Include 911 compliance in due diligence for any acquisition. Assess the target's infrastructure, documentation, and compliance posture. Budget for remediation if gaps exist.

Trigger 6: Public Attention

News coverage, social media posts, or public statements about 911 failures can attract FCC attention even without a formal complaint.

If a 911 failure at your organization makes the local news, there's a reasonable chance the FCC will notice. They monitor for exactly these kinds of reports.

The investigation: Media attention often accelerates and intensifies FCC inquiries. What might have been a routine investigation becomes a priority.

How to avoid it: The only way to avoid negative publicity about 911 failures is to not have 911 failures. Invest in compliance before it becomes a headline.

What Happens When You're Investigated

If the FCC opens an inquiry, here's what to expect:

Letter of Inquiry (LOI): A formal request for information about your 911 infrastructure, including technical specifications, configuration documentation, location records, policies, test results, and any incident reports.

Response deadline: Typically 20-30 days. Extensions are possible but not guaranteed.

Evaluation: The FCC reviews your response to determine whether violations exist and how serious they are.

Possible outcomes:

• No action (you're compliant)
• Warning letter (minor issues, expectation of remediation)
• Consent decree (formal agreement to fix issues, often with monitoring requirements)
• Notice of Apparent Liability (proposed fine)
• Forfeiture order (actual fine)

Penalties for willful or repeated violations can reach $10,000 per violation plus $500 per day for continuing violations.

How to Stay Off the Radar

1. Make sure 911 actually works. Test it. Verify location accuracy. Confirm notifications are reaching the right people.
2. Document everything. If you can't prove compliance, you're not compliant. Maintain policies, configuration records, test logs, and audit trails.
3. Address complaints immediately. When someone raises a 911 concern, treat it seriously. Investigate. Fix issues. Document the resolution.
4. Stay current with requirements. Kari's Law and Ray Baum's Act have implementation deadlines that have passed. Make sure you're meeting current requirements, not just the ones that existed when you deployed your system.
5. Maintain ongoing vigilance. Compliance isn't one-time. Organizations change. People move. Systems get updated. Location data goes stale. Build processes that keep you compliant over time.

The Bottom Line

FCC investigations don't happen randomly. They're triggered by failures, complaints, reports, and attention.

The best way to avoid an investigation is to not give the FCC a reason to investigate. That means actually being compliant — not just assuming you are.

Test your infrastructure. Document your compliance. Fix issues before they become incidents. Stay ahead of enforcement priorities.

The organizations that take 911 seriously don't end up in FCC inquiries. They're too busy being compliant to create triggers.

The FCC investigates organizations that give them reasons to investigate. Don't be one of them.