The Key To Submitting A2P and Getting Accepted

The most common rejection reason, by a wide margin, is this one:

In the submissions we've seen, this is the most common failure by far. It means TCR reviewers visited your opt-in URL and either:

• Couldn't find a clear opt-in form
• The form didn't have explicit SMS consent language
• The opt-in description didn't match what they found
• The opt-in description was too vague

Based on successful approvals, every sample message needs all six of these — not most of them, all of them.

Brand or sender name at the start

❌ "Your appointment is tomorrow at 2pm"

✅ "Northside Medical: Your appointment is tomorrow at 2pm"

A real phone number used naturally in context

❌ Messages will include phone numbers (just checking the box)

✅ "Call us at +1(561) 555-0142 for more information"

A real URL used naturally in context

❌ Messages will include embedded links (just checking the box)

✅ "Visit NorthsideMedical.com to reschedule"

HELP keyword explicitly mentioned

✅ "Reply HELP for help"

STOP keyword explicitly mentioned

✅ "Reply STOP to cancel" or "STOP to opt out"

Message and data rates disclosure

✅ "Msg & data rates may apply"

The winning formula

These are real submissions, not invented examples. Adapt the shape, swap in your own brand, number and domain. In the templates below, [Business Name], [yourdomain] and [phone] are for you to fill in — submit your real name, website and number, not the brackets. Brackets are only for content that changes per message, like [DATE] or [First Name].

This is the field TCR reviewers scrutinize most carefully. The rules:

• Be specific about every method recipients can opt in
• If you mention a web form — the URL must be publicly accessible
• If you mention verbal consent — describe the exact script
• Do NOT describe opt-in methods you don't actually use
• Minimum 40 characters, maximum 2048 characters

For Sole Proprietor campaigns — keep it simple and personal

For Business / Low Volume Mixed campaigns

For Medical / Healthcare campaigns

This is the gold standard — it describes the web form and the verbal script, and it separates consent for Customer Care from consent for Marketing so each declared use case has its own documented opt-in.

TCR reviewers visit your privacy policy URL. It must include this phrase — use it word for word rather than a paraphrase:

Also required on that same page:

• Message frequency disclosure
• "Message and data rates may apply" language
• STOP opt-out instructions
• HELP instructions
• What data you collect and how it's used

The full page-by-page breakdown is in the Privacy Policy Guide.

Read the rejection reason carefully

It tells you exactly what failed. The reason text is the single most useful thing you get out of a rejection — don't skim it.

Fix the specific issue

Don't change things that weren't flagged. Rewriting fields that already passed just gives the next reviewer something new to reject.

Keep the rejection reason with the campaign

Keeping the reason with your campaign notes means the next person to touch the campaign — you, in three weeks — knows what already failed.

Resubmit from where you filed

Filed through Linxi (including a number bought through Linxi): use Update & resubmit in Linxi Settings → Number → Linxi Number or A2P 10DLC Campaign — your earlier answers are kept as a draft. Filed in your own Twilio console: click Fix Campaign there. Either way, do NOT register a new campaign from scratch.

Make only the necessary changes

Edit the flagged fields, leave the rest alone.

Run the pre-submission check before resubmitting

Linxi runs an AI compliance check on your description, samples and opt-in flow before filing; in your own Twilio console, 1console has its own check. Both catch the mechanical problems — missing keywords, under-declared content flags — before a reviewer ever sees them.

Submit and wait 1-3 business days

Low Volume campaigns sometimes clear faster.