The FCC Just Dropped Two Enforcement Actions Against Voice Providers. Here's What You Need to Check This Week.
The FCC Enforcement Bureau released two enforcement actions on April 2, 2026. One voice provider faces permanent traffic blocking. The other faces a $4.5 million fine.
Both made the same fundamental mistake: they didn't verify their own compliance chain.
If you operate a dialer platform, run an AI voice product, buy leads, or use any voice service provider to reach consumers, these two actions contain specific lessons you need to understand right now.
What Happened: Two Providers, Two Failures
Digital Solutions Inc. -- Suspected Illegal Traffic + False RMD Certification
The FCC's Enforcement Bureau notified Digital Solutions (Denver, CO) that it originated apparently illegal robocall traffic. USTelecom's Industry Traceback Group (ITG) traced 51 calls to wireless numbers between May and July 2025. The calls pushed fake "IRS relief programs" and "loan preapproval" schemes using prerecorded voice messages.
The estimated call volume from just one of Digital Solutions' campaigns: 48.4 million calls over four months.
But here's what makes this case interesting for compliant operators: Digital Solutions had three customers responsible for all 51 traced calls. The provider claimed consent existed for 15 of them. The FCC didn't buy it -- the same customer was identified as the source for most of the calls, many went to numbers not in use, and the campaigns looked like textbook financial fraud.
The second problem was worse. Digital Solutions certified in the Robocall Mitigation Database (RMD) that it had "fully implemented STIR/SHAKEN across its entire network." Its own mitigation plan contradicted that -- admitting it hadn't implemented STIR/SHAKEN on portions of its non-IP network. It also failed to authenticate 13 calls it originated despite certifying that all calls were authenticated.
The FCC gave Digital Solutions 48 hours to mitigate illegal traffic and 14 days to implement effective measures. Failure means downstream providers can -- and likely will -- block all of Digital Solutions' traffic. Not just the illegal calls. Everything.
Voxbeam Telecommunications -- $4.5 Million Proposed Forfeiture (FCC 26-22)
Voxbeam (Orlando, FL) is a wholesale voice provider serving carriers in 200+ countries. Between March 31 and April 2, 2025, Voxbeam transmitted 60,873 calls from Axfone, a Czech voice service provider that has never been listed in the RMD.
The calls spoofed caller IDs belonging to Chase Bank, Bank of America, Navy Federal Credit Union, and Kaiser Permanente. Consumers received calls that appeared to come from their bank's fraud department -- and some were defrauded.
The critical failure: Voxbeam never checked whether Axfone was in the RMD before carrying its traffic. Axfone had been a dormant Voxbeam customer since 2018. When Axfone suddenly reactivated and blasted tens of thousands of spoofed calls through a dormant account, Voxbeam had no procedure to flag or verify the traffic.
Voxbeam did block Axfone within 24 hours of the first ITG traceback -- which earned a 20% reduction in the penalty. But the base forfeiture was $5.625 million ($2,500 per verified illegal call x 2,250 verified calls), reduced to $4,500,000.
The FCC's message: responding quickly doesn't excuse the failure to check in the first place.
Why This Matters Beyond These Two Companies
These aren't just enforcement actions against bad actors. They're a blueprint for how the FCC is thinking about voice provider compliance in 2026. Three themes stand out:
1. RMD Certification Accuracy Is Now an Enforcement Priority
Digital Solutions lied on its RMD filing. It certified "complete STIR/SHAKEN implementation" when its own mitigation plan said otherwise. The FCC treated this as a separate violation -- not just a paperwork issue, but evidence of deficient commitment to compliance.
What this means for you: If your voice provider's RMD certification says "fully implemented" but their actual infrastructure tells a different story, they -- and potentially you -- are exposed. The FCC is actively comparing RMD certifications against actual call authentication data.
2. The "Dormant Customer" Problem Is Real
Voxbeam's $4.5M penalty came from a customer that hadn't placed a call since 2018. When that customer suddenly reactivated with a burst of 60,000+ spoofed calls, Voxbeam had no monitoring in place to flag it.
What this means for you: If you operate a platform that routes voice traffic -- or if your voice provider does -- ask about dormant account monitoring. Ask what happens when an inactive account suddenly lights up. If the answer is "nothing," you have a Voxbeam problem.
3. Downstream Blocking Is the Real Threat
For Digital Solutions, the FCC explicitly invoked the permissive blocking provision (Section 64.1200(k)(4)). This means any downstream provider can block all traffic from Digital Solutions without liability. And mandatory blocking (Section 64.1200(n)(2)) means the FCC can order all downstream providers to block.
What this means for you: If your voice provider gets flagged, your legitimate calls get blocked along with the illegal ones. You don't get a warning. You don't get a carve-out. Your traffic dies because your provider's traffic dies. This is existential risk for any business that depends on outbound calling.
What to Check This Week
If You Run an AI Voice Platform
AI voice calls are prerecorded voice messages under the TCPA. Everything in the Digital Solutions letter applies to you. Your voice infrastructure provider's RMD certification, STIR/SHAKEN implementation, and robocall mitigation plan directly affect whether your AI voice calls reach consumers.
Action items:
- Verify your voice provider is listed in the RMD (search at fcc.gov/RMD)
- Request a copy of their STIR/SHAKEN certification level and confirm it matches their RMD filing
- Ask whether they authenticate ALL calls originating on their network -- not just some
- Review your own consent architecture -- if a traceback hits your traffic, can you produce consent records?
If You're a Lead Generation Company Using Outbound Calling
Your dialer platform and voice service provider are links in a compliance chain. If either one has RMD deficiencies, your traffic is at risk of downstream blocking.
Action items:
- Map your call chain: who originates, who intermediates, who terminates
- Verify each provider's RMD status independently -- don't rely on their word
- Review your vendor contracts for indemnification around FCC enforcement actions
- If you're using multiple providers, verify all of them -- one weak link contaminates the chain
If You're an Insurance Agency Using a Dialer
You probably don't think about your dialer's voice provider. You should. If your dialer routes through a provider with RMD deficiencies or STIR/SHAKEN gaps, your calls to insurance leads could get blocked by downstream carriers.
Action items:
- Ask your dialer provider: "Who is your upstream voice service provider, and are they in the RMD?"
- Ask: "Is STIR/SHAKEN fully implemented for calls originating from our campaigns?"
- Document the answers -- if enforcement happens, you want evidence that you asked
The Compliance Chain Is Only as Strong as Its Weakest Link
These two enforcement actions reinforce what I've been telling clients for months: compliance is a chain, not a checkbox.
Digital Solutions' customers originated the illegal calls. But Digital Solutions faces the consequences because it originated the traffic and lied on its RMD certification.
Voxbeam didn't originate a single illegal call. It just carried traffic from a foreign provider it didn't bother to check. That oversight cost $4.5 million.
Your business sits somewhere in this chain. The question isn't whether you're originating illegal calls -- it's whether every link between you and the consumer is compliant. If one link breaks, your traffic breaks with it.
