Why Your 10DLC Campaign Got Rejected (and How to Fix Every Reason)

A 10DLC rejection feels opaque (a terse reason code after two weeks of waiting), but the underlying causes are remarkably formulaic. A handful of issues cover nearly every rejected campaign, and each has a known fix. Find yours below, fix it completely, and resubmit once; every blind resubmission costs another full review cycle.

First: is it even fixable?

Rejections split into two families. Resubmittable: privacy policy, opt-in, description, link, and mismatch issues, which you fix and resubmit. Non-resubmittable: fraud/high-risk determinations and prohibited content (SHAFT, restricted industries). These usually cannot be cured by edits, and if you believe the determination is wrong, escalate through your provider’s support rather than resubmitting. The fixes below address the resubmittable family.

Cause 1: Privacy policy failures (the #1 reason)

The reviewer opened your website and your privacy policy was missing, unreachable, or silent on SMS. Most specifically: carriers require language stating that SMS opt-in data is not shared with third parties for marketing purposes.

Fix: publish a policy on your live site that covers SMS data collection and use, and add the non-sharing sentence, e.g.:

Text messaging originator opt-in data and consent will not be shared with any third parties for marketing or promotional purposes.

Full requirements and template language in our privacy policy guide.

Cause 2: Vague campaign description

"Marketing messages to customers" tells the reviewer nothing verifiable. Fix: rewrite to answer who sends, to whom, what content, under what consent. The four-part formula with examples is in the description guide.

Cause 3: Opt-in problems

The declared consent flow is missing from your site, vague ("users sign up"), pre-checked, or bundled with unrelated consent. Fix: put a compliant disclosure + unchecked checkbox at every number-collection point, then describe that exact mechanism (with URL) in the registration. Patterns per channel in the opt-in examples guide.

Cause 4: Shortened or mismatched links

Any bit.ly/tinyurl-style public shortener in samples is an automatic rejection; so are links to domains unrelated to your registered website. Fix: full branded domains only, and check the "embedded links" flag when samples contain them.

Cause 5: Business information mismatches

Legal name ≠ IRS record, EIN typo, website that doesn’t obviously belong to the registered entity. Fix: re-verify every identity field against tax documents, and make sure your site’s footer/about page names the registered entity. See brand registration.

Cause 6: Sample message failures

No brand name, no STOP language, samples that don’t match the declared use case. Fix: rebuild samples with the passing-sample anatomy.

Cause 7: Use case / content conflicts

Promotional samples on an Account Notification campaign, or content brushing SHAFT / restricted-industry lines. Fix: re-declare honestly (Marketing or Mixed if any promo exists) or remove the offending content entirely.

The resubmission protocol

1. Read the rejection reason and map it to the causes above.
2. Fix everything questionable in one pass, not just the cited item. Reviewers stop at the first blocking issue; there may be a second one waiting.
3. Verify your website the way the reviewer will: open your own site cold and look for the policy and opt-in language. Or let our free scanner do it in 30 seconds; it checks precisely the causes above.
4. Resubmit once, with the site already fixed and live.

Handled this way, a rejection costs one extra cycle instead of a month of ping-pong.

Frequently asked questions

Where do I see why my Twilio campaign was rejected?

In the Twilio Console under the campaign’s details, the status shows FAILED with a rejection reason/error code from the reviewing DCA. Match that reason against the causes in this guide.

How many times can I resubmit a rejected campaign?

There is no hard public limit, but repeated failures can consume paid review attempts (depending on provider), and chronic failures may require support escalation. Treat resubmissions as expensive: fix comprehensively, resubmit once.

My campaign was rejected for the privacy policy, but I have one. Why?

Existence isn’t sufficient. Common gaps: the policy isn’t linked where the reviewer looked (footer), it never mentions SMS/text messaging data, or it lacks the statement that opt-in data isn’t shared with third parties for marketing. All three must hold.