Number reputation · 2026
Your Twilio number shows Spam Likely: the fix, in order
Last updated September 3, 2026
You bought a number, dialled a few hundred prospects, and now a colleague on T-Mobile sees "Scam Likely" when you ring. The advice online is either "register with STIR/SHAKEN" (which does not remove a label) or "buy a new number" (which earns the same label next week). This page is the remediation sequence: who applies the label, the free forms that actually reach them, what to switch on in Twilio, and the behaviour change that makes any of it stick. Checked against Twilio, Hiya and the Free Caller Registry in September 2026.
The short answer
Twilio is not labelling you; three analytics engines are. Hiya scores calls for AT&T, First Orion for T-Mobile, TNS for Verizon. Register at freecallerregistry.com (free, one form, all three), get a Business Profile approved in Twilio Trust Hub and turn on SHAKEN/STIR, CNAM and Voice Integrity, ask Twilio support to escalate, and then keep every number under about 200 dials a day with calls that last longer than a hang-up. Expect two to four weeks. If it does not lift, retire the number from outbound and warm up a fresh one from a pool.
Who applies the label, and why it differs by carrier
When your call leaves Twilio it carries a SHAKEN/STIR signature and lands on the prospect's carrier. That carrier hands the caller ID to an analytics vendor, which returns a verdict: nothing, a name, or a nuisance label. The three vendors that serve the big US mobile networks are Hiya (AT&T), First Orion (T-Mobile) and TNS (Verizon); that mapping comes from the vendors' own announcement of the Free Caller Registry, not from a listicle. Each keeps its own score for your number, built from call patterns, answer rates, call length and consumer reports across everything it sees, so one number can be clean on one network and flagged on another. That is why the first step is to find out which network is labelling you.
Twilio's role is originating carrier. Its support article on blocked and labelled calls is explicit that the label is set downstream and that the fix is to work with the terminating carrier's registry, keep behaviour consistent, and treat SHAKEN/STIR as a long-term answer-rate improvement rather than a label remover. A thread on r/VOIP from a Canadian Twilio customer confirms the practical version: Twilio support told them Twilio was not applying the tag and pointed them at First Orion's CallTransparency and the Free Caller Registry.
The remediation sequence
- Locate the label. Call a handset on each of AT&T, T-Mobile and Verizon (teammates, family, a prepaid SIM) and note exactly what each one shows. "Spam Likely", "Scam Likely" and "Potential Spam" are different verdicts from different engines. The sibling page on how many calls a day before you get flagged covers the checking tools; here you only need to know which network to chase.
- Stop feeding the score. Pause outbound from the flagged number for a day or two while you do the paperwork. Every short, unanswered dial you add now is another data point on the wrong side. Keep the number live for inbound: prospects who call back and get answered are a positive signal.
- File the Free Caller Registry form. One submission at freecallerregistry.com reaches Hiya, First Orion and TNS. You give company name, address, email, website and the numbers you call from. It is free, it is the step every vendor agrees on, and it explicitly does not guarantee anything; the engines describe it as improving the accuracy of their scoring for legitimate callers. Register every number you own, including the ones you have not burned yet.
- Get a Twilio Business Profile approved. In Console → Trust Hub, submit a Primary Business Profile: EIN or DUNS number, a US business address, an authorised representative with a US phone number, and a working HTTPS website. Everything else in Trust Hub hangs off this, and it is the same profile you need for A2P 10DLC texting.
- Turn on SHAKEN/STIR, CNAM and Voice Integrity. With the profile approved, add the SHAKEN/STIR trust product so your calls get A-level attestation (the carrier is told Twilio knows you and you own the number). Set CNAM, which is free and shows your business name on landlines within 48 to 72 hours. Then create a Voice Integrity registration: this is Twilio submitting your numbers to the analytics engines for T-Mobile, Verizon and AT&T on your behalf, which is the closest thing to a direct line to the people scoring you. Branded Calling, which puts your name on T-Mobile and Verizon mobile screens, sits on top of Voice Integrity and is billed only when the brand is delivered.
- Open a Twilio support ticket. Give three or four call SIDs that were labelled, the carrier and label seen, and ask them to escalate to the terminating carrier. The r/twilio thread on this is instructive: one team did every registration, and it took three weeks to discover the carrier itself had been blocking them all along. Support is how you find that out.
- Change the pattern. Registration without a behaviour change is a request the engines will quietly deny. Cap each number at roughly 200 dials a day, spread through the day; let voicemail greetings finish or leave a real message rather than hanging up at three seconds; answer callbacks; scrub the list against the DNC registry so you stop generating reports. The next section has the numbers.
- If it survives three to four weeks, rotate. Retire the number from outbound (keep it for callbacks), buy a fresh local number for $1.15 a month, and warm it up per the warm-up schedule. Twilio also suggests a toll-free caller ID, which is rarely labelled; for cold calls it costs you the local look that gets answered, so treat it as a fallback for reminders and callbacks rather than first touches.
What the fix costs on your own Twilio
| Step | Cost | Time |
|---|---|---|
| Free Caller Registry (Hiya, First Orion, TNS in one form) | $0 | Ten minutes to file; days to weeks to take effect |
| Twilio Trust Hub Business Profile | $0 | EIN or DUNS, US address, HTTPS website; usually a few business days |
| SHAKEN/STIR A-level attestation via Trust Hub | No separate charge we could find | Approval after the profile; signs every call |
| CNAM (caller-ID name, landlines) | $0 per Twilio | 15 characters; 48–72 hours to propagate |
| Voice Integrity (Twilio registers you with the engines) | Fee shown in the console, not on the docs page we checked | Needs the approved profile first |
| Branded Calling (name on T-Mobile and Verizon mobiles) | Billed per delivered call; public beta | Needs approved Voice Integrity |
| A fresh local number to rotate onto | $1.15 per month | Instant; then warm it up |
Prices from Twilio's docs and pricing pages and the Free Caller Registry site, checked September 2026. Because the numbers sit in your own account, all of this is yours to do and keep; a managed line on any vendor, DialSheet's $49-a-month one included, means the vendor holds the attestation and the registrations. Several hosted dialers sell number "whitelisting" as a paid add-on; what they are selling is mostly the registrations above, done for you.
The behaviour that caused it
Hiya publishes the shape of its scoring: maturity (age of the number and whether you keep rotating), connection (answer rate), engagement (how long people stay on) and sentiment (blocks and reports). Every engine weighs roughly the same things. A cold-calling number is weak on all four by construction, which is why the goal is not a perfect score but staying out of the pattern that looks like a robocaller: a fresh number that fires hundreds of calls in a burst, most unanswered, the answered ones lasting seconds.
- Volume per number. Under about 200 dials a day, spread across the day. Twice that on one number is the single most common cause we see.
- Call length. Hanging up the instant voicemail answers produces a stream of three-second calls. Either let the greeting play and drop a message, or use answering-machine detection that hangs up early on your side without connecting.
- Answer rate. A cleaner list raises it. Scrub disconnected numbers before you dial; a 20% answer rate on 150 dials looks much healthier than 8% on 400.
- Callbacks. Forward the number to a phone that gets answered. An inbound call that connects and lasts is the strongest positive signal a number can earn.
- Reports. DNC scrubbing and calling hours. One complaint outweighs a lot of clean dials; see DNC and TCPA compliance.
- Parallel dialers. Two to four simultaneous lines multiply the short-call fingerprint per number. If you run one, run it across a larger pool.
How many numbers keep you under the ceiling
| Team | Dials / day | Numbers at ≤200/day | Per month | With one resting spare per rep |
|---|---|---|---|---|
| 1 rep | 120 | 1 | $1.15 | 2 numbers, $2.30 |
| 1 rep | 300 | 2 | $2.30 | 3 numbers, $3.45 |
| 3 reps | 450 | 3 | $3.45 | 6 numbers, $6.90 |
| 3 reps | 750 | 4 | $4.60 | 7 numbers, $8.05 |
| 5 reps | 1,000 | 5 | $5.75 | 10 numbers, $11.50 |
Numbers at ~$1.15/month each on Twilio. The spare column is the pool model: one number resting and taking callbacks while its twin dials, swapped weekly. On DialSheet the rotation is the local-presence feature; on a hand-built dialer it is a column in a spreadsheet. Either way the whole pool costs less than a single seat on any hosted dialer, which is the argument for owning the numbers.
Prevention checklist for the next number
- Register at the Free Caller Registry and finish Trust Hub (profile, SHAKEN/STIR, CNAM, Voice Integrity) before the first cold dial, not after the first label.
- Warm up over a week or two: known contacts and callbacks first, then volume.
- Keep each number under about 200 dials a day; buy numbers rather than pushing one harder.
- Let voicemails play or leave messages; kill the three-second hang-up habit.
- Forward every number to a phone that answers, and answer it.
- Scrub the list: DNC, disconnected numbers, wrong time zones.
- Recheck the label monthly on all three networks, and rest a number at the first sign.
Own the numbers, own the reputation
DialSheet is a free browser power dialer that runs on your own Twilio account: the numbers, the Trust Hub registrations and the recordings are yours, rotation is built in, and the software is $0 for one person or $29 a month for a 3-seat pack. No credit card.
Start dialingQuestions people actually ask
How do I remove Spam Likely from my Twilio number?
In this order: stop dialing from the number for a day so you stop feeding the score; file the free form at freecallerregistry.com, which goes to all three analytics engines (Hiya, First Orion, TNS) at once; in Twilio Trust Hub get a Business Profile approved, then turn on SHAKEN/STIR A-level attestation and CNAM (both free) and Voice Integrity; open a Twilio support ticket asking them to escalate to the terminating carrier with call examples; then fix the pattern that caused it — keep each number under about 200 dials a day, let voicemails play out, answer callbacks. If the label survives three or four weeks of clean behaviour, retire the number from outbound and warm up a fresh one.
Who actually puts the Spam Likely label on a call?
Not Twilio, and not the FCC. The label is applied on the receiving side by an analytics engine that each US wireless carrier contracts: Hiya for AT&T, First Orion for T-Mobile, and TNS for Verizon (the three vendors say so themselves in the Free Caller Registry launch announcement). Each engine scores your number independently, which is why a number can read Spam Likely on a T-Mobile handset and look clean on Verizon. Twilio is the originating carrier: it signs the call with a SHAKEN/STIR attestation and passes it on, but it does not decide what the handset displays.
What is the Free Caller Registry and does it work?
freecallerregistry.com is a single free form, run jointly by Hiya, First Orion and TNS, that sends your company details (name, address, email, website) and the list of numbers you call from to all three engines. It is the one step every remediation guide agrees on, and it costs nothing. It is not an allowlist: the engines say registration improves the accuracy of their scoring but does not guarantee a number will never be labelled, and re-submitting a flagged number does not clean it. Register before you start calling, not after the label appears, and keep dialing behaviour consistent with what you registered.
Will SHAKEN/STIR or CNAM remove a spam label?
No, and Twilio says as much in its own support article. SHAKEN/STIR attestation tells the receiving carrier that Twilio knows who you are and that you have the right to use the number (level A). It can earn a Verified label and it stops your calls being treated as possibly spoofed, but the spam score is a separate system driven by call behaviour and complaints. CNAM only sets the name shown on landlines. Both are worth turning on because they are free and they raise answer rates, but they are inputs to reputation, not an eraser for it.
What calling behaviour gets a number flagged?
Hiya describes its scoring as four factors: maturity (how long the number has been in use, and whether you rotate constantly), connection (answer rate), engagement (how long people stay on the line) and sentiment (blocks and reports). Cold calling is bad at all four by nature: a new number, lots of unanswered dials, short calls, and the occasional report. The controllable parts are volume per number (stay under about 200 dials a day), call length (let voicemail greetings finish rather than hanging up at three seconds), spreading dials through the day instead of bursts, and answering when prospects call back.
Should I just buy a new Twilio number instead?
A fresh number costs $1.15 a month, so it is the cheapest fix and Twilio lists it as a legitimate option. But a new number dialled the same way earns the same label — people on r/sales report a fresh number showing as probable scam within a week. Rotate only after you have registered your numbers and changed the pattern, keep the old number alive so callbacks still reach you, and warm the new one up over a week or two. A pool of numbers you rotate through, each under the daily ceiling, is the durable version of this.
Does a toll-free number avoid Spam Likely?
Twilio suggests a toll-free caller ID because toll-free numbers are treated differently by the carriers and are labelled far less often. For cold calling it is a trade: the label problem shrinks, but an 800 or 888 number on a mobile screen looks like a call centre and answer rates for local-looking numbers are consistently better. It is a reasonable choice for appointment reminders and customer-service callbacks, and a poor one for a first cold touch where the whole game is looking like a neighbour.
Sources checked September 2026:
- Twilio: outbound calls blocked or labelled as spam or scam likely
- Twilio docs: Voice Integrity
- Twilio docs: trusted calling with SHAKEN/STIR
- Free Caller Registry
- First Orion, Hiya and TNS: launch announcement naming the carrier each serves
- r/VOIP: how to stop my Twilio number showing as spam
- r/twilio: Twilio calls being marked as spam
Related reading: