How to Fix a Rejected A2P 10DLC Campaign

Receiving a campaign rejection from The Campaign Registry or from a carrier is frustrating but almost always fixable once you understand why the rejection occurred. The challenge is that rejection notices from TCR and carriers are often terse, citing a general policy category rather than a specific fix, which leaves businesses guessing about what to change. Having worked through dozens of A2P 10DLC rejections, the patterns are consistent, and most rejections fall into four primary categories: content policy violations, missing or inadequate opt-in documentation, use case mismatch, and brand information problems.

Content Policy Violations in Sample Messages

The most common campaign rejection reason is sample messages that violate carrier content policies. This includes messages that omit the sender business name, messages without an opt-out instruction for marketing use cases, messages containing URL shorteners such as bit.ly or tinyurl.com, and messages that include language associated with high-risk content categories like gambling, cannabis, payday lending, or adult content. When rejected for content, review each sample message against the CTIA Messaging Principles and Best Practices guidelines and the specific carrier policies listed in Twilio's documentation. Replace any URL shorteners with branded short domains or full URLs, add your business name to every sample message, and append the STOP opt-out instruction where required. After editing, resubmit the campaign without increasing the scope of the use case, as changing use case type on a resubmission resets the review queue.

Inadequate Opt-In Description

The second most common rejection is an opt-in description that does not satisfy carrier requirements for documented consent. A description that says subscribers opted in through our website is insufficient because it does not specify the mechanism, the disclosure language shown to subscribers, or how the consent record is stored. A compliant opt-in description names the specific page or form where consent is collected, quotes or paraphrases the disclosure statement that subscribers see before agreeing, confirms that the form does not pre-check the consent box, and states how records are retained. If you use SMS keyword opt-in such as texting JOIN to a number, describe the keyword, the reply confirmation message that subscribers receive, and whether the subscription is confirmed via double opt-in. Carriers reject campaigns where the opt-in description does not match common legitimate opt-in patterns.

Use Case Mismatch Between Campaign Type and Sample Messages

Registering your campaign under the wrong use case type and then providing sample messages that do not match that use case is a third common rejection path. A campaign registered as account notifications that submits sample messages promoting a sale or including a discount code will be rejected because promotional content belongs in the marketing use case category. Similarly, a customer care campaign that includes upsell language in sample messages creates a mismatch. When fixing a use case mismatch rejection, decide whether to change your use case category to match your actual message content or change your sample messages to match the declared category. Do not do both simultaneously, as layered changes make it harder to identify which change resolved the issue on resubmission.

What to Do If Your Resubmission Is Also Rejected

If your first resubmission is rejected again, request a detailed explanation through Twilio support rather than guessing and resubmitting again. Multiple rejections for the same campaign can flag your brand account for additional scrutiny, which increases the difficulty of future approvals. Twilio's compliance support team has direct lines of communication with TCR and can sometimes obtain specific feedback from carrier reviewers that is not included in the standard rejection notice. In some cases, a campaign that has been rejected twice is better abandoned and replaced with a newly created campaign that addresses all known issues from scratch, rather than resubmitting the same campaign a third time. Document each rejection reason and each change made so that you have a clear record of what was tried if you need to escalate through Twilio support.

Conclusion

A campaign rejection is not the end of your SMS program, but fixing it without understanding the root cause results in repeated rejections that delay your launch further each time. Speak with our compliance team and we will diagnose your rejection, rewrite your submission, and resubmit on your behalf.