Partner Program
IntegrationsCarrier Filtering in 2026: What Gets Your Texts Filtered, and Why Nobody Has to Tell You
Why does a registered, vetted 10DLC campaign still get filtered?
Does the carrier have to tell you why a text was filtered?
What’s the difference between filtered, delivered, and seen?
What actually builds a sending number’s reputation?
What should you fix before your next campaign?
Where does VORTxT fit?
Voice callers got a mandated reason code in March. Text senders got nothing, and the FCC decided that on the record. Here’s what actually happens between send and seen, and what to fix first.
By Robert Moody, Managing Partner and COO, VVP USA. 25 years in telecom infrastructure, carrier relationships, and TCPA/CTIA compliance.
Your campaign is registered. Your brand is vetted. Your customer opted in.
And the message shows “delivered” in your dashboard while the customer never sees it, or it fails with a code that tells you nothing.
Most senders treat that as a black box. After 25 years on the carrier side of this, I can tell you it’s three separate problems wearing one label, and the fix for all three starts in the same place.
Here’s what actually happens between send and seen.
Why does a registered, vetted 10DLC campaign still get filtered?
Because registration gets you in the door and the carrier keeps scoring your traffic after you walk through it. The Campaign Registry doesn’t approve or reject campaigns at all, your CSP and its upstream aggregator do, some use cases go to a separate carrier review, and once you’re live each carrier scores the traffic in real time on complaint rate, opt-out hygiene, content, and volume patterns.
What gets scored after approval:
- Registration fit. Traffic that doesn’t match the registered use case. A campaign approved for appointment reminders that starts sending promotions is the most common post-approval filter I see.
- Content triggers. SHAFT categories and the industries next to them (CBD, gambling, short-term loans), public link shorteners, bare URLs, all caps. Shared shortener domains inherit everyone else’s abuse.
- Volume behavior. A number that goes from a few thousand messages to hundreds of thousands overnight looks exactly like a spam operation, and carriers throttle or filter traffic that ramps that way.
- Consumer signals. STOP replies, 7726 spam forwards, and sends to numbers that are dead, invalid, or reassigned.
- Throughput class. Throughput is assigned per carrier, not per campaign. A TCR-verified brand on the Russell 3000 gets top class on AT&T and Tier TOP on T-Mobile automatically. Everyone else starts at AT&T Class E or F and T-Mobile Tier LOW and has to raise it through a Standard or Enhanced vet scored 0 to 100.Â
Â
Registered doesn’t mean delivered. The carriers are scoring behavior, not paperwork.
Does the carrier have to tell you why a text was filtered?
No, and that is a decision, not an oversight. In its 2023 text-blocking order, the FCC considered requiring text blocking notifications and declined, saying the record showed providers were already giving adequate notice. What it required instead was a point of contact where senders can report erroneous blocking, and providers only have to take complaints from senders who bring documented evidence.
Compare voice. Since March 25, 2026, a call blocked on analytics has to come back with SIP code 603+, a Reason header naming the blocking party, and a redress contact, passed back through every provider in the call path. Text has nothing like it.
What you actually get is a carrier reject code interpreted by whoever sits between you and the carrier. Unregistered traffic comes back as a hard error (one major CPaaS returns it as error 30034). Registered traffic that gets filtered comes back as a generic “filtered” or “undelivered” status, or as “delivered” that never lit up a phone. Textdrip’s founder wrote in Forbes this week that senders call him every week because a campaign got flagged or a number was suspended overnight with no warning.
There’s a structural reason for that. The carrier tells its direct connection what it tells it. Every hop between you and that connection is a place where the reason gets flattened into a status code. Your vendor’s vendor matters, and on SMS there is no rule forcing the reason to survive the trip.
What’s the difference between filtered, delivered, and seen?
Filtered means the carrier didn’t hand it to the phone and you got a code. Delivered means the phone accepted it. Seen means a human looked at it, and since iOS 26, delivered and seen can be a long way apart.
With Screen Unknown Senders turned on, a text from a number the recipient hasn’t saved or replied to goes to a separate Unknown Senders folder and stays there until the person marks the sender as known or adds the contact. Apple ships the setting off by default, but anyone who had the older Filter Unknown Senders setting on in iOS 18 got it switched on automatically when they upgraded. iOS 27 shipped on September 14 and carries the same folder structure forward.
So the carrier reports delivered. Your dashboard reports delivered. The customer’s phone never buzzed. Android’s default spam folder has been doing a quieter version of this for years.
What actually builds a sending number’s reputation?
Complaints, and the behavior that causes them. Every negative signal a carrier scores traces back to a message somebody didn’t want: a STOP, a 7726 forward, a send to a number that was disconnected or reassigned months ago.
Registration, vetting, and clean content all have a ceiling. They tell the carrier who you are. They don’t change what your traffic looks like. If your list includes people who revoked consent, numbers reassigned to strangers, and contacts whose permission ended when their account closed, the complaints will come and the carrier will score them.
The consent rules are getting more granular, not simpler. Since April 2025, a consumer can revoke consent for calls or texts by any reasonable means and you have 10 business days to honor it. The “revoke all” provision, which reads one STOP as covering every message stream from your company, is currently delayed to January 31, 2027. On September 30, 2026, the FCC votes on a draft order that would split revocation into informational and marketing buckets and let callers designate one exclusive opt-out channel. If it passes, it takes effect 30 days after Federal Register publication and replaces the January 2027 date. The same item opens a proposal on faster opt-out processing, mandatory two-way texting, and an automated revoke-all option.
Read that as an engineering requirement. Your system has to know which bucket every message belongs to and route a STOP to the right place, across every number and every vendor you send through. A STOP that lands in one campaign while another campaign keeps sending marketing to the same person is a 7726 complaint you scheduled yourself.
States are stacking on top. Texas now treats text messages as telephone solicitations with statutory penalties up to $1,500 per violation, and Virginia requires text opt-outs to be honored for 10 years.
Carrier filtering is the symptom. Stale consent is the cause.
What should you fix before your next campaign?
Start with what your provider can show you, then registration fit, then visibility on the handset, then the two numbers that move filtering, then consent state. Each one depends on the one before it.
1. Ask your provider what the carrier actually told them. For every filtered message, can they show you the carrier’s response, per carrier and per campaign, not a rolled-up “undelivered”? How many hops sit between them and the carrier? If the answer is a shrug, the reason died somewhere in the chain. Direct carrier connections exist so it doesn’t.
2. Make the registration match reality. One use case per campaign, sample messages that look like what you actually send, opt-in URLs that resolve. Mismatch between the registered flow and the live traffic is the filter you can fix in an afternoon.
3. Get out of the Unknown Senders folder. Design the opt-in so the customer sends the first message (tap-to-text, keyword to join). Attach a contact card to the welcome message and ask them to save it. Reply to their replies. Where your carrier supports RCS for Business, send under a verified sender name and logo instead of a bare 10-digit number. Apple’s own documentation treats RCS Business Messages as a normal category on iPhone now, with availability varying by carrier.
4. Watch opt-out rate and complaint rate per campaign, weekly. Those two numbers are what carriers weight most after approval. A registered campaign with a bad complaint rate still gets filtered, and by the time throughput drops, the carrier has been scoring you for weeks.
5. Fix the consent state before the send, not after the complaint.Scrub against revocations and reassigned numbers before every campaign. Honor STOP across every campaign and every channel it applies to. Build for bucketed revocation now, because the September 30 vote decides the rule you’ll be living under by year end either way. This is the only item on the list that stops feeding the filter instead of arguing with it.
Where does VORTxT fit?
VORTxT is a patented consent compliance platform built by VVP USA that verifies subscriber consent in real time before SMS and MMS messages are sent, processes revocations within the FCC’s 10-business-day window, and keeps an immutable audit trail for TCPA defense. It exists because consent is not a checkbox you collected once. It’s a state that changes every time a customer replies STOP, closes an account, or hands a number back to the carrier, and it’s about to become a state with buckets.
The consent decision has to happen before the send, against a live record. Not get reconstructed after the 7726. That’s why we built it into the aggregation layer, where TxTRIA’s direct carrier connections mean the carrier’s answer comes back to us and not to a reseller three hops up.
Registered, delivered, seen. None of the three happens for a message you shouldn’t have sent.
Built-in. Not bolted-on.
Quick answers
Does the FCC require carriers to tell you when a text is filtered? No. The FCC’s 2023 text-blocking order considered a notification requirement and declined it. Providers must maintain a point of contact for senders to report erroneous blocking with documented evidence, and that’s all.
Does 10DLC registration guarantee delivery? No. Registration is necessary, not sufficient. Carriers keep scoring registered traffic in real time on complaint rate, opt-out rate, content, and volume patterns, and a registered campaign with a bad complaint rate still gets filtered.
What’s the difference between filtered and delivered? Filtered means the carrier rejected the message before it reached the phone and returned a status code. Delivered means the handset accepted it. Neither one tells you whether the customer saw it.
Is Screen Unknown Senders on by default on iPhone? No. It ships off, but anyone who had Filter Unknown Senders on in iOS 18 was switched on automatically at upgrade. When it’s on, texts from unsaved numbers the person hasn’t replied to go to a separate folder with no notification.
When does the TCPA revoke-all rule take effect? As of this writing, January 31, 2027. The FCC votes September 30, 2026 on a draft that would replace it with separate revocation standards for informational and marketing messages, effective 30 days after Federal Register publication if adopted.
