Who puts the label there
"Spam Likely", "Scam Likely" and similar warnings are added by the recipient's carrier, usually based on scores from a call analytics company. Your voice provider doesn't apply them and usually can't remove them directly. Because the label appears only on the recipient's screen, the business placing the call never sees it. All it notices is that fewer people pick up.
According to Hiya, the three major US carriers each rely on a different engine: Hiya for AT&T, First Orion for T-Mobile, and TNS for Verizon. Each scores numbers independently, so a number can be labeled on one carrier and clean on the others. Phone makers and third-party apps may run their own screening on top.
SHAKEN/STIR attestation is one input, not a pass
SHAKEN/STIR signs each call with an attestation level that says how well the originating provider knows the caller. Full attestation (A) helps. Partial (B) or gateway (C) attestation makes a label more likely.
But attestation only says the caller is entitled to use the number. It says nothing about whether the calls are wanted. A fully attested number that places hundreds of short, unanswered calls can still be labeled. The FCC's 2019 ruling on call blocking listed whether the originating provider signs calls under SHAKEN/STIR as one factor among many that analytics may weigh.
Call patterns that trigger labels
In the same 2019 ruling, the FCC gave examples of factors a reasonable analytics program might use. They map closely to what gets business numbers labeled:
- Large bursts of calls in a short time from one number.
- Low average call duration.
- Low call completion ratios, meaning most calls go unanswered.
- A high volume of complaints about the number.
- Sequential dialing patterns.
- Neighbor spoofing patterns, where the caller ID shares the recipient's area code and prefix.
- Calls to numbers on the National Do Not Call Registry.
Why platform calls are especially exposed
Several features platforms build line up with the FCC's list. Reminder calls fire for a whole day of appointments at once, which is a burst. Automated calls that reach voicemail and hang up have short durations. A new number has no history, so a few complaints weigh heavily. And calls using a caller ID the provider doesn't host tend to get partial attestation.
None of this means the calls are unwanted. It means they look like unwanted calls to a system that only sees patterns, so the fix is to change the pattern where you can and give the engines more context where you can't.
- Spread automated calls over time instead of sending them in one batch.
- Call during reasonable local hours for the recipient.
- Leave a short voicemail that names the business rather than hanging up.
- Make sure the number accepts callbacks and reaches the business. A number that can't be called back looks suspicious to people and to analytics.
- Honor requests to stop calling across every feature that places calls.
Register numbers with the analytics engines
Hiya, First Orion and TNS run the Free Caller Registry, a free form where a business submits its numbers, business details, call purpose and monthly call volume. Registration gives the engines context. It doesn't guarantee a clean label, and Hiya says registering the same numbers repeatedly is not a fix.
The form asks for the business name, address and website, a contact, the call purpose and calls per month. Numbers can be added one at a time, up to 20, or uploaded as a file. The registry also says registration data isn't used to display caller name, so it doesn't replace CNAM.
There's a catch for platforms. The registry says it's only for businesses calling on their own behalf. Service providers and third parties registering numbers for another business are told to contact the analytics providers directly. A platform can't simply bulk-register every customer's numbers through the free form. It needs to work with the engines directly, or through a provider that does.
Branded calling and caller name
Showing the business name helps people answer. Classic caller name (CNAM) is a short name looked up by the recipient's carrier, and display depends on carrier and device.
CNAM and spam labels are separate systems. A registered name doesn't remove a label, and on some phones the warning replaces the name entirely, so fix the label first.
Branded Calling ID, an industry program governed by CTIA, carries a verified name, and in some cases a logo and call reason, with the signed call. Carrier support has been expanding, with Verizon going live in 2025, but display still varies by carrier and handset. Treat it as an improvement for some recipients, not a guaranteed fix.
Labeled versus blocked
A label still lets the call ring. A block stops it. FCC rules require providers that block calls to give callers a point of contact for blocking disputes at no charge. In February 2025 the FCC also made SIP code 603+ the code providers must return when they block a call based on analytics, so callers learn the call was blocked.
If a business reports that calls ring once and drop, or never ring at all, check the call logs for blocking codes before assuming it's a label. A label shows up as low answer rates on calls that did ring. A block shows up as failed calls with a reason code. The fixes overlap, but disputes go to different places: the analytics engine for a label, the blocking provider's point of contact for a block.
Remediation for a platform with many businesses
- Find out which numbers are affected and on which carriers. Labels are invisible to the caller, so check rather than wait for complaints.
- Confirm the business is registered for call signing and every one of its numbers is attached, including recently added ones.
- Look at the number's calling pattern: volume per hour, answer rate, average duration. Fix the pattern first or the label returns.
- File remediation with each analytics engine that labeled the number, using the business's details and call purpose.
- Register the business's caller name so recipients see who is calling.
- If a number stays labeled after the pattern is fixed, replacing it can be faster than disputing. Don't rotate numbers to dodge labels, which itself looks like spam.
- Track answer rates per number before and after remediation. Each engine updates on its own schedule, so measure on each carrier rather than assuming one fix cleared them all.
How Wirebird handles it
Wirebird registers each business for SHAKEN/STIR call signing and attaches every number automatically, including new ones. We register caller ID names per business, check your customers' numbers for spam labels on a schedule, and alert you by webhook and email when one is flagged. Where carriers allow it, we file the remediation request, so a flagged number can be fixed or swapped before the business notices its calls going unanswered.
Sources
- Hiya: What Free Caller Registry is and what it does
- Free Caller Registry
- FCC 19-51: Declaratory Ruling on call blocking (June 2019)
- FCC 25-15: Eighth Report and Order on robocalls (February 2025)
- Federal Register: Call blocking safe harbor and redress (2020)
- FCC: Combating spoofed robocalls with caller ID authentication
- TransNexus: Exchanging BCID calls with Verizon