STIR/SHAKEN and the TRACED Act: What Callers Actually Have to Do
A business that calls and texts customers hears “STIR/SHAKEN” and assumes there’s a compliance box it has to check. For most companies, there isn’t. The TRACED Act and the FCC’s call-authentication rules put the hard obligations on voice service providers and the carriers in the middle, not on the company that buys phone service and places calls. That doesn’t let a caller off the hook. These rules decide whether your calls connect, how they get labeled, and whether a carrier will carry your traffic at all.
Does the TRACED Act require your business to do anything?
Probably not directly, if you place calls through a normal carrier. The TRACED Act, signed December 30, 2019 as Public Law 116-105, told the FCC to make carriers authenticate caller ID. It directs the Commission to “require a provider of voice service to implement the STIR/SHAKEN authentication framework” in its internet protocol networks. The duty in that sentence runs to the provider of voice service. A company that signs up for business phone lines and dials customers is an end user of that service, not a provider of it.
So the statute’s main command skips right past the ordinary caller. That’s the part most compliance guides get backwards. They treat STIR/SHAKEN as a to-do list for marketers and collection shops, when it’s really a mandate on the phone network your business sits on top of.
The line blurs in one situation worth watching. If your company obtains telephone numbers directly from the numbering plan and originates its own traffic, instead of buying service from a carrier, you can slide into the regulatory definition of a voice service provider and pick up real filing duties. Large call centers and lead-generation operations that have built their own origination sometimes cross that line without realizing it. If that might be your setup, don’t guess. The definitions in the rules are technical, and the consequences of landing on the wrong side of them are not.
What is STIR/SHAKEN, and what does it do to your calls?
STIR/SHAKEN is the industry system that lets one carrier vouch for the caller ID on a call before handing it to the next carrier. The initials stand for Secure Telephone Identity Revisited and Signature-based Handling of Asserted information using toKENs, which is a mouthful nobody says out loud. In plain terms, your carrier attaches a digital signature to your call that tells the receiving carrier how confident it is about who you are and whether you’re entitled to use the number showing on the display.
The FCC’s rule set a hard date. Under 47 C.F.R. § 64.6301, “a voice service provider shall fully implement the STIR/SHAKEN authentication framework in its internet Protocol networks” by June 30, 2021. Your carrier signs your calls with one of three attestation levels, and the level it assigns depends on whether it can confirm your identity and your right to the number. The attestation your traffic earns is what drives whether a call rings through clean or lands as “Spam Likely.” How those levels work and what to ask your carrier about them is its own subject, covered in a separate post on caller ID spoofing and spam labels.
Two protections in the statute matter to a caller. First, the TRACED Act says the FCC “shall prohibit providers of voice service from adding any additional line item charges” to consumer and small business subscribers for the authentication technology. You should not be seeing a STIR/SHAKEN surcharge on your bill. Second, the statute is built so that a caller whose calls get wrongly flagged has a way to push back, which is the next question.
What is the Robocall Mitigation Database, and can it block your calls?
The Robocall Mitigation Database is a public FCC filing system, and it’s the quiet gatekeeper most callers have never heard of. Every carrier in the call path has to file in it. Under 47 C.F.R. § 64.6305, “Each voice service provider shall implement an appropriate robocall mitigation program” and certify that program in the database, with a commitment to answer traceback requests within 24 hours.
The gatekeeping has teeth. The same rule tells carriers to accept traffic “only if that voice service provider’s filing appears in the Robocall Mitigation Database”. A carrier that isn’t properly listed gets cut off, and so does everything flowing through it. For a business that places calls, that’s the exposure: if one of the carriers your traffic rides through loses its listing or gets de-listed in an enforcement action, your calls can stop connecting even though you did nothing wrong.
Again, the filing duty itself sits with the carriers, not with the ordinary business placing calls. But the database is why vendor selection is a compliance decision, not just a price decision. A cheap origination route that cuts corners on robocall mitigation is a route that can vanish, and it tends to be the kind of route that drags your attestation down with it.
Who the rules actually bind
The obligations below are easy to mix up, and the confusion usually runs in the caller’s disfavor, because companies spend money chasing duties that were never theirs. This table keeps them straight.
| What the rule requires | Who it binds | Source | What it means for a business that places calls |
|---|---|---|---|
| Implement STIR/SHAKEN in IP networks | Voice service providers | 47 C.F.R. § 64.6301 | Your carrier signs your calls, not you |
| Run a robocall mitigation program and certify it | Carriers in the call path | 47 C.F.R. § 64.6305 | A duty on your carriers, but their compliance decides whether your calls get carried |
| Appear in the Robocall Mitigation Database | Carriers in the call path | 47 C.F.R. § 64.6305(g) | If a carrier you use isn’t listed, your traffic can be refused |
| Respond to traceback requests within 24 hours | Carriers | 47 C.F.R. § 64.6305 | Your calling records can surface fast when a carrier gets a traceback on your campaign |
| No line-item charge for authentication | Imposed on providers, protects you | 47 U.S.C. § 227b(b)(6) | You should not pay a separate STIR/SHAKEN fee |
What can you do when your legitimate calls get blocked or mislabeled?
The TRACED Act anticipated this, and it built in a path for callers. It directs the FCC to set up a process “establishing a process to permit a calling party adversely affected by the information provided” by the authentication framework to verify that its calls are genuine. In practice that runs through your carrier and the redress tools the carriers and analytics companies maintain. If your numbers are getting throttled or labeled, the first move is to work that process, confirm your attestation level, and get the mislabel corrected at the source.
What you usually can’t do is sue the carrier that blocked you. The statute also told the FCC to build a safe harbor shielding providers from liability for inadvertent blocking or misidentification. That safe harbor is deliberate, and it’s a reason the fix for a blocked-calls problem is operational and administrative, not a lawsuit.
The deeper point for a company with TCPA exposure is one most callers miss. A pattern of calls that keep getting flagged or blocked is evidence. When a consumer sues over unwanted calls, a record showing your traffic was persistently labeled as likely spam gives the other side a story about volume and intent, whatever the authentication rules technically require of you. Clean authentication is partly a defense-posture decision, not just a deliverability one. If your calls are being blocked, preserve the records behind the blocking before they age out.
When a demand letter or a lawsuit does land, the authentication picture is one piece of a larger record you need to lock down fast:
- Place a litigation hold on your call and text logs, your dialer and platform data, and the consent records for the numbers you dialed, so nothing is overwritten on a routine retention schedule.
- Pull your carrier’s attestation records and any correspondence about blocking, mislabeling, or traceback requests tied to your campaigns.
- Pull your opt-out and internal do-not-call logs, with dates, and your National Do Not Call Registry scrub records with the version dates you used.
- Gather your vendor and origination contracts, calling scripts, and any recorded or prerecorded message files, along with each vendor’s robocall mitigation representations.
- Talk to a lawyer before you respond to a demand letter, contact the person who complained, or offer anything to settle. California TCPA defense counsel can tell you quickly whether the authentication record helps you or hurts you. The firm’s California TCPA defense practice handles exactly this kind of record review when a claim arrives.
Questions businesses ask about STIR/SHAKEN and the TRACED Act
Does my company have to register in the Robocall Mitigation Database?
Not if you place calls through a normal carrier. The database filing is a duty on voice service providers, gateway providers, and intermediate carriers, not on the ordinary business that buys phone service. The exception is a company that obtains its own numbers and originates its own traffic, which can meet the definition of a voice service provider. If that describes your operation, get the definitions checked instead of assuming you’re exempt.
Is a robocall illegal just because it isn’t authenticated?
No. STIR/SHAKEN authentication and TCPA liability are separate questions. The TCPA is about consent and the do-not-call rules, not about whether a call carried an A-level attestation. A call can be fully authenticated and still violate the TCPA, and an unauthenticated call isn’t automatically unlawful. Authentication affects whether your call connects and how it’s labeled, not whether it broke the statute.
Why do my legitimate business calls show up as “Spam Likely”?
Usually because of attestation and analytics, not because anyone decided you’re a spammer. If your calls route through a carrier that didn’t assign your numbers, they may get a lower attestation level, and the analytics engines that terminating carriers use read that as a risk signal. High call volume and short call durations feed the same engines. The fix starts with your carrier and the attestation your traffic receives.
Can we be fined under the TRACED Act for how we make calls?
The TRACED Act is best known for expanding the FCC’s power to impose forfeitures for illegal robocalls, and that exposure is real and separate from a private lawsuit. It’s a different track from the authentication rules discussed here. The FCC forfeiture risk, and how a Notice of Apparent Liability works, is covered in a separate post on TRACED Act penalties and FCC forfeiture exposure.
If your company is the one getting the demand letter
If your business is accused of making unwanted calls or texts, the authentication and blocking record is often one of the first things worth pulling, because it can either support your consent story or undercut it. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving high-volume calling campaigns and blocked or mislabeled traffic. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.
Sources
Telephone Consumer Protection Act, call authentication, 47 U.S.C. § 227b (TRACED Act, Pub. L. 116-105).
Caller ID authentication, 47 C.F.R. § 64.6301.
Robocall mitigation and certification, 47 C.F.R. § 64.6305.
This post is general information about the Telephone Consumer Protection Act and related laws as of August 4, 2026. It is not legal advice, and reading it does not create an attorney-client relationship. Courts and the FCC change the rules in this area often, and the outcome of any claim depends on its facts. Past results do not guarantee future outcomes.