What STIR/SHAKEN Attestation Does Not Do

It Does Not Prevent Your Number From Being Labeled

This is the most damaging misconception. A-level attestation does not immunize a telephone number against spam labels, "Scam Likely" overlays, or carrier-level call screening.

The major carriers — T-Mobile, AT&T, Verizon — operate layered analytics platforms that score calls using multiple signals. STIR/SHAKEN attestation is one of those signals. Consumer complaint data, call volume per number per day, average call duration, call frequency patterns, and third-party reputation database inputs are also signals. When behavioral signals strongly indicate high-volume or unwanted calling, the analytics engines weight those signals over the attestation level.

In practice: a number with A-level attestation that completes 600 calls under 45 seconds in a single business day will generate spam complaints. Those complaints feed into the carrier's analytics. The analytics will label the number. The A-level attestation helped at the margins — the threshold was higher than it would have been at B-level — but it did not prevent the outcome.

It Does Not Replace List Hygiene

STIR/SHAKEN tells the network who is making the call. It says nothing about whether the person being called wants the call. List quality is entirely outside the attestation framework.

A fully attested outbound campaign dialing a list with 40% DNC-registered numbers is a compliance liability, not a protected operation. A-level signing does not filter your list, does not check numbers against the National DNC Registry, does not validate consent records, and does not satisfy TCPA express written consent requirements for prerecorded messages.

This is not a technicality. Regulatory enforcement in the US outbound space — FTC, FCC, and state AGs — is behavior-based, not attestation-based. An enforcement action following a consumer complaint does not ask what attestation level was on the call.

It Does Not Guarantee Call Delivery

A-level attestation improves the probability of clean call delivery. It does not guarantee it. Carrier routing decisions, number-level spam flags, post-dial screening by the terminating carrier's analytics engine, and consumer-set call screening preferences can all affect whether a call connects — independently of attestation level.

This matters for volume forecasting. If your planning model assumes A-level attestation equals clean delivery, you will overbuild capacity for answer rate expectations that the actual delivery environment will not meet. Model attestation as a factor that reduces labeling risk, not as a factor that eliminates delivery variability.

It Does Not Cover Calls Outside the US and Canada

STIR/SHAKEN is a North American protocol. Calls to the 31 other markets in UnlimCall's live network are not covered by any equivalent framework that operates the same way.

European carriers have partial CLI authentication deployments under different standards. The UK's OFCOM has its own CLI transparency initiative. APAC has no unified authentication framework with enforcement teeth. For outbound operations running campaigns into Germany, France, the Netherlands, Poland, Australia, or any other non-US-CA market, STIR/SHAKEN attestation is simply not part of the delivery equation. Answer rate optimization in those markets is a different problem with different tools: local number presentation, carrier relationship quality, and appropriate calling windows.

Teams running global outbound campaigns need a provider that covers the full footprint — not just the US — with local routing that performs well on its own terms. See the full 33-market network breakdown.

It Does Not Stop All Robocalls

STIR/SHAKEN was designed to make it harder to spoof telephone numbers — to impersonate the IRS, a Social Security Administration number, or a local bank. It addresses number spoofing, not call volume, not call content, and not unsolicited calling.

An organization can fully comply with STIR/SHAKEN, have A-level attestation on every call, and still be running a high-volume unsolicited outbound campaign that violates the TSR. The FTC's enforcement authority covers the campaign behavior, not the signing level. STIR/SHAKEN authentication does not create a compliance safe harbor for calling practices.

It Does Not Make Your Caller ID Permanent

A-level attestation on a number does not prevent that number from being flagged in reputation databases. YouMail, Nomorobo, Hiya, and other third-party services maintain their own databases of flagged numbers based on consumer reports. Carrier analytics platforms query these databases as inputs to their scoring models.

A number that has been flagged in a third-party reputation database is a harder delivery problem than one that lacks A-level attestation. Attestation helps on the carrier scoring side; it does nothing on the third-party reputation database side. The only remediation for a flagged number in a reputation database is to stop using it and allow the flag to age out, or to dispute the flag directly with the database operator — a process that works inconsistently.

This is why on-demand caller ID issuance matters independently of attestation. Fresh numbers have no reputation database history. Combined with A-level attestation, a fresh number starts every campaign with the maximum possible trust baseline.