A2P SMS testing — pre-test your 10DLC campaign before carriers do
A2P SMS testing is the pre-submission pass you run before carriers review your 10DLC campaign. Check the campaign packet now so Twilio / TCR are not the first ones to find weak samples, missing consent, or broken policy URLs.
Guidance only — A2PCheck is independent and not affiliated with Twilio, The Campaign Registry, or any carrier, and we can't guarantee approval.
Run a pre-submission SMS test
Paste the fields you plan to submit. A2PCheck tests the campaign packet for common 10DLC rejection patterns before you send it to Twilio. Free, no signup.
The five checks to run before submission
1. Test that the use case matches the actual messages
Marketing, account notifications, appointment reminders, and mixed-use traffic are reviewed differently. If your campaign says transactional but your samples include offers, carriers treat that as a mismatch.
2. Test the sample messages like a carrier reviewer
Every sample should include a recognizable brand, specific content, and the right opt-out / HELP / rate-disclosure language for the use case. Placeholder copy is one of the easiest failures to catch before submission.
3. Test the opt-in evidence
The campaign should explain exactly where the user gives consent, quote the consent language, and match the web form or keyword flow a reviewer can inspect. “Users sign up on our website” is not enough.
4. Test the public URLs
Open the website, opt-in page, privacy policy, and terms in a private browser. They should be public, crawlable, and visibly mention SMS/messaging where relevant — no login walls, 404s, or generic policies.
5. Test the resubmission packet
If you were rejected already, test the fixed campaign as a complete packet: updated description, samples, opt-in evidence, policy URLs, and a short note explaining what changed.
Pre-submission testing vs. live delivery testing
A2PCheck is for pre-submission readiness: it checks the fields that decide whether your campaign gets approved. After approval, you should still run live SMS tests for STOP/HELP handling, suppression, delivery, latency, and drift. Keep those motions separate: check before launch here, monitor after launch elsewhere.
Try a weak sample message
This sample looks harmless, but it is missing brand context and does not prove the campaign has a clear, registered use case. Run it to see how the scanner flags weak evidence.
What to read next
If the test fails on message copy, use the sample message checklist. If it fails on consent, use the opt-in flow examples. If your privacy policy is weak, review the privacy policy requirements. Already rejected? Work through the resubmission checklist.
Frequently asked questions
What does A2P SMS testing mean?
It means dry-running the campaign fields carriers and TCR review — description, use case, sample messages, opt-in flow, and policy URLs — before submitting them through Twilio. It is not a live deliverability test after launch.
Can I send real test messages instead?
Sending test SMS can verify your application flow, but it does not catch the registration issues that cause A2P 10DLC rejection. You need both: pre-submission content/readiness checks, then post-approval delivery monitoring.
Does A2PCheck test voice calls?
No. A2PCheck focuses on SMS/MMS campaign readiness for A2P 10DLC. Voice calling uses separate compliance and caller-ID frameworks, so a voice or call test is outside this scanner's scope.
Should agencies test every client campaign?
Yes. Agencies submitting many campaigns should run the same pre-submission tests on each client campaign and keep a readiness record so resubmissions are faster and more consistent.