Campaign Auditor — Beta

Stop carrier rejections before they happen.

The #1 reason A2P 10DLC campaigns get rejected by AT&T and T-Mobile is inconsistency between your Campaign Description, Use Case, and Sample Messages. Paste them in below — we'll audit the story before you submit to TCR.

📋

Campaign Description

Must be specific, accurate, and match both the selected use case and your sample messages. Vague descriptions are auto-flagged.

🏷️

Use Case

Your TCR use case category is the box carriers use to route review. Mismatch between category and content = instant rejection.

💬

Sample Messages

Treated as a binding contract by carriers. Must include opt-out language, match your use case, and reflect what you'll actually send.

Campaign Auditor

Enter your campaign details exactly as you plan to submit them to TCR.

Your Mobile Number *

E.164 format — include country code (e.g. +12125551234). Your report link will be delivered here via SMS.

Campaign Information

Carriers use these fields to classify and score your campaign before a human ever sees it.

Campaign Description *0 / 4096

Describe what messages will be sent, to whom, and why. Be specific — carriers reject generic copy. Minimum 40 chars; aim for 200+.

Campaign Use Case *

Choose the single best-fit category. Only pick MIXED if the campaign genuinely spans unrelated use cases — it attracts heavier scrutiny.

Messaging Content

Sample messages are a binding contract with carriers. Content flags affect vetting tier.

Sample Message 10 / 160

Sample Message 20 / 160

Sample Message 3 (optional)0 / 160

Content flags

These disclosures are required by TCR. Enabling a flag doesn't cause rejection — undisclosed flags do.

Embedded links

Messages will include URLs. Samples must contain at least one URL.

Embedded phone numbers

Messages will contain a phone number. Describe why in your campaign description.

Age-gated content

Content restricted to users 18+/21+. Description must reference age verification.

Loan / lending related

Restricted use case — subject to additional TCR vetting and financial compliance review.

Recipient Consent

Critical

This section maps to TCPA compliance. Incomplete or vague consent fields are the primary reason campaigns survive TCR auto-approval but get suspended during carrier audit.

How do end-users opt in to receive messages? *

Describe the exact mechanism and location where consent is collected. TCR reviewers need to be able to mentally picture the opt-in moment. Must be at least 20 characters.

Example: Customers enter their phone number on the checkout page at acme.com and check a box reading: 'I agree to receive order updates via SMS.'

Consent language shown to the user at opt-in

The exact text the user reads before agreeing — e.g. the checkbox label or the terms shown on your SMS sign-up page.

Example: By providing your phone number you agree to receive SMS alerts from Acme Inc. Msg & data rates may apply. Reply STOP to cancel, HELP for help.

Opt-in confirmation message

The SMS sent to the user after they successfully opt in. Should confirm enrollment and remind them how to opt out.

Example: Acme Alerts: You're subscribed! Msg freq varies. Msg & data rates may apply. Reply STOP to unsubscribe, HELP for help.

Opt-out message (STOP response)

The SMS sent when a user texts STOP. Must acknowledge the STOP keyword and confirm unenrollment. This is verified by carriers.

Example: Acme Alerts: You have been unsubscribed. No more messages will be sent. Reply START to resubscribe.

Help message (HELP response)

Sent when a user texts HELP. Must identify the service, explain how to opt out, and provide a support contact. Carrier-verified.

Example: Acme Alerts: Order & shipping notifications. Msg freq varies. For support: acme.com/help or 1-800-555-0100. Reply STOP to cancel.

Opt-in keywords

Comma-separated. Including START or YES is best practice.

Opt-out keywords *

STOP is CTIA-mandated. Must be included.

Help keywords *

HELP is CTIA-mandated. Must be included.

Complete all required fields to continue

This tool is for internal Twilio training purposes only — a2pcampaignhelp.com. Not a substitute for official TCR submission review.