Why 10DLC campaigns get rejected (and how to fix each one)

Plain-English explanations of the most common A2P 10DLC rejection reasons, drawn from provider documentation. Fix every listed reason before resubmitting.

• Opt-in flow can't be verified
  Reviewers couldn't see how a person agrees to receive your texts. If they can't find or reproduce the consent step, they…
• Call-to-action missing required disclosures
  The consent language exists, but it leaves out the details carriers expect: brand name, what messages are for, frequency…
• Website doesn't match the business or use case
  The website listed is unreachable, belongs to a different business, or doesn't show the product or service the texts are…
• Privacy policy or terms missing or inaccessible
  Reviewers couldn't load a privacy policy or terms page, or the policy doesn't cover SMS.…
• Sample messages don't match the stated use case
  The sample texts look different from the campaign description (e.g. a ‘customer care’ campaign with promotional samples)…
• Campaign description is vague or incomplete
  The description doesn't explain who is texting whom, why, and how they opted in.…
• Wrong use case selected
  The use case chosen doesn't fit the messages. Carriers check that the use case aligns with your description and samples;…
• Brand details don't match tax records (EIN mismatch)
  The legal name, EIN or address you entered doesn't match what verification systems have on file, or the EIN is too new t…
• DBA / brand name inconsistency
  The trade name used in messages, website and the registration doesn't line up with the legal entity, so reviewers can't …
• Prohibited or high-risk content
  The campaign involves content carriers restrict, such as SHAFT categories (sex, hate, alcohol, firearms, tobacco), canna…