Skip to content
WirebirdTalk to sales

Why registered texts still get filtered, and how to fix it

An approved campaign doesn't guarantee delivery. Carriers still filter messages for content, volume and sending patterns, and each provider reports it with its own error codes. This guide covers how to read those codes, what triggers filtering, and a step-by-step way to find and fix the cause for one business or many.

Updated

Registered is not the same as delivered

10DLC registration tells carriers who is sending and why. It doesn't exempt the traffic from filtering. Carriers and providers keep scanning messages for spam, phishing and content that doesn't match the registered campaign, and they enforce volume limits tied to the brand.

On a platform, filtering usually shows up as one business saying its texts "aren't going through" while everyone else is fine. The cause is almost always in that business's content, volume or registration state, so start there.

Filtering also isn't always visible. Some filtered messages come back with a clear error. Others are reported as sent and simply never arrive, which is why a business's own reports of "my clients aren't getting texts" deserve a look even when your logs are clean.

Read the error code first

Every provider returns a code on undelivered messages. The code tells you which kind of problem you have. Common ones from Twilio and Bandwidth:

  • Twilio 30007, message filtered: blocked by Twilio or a carrier as spam or for violating policy.
  • Twilio 30034, message from an unregistered number: the sending number isn't attached to an approved 10DLC campaign.
  • Twilio 30035, number still being configured: the number was just added to a campaign and its registration hasn't finished.
  • Twilio 30023, daily message cap reached: the brand used up its T-Mobile daily allowance.
  • Twilio 30022, rate limits exceeded: traffic went faster than the campaign's allowed throughput.
  • Twilio 30003, 30005, 30006: unreachable handset, unknown number or landline. These are usually about the recipient, not filtering.
  • Bandwidth 4470 and 4770: rejected as spam by Bandwidth or by the carrier.
  • Bandwidth 4771: rejected because of a shortened URL.
  • Bandwidth 4476: the source number isn't registered to a 10DLC campaign.
  • Bandwidth 4780 and 4781: T-Mobile or AT&T volume violation.

Content that triggers filters

Filters look at what the message says and where it links. The common triggers:

  • Public URL shorteners: CTIA's messaging principles say senders using a shortener should use one dedicated to their exclusive use. Shared shorteners like bit.ly are a frequent cause of blocks and of campaign rejections.
  • Links that hide the sender: CTIA says links should unambiguously identify the website owner. A link to an unrelated domain looks like phishing.
  • Phone numbers in the message that forward to unpublished numbers, unless the owner is clearly named.
  • SHAFT content (sex, hate, alcohol, firearms, tobacco) and cannabis, which carriers restrict or prohibit for most senders.
  • Content that drifts from the registered use case, such as promotions sent on a campaign registered for appointment reminders.
  • Messages that look like phishing: urgent account warnings, requests for codes or card numbers, or a missing business name.

Volume and pattern triggers

T-Mobile sets a daily cap per brand, shared across every campaign and every provider that brand uses. Twilio notes the cap is tied to the EIN and resets at midnight Pacific time. Once it's spent, further messages to T-Mobile subscribers fail until the reset. AT&T limits campaigns to a rate per minute based on use case and vetting score.

Sending pattern matters too. CTIA's principles say senders should not engage in snowshoeing, which means spreading similar messages across many numbers to dodge filters. Adding numbers to a campaign to push more volume can make filtering worse, not better.

A burst also raises opt-outs and spam reports, which carriers watch. A business that imports an old list and blasts it is the classic case.

Registration and number states

Some failures look like filtering but are really setup problems. They tend to appear right after a business goes live or changes its numbers.

  • A number added to a campaign isn't usable right away. Twilio returns 30035 while registration with the carriers finishes, and 30024 can appear while a newly registered sender is still being provisioned.
  • Moving a number between campaigns, or removing and re-adding it, restarts registration. Repeated changes extend the wait.
  • Sole proprietor campaigns allow one number. With Twilio, extra numbers added to a sole proprietor campaign stay unregistered and fail with 30034.
  • Toll-free numbers need their own verification. Twilio blocks unverified toll-free traffic to the US and Canada with 30032.

Opt-outs that look like failures

Some rejections are the system working. Bandwidth returns 4475 and 4775 when a recipient has opted out of the sender. CTIA's principles say opt-outs should be honored for plain-language requests like stop, end, unsubscribe, cancel and quit, not only the exact keyword, with one final confirmation message.

If a business keeps sending to people who opted out, carriers see complaints and the problem turns into real filtering. One suppression list per business, checked on every send from every feature, prevents it.

A step-by-step diagnosis

  1. Pull the error codes for the failed messages and group them. One code dominating tells you the category.
  2. If the codes say unregistered or still configuring, check that the number is attached to an approved campaign and that its registration has finished.
  3. If the codes say filtered or spam, read the actual message bodies. Look for shorteners, unfamiliar domains, missing business name and content outside the use case.
  4. Compare the failing messages to the campaign's sample messages. Large differences are a red flag.
  5. If the codes point to volume, check the brand's T-Mobile daily usage and how fast messages left your queue.
  6. Check whether failures are concentrated on one carrier. That points to a carrier-specific limit or filter.
  7. Send a controlled test of a plain message to a few consenting numbers. If plain text delivers and the real message doesn't, it's the content.

Fixing it and escalating

Most fixes are content fixes: full links on the business's own domain, the business name in every message, and messages that match the registered use case. If the business has really changed what it sends, register a campaign for the new use case instead of stretching the old one.

Retrying a filtered message unchanged rarely helps and adds to the pattern carriers are reacting to. Change the content first, then resend to a small group and watch the results before sending the rest.

For volume problems, pace sends to stay inside the campaign's rate, spread large sends across days, and consider a better vetting score if the business routinely needs more. See the throughput guide for the numbers.

If you believe messages are being filtered wrongly, escalate with evidence. Twilio asks for three or more message SIDs that failed with 30007 so its team can review them. Other providers ask for similar examples.

How Wirebird handles it

Wirebird reports delivery per tenant across your platform, so a business whose messages are failing stands out instead of showing up as a support ticket. Delivery events arrive through signed webhooks with the tenant on every event. Numbers are registered before a business can text, and every send is checked against consent, opt-out status and quiet hours, which removes two common causes of failed messages before anything leaves.

Sources

Rather not run this yourself?

Wirebird files, tracks and fixes registrations for every business on your platform.