Free 10DLC compliance checker — campaign readiness scan
Run a practical 10DLC check before you submit an A2P SMS campaign. A2PCheck reviews the campaign packet — not just one message — for the consent, sample, policy, URL, and restricted-content issues that commonly lead to rejection.
Guidance only — A2PCheck is independent and not affiliated with Twilio, The Campaign Registry, any provider, or any carrier, and we can't guarantee approval.
Free 10DLC campaign checker
Paste the description, sample messages, opt-in flow, and policy URLs you plan to submit. The scanner flags likely rejection risks before you send the campaign to your provider.
What this 10DLC check covers
- Campaign description: audience, use case, message purpose, and sending frequency.
- Sample messages: brand prefix, STOP/HELP language, rate disclosure, and concrete copy.
- Opt-in evidence: where consent is captured, the exact consent text, and confirmation step.
- Website and policy URLs: public pages, SMS-specific privacy language, and matching brand/use case.
- Risk flags: SHAFT/restricted content, generic short links, mismatched URLs, or missing disclosures.
More than an SMS validator
Some tools focus on whether one SMS contains STOP/HELP, links, or SHAFT keywords. Those checks matter, but carrier review also compares the message to your campaign description, consent path, privacy policy, terms, and website. A2PCheck is built for that fuller campaign-readiness check.
| Check area | Basic SMS validator | A2PCheck |
|---|---|---|
| Sample message text | Yes | Yes |
| SHAFT / restricted-content flags | Yes | Yes |
| STOP / HELP and opt-out wording | Yes | Yes |
| Campaign description clarity | Limited | Yes |
| Opt-in flow and consent evidence | Limited | Yes |
| Privacy policy and terms URLs | Limited | Yes |
| Website / brand / use-case fit | Limited | Yes |
Common 10DLC checks
10DLC compliance checker
Review the full campaign packet before submission.
10DLC SMS validator
Focus on sample copy, STOP/HELP, risky links, and message-use-case fit.
10DLC sample message checker
Check representative campaign samples with bad-vs-good examples.
10DLC opt-in examples
Fix weak consent language before it becomes a rejection reason.
10DLC privacy policy requirements
Add SMS-specific disclosure and no-sale language reviewers expect.
Best fit
- Twilio, Telnyx, Vonage, Plivo, or Bandwidth teams preparing a 10DLC submission.
- Agencies checking client campaigns before resubmitting after a carrier/TCR rejection.
- Builders who need a fast 10DLC check before they spend time in a provider portal.
Try a deliberately weak campaign
The fastest way to understand the report is to scan a weak example: vague description, generic samples, missing opt-out language, and weak policy evidence.
Before you submit or resubmit
If your scan flags sample copy, use the sample message checklist. If consent evidence is weak, review opt-in flow examples. If the privacy policy is missing SMS language, use the privacy policy requirements. If this campaign has already been rejected, follow the resubmission checklist.
Frequently asked questions
What does a 10DLC checker look for?
A useful 10DLC checker reviews the same evidence carriers and TCR reviewers look at: campaign description, sample messages, opt-in flow, privacy policy, terms, website fit, and restricted-content flags. A2PCheck does that without asking for end-user PII.
Is this only for Twilio 10DLC campaigns?
No. A2PCheck started with Twilio wording because many teams submit through Twilio, but the campaign-readiness checks apply across providers that route A2P 10DLC traffic through carrier/TCR review, including Telnyx, Vonage, Plivo, and Bandwidth.
Can a 10DLC check guarantee approval?
No. Carriers and TCR can apply unpublished or provider-specific review criteria. The scanner reduces avoidable rejections by catching common evidence gaps before you submit, but it cannot guarantee approval.
Should I paste real customer phone numbers or messages?
No. Paste campaign-level details only: representative sample messages, URLs, opt-in description, and use-case metadata. Do not paste end-user PII or secrets.