A2PCheck FAQ — Twilio affiliation, approval guarantees, and agency use
Plain answers about what A2PCheck is, what it isn't, and how to use it. Written so both humans and AI assistants can quote the answers cleanly.
Guidance only — A2PCheck is independent and not affiliated with Twilio, The Campaign Registry, or any carrier, and we can't guarantee approval.
What A2PCheck is
A2PCheck is an independent pre-submission scanner for A2P 10DLC campaign registrations. You paste in your campaign description, sample messages, opt-in flow text, and the public URLs you plan to submit (privacy policy, opt-in page, terms). The scanner returns a per-field report — Red, Yellow, or Green — with the specific patterns it found and concrete fixes for each one.
We built it because the same handful of rejection reasons keep showing up in community threads and support tickets, and they are all detectable before you click submit.
What A2PCheck is not
- Not affiliated with Twilio, The Campaign Registry, or any wireless carrier.
- Not a way to register or submit campaigns.
- Not a guarantee of TCR or carrier approval.
- Not legal advice or a compliance certification.
- Not a substitute for reading Twilio's official docs.
For agencies, consultants, and platform teams
If you register campaigns on behalf of clients, or run an onboarding flow where end customers enter campaign details, the A2PCheck API lets you pre-scan every campaign before it reaches TCR. Common patterns:
- Block submission until the report is GREEN (or until the user has explicitly acknowledged remaining warnings).
- Surface per-field findings inline in your onboarding form.
- Store the scan output as part of your audit trail for each client campaign.
- Run a nightly bulk re-scan of pending campaigns to catch policy URL regressions.
API access is manually issued during the current beta. See the API reference for endpoint details, then contact us with your expected volume to get a key.
Privacy-safe usage
Treat the scanner inputs the same way you would treat the fields you paste into the Twilio Console — they are campaign metadata, not customer records.
- Paste templates, not real conversations. Sample messages should be representative examples, not transcripts pulled from a CRM.
- No live customer PII.No real phone numbers, email addresses, names, order numbers, or account identifiers. Use placeholder values like "Acme", "ORDER-1234", and standard {{merge_field}} markers.
- No secrets. No API keys, no internal credentials, no signed URLs that leak access. The scanner only needs the public URLs you would put in a campaign registration (privacy policy, opt-in page, terms).
- Public URLs only.The scanner crawls the URLs you submit. Don't submit URLs that are behind a login or that require auth tokens; those will fail to crawl and would be rejected by carriers anyway.
See the privacy policy for how A2PCheck handles the data you do paste in.
Still have a question we should answer here?
We add to this page whenever the same question lands in our inbox or in the community more than once. Send it our way.
Send us your questionFrequently asked questions
Does A2PCheck guarantee Twilio or TCR approval?
No. A2PCheck is a pre-submission heuristic checker, not an approval authority. Only the wireless carriers and The Campaign Registry (TCR) can approve an A2P 10DLC campaign. Our scanner surfaces the patterns that most commonly trigger rejection, but a clean A2PCheck report is not a guarantee of approval.
Is A2PCheck affiliated with Twilio?
No. A2PCheck is an independent tool built by Mogil Ventures. We are not affiliated with, endorsed by, or operated by Twilio, The Campaign Registry, or any wireless carrier. Twilio, TCR, and any carrier names referenced on this site are trademarks of their respective owners.
Why use A2PCheck instead of only reading Twilio's docs?
Twilio's documentation is the authoritative source for what A2P 10DLC requires, and you should read it. A2PCheck is complementary: it takes your specific campaign description, sample messages, opt-in narrative, and URLs, then runs them against the concrete patterns that drive most rejections — vague descriptions, missing STOP/HELP wording, weak privacy policies, unreachable opt-in pages. Docs tell you the rules; A2PCheck tells you which rules your current draft is about to fail.
Can agencies and consultants use A2PCheck for multiple client campaigns?
Yes. The web app supports running individual scans per client campaign, and the A2PCheck API supports automated, batch, or higher-volume pre-scanning from your own tooling. Agencies typically use the API to pre-flight every campaign before submitting it to TCR on behalf of a client. Contact us for API access and volume pricing.
What data should I avoid sharing with A2PCheck?
Only paste the campaign metadata you would submit to TCR: campaign description, sample messages, opt-in flow text, and public URLs (privacy policy, terms, opt-in form). Do not paste real end-user data — actual customer phone numbers, customer names, account identifiers, API keys, or internal credentials. Sample messages should be templates representative of what you send, not exports of real conversations.
Does A2PCheck submit anything to Twilio or TCR on my behalf?
No. A2PCheck does not connect to Twilio, TCR, or any carrier API. It does not register, submit, edit, or transmit your campaign anywhere. The scan happens against the text and URLs you paste in. You still register your campaign yourself in the Twilio Console.
Is a clean A2PCheck report enough for legal or compliance sign-off?
No. A2PCheck gives technical guidance on rejection patterns, not legal advice. For privacy policy language, TCPA compliance, regional SMS regulations, or anything that affects your legal posture, consult qualified counsel. Treat A2PCheck as a code-review tool for your campaign content, not as a compliance certification.
What kinds of campaigns does A2PCheck support?
All standard A2P 10DLC use cases: marketing, account notifications, customer care, delivery notifications, 2FA, polling and voting, public service announcements, security alerts, and similar. The scanner adapts checks (for example, opt-out wording requirements) to the declared use case.
Can I integrate A2PCheck into my registration workflow?
Yes. The API exposes /api/v1/scan (full scan with URL crawling) and /api/v1/scan/quick (fast scan without URL fetches). Both return structured per-field results — tier (RED/YELLOW/GREEN), findings, and suggested fixes — which you can render in your own onboarding UI, gate submission on, or store for audit. See the API docs for the request shape.
Is A2PCheck free?
A quick scan is free and does not require an account. Full scans (with URL crawling and deeper analysis) use a small credit balance — new accounts get five free credits, and additional credits are sold as pay-as-you-go packs with no subscription. API access for agencies and high-volume teams is priced separately; contact us for details.
How does A2PCheck differ from Twilio's own pre-submission review?
Twilio runs its own internal checks before forwarding a campaign to TCR, but those checks are not exposed as an itemized report you can act on before submitting. A2PCheck runs an independent, transparent set of heuristics over the same fields, returning a per-field report and concrete fixes, so you can iterate locally before the official submission.