10DLC rejection reasons · Critical
Opt-in / consent not described
Unclear or unverifiable opt-in is the number-one reason 10DLC campaigns get rejected. Here is how to describe consent so a reviewer can approve it.
Not sure this is your reason? Paste your rejection into the free lookup →
Rejection said “The opt-in workflow / call-to-action is not clearly described”? Decode that exact wording →
Haven't submitted yet? Start your registration, the guided pre-submission flow →
When a carrier reviews your campaign, they are trying to answer one question: can this business prove that every person it texts actually agreed to be texted? If your registration only says something like "customers give us their number," that does not prove consent. A phone number is not permission. The reviewer cannot see the moment a customer opted in, so you have to describe it in enough detail that they can picture it and, ideally, verify it.
A passing opt-in description names the exact place consent is collected (a specific web form, a keyword, a checkbox at checkout, a paper form), states that the customer takes a deliberate action to agree, and confirms the consent is not bundled with anything else. "Consent is not a condition of purchase" is a phrase reviewers look for. If your opt-in happens on a website, the consent language and a link to your privacy policy must be visible next to the field, not hidden behind a link, and the page must be live so the reviewer can load it.
The fastest way to fix this rejection is to rewrite the opt-in description with those specifics and attach a screenshot of the actual consent moment. Paste your rejection reason into Fix and it will rebuild the opt-in language for you, matched to the method you actually use.
The fix
Describe the opt-in method in detail (web form, keyword, point of sale, paper form) and capture a screenshot of the exact CTA. Consent must be explicit and not bundled with other terms.
Paste your rejection and rebuild the package →Rejected on a specific provider?
Same reason, walked through for your provider's dashboard.
Common questions
What counts as verifiable opt-in for 10DLC?
A deliberate customer action to agree to texts, collected at a specific, describable place (a web form checkbox, a text-in keyword, a point-of-sale prompt, or a signed paper form), with the consent language visible and not bundled with a purchase. You should be able to show a screenshot of that moment.
Is having a customer's phone number enough to text them?
No. Possessing a number is not consent. The customer has to have explicitly agreed to receive text messages, and your campaign has to describe how and where that agreement was captured.