TL;DR
Quick Answer
TL;DR
Key Facts
- Caller ID authentication: STIR/SHAKEN authenticates caller ID information between originating and terminating service providers.
- Spoofing prevention: The framework helps reduce illegal caller ID spoofing but does not block calls by itself.
- Legal robocalls exist: Many automated calls are lawful and used for appointment reminders, fraud alerts, school notifications, and other legitimate communications.
- Authentication is not intent analysis: STIR/SHAKEN cannot determine whether a call is legal, illegal, wanted, or unwanted.
- Attestation is limited: A-Level Attestation reflects a provider's confidence that a caller is authorized to use a number, not whether the caller is trustworthy or compliant.
- Provider accountability: The originating provider is responsible for assigning attestation and authenticating calls.
- Reputation still matters: Call labeling, blocking, and reputation analytics continue to influence how calls are treated after authentication.
Does STIR/SHAKEN Stop Robocalls?
No. STIR/SHAKEN was designed to help authenticate caller ID information and reduce caller ID spoofing. It helps providers verify that a call is associated with an authorized telephone number and makes suspicious traffic easier to trace back to the provider that authenticated it.
However, robocalls and spoofing are different problems. A robocall is simply an automated call. Many robocalls are legitimate, including appointment reminders, fraud alerts, school notifications, delivery updates, and emergency communications. STIR/SHAKEN does not determine whether a call is legal, whether consent exists, or whether a recipient wants the call.
Because of this limitation, robocalls can still occur even when STIR/SHAKEN authentication is functioning properly. The framework improves accountability and traceability, but it is only one part of a broader robocall mitigation strategy.
How It Works
What STIR/SHAKEN Solves
STIR/SHAKEN helps providers verify caller ID information before calls move through the voice network. When a provider authenticates a call, downstream providers can validate that authentication and determine whether the displayed caller ID information can be trusted. This creates a greater level of accountability than existed under traditional caller ID systems.
STIR/SHAKEN Doesn't Stop Robocalls
Because authentication and call legality are different issues. STIR/SHAKEN helps answer: "Can the caller ID information be authenticated?"
It does not answer:
- Is this call legal?
- Does the caller have consent?
- Is this call wanted?
- Should this call be blocked?
Those decisions require separate policies, analytics, enforcement mechanisms, and compliance controls.
A Robocall Can Be Authenticated
An automated call can authenticate successfully if the originating provider has authorized the caller to use the telephone number being displayed. Automation alone does not prevent successful authentication.
Why This Matters
Why This Is Important for Businesses
Many businesses expected STIR/SHAKEN implementation to eliminate robocall problems. In reality, the framework was designed to improve trust in caller ID information and reduce spoofing. That distinction matters because organizations may still encounter challenges related to call treatment, consumer trust, and outbound calling performance even after their calls are successfully authenticated.
Why STIR/SHAKEN Is Still Valuable
Even though it does not eliminate robocalls, STIR/SHAKEN significantly improves accountability throughout the voice ecosystem. By identifying which provider authenticated a call, the framework supports traceback efforts and helps investigators identify the source of suspicious traffic.
Other Methods to Reduce Illegal Robocalls
Effective robocall mitigation relies on multiple layers of protection, including:
- Caller authentication
- Traceback programs
- Analytics-based call blocking
- Enforcement actions
- Robocall Mitigation Database requirements
- Provider accountability measures
STIR/SHAKEN is an important part of that framework, but it is not a complete solution by itself.
Common Questions
If STIR/SHAKEN doesn't stop robocalls, what does it do?
STIR/SHAKEN helps authenticate caller ID information and reduce illegal caller ID spoofing. By allowing providers to verify who authenticated a call and which provider introduced it into the network, the framework improves traceability and supports traceback investigations. This makes it more difficult for bad actors to hide behind falsified caller ID information, even though the framework itself does not block robocalls.
Are all robocalls illegal?
No. A robocall is simply an automated call, and many automated calls are legitimate. Common examples include appointment reminders, prescription notifications, school alerts, delivery updates, fraud warnings, and emergency communications. Whether a robocall is legal depends on factors such as consent, purpose, and regulatory compliance, not whether the call was placed automatically. STIR/SHAKEN was designed to authenticate caller identity information, not eliminate all automated calling.
What is the difference between a robocall and a spoofed call?
A robocall is an automated call, while a spoofed call uses misleading or falsified caller ID information. These concepts are often confused because many illegal robocall campaigns rely on spoofing. However, a robocall can use a legitimate phone number, and a spoofed call does not have to be automated. STIR/SHAKEN primarily addresses caller ID spoofing by authenticating caller identity information rather than determining whether a call is automated.
Why did the FCC require STIR/SHAKEN if it doesn't stop all robocalls?
The FCC adopted STIR/SHAKEN to improve trust in caller ID information and make illegal spoofing more traceable. Before caller authentication became widespread, providers had limited ability to verify whether caller ID information was legitimate. STIR/SHAKEN increases accountability by identifying which provider authenticated a call, helping support traceback efforts and enforcement actions even when calls are not automatically blocked.
What else is needed besides STIR/SHAKEN?
Caller authentication is only one part of a broader robocall mitigation strategy. Additional measures include traceback programs, Robocall Mitigation Database requirements, analytics-based call blocking, enforcement actions, and provider accountability initiatives. These tools address risks that caller authentication alone cannot solve, including illegal calling campaigns that use legitimately assigned telephone numbers.
Our platform empowers organizations to manage branded calling, improve caller id reputation, and stay compliant with evolving regulatory and industry standards. FAQs and Glossary terms like this are designed to provide clear, actionable guidance backed by our expertise in verified identity, call labeling mitigation, and spam prevention.
To explore how Numeracle supports trusted and effective outbound communications, visit www.numeracle.com.
