Potential Spam: How to Fix the Label on Your Calls

“Potential Spam” is the warning label Verizon shows when a call-analytics engine scores the calling number as likely unwanted. The label is a prediction about the number’s behavior, not proof of fraud. It is fixable.

The remediation takes five steps:

1. Verify your STIR/SHAKEN attestation level.
2. Register your numbers at the Free Caller Registry, then file remediation with TNS, First Orion, and Hiya.
3. Fix the calling behavior that earned the score.
4. Monitor all three carriers every week.
5. Keep your number assignments stable.

One rule before step 2: the Free Caller Registry accepts only businesses calling on their own behalf. If you call for other businesses, register direct through First Orion Free Number Registration; the business phone number registration hub sorts which portal fits which caller type.

This is the business-side playbook, for when your business is the one being labeled. It is written from the carrier side: SIPNEX is an FCC-licensed carrier, holds its own STIR/SHAKEN SP-KI certificate, and signs originating calls from verified DIDs at A-level.

Key takeaways

• The label comes from call-analytics engines — TNS, First Orion, and Hiya — not from the FCC or the person you called.
• No single fix clears it. Registration, per-engine remediation, and behavior change must all happen.
• Labels are carrier-specific. A number can be flagged on Verizon and clean on T-Mobile, so check each one.
• Swapping to new numbers makes flagging worse, not better.

Why does my number show as Potential Spam?

Your number shows as Potential Spam because a call-analytics engine working for the recipient’s phone carrier scored its calling patterns — high call volumes, short durations, low answer rates, complaint reports, and STIR/SHAKEN attestation level — as spam-like. The verdict is algorithmic, applied without human review, and legitimate calls get flagged whenever their traffic resembles robocall behavior.

The label does not come from the person you called, or from the FCC. It comes from a third-party call-analytics engine. Three engines matter in the US market: TNS, First Orion, and Hiya. Major wireless carriers rely on them to score incoming calls. When your call hits a mobile network, the engine returns a verdict on your number. If that verdict flags the call as potential spam, the handset displays the carrier’s label for it.

The engines analyze call behavior, not intent. They cannot see your business license, your opt-in records, or your agents’ scripts. They see call patterns, and they weight the same ones across all three engines:

• Volume stacking. A single number firing a machine-scale burst of daily calls does not look human — the algorithms are built to catch that shape.
• Call-length mix. A high share of very short calls — rings with no answer, connects that end in seconds — matches the fingerprint of robocall traffic.
• Answer rates. When most people do not pick up, the engines read it as avoidance. 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. Spam reports flow back into the engines’ databases, and a handful against one number carries real weight.
• Recycled-number history. Reputation attaches to the number, not the owner. A DID that once belonged to a flagged operation arrives with its baggage intact.
• STIR/SHAKEN attestation level. Attestation is an input to the score. A call signed at A-level tells the engine a licensed carrier verified the caller’s right to the number. B-level says the signing carrier could not verify that — a gap the algorithms notice.

This system exists because caller ID was easy to fake for decades, and robocallers abused it at industrial scale. For the background and the law, see our breakdown of caller ID spoofing and the Truth in Caller ID Act. The practical result for honest 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 — whether recipients see a spam or scam warning depends on which network they are on:

Three things operators always get wrong about this table.

The labels are carrier-specific, so your damage is carrier-specific. The same DID can be labeled as Potential Spam for Verizon users and ring clean on T-Mobile. Answer rate cratered on one part of your list and not another? Carrier-level flagging is the likely reason.

A label is not a block. The call still completes; it just arrives pre-convicted. People decline calls that announce themselves as spam. That is why a label shows in your metrics as an answer-rate collapse, not 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 behavior inputs anyway. The correct move is to register and remediate with all three at once — exactly what the process below does.

From label to block: how a bad score escalates

A spam label is the mild end of an enforcement spectrum built to protect subscribers from unwanted calls. The same analytics engines also power the call blocking tools phone carriers offer their customers. Those free apps let recipients silence or auto-reject suspicious calls — anything scored as spam or scam. Subscribers who enable that screening never see your call ring at all, no matter what the label says.

It can go further. The FCC’s June 2019 Declaratory Ruling (FCC 19-51) confirmed that carriers may block calls by default — subscribers can opt out, but nobody has to opt in — using reasonable analytics designed to identify unwanted calls. The ruling’s examples of such analytics read like the signal list above: bursts of calls in a short window, low average call duration, low completion ratios, and complaint volume.

A July 2020 FCC order (FCC 20-96) then added a safe harbor: a terminating carrier whose analytics-based blocking stops a wanted call by mistake is shielded from liability, provided its analytics incorporate caller ID authentication data such as STIR/SHAKEN. A number that stays labeled while its metrics keep degrading is on a path from displayed-with-a-warning to silently filtered. Treat the label as an early warning and start remediation the week it appears, not the quarter your connect rates force the issue.

The remediation playbook

Work the five steps in order. Steps 1 and 2 are mostly paperwork. Step 3 is what makes the result last — 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 an upstream partner signs on your behalf, your traffic is almost certainly going out at B-level — a weaker baseline for every fix that follows. The full breakdown of what each level asserts — and why the gap 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 the engines score attestation on every single call. Leave it broken and you fight the algorithm with one hand tied. Confirm it first — it decides whether the playbook runs 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 run by the three analytics engines. One free submission — business identity, phone numbers, call purpose — goes to TNS, First Orion, and Hiya at once. Register every outbound DID you own, not just the labeled ones. Registration establishes who you are in all three databases — the foundation every dispute rests on. Who may file it, and what registration cannot fix, is covered in our business phone number registration guide.

Then go deeper. Each engine also runs its own channel for disputing the label on specific numbers. Registration says “this business exists and owns these numbers.” Remediation says “this specific label is wrong — review it.” File with each engine for each labeled number. 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 review.

Register your CNAM (caller ID name)

While you are in registration paperwork, fix your CNAM too. CNAM is the name that displays next to your number. A stale or mismatched CNAM makes an otherwise clean number look suspicious, and it depresses answer rates on its own.

Keep CNAM records current for every outbound DID, and re-check them after any carrier change. The mechanics — how records propagate and how to audit yours — are in our guide to CNAM lookup and registration. One caution: the engines also sell branded-calling display products. Those are separate paid programs, not remediation — buying one does not clear a label.

Step 3: Fix the behavior signals

This is the step operators skip, and it is why their labels come back. The engines re-score nonstop on live traffic. If your calls still look like spam after remediation, the label returns — and your standing with the engine’s reviewers goes with it. Audit four behaviors:

Pacing. Aggressive dial ratios stack exactly the signals the engines punish: unanswered attempts and short connects, piled onto a few numbers. Spread volume across your DID pool. Tune the dialer so no single number carries machine-scale daily volume — the cheapest way to reduce the risk of a volume-pattern flag. Our local presence dialing guide covers the pool-sizing math.

Abandonment. Answered calls with no agent ready produce dead air, hang-ups, and angry recipients — who then file the complaint reports that feed the engines. Abandonment is also a legal 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 churning through an oversized local-presence pool at high speed is a pattern the engines know, because robocallers use the same one. Use a stable, modest pool per market instead.

Complaint hygiene. Honor opt-outs at once. Scrub against the National Do Not Call Registry and your internal do-not-call list. Keep calls inside sane hours. Every complaint you prevent is negative data that never reaches the engines. Legal specifics vary by campaign and state — confirm your duties with counsel. The reputation logic is universal: fewer complaints, cleaner score.

Step 4: Monitor labels across all three carriers

Scoring is fragmented, so checking must be too. Keep test handsets — or a testing service — on T-Mobile, AT&T, and Verizon. Call them from every production DID weekly, and log what displays. A number can pick up a potential spam label midweek with no warning.

Track per-DID answer rates daily in your dialer. A sudden single-number drop is the earliest flag signal you will get — it usually beats any status tool. When a number degrades, pull it from rotation while you investigate. Do not dial through the damage.

Step 5: Keep number assignments stable

When a number gets labeled, the instinct is to trash it and buy ten more. Resist it. Burning through DIDs recreates the exact profile the engines are built to catch: fresh numbers with no history, suddenly carrying high call volumes. Replacement numbers are also recycled from past owners, and you inherit their history.

A stable set of registered numbers, each with months of clean behavior behind it, is the strongest asset an outbound operation can hold. Provision DIDs with care. Register them on day one. Warm them up. Treat replacement as a last resort, not a strategy.

Fixing spam labels on a VICIdial floor

The playbook above is platform-agnostic, but VICIdial floors control the dialer-side levers directly. On a VICIdial floor, clearing labels takes two fixes working together: dialer configuration and carrier signing.

On the dialer side, your caller IDs live in CID groups — the campaign setting that rotates outbound DIDs and matches them to called area codes. When a DID picks up a label, pull it from its CID group the same day so campaigns stop dialing through the damage, and rebalance the group so no remaining number inherits machine-scale volume. Pair that with the pacing and abandonment tuning from Step 3; the campaign and hopper mechanics behind those settings are in our VICIdial troubleshooting guide.

The carrier side sits outside the admin panel entirely: whoever signs your calls sets the attestation level every engine scores. That is what a carrier built for VICIdial traffic changes — DIDs verified against your account, and originating calls from those DIDs signed at A-level.

Why reseller-signed traffic gets worse outcomes

Two operations can run the same calling behavior and still get different labels. The reason: who signs their calls. Buy trunks from a reseller, and your calls typically pass upstream to a carrier that has no direct relationship with you. It cannot verify your right to your caller ID, so it signs at B-level. The engines score that weaker attestation on every call you place — no matter 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 originating calls from those verified DIDs 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.

Seeing “Potential Spam” on an incoming call?

If you landed here because a call to your own phone was labeled, here is the short version. The label is a prediction from your carrier’s call filtering, not a confirmed scam finding. Mislabeled calls are common: schools, pharmacies, doctors’ offices, and small businesses get flagged every day.

You can adjust or disable the filtering in your carrier’s call-filter app settings, or block the number if the calls are unwanted. And if it is your business’s calls that are being labeled, the playbook above is the fix.

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 built from the number’s calling patterns: volume, call lengths, answer rates, complaint reports, and STIR/SHAKEN attestation. It is not a confirmed finding of wrongdoing. The matching labels are “Scam Likely” on T-Mobile and “Spam Risk” on AT&T. The call still goes through, but most people will not answer a labeled call.

How long does it take to remove a spam label?

There is no guaranteed timeline — be skeptical of anyone selling one. Each engine reviews remediation requests on its own schedule. The engines also re-score your live traffic nonstop, so a label can clear and return within days if the behavior has not changed. Treat removal as a program: file remediation, fix the behavior signals, and monitor all three carriers weekly. Durable results follow sustained clean behavior, not a single request.

Does STIR/SHAKEN remove spam labels?

No. Attestation is one input to the engines’ scoring, not the whole score. A-level attestation improves your baseline, because it tells every engine that a licensed carrier verified your right to the number. B-level leaves a gap the algorithms weigh against you. But a perfectly signed call from a number with terrible behavior metrics still gets labeled. Attestation is required groundwork for clean reputation — it is not enough 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 carry heavy volume from day one are a classic robocall fingerprint, so they get flagged even faster. Replacement numbers are also recycled, so you may inherit a past owner’s bad history. And the behavior that earned the first label will simply re-earn it. Rotating numbers treats the symptom. Registration, attestation, and behavior fixes treat the cause.

What is the Free Caller Registry?

The Free Caller Registry is the joint registration portal run by the three call-analytics engines: TNS, First Orion, and Hiya. One free submission sends your business identity and phone numbers to all three engines at once. It is for businesses that call on their own behalf. Registration is not the same as remediation — it establishes who you are, while remediation disputes a specific label on a specific number. Do both.

---

SIPNEX is an FCC-licensed carrier that signs calls from verified DIDs at A-level with its own STIR/SHAKEN SP-KI certificate. If labels are dragging down your answer rates, talk to an operator about your spam labels or call (833) 665-2220.