Fixing Twilio A2P rejection for opt-in SMS campaigns (checklist + alternatives)
Getting rejected from Twilio A2P (10DLC)? This checklist covers opt-in proof, compliance language, sample message fixes, and fallback SMS options.
TABLE OF CONTENTS
Twilio A2P (10DLC) rejections almost always come down to (1) unclear/insufficient opt-in proof, (2) missing/incorrect compliance language (STOP/HELP, message frequency, “Msg & data rates may apply”), or (3) campaign details that don’t match your real message flow. Use the checklist below to tighten your submission, then resubmit.
What “A2P rejection” usually means
A2P 10DLC is the US carrier compliance process for application-to-person texting. A rejection usually means: “we don’t have enough evidence that the recipient explicitly agreed to receive these messages, and that they can easily stop receiving them.”
A2P rejection troubleshooting checklist (copy/paste)
1) Confirm you’re registering the right campaign type
- Customer care vs marketing matters. If you're sending appointment/service updates, it should be customer-care/notifications (not promotional marketing).
- Make sure the campaign description matches the actual usage (who sends, why, and what kinds of messages).
2) Tighten your opt-in proof (this is the #1 failure point)
Your goal: make it obvious to a reviewer how a specific person gives consent.
- Use an explicit checkbox (unchecked by default). Avoid “By submitting you agree…” hidden language.
- Put the key consent language right next to the checkbox, not only in a privacy policy.
- The checkbox text should clearly state:
- what messages they’ll receive (e.g., “appointment reminders”, “service updates”)
- who is sending (your brand name)
- If a property manager is providing numbers for tenants (third-party consent), you’re in a higher-risk zone:
- Best: collect opt-in directly from the tenant (a short form + checkbox) before sending recurring messages.
- If you must rely on third-party-provided numbers, make your opt-in language extremely clear about who consented and on behalf of whom — and expect more scrutiny.
3) Make sure your privacy policy + terms are reachable
- Include links to Privacy Policy and Terms wherever opt-in happens (form, checkout, intake page).
- Ensure those pages are public and not behind a login.
4) Fix your sample messages (reviewers check these closely)
Include sample messages that look like what you’ll actually send.
- Avoid “spammy” language (all-caps, excessive urgency, lots of links).
- Include brand identification in the body when appropriate.
- Keep your use case consistent across all fields.
5) Required compliance keywords & auto-responses
Even if your platform handles these, your registration should reflect them.
- STOP: opt-out keyword
- HELP: help keyword
- Opt-in confirmation (for recurring programs)
Your message copy should include (where appropriate):
- “Reply STOP to opt out”
- “Reply HELP for help”
- “Msg & data rates may apply”
- Frequency expectations (“Up to X msgs/month” or “Message frequency varies”)
6) Data consistency checks (easy-to-miss rejection triggers)
- Company/brand name matches across: website, campaign submission, message samples, and opt-in pages.
- URLs match (no typos, no redirects to dead pages).
- Use-case matches the message flow (don’t describe marketing if you’re sending appointment notices).
If you keep getting rejected: practical fallback options
Option A: Use a different SMS provider (still requires compliance)
If you’ve been rejected multiple times, sometimes it’s faster to try a new provider and re-register cleanly (new campaign, updated copy, cleaner opt-in proof). You’ll still need compliance, but reviewers/providers can vary in strictness.
Option B: “SMS by Zapier” for very low volume alerts (not customer messaging)
If the goal is internal alerts (texting your team) rather than texting customers, SMS by Zapier can work — but it has strict limitations and is not designed for customer-facing campaigns:
- ~15 messages per hour (account-wide) — check current Zapier limits
- US/Canada only
- confirmed numbers only
- delivery issues reported with some carriers (including T-Mobile) due to A2P filtering
If you want to explore Zapier-first workflows, see Zapier.
Option C: Use a dedicated business phone/SMS platform + Zapier
For customer texting workflows, a dedicated platform is the right long-term path. Connex has existing Zapier + business-SMS workflows documented (example: How to Send SMS from Pipedrive Using OpenPhone and Zapier).
Quick “submission ready” opt-in checkbox example (template language)
Use legal review if needed, but this is a practical starting point:
- Checkbox label: “I agree to receive SMS appointment reminders and service updates from [Brand Name]. Message frequency varies. Msg & data rates may apply. Reply STOP to opt out, HELP for help.”
Get help getting your SMS campaigns approved
Twilio A2P rejections are frustrating — but most are fixable with tighter opt-in documentation and consistent campaign details. If you need help getting your SMS messaging approved and building the end-to-end workflow in Zapier, Twilio, or a dedicated SMS platform, book a free discovery call with Connex.
