Companies Face Removal From Key Database for Skirting Anti-Robocall Rules

WASHINGTON — Seven voice service providers face removal from a key database managed by the Federal Trade Commission if they fail to demonstrate they’re taking concrete steps to comply with the agency’s anti-robocall rules.

The first-of-their-kind FCC Enforcement Bureau orders give the companies until Oct. 18 to explain why they shouldn’t be removed from the so-called “Robocall Mitigation Database” or to complete remediation efforts to bring their operations into agency compliance.

The companies involved are Akabis, Cloud4, Global UC, Horizon Technology Group, Morse Communications, Sharon Telephone Company, and SW Arkansas Telecommunications and Technology.

Removal from the Robocall Mitigation Database would require all intermediate providers and terminating voice service providers to cease accepting their traffic.  

In other words, their calls would be blocked and no call traffic originating from them would reach a called party.

“This is a new era,” said FCC Chairwoman Jessica Rosenworcel in a written statement. 

“If a provider doesn’t meet its obligations under the law, it now faces expulsion from America’s phone networks. Fines alone aren’t enough,” she continued. “Providers that don’t follow our rules and make it easy to scam consumers will now face swift consequences.”

As part of the FCC’s multipronged approach to combating illegal robocalls, the agency has mandated adoption of the Secure Telephony Identity Revisited/Signature-based Handling of Asserted Information using toKENs, or STIR/SHAKEN, caller ID authentication framework.

The FCC extended the implementation deadline for certain voice service providers on the basis of undue hardship or material reliance on a non-IP network, and those that received an extension were required to begin a robocall mitigation program to prevent unlawful robocalls from originating on their networks. 

In addition, the agency required all voice service providers — not only those granted an extension — to file certifications with the commission, stating whether their traffic is authenticated with STIR/SHAKEN or subject to a robocall mitigation program.   

Voice service providers whose traffic is subject to a robocall mitigation program must detail in their certifications the specific reasonable steps that they have taken to avoid originating illegal robocall traffic.   

These certifications and robocall mitigation plans are publicly available in the Robocall Mitigation Database. 

“These and other recent actions reflect the seriousness with which we take providers’ obligations to take concrete and impactful steps to combat robocalls,” said Loyaan A. Egal, acting chief of the Enforcement Bureau. 

“STIR/SHAKEN is not optional. And if your network isn’t IP-based so you cannot yet use these standards, we need to see the steps taken to mitigate illegal robocalls.  

“These providers have fallen woefully short and have now put at risk their continued participation in the U.S. communications system. While we’ll review their responses, we will not accept superficial gestures given the gravity of what is at stake,” Egal said.

Dan can be reached at [email protected] and @DanMcCue