10DLC SMS validator — validate your campaign before submission
Validate your A2P 10DLC SMS campaign against common carrier and TCR rejection patterns before you submit. The validator reviews the full campaign packet — not just one message — so you can fix consent gaps, sample issues, and policy problems before they cost you a rejection.
Guidance only — A2PCheck is independent and not affiliated with Twilio, The Campaign Registry, or any carrier, and we can't guarantee approval.
Free 10DLC SMS validator
Paste your campaign description, sample messages, opt-in flow description, and policy URLs. Get a RED / YELLOW / GREEN readiness verdict before you submit to your provider.
What the SMS validator reviews
- Campaign description: use case, audience, declared content, and sending frequency — not just a name.
- Sample messages: brand identifier, specific content, opt-out language (STOP/HELP), and rate disclosure.
- Opt-in flow: where and how users consent, exact consent copy, and whether confirmation is documented.
- Privacy policy: SMS data-use language, no-sale-of-phone-numbers statement, and reachable public URL.
- Terms of service: present and accessible, not login-gated.
- Website and URL match: brand and use case consistent between the campaign packet and the linked site.
- Restricted-content signals: SHAFT categories, deceptive framing, or high-risk-lending indicators.
Full-packet validation, not one-message scanning
Many tools check whether a single SMS body contains certain keywords or opt-out phrases. That matters, but A2P 10DLC registration review compares your messages against the campaign description you submitted, the opt-in flow you described, the privacy policy your URL resolves to, and the content on your website. A2PCheck validates that the whole packet is internally consistent before it goes in front of a reviewer.
Common validation failures
Sample message mismatch
Messages don't match the declared use case. A campaign registered as 'order updates' that submits promotional copy will be flagged.
Missing opt-out wording
Promotional samples without 'Reply STOP to opt out' are a common rejection trigger. Transactional samples have more flexibility but still require a brand prefix.
Privacy policy gaps
A policy without SMS-specific data-use language, or one that's behind a login, gives reviewers nothing to validate against.
Brand not identified
Samples that don't open with a brand name (e.g. 'Acme:') make it impossible for a reviewer to confirm who sent the message.
Generic short links
Links via bit.ly, t.co, or other generic shorteners are flagged because carriers can't inspect the destination domain.
After the validation report
RED on sample messages? See the sample message checker and the sample message checklist. Consent evidence weak? Opt-in flow examples show what documented consent looks like. Privacy policy issues? The privacy policy requirements guide covers exactly what SMS-specific disclosures carriers expect.
Frequently asked questions
What does a 10DLC SMS validator check?
A 10DLC SMS validator reviews the campaign packet submitted for A2P registration: campaign description, sample messages, opt-in flow, privacy policy URL, terms URL, website, and restricted-content signals. The goal is to surface patterns that commonly lead to TCR or carrier rejection before you submit.
Is this the same as a message-body spam checker?
No. Spam filters look at whether one message contains certain keywords or link patterns. This validator looks at how all campaign fields relate to each other — whether the description matches the samples, whether the opt-in flow is documented, whether the policy has SMS-specific language. Those cross-field relationships are what A2P 10DLC review actually scrutinizes.
Can the validator guarantee carrier approval?
No. Carriers and TCR apply additional unpublished criteria and may conduct manual review. The validator reduces avoidable rejections by catching common evidence gaps before you submit. A2PCheck is independent and not affiliated with Twilio, TCR, or any carrier.
What inputs do I need for the validator?
Paste the same content you'd enter in your provider portal: the campaign description, at least two sample messages, a description of your opt-in flow, and URLs for your website, privacy policy, and terms of service. Do not paste real customer messages or PII.
Does it work for providers other than Twilio?
Yes. TCR and carrier review criteria apply across providers that route A2P 10DLC traffic through TCR, including Telnyx, Vonage, Plivo, and Bandwidth. The validator applies the same packet-level checks regardless of which provider you plan to register through.