STIR/SHAKEN Attestation Levels Explained for Outbound TeamsAvatar photo by Christiana Ioannou | November 19, 2026 |  Security & Compliance

STIR/SHAKEN Attestation Levels Explained for Outbound Teams

Outbound calls carried over IP are signed under STIR/SHAKEN, and each signature carries an attestation level of A, B or C. Not every call arrives with one, for reasons covered further down. Most vendor explainers treat the letters as a quality score, as though an A meant a good call and a C meant a […]
How to Build a High-Performance Inbound Call Center Workflow

Outbound calls carried over IP are signed under STIR/SHAKEN, and each signature carries an attestation level of A, B or C. Not every call arrives with one, for reasons covered further down. Most vendor explainers treat the letters as a quality score, as though an A meant a good call and a C meant a suspicious one. That reading is wrong, and acting on it leads outbound teams to chase a letter that was never going to fix their answer rates.

Short answer: the STIR/SHAKEN letter records what the originating carrier knows about its own client and that client’s right to use the number on the line. It says nothing about whether the call is wanted, lawful or likely to be picked up. A tells you the signer knows the caller and has verified the number. B tells you it knows the caller but has not verified the number. C tells you the signer has no relationship with whoever originated the call, so it cannot make either assertion.

Every rule below is taken from the instrument that issued it, with the citation given so you can check it. Where the controlling text sits in an industry standard rather than in a federal rule, that is said. Position reviewed 13 October 2026.

Where the three STIR/SHAKEN levels are actually defined

The first surprise is that the Federal Communications Commission did not write the definitions. They live in an industry standard, ATIS-1000074, and the Commission adopted STIR/SHAKEN by reference rather than restating it. RFC 8588 says as much on its face, noting that the values correspond to full, partial and gateway attestation, and pointing to ATIS for what those mean.

The three levels, as the standard words them

Level What the signer must be able to say Typical situation
A, full It put the call on its own IP network, has a direct authenticated relationship with the customer and can identify them, and has established a verified association with the number used A carrier signing calls from its own subscriber, on a number it assigned or verified
B, partial The first two conditions hold, but it has NOT established a verified association with the number. That means the signer has not verified it, not that the number is unauthorised Bring-your-own-number setups, where the carrier knows you but has not confirmed your right to the digits
C, gateway It has no relationship with the originator of the call International gateways passing traffic in from abroad

The Commission reproduced those three conditions word for word in its 2024 enforcement action against Lingo Telecom, and summarised their purpose in a sentence worth keeping: the level a carrier applies signifies what it knows about the identity of the calling party, and therefore how much trust downstream carriers can place in the caller ID shown.

The two phrases nobody defines

Here is the part that matters commercially and goes unmentioned almost everywhere. Neither the standard nor the Commission prescribes what evidence establishes a direct authenticated relationship or a verified association with the number. The conditions are stated; the documentary test for meeting them is not.

The practical effect is that two carriers can look at identical paperwork and grade the same traffic differently. One treats a signed order form and a billing relationship as enough to verify your right to a number you brought with you; another wants evidence of the original assignment. Both are exercising judgement over evidence, within the standard and subject to enforcement if the judgement is unjustified, which is what the Lingo proceeding was about. If your traffic is signed B and you expected A, that gap is where to look, and it is a conversation with your carrier rather than a technical fault.

Who decides the level, and why it is not your platform

A persistent misunderstanding is that a contact centre system assigns the grade. It does not, and the STIR/SHAKEN rules are explicit about this. Under 47 CFR 64.6301, the voice service provider makes all decisions about the level applied to the caller ID information of each SIP call it originates. Where signing is delegated under a written agreement, the same rule requires that agreement to confirm the provider still makes those decisions and that calls are signed with the provider’s own certificate.

The Commission tightened the third-party signing arrangements in its Eighth Report and Order, FCC 24-120, released in November 2024, and compliance with those particular rules was required by 18 September 2025. The principle it stated is short: responsibility stays with the party carrying the STIR/SHAKEN implementation obligation.

So the question to put to a supplier is not “can you give us A”. It is which carrier originates your traffic, what that carrier requires before it will verify your right to a number, and whether anything in your routing sends calls out through a path that signs them lower.

What the STIR/SHAKEN rules require, and by when

The framework rests on the Pallone-Thune TRACED Act, Public Law 116-105, enacted 30 December 2019. Section 4 told the Commission to require STIR/SHAKEN in the IP networks of voice service providers, and separately to require only reasonable measures off IP. That split explains almost everything awkward about the current position.

The dates that bind

  • Voice service providers had to implement STIR/SHAKEN across their IP networks by 30 June 2021, the statutory eighteen months after enactment.
  • The rules define small-provider eligibility for extensions rather than a standing large-provider class, despite that phrase circulating widely. The June 2021 duty applied broadly, and relief was carved out afterwards.
  • Small providers, meaning 100,000 or fewer subscriber lines counted across affiliates, were exempt until 30 June 2023.
  • Non-facilities-based small providers lost that cover early, on 30 June 2022, under the Fourth Report and Order.
  • Gateway providers came in on 30 June 2023, and non-gateway intermediate providers on 31 December 2023, the latter through the Sixth Report and Order adopted in March 2023.
  • None of this amounts to a security certification, and nothing in it vouches for the content of a call.
  • Two extensions are open-ended rather than permanent, and both depend on continued eligibility and on what the Commission does next: carriers unable to obtain a signing token, and the non-IP portions of any network.

That last extension is the gap nobody closes, and a later section is about living with it.

Everything your team needs in one platform

Manage voice, SMS, messaging apps, AI-powered dialing, analytics, and reporting from a single contact center solution.

The database that decides who will accept your traffic

Alongside STIR/SHAKEN sits a registry, and for an outbound operation its commercial consequence is sharper than anything about letters. Providers file a certification covering their robocall mitigation programme, stating whether they have implemented across the whole network, part of it, or none of it. What else the filing must contain depends on the provider’s classification, and the rule names the analytics used to identify illegal traffic and a commitment to answer traceback requests within 24 hours.

The teeth are in the acceptance rule. Providers may accept calls directly from another domestic provider only where that provider’s filing appears in the database and has not been removed through enforcement. An unlisted carrier is not fined into compliance so much as cut off from direct interconnection, because its peers may no longer accept traffic from it directly. Recertification falls due by 1 March each year, and since February 2026 inaccurate filings carry a base forfeiture of $10,000 with $1,000 for failing to update within ten business days. Twelve carriers were removed in September 2025 for ignoring tracebacks.

For a contact centre this is a due diligence question, not a technical one. Ask which carrier originates your calls, confirm it is listed, and confirm it answers tracebacks, because a removal upstream takes your outbound capability with it.

What an A level does not tell you

This is where honest writing about STIR/SHAKEN gets thin, so it is worth being careful about what has actually been said and by whom.

What the Commission has said, and what it has not

The Commission has stated that call authentication often does not let consumers know who is calling, and that an A-level indicator alone does not give consumers enough information to treat a call as an assurance that it is not a scam. It has also recorded commenters cautioning that verifying a caller’s identity does not equate to the call being lawful, though support in the Commission’s own voice for that stronger formulation is not there. Set against that, in the Lingo matter it said an A level signifies to downstream carriers that the displayed number can be trusted as accurate.

Both are true because they answer different questions. The grade is a claim about the number and about the signer’s knowledge of its customer. It is not a claim about the content, purpose or legality of what follows when somebody answers. No single Commission document states that synthesis in those words, so treat it as a reading of the sources rather than a holding.

One figure circulates and deserves its provenance attached: in a 2026 rulemaking the Commission recorded a submission from TransUnion that 89.4 percent of calls originated by the ten carriers considered the most prolific generators of robocalls were signed at the A level. 

That is a commenter’s number appearing in a Commission document, not a Commission finding, and the dataset behind it is the commenter’s own. It is still the clearest available answer to anyone who believes a top grade means a clean call.

Where calls still travel unsigned

STIR/SHAKEN works on IP. Where a call crosses a time-division network, the signature has nowhere to ride, and the rules currently ask only that a carrier either upgrade its network to carry SIP end to end or keep documented proof that it is taking part in industry work on a non-IP solution. Participation in a standards body or in active testing satisfies the obligation, and the non-IP portions of a network sit under a continuing extension.

A proceeding opened in April 2025 proposes to end that, mandating deployment of a non-IP method and repealing the extension, with out-of-band approaches named as candidates. As of today it has produced no rule. Until it does, a call that traverses legacy infrastructure can arrive unsigned through no fault of anybody in the path, which is the usual explanation when your own test calls show a signature on some routes and nothing on others.

What an outbound team should actually do

  • Find out which carrier originates your traffic, since that is who signs it and who carries the STIR/SHAKEN obligation.
  • Get the carrier’s answer in writing, because the person who told you on a call will have moved on by the next audit.
  • Ask what that carrier requires before it will confirm you are entitled to a number you brought with you, and supply it.
  • Check your own numbers are registered to you in the carrier’s records, since an unverified number association is the condition that produces a B.
  • Confirm the carrier is listed in the mitigation database and answers tracebacks, then re-check after each March recertification.
  • Test from numbers in several area codes and across several terminating carriers, because results vary by network.
  • Check the SIP identity header for what was actually signed, and check a handset separately for what gets displayed, since these are two different questions.
  • Treat labelling as a separate matter: terminating-carrier analytics and handset-level services shape what a recipient sees, weighing complaint rates and dial patterns, not only the signature.
  • Fix the behaviour that drives complaints, because no grade compensates for calling the same number six times before lunch.
  • Keep call-origin, customer and campaign records so you can answer a traceback, and keep consent records separately for the telemarketing rules, which are a different obligation.
  • Remember that legacy segments can interrupt the identity information in transit, so an unsigned call is not necessarily a fault in your own setup.
  • Keep the caller ID you present consistent with the business name people expect to see.
  • Review the whole picture quarterly, since the rules and the analytics engines both move.
  • Give one person ownership of it, because a shared responsibility here becomes nobody’s.

Voiso’s outbound compliance guidance covers the dialling behaviour that sits underneath STIR/SHAKEN, the risk mitigation guide covers the surrounding controls, and call detail records are where you look when you need to reconstruct what a particular call did. The Trust and Compliance Center sets out the certifications Voiso states it holds.

Requirements here change, and several of the positions above moved between 2023 and 2026. Confirm the current rule with your carrier and your own advisers before relying on any of it.

Frequently asked questions

What do A, B and C actually mean?

The three STIR/SHAKEN levels record how much the signing carrier knows. A means it originated the call on its own network, has an authenticated relationship with the client, and has verified that client’s right to the number. B means the first two hold but the number has not been verified. C means it has no relationship with whoever originated the call, which is the normal grade on traffic arriving from an international gateway. The definitions sit in ATIS-1000074 rather than in any federal rule.

Does an A grade stop my calls being marked as spam?

No, and expecting it to is the commonest disappointment in outbound. The letter does not determine the label by itself. Those decisions sit with terminating-carrier analytics and handset-level services, which weigh complaint rates, how many distinct numbers you dial, how short your connected calls run and how often people block you. Authentication status can be one input among those. Reducing the behaviour that generates complaints can improve how you are treated, though outcomes vary by carrier, while chasing the letter alone rarely moves anything.

Why are my calls signed B instead of A?

Because the carrier has not established a verified association with the number you present, which is the defining condition for B rather than a guess at the cause. It is routine when you brought numbers in from elsewhere. The standard does not say what evidence suffices, so each carrier sets its own bar. Ask yours what it needs, usually documentation of the original assignment or a completed port, and supply it. The relationship half of the test is rarely the obstacle, since the carrier already bills you.

Can my contact centre platform give me an A?

Not on its own. The rules put every grading decision on the voice service provider that originates the call, and where signing is delegated the written agreement must confirm that and require the provider’s own certificate. Software can route your traffic to a carrier that grades it well, and can show you what happened on each call, but the letter is assigned upstream of it. Judge a supplier on which carrier it originates through, and on what that carrier asks for.

What happens if my carrier is not in the mitigation database?

Other providers are barred from accepting calls directly from it, which disrupts outbound traffic materially even where indirect paths exist. Registration is not a formality: filings must be recertified by 1 March each year, updated within ten business days of any change, and an inaccurate filing now carries a base forfeiture of $10,000. Carriers have been removed for failing to answer tracebacks inside 24 hours. Ask about this before you sign, because the failure arrives without warning and you cannot fix it from your end.

Why do some of my calls arrive with no signature at all?

Because STIR/SHAKEN only works over IP, and parts of the network have not moved. Where a call crosses legacy infrastructure the signature cannot travel with it, and the rules presently require only that carriers upgrade or document their participation in developing a non-IP method. A proceeding opened in 2025 proposes to change that and has not yet produced a rule, so unsigned calls on some routes remain normal rather than a defect in your configuration.

Find out what your traffic is actually carrying

Most outbound problems blamed on STIR/SHAKEN turn out to be two separate things: a number the carrier never verified, and a dialling pattern that earns complaints. Both are fixable, and neither is fixed by asking for a better letter.

Talk to the Voiso team about how your traffic is routed, which carrier signs it, and what your call records show about the numbers you present.

Read More:

18 Nov 2026
Collections of good customer service examples recycle the same four stories. The shoe retailer that sent flowers. The hotel that posted a lost toy home with a photo album of its holiday. The supermarket that drove groceries to a housebound customer. The airline that refunded a fare nobody expected back. They may well have happened […]
17 Nov 2026
Number porting is the process of taking a telephone number you already own and moving it to a different provider, so the same digits keep ringing after you change supplier. For a business the stakes run higher than for a personal handset, because that phone number sits on invoices, vehicle livery, directory listings and the […]
16 Nov 2026
An AI receptionist is software that picks up your main line, greets whoever rang in natural speech, works out what they need, and then either answers from your own documents or hands the conversation to a person on your team. A virtual receptionist service does that same job using trained staff in a remote office, […]

Subscribe to our newsletter

Stay updated with the latest product updates from Voiso and news from the industry.

Voiso Authors