Are SHAKEN and robocall mitigation preventing robocalls?
STIR/SHAKEN call authentication and/or robocall mitigation programs were mandated to be used starting June 30, 2021. So robocalls plummeted in July 2021, yes? Well, not exactly. Let’s have a look.
You may recall that robocalls plummeted from February through March 2020, mostly because call centers shut down during the pandemic. From April 2020, robocalls crept upward each month, reaching pre-pandemic levels by March 2021.
Here’s the bad news: robocalls in July 2021 were down only 0.3% from June. The combination of STIR/SHAKEN and robocall mitigation programs deployed by the end of June didn’t make a dent in robocalls during July.
This doesn’t seem to be working. Why?
First, it’s helpful to remember that call authentication is necessary, but not sufficient, to prevent unlawful robocalls.
- Call analytics can prevent unlawful robocalls.
- But analytics are not as effective when the calling number is spoofed, especially neighbor spoofing a legitimate number.
- Call authentication is a powerful, essential input to call analytics to signal when the calling number was not spoofed.
We need STIR/SHAKEN and call analytics in order to make a dent in unlawful robocalls.
Robocalls by attestation level
We shared this graph in a recent blog post on spam robocalls and SHAKEN attestation in July 2021. It tells an interesting story:
- 85% of calls are unsigned.
- 3% of calls were spam robocalls.
- Fewer than 1% of calls signed with Full Attestation (A) were spam robocalls.
- This is a significant improvement.
- However, full attestation doesn’t guarantee the call isn’t a spam robocall.
- Calls signed with Partial (B) or Gateway (C) attestation aren’t any better than unsigned calls.
- In fact, calls signed with partial attestation were much worse. 7.3% were spam robocalls!
Why were there so many spam robocalls signed with partial attestation? Many of these calls were signed by downstream providers for their upstream service provider customers.
Pathway to improvement
What’s it going to take to make a dent in spam robocalls? We think the pathway to improvement must include these steps:
- Originating service providers should use both robocall mitigation and SHAKEN. They go together. Neither is sufficient without the other.
- There needs to be more widespread use of SHAKEN. The recent approval of ATIS standards for non-IP call authentication provide effective ways to bring many more calls into the SHAKEN ecosystem.
- Something needs to be done about spam robocalls signed by downstream providers with partial attestation. Clearly, this is not working as intended.
In addition, we help service providers with all aspects of STIR/SHAKEN deployment, including registering with the Policy Administrator and filing their certification with the FCC.
Contact us today to learn more.
This information will only be used to respond to your inquiry. TransNexus will not share your data with any third parties. We will retain your information for as long as needed to retain a record of your inquiry. For more information about how we use personal data, please see our privacy statement.
Our STIR/SHAKEN products:
- Work with your existing network
- Support SIP and TDM
- Affordable, easy to deploy