A2P 10DLC opt-in / consent rejection — how to fix it
Opt-in rejections happen when the campaign does not prove that recipients knowingly agreed to receive SMS. Generic phrases like “users sign up on our website” usually are not enough.
Guidance only — A2PCheck is independent and not affiliated with Twilio, The Campaign Registry, or any carrier, and we can't guarantee approval.
What this rejection usually means
The consent path is missing, too vague, not publicly verifiable, or does not include the disclosures reviewers expect before someone receives SMS/MMS.
Why reviewers care
A2P 10DLC review is partly about preventing unwanted messaging. Reviewers need to see where consent happens, what language users see, whether the checkbox or keyword is explicit, and how opt-out/help expectations are disclosed.
Common rejection wording
- “opt in consent rejected”
- “message flow opt in rejected”
- “users sign up on our website rejection”
- “10DLC consent evidence”
Bad vs. better
Weak submission pattern
Customers opt in when they create an account or buy something.
Stronger submission pattern
Customers opt in at https://acme.example/checkout by checking an unchecked box next to: 'Text me order updates and occasional offers from Acme. Msg & data rates may apply. Msg frequency varies. Reply STOP to opt out, HELP for help.' The privacy policy and terms are linked next to the checkbox.
Fix checklist before resubmitting
- Name the exact web page, keyword flow, paper form, QR code, or offline process where consent is captured.
- Quote the consent language users see before messages start.
- State whether the checkbox is unchecked by default or how the keyword opt-in is confirmed.
- Include message frequency, STOP/HELP, and msg&data rates disclosures where appropriate.
- Link to privacy policy and terms from the opt-in surface.
- Capture/retain evidence such as URL, timestamp, source, and screenshot for each subscriber.
Related A2PCheck guides
Concrete examples for web forms, checkboxes, and keyword opt-in.
Consent and privacy disclosures are reviewed together.
Map the rejection category to the right fix path.
Carriers re-review the whole packet, not just one field.
Dry-run the campaign before your next submission.
Fix the full packet, not just the cited field
A rejection reason is a starting point, not the whole review. Before resubmitting, run the full campaign through the scanner and walk the resubmission checklist. Description, samples, consent, privacy, terms, and URLs should all tell the same story.
Frequently asked questions
What does an A2P 10DLC opt-in consent rejection mean?
The consent path is missing, too vague, not publicly verifiable, or does not include the disclosures reviewers expect before someone receives SMS/MMS.
Can A2PCheck guarantee approval after I fix it?
No. A2PCheck is independent and is not affiliated with Twilio, The Campaign Registry, or any carrier. It catches common readiness issues, but providers and carriers may apply additional review checks.
Should I resubmit after changing only this one field?
Usually no. Carriers re-review the full campaign packet, so fix the cited issue and then re-check the description, samples, opt-in evidence, privacy policy, terms, and website URLs before resubmitting.
Check for opt-in consent issues
Paste the campaign packet you plan to submit or resubmit. A2PCheck checks the description, sample messages, opt-in flow, and URLs for common rejection patterns. Free, no signup.