Twilio A2P 10DLC registration checker — pre-scan before you submit

Registering A2P 10DLC in Twilio is often where teams discover their campaign description, sample messages, consent flow, or policy URLs are not ready for carrier review. Pre-scan the packet before you submit it in Twilio Console.

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

Free — no signup required

Pre-scan your Twilio 10DLC campaign

Paste the campaign details you plan to submit through Twilio Console. A2PCheck checks for common carrier/TCR rejection patterns before you submit. Free, no signup.

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

Where A2PCheck fits in the Twilio registration flow

Twilio documents the A2P 10DLC registration flow for business profiles, brands, campaigns, and ISV/customer onboarding. A2PCheck does not replace Twilio's registration process; it checks the campaign materials you plan to submit so common content and evidence issues are caught first. Use the official Twilio documentation for provider-specific submission steps; use A2PCheck to review whether the campaign packet itself is coherent before it reaches carrier review.

Official provider reference: Twilio A2P 10DLC docs.

What is reviewed before a 10DLC campaign is accepted

Twilio routes US long-code business texting through A2P 10DLC registration and carrier/TCR review.
The review depends on both business identity details and campaign-level materials such as descriptions, samples, opt-in flow, and policy URLs.
ISVs registering customers through Twilio still need clean customer campaign packets before submission.

Common risks to fix before submitting through Twilio

The campaign description is vague about who receives messages, why they receive them, and how often messages are sent.
Sample messages do not include a recognizable brand name, opt-out language, or the expected rate/help disclosures.
The opt-in flow does not quote the consent language users actually see before receiving SMS/MMS.
The website, privacy policy, terms, or opt-in URL is unreachable, generic, or inconsistent with the campaign use case.

Twilio pre-submission checklist

Campaign description names the brand, audience, use case, message frequency, and consent path.
At least two realistic sample messages include brand context, STOP/HELP language, and rate disclosure where appropriate.
Opt-in flow explains the exact page, form, checkbox, keyword, or offline process where consent is captured.
Privacy policy and terms are public and include SMS-specific disclosures, including no sale/sharing of phone numbers for marketing.
Rejection fixes are applied to the full packet before resubmitting through the provider portal or API.

Useful A2PCheck guides before you resubmit

If the scan flags sample copy, use the sample message checklist. If consent is weak, review opt-in flow examples. If policy evidence is missing, use the privacy policy requirements. If this is a rejected campaign, walk through the resubmission checklist. For broader context, start with what A2P verification means or the A2P wizard.

Do not treat provider registration as copy cleanup

The provider portal or API captures your campaign details, but the approval decision depends on whether the story is specific, consistent, and backed by consent/policy evidence. Fixing one field while leaving the rest inconsistent is how teams end up in repeated rejection loops.

Frequently asked questions

Is A2PCheck affiliated with Twilio?

No. A2PCheck is independent and is not affiliated with Twilio, Twilio, The Campaign Registry, or any carrier. Use the official Twilio registration flow to submit; use A2PCheck to pre-check the campaign packet first.

Can this guarantee my Twilio campaign is approved?

No. Carriers and TCR may apply additional unpublished checks. A2PCheck catches common, documented readiness issues so you can fix weak evidence before submitting or resubmitting.

What should I paste into the scanner?

Paste the same campaign description, sample messages, opt-in flow, business website, privacy policy, and terms URLs you plan to submit through your provider. Do not paste end-user PII.

Check my Twilio campaign All provider checkers