A2P 10DLC sample message rejection — how to fix it
Sample messages are the reviewer’s closest proxy for what subscribers will actually receive. If they look generic, omit opt-out language, hide links, or do not match the selected use case, the campaign can be rejected even when the description sounds fine.
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 submitted examples do not prove compliant, expected traffic: missing brand identity, no STOP/HELP language where needed, vague placeholders, mismatched use case, or risky links/phone numbers.
Why reviewers care
Carriers use sample messages to detect spam patterns, prohibited content, misleading consent, and whether the declared use case matches the real traffic. Realistic examples reduce ambiguity.
Common rejection wording
- “A2P sample messages rejected”
- “missing opt out in sample message”
- “10DLC sample message examples rejected”
- “Twilio sample messages rejection”
Bad vs. better
Weak submission pattern
Huge sale today! Click bit.ly/acme-sale. Reply stop.
Stronger submission pattern
Acme Fitness: Summer membership sale ends Friday. Save 20% on annual plans at https://acme.example/summer. Msg freq varies. Msg&data rates may apply. Reply STOP to opt out, HELP for help.
Fix checklist before resubmitting
- Start each message with the brand or a clearly recognizable sender identity.
- Use realistic message content rather than placeholders or lorem ipsum.
- Include Reply STOP/HELP language and rate/frequency disclosure when appropriate for the use case.
- Use branded domains instead of generic link shorteners.
- Make sure the samples match the selected campaign use case.
- Set embedded link/phone flags honestly if samples contain them.
Related A2PCheck guides
Bad-vs-good examples and a copy-paste checklist.
Some sample messages reveal prohibited or restricted content.
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 sample messages rejection mean?
The submitted examples do not prove compliant, expected traffic: missing brand identity, no STOP/HELP language where needed, vague placeholders, mismatched use case, or risky links/phone numbers.
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 sample message 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.
Your own campaign
Scan the packet you plan to submit. After the verdict, use the result action to save the report with your account.
Client campaigns
Run the same scan one client campaign at a time and keep the saved report with the handoff. Do not include recipient data.