Only 8 spots left$15 $2/seat/month for life for the next 8 founding teams.Claim your spot →

Guide

How to Get STIR/SHAKEN A Attestation on Twilio

How to register your business and numbers in Twilio’s Trust Hub so outbound calls are signed with full A attestation, and how to check it worked.

Updated · By

Key takeaways

  • Twilio signs a call A only when its number is assigned to both an approved Business Profile and an approved SHAKEN/STIR Trust Product.
  • With the profile and Trust Product approved but a number left unassigned, Twilio signs that number’s calls B; with no approved registration, C.
  • A caller ID that is not a Twilio number, such as a verified caller ID, can reach B at most.
  • Twilio says vetting takes up to 24 hours for a Business Profile and up to 72 hours for a SHAKEN/STIR Trust Product.
  • The StirVerstat parameter on a Twilio number’s incoming webhook shows the attestation a test call arrived with, such as TN-Validation-Passed-A.

Twilio STIR/SHAKEN A attestation needs two approved registrations in Trust Hub: a Primary Business Profile with your numbers assigned, and a SHAKEN/STIR Trust Product with the same numbers assigned. Once both are approved, Twilio signs calls from those numbers A. Numbers left unassigned are signed B, and with no approved registration every call is signed C. Twilio lists no fee for it, and vetting takes up to 72 hours (Twilio SHAKEN/STIR onboarding).

This guide walks through the setup for a business whose own staff make the calls, from the Console steps to a test that proves it worked. For what the framework is and why carriers sign calls, start with what STIR/SHAKEN is. Steps were checked against Twilio’s documentation in November 2026.

What do A, B and C attestation mean on Twilio?

A means the number is assigned to an approved Business Profile and SHAKEN/STIR Trust Product; B means the account is registered but the number isn’t assigned; C means no registration. Twilio decides the level from your Trust Hub registrations, not from anything in your call code. Its onboarding guide sets out the rules:

LevelWhat Twilio needsWhich calls get it
A (full)An approved Business Profile and SHAKEN/STIR Trust Product, with the number assigned to bothCalls from those assigned Twilio numbers
B (partial)An approved Primary Business Profile and Trust Product on the parent account; numbers need not be assignedOther calls from the parent account and its subaccounts, and calls whose caller ID is not a Twilio number
C (gateway)No approved Business Profile and Trust Product, or rejected onesEvery call from the account

So the work is mostly paperwork: an approved business identity, and every outbound number linked to it. The obligation to sign sits with the voice provider under FCC rules (47 CFR 64.6301); what you control is how much Twilio can vouch for.

What do you need before you start?

You need an upgraded account, numbers held in Twilio, and your business’s official details. Four checks save a rejected review:

  • Know which kind of customer you are. Twilio treats you as a direct customer when your own employees make the calls, call centers you run included, and as an ISV or reseller when your customers call through your product. Each has its own path. A sales team that connects its own Twilio account to a dialer is a direct customer.
  • Upgrade the account. Trial accounts are for testing and can only call verified numbers (Twilio trial limits).
  • Hold your numbers in Twilio. Numbers you bought in Twilio or ported into Twilio can reach A; a verified caller ID cannot go above B.
  • Gather your business details. Legal business name and address, EIN, website, and an authorized representative’s contact details, exactly as they appear in official records.

How do you set up STIR/SHAKEN in the Twilio Console?

Create the profile, assign numbers, create the Trust Product, assign the same numbers, then test. For a direct customer without subaccounts, Twilio’s Console guide gives these steps (Twilio Console onboarding):

  1. Create a Primary Business Profile in Trust Hub, in your parent account, and submit it for vetting. Every other registration (SHAKEN/STIR, CNAM, Voice Integrity, Branded Calling) builds on it.
  2. Assign your phone numbers to the profile. Include every number a rep might call from: their own lines, your default number and any numbers kept for local presence.
  3. Create a SHAKEN/STIR Trust Product in Trust Hub, linked to the approved profile, and submit it for vetting.
  4. Assign the same numbers to the Trust Product. A number must already be on the profile before it can be added.
  5. Test one number from each batch, as described below.
  6. Repeat steps 2 and 4 for every new number, because Twilio does not add new numbers for you.

Twilio’s onboarding guide says vetting takes up to 24 hours for the profile and up to 72 hours for the Trust Product. With subaccounts, Twilio’s guide uses a Secondary Business Profile under each subaccount, so check which account is selected in the Console before you create anything.

Can you do it through the Trust Hub API?

Yes. Twilio’s Trust Hub REST API runs the same steps in code: create the Business Profile and the SHAKEN/STIR Trust Product, attach phone numbers by their SIDs, and submit each for review (Trust Hub API guide for direct customers). It is the practical route when you buy numbers in batches, because the purchase and both assignments can run in one script.

The API also helps you audit. Listing the numbers assigned to each registration and comparing them with your full number list catches the most common failure, a number on the profile but not the Trust Product. Run that comparison after every batch of new numbers, and before a campaign that will call from numbers that have sat idle. Teams that make outbound calls with Twilio from their own code can also read the outgoing call’s StirStatus in the status callback, which reports the attestation Twilio gave the call.

How do you check that calls are signed A?

Call a second Twilio number you control and read the StirVerstat value on its incoming webhook. Twilio verifies STIR/SHAKEN on incoming calls and passes the result in that parameter, with values such as TN-Validation-Passed-A, TN-Validation-Passed-B or No-TN-Validation (Twilio trusted calling docs). Place a call from a registered number, log the parameter, and you have proof of the level.

A second, weaker check is to call a mobile on a network that shows a verified indicator for fully attested calls. Not every network or phone shows one, so treat its absence as inconclusive. Repeat the webhook test for one number from each batch you register, and whenever you add numbers.

Why are calls not signed A?

Almost always because a number is missing from one of the two registrations. The common causes:

  • The number is assigned to only one of the two. It must be on both the Business Profile and the Trust Product.
  • A registration is pending or was rejected. Fix the details Twilio flagged and resubmit; calls stay at C until both are approved.
  • The caller ID is not a Twilio number. Verified caller IDs top out at B.
  • The numbers live in a subaccount without its own Secondary Business Profile and Trust Product.
  • A new number was never assigned. Buying a number does not register it.

Attestation does not decide spam labels on its own. Carrier analytics still judge each number’s behavior, so pair it with the steps in why Twilio calls show as Spam Likely and the Free Caller Registry.

How does attestation work with Rapidialer?

Rapidialer places every call through your own Twilio account, so once your numbers are registered, calls from Rapidialer carry A attestation with no setting in Rapidialer. The catch is the number set: with local presence on, Rapidialer may call from any synced number that matches the lead’s area code, and caller-ID rotation spreads calls across your numbers. Assign every synced number to both registrations, or calls from an unregistered one go out signed B.

Rapidialer does not read or display attestation. Its caller-ID health view tracks answer rates per number and flags numbers likely to carry a spam label, which is the problem attestation alone does not solve.

When is STIR/SHAKEN registration not the fix?

Registration is the wrong lever when your numbers are already A and still go unanswered. Then the issue is a spam label or an unknown name, not the signature: add a CNAM caller ID name, consider Twilio Branded Calling for mobile phones, and look at call volume per number. ISVs whose customers make the calls need Twilio’s ISV path, with a Secondary Business Profile per customer, rather than these direct-customer steps.

Questions and answers

Do I need to register every Twilio number?

Every number you call from. Twilio signs a call A only when its number is assigned to both your approved Business Profile and your SHAKEN/STIR Trust Product. Numbers you leave out are signed B while the profile and Trust Product are approved, and new numbers are not added for you, so assign each number on the day you buy it.

Can a number I do not hold in Twilio get A attestation?

No. Twilio says B is the highest level it can give a number it does not provide, such as a verified caller ID, because it cannot attest to your right to use it. To get A on a number you already publish, port it into Twilio, then assign it to your Business Profile and SHAKEN/STIR Trust Product like any other Twilio number.

How long does STIR/SHAKEN registration take on Twilio?

Usually a few days. Twilio’s onboarding guide says vetting takes up to 24 hours for a Business Profile and up to 72 hours for a SHAKEN/STIR Trust Product, and its Console guide says 24 to 48 hours. A rejected registration starts again after you fix the details Twilio flagged, so match your business name and EIN to your official records the first time.

Does Twilio charge for SHAKEN/STIR?

Twilio’s US voice pricing page lists no fee for SHAKEN/STIR registration, and Twilio signs every outbound call whether or not you register. What registration changes is the level: C with nothing approved, B with an approved profile and Trust Product, and A for the numbers assigned to both. You still pay the usual per-minute and per-number rates.

Does A attestation stop Spam Likely labels?

Not on its own. Full attestation tells the receiving carrier that the caller ID is genuine and that you are entitled to use it, but carrier analytics still judge each number by how it is used: volume, very short calls, answer rates and complaints. Pair attestation with Voice Integrity, the Free Caller Registry and steady calling habits to keep labels off.

Does Rapidialer register my numbers in Trust Hub?

No. Trust Hub registration happens in your own Twilio account, in the Twilio Console. Rapidialer places calls through that account, so the attestation Twilio gives your numbers applies to every call you make from Rapidialer, including calls placed with local presence or caller-ID rotation, as long as every number in your set is assigned to both registrations.

Start today

Import your list and make your first call today

Connect Twilio, upload a CSV and start dialing.