Potential Spam: How to Fix the Label on Your Calls

“Potential Spam” means a call-analytics engine working for the recipient’s wireless carrier scored your number as likely unwanted — and it is fixable: verify your STIR/SHAKEN attestation level, register your numbers at the Free Caller Registry, file remediation with each analytics engine, and change the calling behavior that triggered the score. No single step clears the label on its own. The operators who get labels removed — and keep them removed — run this as a remediation program, not a one-time form submission.

This is the business-side playbook. Most of what ranks for “potential spam” is consumer advice about blocking robocalls — useless when you are the business being labeled and your connect rates are collapsing. We wrote this from the carrier side. SIPNEX is an FCC-licensed carrier that holds its own STIR/SHAKEN SP-KI certificate and signs every originating call at A-level, and label remediation is a conversation we have with call center operators weekly.

If you want the prevention side — reputation scoring end to end, DID pool sizing, number warm-up, per-DID monitoring — that lives in our caller ID reputation guide. This post is narrower: your numbers are already labeled, and you need them clean.

Why business calls get flagged

The label does not come from the person you called, and it does not come from the FCC. It comes from a third-party call-analytics engine. Three engines matter in the US market — TNS, First Orion, and Hiya — and the major wireless carriers rely on them to score calls arriving for their subscribers. When your call hits a mobile network, the analytics engine returns a verdict on your calling number, and the handset displays whatever label that verdict maps to.

The engines score behavior, not intent. They cannot see your business license, your opt-in records, or your agents’ scripts. They see call detail patterns, and the patterns they weight are consistent across engines:

• Volume concentration. A single number generating a machine-scale burst of daily calls does not look like a human, and the algorithms are built to catch exactly that shape.
• Duration distribution. A high percentage of very short calls — rings with no answer, connects that end in seconds — matches the statistical fingerprint of robocall traffic.
• Answer rates. When most recipients do not pick up, the engines read it as recipients avoiding the number. Low answer rates feed the score, and the score lowers answer rates further. This loop is why labeled numbers rarely recover on their own.
• Complaint reports. Recipient spam reports flow back into the engines’ databases. A handful of reports against one number carries real weight.
• Recycled-number history. Reputation attaches to the number, not the owner. A DID that previously belonged to a flagged operation arrives at your account with its baggage intact.
• STIR/SHAKEN attestation level. Attestation is an input to analytics scoring. A call signed at A-level tells the engine a licensed carrier verified the caller’s authority over the number. B-level says the signing carrier could not verify that — a gap the algorithms notice.

This entire scoring ecosystem exists because caller ID spent decades being trivially fakeable, and robocall operations exploited it at industrial scale. If you want the background on how that happened and what the law says, see our breakdown of caller ID spoofing and the Truth in Caller ID Act. The practical consequence for legitimate operators: the engines default to suspicion, and the burden of looking legitimate falls on you.

”Spam Risk” vs “Scam Likely” vs “Potential Spam”: which carrier shows what

Each major US wireless carrier displays its own label text, powered by its analytics partner:

Label	Where recipients see it
”Scam Likely”	T-Mobile — commonly misread and searched as “Spam Likely"
"Spam Risk”	AT&T
”Potential Spam”	Verizon

Three things operators consistently get wrong about this table.

The labels are carrier-specific, so your damage is carrier-specific. Each engine maintains its own database and scores independently. The same DID can display “Potential Spam” to Verizon subscribers and ring clean on T-Mobile. If your answer rate cratered on one segment of your list and not another, carrier-level flagging is the likely explanation.

A label is not a block. The call still completes; it just arrives pre-convicted. Recipients decline calls that announce themselves as spam, which is why a label shows up in your metrics as an answer-rate collapse rather than failed calls.

Do not waste time reverse-engineering which engine flagged you. The carrier-to-engine pairings have shifted over the years, and the engines share the same behavioral inputs anyway. The correct move is to register and remediate with all three at once — which is exactly what the process below does.

The remediation playbook

Work these five steps in order. Steps 1 and 2 are administrative and fast. Step 3 is where labels actually die, because labels recur if the calling behavior that earned them does not change.

Step 1: Verify your attestation level with your carrier

Ask your carrier two direct questions: “Do you hold your own STIR/SHAKEN Service Provider certificate?” and “What attestation level do my calls receive?” If the answer involves an upstream partner signing on your behalf, your traffic is almost certainly going out at B-level, and every remediation effort you make downstream starts from a weaker baseline. The full breakdown of what each level asserts — and why the difference shows up in answer rates — is in our A-level vs B-level attestation guide.

Fixing attestation does not remove an existing label by itself. But attestation is an input the engines score on every single call, so leaving it broken means fighting the algorithm with one hand tied. Confirm this first because it determines whether the rest of the playbook is running uphill or downhill.

Step 2: Register at the Free Caller Registry, then work each engine’s channel

The Free Caller Registry is the joint portal operated by the three analytics engines. One submission — business identity, phone numbers, call purpose — distributes to TNS, First Orion, and Hiya simultaneously, at no cost. Register every outbound DID you own, not just the labeled ones. Registration establishes who you are in all three databases, which is the foundation every subsequent dispute rests on.

Then go deeper: each engine also operates its own remediation channel for disputing the label on specific numbers. Registration and remediation are different actions — registration says “this business exists and owns these numbers,” remediation says “this specific label is wrong, review it.” File remediation with each engine for each labeled number, and include your business details, your carrier, and your attestation level. Expect to supply evidence, and expect the engines to keep scoring your traffic while they process the request.

Step 3: Fix the behavioral signals

This is the step operators skip, and it is why their labels come back. The engines re-score continuously on live traffic. If your call patterns still look like spam after remediation, the label returns and your credibility with the engine’s review process goes with it. Audit four behaviors:

Pacing. Aggressive dial ratios concentrate exactly the signals the engines punish: unanswered attempts and short-duration connects, stacked onto a small set of numbers. Spread volume across your DID pool and tune the dialer so no single number carries machine-scale daily volume. Our reputation guide covers pool sizing math in detail.

Abandonment. Answered calls with no agent available produce dead air, hang-ups, and angry recipients who file the complaint reports that feed the engines. Abandonment is also a regulatory exposure in its own right — see the FCC abandoned-call rules — so fixing it pays twice.

Local presence rotation abuse. Matching your caller ID area code to the recipient lifts answer rates, but rotating through an oversized local-presence pool at high velocity is a pattern the engines recognize, because it is the same pattern robocallers use. Use local presence with a stable, modest pool per market rather than a churning one.

Complaint hygiene. Honor opt-outs immediately, scrub against do-not-call lists, and keep calls inside sane hours. Every complaint you prevent is negative data that never enters the engines’ databases. The regulatory specifics vary by campaign type and jurisdiction, so confirm your obligations with your counsel — but the reputation logic is universal: fewer complaints, cleaner score.

Step 4: Monitor labels across all three carriers

Because scoring is fragmented, verification must be too. Keep test handsets — or a testing service — on T-Mobile, AT&T, and Verizon, and call them from every production DID on a weekly cadence. Log what displays. Track per-DID answer rates daily in your dialer: a sudden single-number drop is the earliest flag indicator you will get, usually appearing before any status tool updates. When a number degrades, pull it from rotation while you investigate rather than dialing through the damage.

Step 5: Keep number assignments stable

The instinct when a number gets labeled is to trash it and buy ten more. Resist it. Burning through DIDs recreates the exact signal profile the engines are built to catch — fresh numbers with no history suddenly producing high volume — and replacement numbers are recycled from previous owners whose history you inherit. A stable set of registered numbers, each with months of clean behavior behind it, is the most defensible asset an outbound operation can hold. Provision DIDs deliberately, register them on day one, warm them up, and treat replacement as a last resort rather than a strategy.

Why reseller-signed traffic gets worse outcomes

There is a structural reason two operations with identical calling behavior can receive different labels: who signs their calls. When you buy trunks from a reseller, your calls are typically passed upstream to a carrier that has no direct relationship with you — so it cannot verify your authority over your caller ID, and it signs at B-level. That weaker attestation is scored by the analytics engines on every call you place, forever, regardless of how clean your behavior is. SIPNEX is an FCC-licensed carrier with its own SP-KI certificate; we verify your DIDs against your account and sign every originating call at A-level, directly — the exact mechanics are in our STIR/SHAKEN technical deep dive. A-level signing is not a spam-label eraser, but it moves your baseline from “unverified” to “carrier-vouched” on every call the engines score.

Frequently asked questions

What does “Potential Spam” mean on a phone call?

“Potential Spam” is the label Verizon displays when its call-analytics partner scores the calling number as likely unwanted. It is a prediction based on the number’s calling patterns — volume, call durations, answer rates, complaint reports, and STIR/SHAKEN attestation — not a confirmed finding of wrongdoing. The equivalent labels are “Scam Likely” on T-Mobile and “Spam Risk” on AT&T. The call still goes through, but most recipients will not answer a call that is labeled.

Why are my business calls marked as Spam Risk?

Because an analytics engine scored your number’s behavior as spam-like. “Spam Risk” is AT&T’s label, and the common triggers are high call volume concentrated on one number, low answer rates, a pattern of very short calls, recipient complaint reports, B-level or unsigned STIR/SHAKEN attestation, or a recycled number that inherited a bad history. Legitimate businesses get labeled constantly — the engines score patterns, not intent, and dialer traffic naturally resembles the patterns they were built to catch.

How long does it take to remove a spam label?

There is no guaranteed timeline, and be skeptical of anyone who sells you one. Remediation requests are processed on each engine’s schedule, and the engines re-score continuously on your live traffic — so a label can clear and return within days if the underlying calling behavior has not changed. Treat removal as a program: file remediation, fix the behavioral signals, monitor across all three carriers weekly, and expect durable results to follow sustained clean behavior rather than a single request.

Does STIR/SHAKEN remove spam labels?

No. STIR/SHAKEN attestation is one input to the analytics engines’ scoring, not the whole score. A-level attestation improves your baseline because it tells every engine that a licensed carrier verified your authority over the number, while B-level leaves a verification gap the algorithms weigh against you. But a perfectly signed call from a number with terrible behavioral metrics will still get labeled. Attestation is necessary infrastructure for clean reputation — it is not sufficient on its own.

Can I just switch to new phone numbers instead of fixing the label?

You can, and it will backfire. Fresh numbers that immediately carry high volume are a classic robocall fingerprint, so the new numbers get flagged faster than the old ones did. Replacement numbers are also recycled, meaning you may inherit a previous owner’s bad history on day one. And the behavior that earned the first label will simply re-earn it. Rotating numbers treats the symptom; registration, attestation, and behavioral fixes treat the cause.

---

SIPNEX is the FCC-licensed carrier for outbound operations that cannot afford a Potential Spam label on their calls: A-level STIR/SHAKEN signing with our own SP-KI certificate, unlimited concurrent channels, sub-3-second average PDD, published rates, and trunks provisioned in 24 hours with no long-term contracts. See our call center solutions or talk to an operator about your spam labels — (833) 665-2220.