Pre-scan your A2P 10DLC campaign before you resubmit
If your campaign was rejected, the most common reasons are predictable: vague campaign descriptions, sample messages without opt-out language, opt-in flows that aren't described in enough detail, and missing privacy / terms URLs on the website you point to. This scanner checks for those patterns in seconds — free, no signup required for a quick scan.
A2PCheck is not affiliated with Twilio, The Campaign Registry, or any carrier.We can't guarantee approval — only carriers and TCR can do that. This tool runs the same kinds of heuristic checks the community keeps rediscovering in rejection threads.
Guidance only, not legal advice.
Common Twilio / TCR rejection patterns this scanner checks for
- Vague campaign description."Marketing messages" is the canonical rejection. Carriers want specifics: who you message, how they consented, what the content is, and how often.
- Sample messages missing opt-out wording.Every promotional sample typically needs "Reply STOP to opt out" and message frequency / Msg&data disclosures.
- Opt-in flow described in one sentence.If you wrote "website signup" you'll get bounced. You need URL of the form, the exact consent text, and a screenshot-quality narrative.
- Privacy policy / terms URLs missing or thin. Your privacy policy needs to disclose SMS data collection and state that mobile opt-in data isn't shared with third parties.
- Use-case mismatch."Mixed" is a frequent trap — pick the narrowest use case that fits.
From the community
Folks on r/twilio keep posting the same handful of rejection reasons. A pre-scan against those patterns won't catch everything Twilio or TCR checks internally, but it covers the ones that show up week after week.
Sample message checklist
Concrete bad / good examples for the two required samples.
Opt-in flow examples
Web form, checkout, keyword opt-in, and verbal — what to describe.