10DLC compliance checker — pre-scan before you submit

Run a 10DLC compliance check before submitting your A2P SMS campaign. A2PCheck scans the full campaign packet — description, sample messages, opt-in consent, privacy policy, and website URLs — against the patterns that commonly trigger TCR and carrier rejection.

Guidance only — A2PCheck is independent and not affiliated with Twilio, The Campaign Registry, or any carrier, and we can't guarantee approval.

Free — no signup required

Free 10DLC compliance check

Paste your campaign description, sample messages, opt-in flow, and policy URLs. The scanner flags compliance gaps before you submit to your provider.

Independent pre-submission check

No Twilio or TCR submission

Use campaign metadata, not customer PII

Use representative templates and public URLs only. Do not paste real customer phone numbers, customer records, API keys, or internal/signed URLs.

New here? Try a realistic example

Load a complete, carrier-friendly campaign to scan in one click — then tweak it for your own.

Campaign Info

Basic details about your messaging campaign.

Use Case Type *

Business Name

Campaign Description *

0 characters — Too short — describe who opts in, what you send, and how often.

Sample Messages

Provide at least 2 example messages you'll send.

STOP foundHELP foundchecked across your keywords & messages

Opt-In / Message Flow

How users consent to receive your messages.

Message Flow / Opt-In Description *

Consent evidence readiness

Describe where and how subscribers consent — name the opt-in location and the consent language they agree to.

Name the opt-in location (web form, checkout, keyword, QR code, paper form, etc.).
Spell out the consent language — what the subscriber explicitly agrees to.
State the message frequency (e.g. recurring, varies, msgs/month).
Include a "Message and data rates may apply" disclosure.
Link a privacy policy describing how you handle subscriber data.
Clarify that consent isn't a condition of purchase, where that applies.
Capture and retain opt-in evidence (timestamp, source URL, exact consent text/screenshot) for each subscriber.

Guidance only — consent requirements can vary by use case and jurisdiction.

or sign up to run a Full scan

What the compliance check covers

Campaign description: audience, declared use case, message content, sending frequency, and brand clarity.
Sample messages: brand prefix, specific content, opt-out wording, rate disclosure, and URL quality.
Opt-in / consent path: where consent is captured, the exact consent language, and a confirmation step.
Privacy policy: SMS-specific data-use disclosure, no-sale-of-phone-numbers statement, and reachable URL.
Website match: brand, use case, and messaging type must be consistent across the campaign and website.
Restricted-content flags: SHAFT categories, high-risk lending, generic short links, and missing disclosures.

Compliance is a campaign-packet problem, not a message-body problem

Carriers and TCR don't only inspect whether one message contains STOP wording or SHAFT keywords. They compare each field against the others: does the description match what the website offers? Do the sample messages reflect the opt-in flow that was described? Is there a live privacy policy with SMS-specific language? A compliance check that looks at only one message misses the cross-field failures that cause most rejections.

Common compliance gaps

Campaign description is too vague — 'sending promotional messages' without specifying what or to whom.
Sample messages omit a brand prefix or opt-out wording, making the use case unverifiable.
Opt-in flow description doesn't specify where on the website consent is collected.
Privacy policy has no SMS-specific language or the URL is behind a login wall.
Website doesn't mention the business category or messaging program the campaign claims.

Fix the highest-priority gaps first

If your scan returns a RED result on sample messages, use the sample message checklist. If opt-in evidence is weak, review opt-in flow examples. If the privacy policy is missing SMS-specific disclosures, see the privacy policy requirements guide. If this campaign was already rejected, follow the resubmission checklist.

Frequently asked questions

What does 10DLC compliance mean?

10DLC compliance refers to meeting the evidence requirements that The Campaign Registry (TCR) and carriers evaluate when reviewing an A2P SMS campaign registration: a clear description, representative sample messages, documented opt-in consent, a reachable privacy policy with SMS-specific disclosures, and a website that matches the campaign's declared use case. Compliance is about the campaign packet as a whole, not just one message body.

Does passing this compliance check guarantee carrier approval?

No. TCR and carriers apply additional unpublished criteria and may request manual review. The checker reduces avoidable rejections by surfacing common evidence gaps before you submit, but it cannot guarantee approval. A2PCheck is independent and not affiliated with Twilio, TCR, or any carrier.

Is this only for Twilio 10DLC campaigns?

No. The compliance evidence TCR and carriers evaluate is the same regardless of which provider you register through. A2PCheck works for campaigns submitted via Twilio, Telnyx, Vonage, Plivo, Bandwidth, and others that route A2P 10DLC traffic through TCR.

How is this different from checking just one SMS message?

A single-message checker can flag missing STOP wording or SHAFT keywords, but carrier review compares that message against your campaign description, opt-in path, privacy policy, and website. A2PCheck evaluates the full campaign packet together so cross-field mismatches don't slip through.

What should I paste into the scanner?

Paste the same content you plan to submit in your provider portal: campaign description, two or more sample messages, a description of your opt-in flow, and your website, privacy policy, and terms URLs. Do not paste end-user PII or real customer messages.

Run a free compliance check 10DLC checker