STIR/SHAKEN for Enterprise & BPO

post june 30th deadline

STIR/SHAKEN Doesn't Fix it All...

The June 30th STIR/SHAKEN implementation deadline may have passed, but that does not mean it has solved spam labeling for you.

Do you still have 'Spam' labels appearing on your calls? Not sure why they're still there?

Your relationship with STIR/SHAKEN

The aim of STIR/SHAKEN is to confirm the origination of the identity and number behind phone calls, not their intent.
This means that it will not fix all improper labeling issues for you.
Your service provider is responsible for to validating the traffic originating on their networks to comply with STIR/SHAKEN

We've got you covered

Frequently Asked Questions

STIR/SHAKEN FAQ Guide

My carrier completed STIR/SHAKEN, so why are my calls still being labeled?

External to the STIR/SHAKEN call authentication framework are 3rd party algorithms deployed at the wireless carrier level which are known as call reputation analytics. These analytics have been deployed across mobile networks since late 2017 and are responsible for calls labeled as “Potential Spam,” “Spam,” “Scam,” “Scam Likely,” “Fraud Alert,” etc.

These technologies will continue to be deployed in parallel with STIR/SHAKEN, so if you’re hearing reports from your agents that your calls are ringing through as a “Spam” or equivalent, this is due to reputational analytics, not STIR/SHAKEN.

Numeracle can help clean up your number reputation and addressing phone numbers labeled as 'Scam' or 'Spam'.

Will STIR/SHAKEN stop all robocalls?

While STIR/SHAKEN will help identify harmful robocalls, it will not completely eliminate all illegal robocalls for good. It's important to note that not all robocalls are bad. Many legitimate companies communicate all sorts of information via 'robocalls’ especially automated communications such as appointment reminders, delivery notifications, school closures, etc.
‍
While the STIR/SHAKEN framework allows authentication of call originators and their numbers, it is not a silver bullet solution and it cannot determine the illegitimacy or legitimacy of the intent of an incoming call. It can validate that an incoming call is originating from a real phone number, which is not being 'made up' or stolen from a legitimate business, organization, or consumer.
‍
The STIR/SHAKEN framework does not have the ability to weigh in on whether or not the content of the call itself is potentially malicious or unwanted, making call blocking and labeling analytics are still relevant despite the framework.

Will Numeracle's Platform take care of STIR/SHAKEN for me?

While the Platform itself does not ‘attest’ or ‘sign’ calls, it can be used by service and platform providers to implement a local policy solution to manage the verification of calling identity and the authorization of phone numbers in order to elevate an enterprise brand into the STIR/SHAKEN framework.

What do "calls with a checkmark have been verified by carrier" mean?

Calls that display a checkmark at the time of call or in the call history log represent the establishment of the caller as a legal and verified calling party confirmed via STIR/SHAKEN. The identity of the caller has been vetted and validated and you can trust that the caller is who they say they are, and that the call has not been spoofed by a bad actor.

How does Numeracle price their services?

Pricing for Identify Verification and Number Reputation starts with us gaining an understanding into your calling structure. How many entities/brands do you represent, how many numbers do you use, etc.

To learn more about pricing for branded calling capabilities, reach out to start a conversation!

caller id authentication

What is STIR/SHAKEN?

STIR (Secure Telephone Identity Revisited) / SHAKEN (Signature-based Handling of Asserted information using toKENs) is a framework designed to assign a certificate of authenticity to each phone call for use across the telecom network. These certificates act as a digital signature of trust passed from carrier to carrier to improve traceable call delivery.

STIR/SHAKEN is a requirement of the TRACED Act, and the FCC has also mandated that both originating and terminating voice service providers were to implement the STIR/SHAKEN caller ID authentication framework by June 30, 2021.

The execution of STIR/SHAKEN deployment requires that the relationship between the identity of the caller and the authorized use of its phone numbers be verified in order to pass STIR/SHAKEN authentication and achieve the "Verified Caller" display. If a service provider hasn't filed its certified Robocall Mitigation Plan with the FCC, its call may be blocked based on the upcoming September deadline.

for more on stir/shaken,
visit our knowledge center

videos, articles, and more

More STIR/SHAKEN Resources

What do STIR/SHAKEN Verified Calls Tell you?

Exploring the Path to Authenticated Communication

Will the USA Dominate Global Call Authentication? A Conversation with a US Telecoms Legend