Campaign description rejected (Twilio 30886): who, to whom, and why
Short answer
The description must say who is sending, who receives the messages, and why, in plain English, and it must match your brand, use case and samples. One clear paragraph is enough. Don't paste your marketing copy or reuse the message flow text.
What you'll see
| Where | Code | Wording |
|---|---|---|
| Twilio (10DLC) | 30886 | “Campaign vetting rejection - Invalid Campaign Description” |
| Twilio (both) | 30497 | “Use case summary is incomplete or unrelated to the messaging” |
| Twilio (10DLC) | 30910 | “Campaign rejected: A2P 10DLC campaigns must be submitted in English” |
| Twilio (10DLC) | 30912 | “Campaign rejected: A2P 10DLC is for application-to-person messaging only” |
| Bandwidth Proxy, Infobip | 2002 / 2006 | Unclear description / brand named in the description differs from the registered brand or DBA |
| Telnyx, Bandwidth | 506 | Campaign must be in English |
Text in curly quotes is the provider's wording; the rest is our summary.
Why it happens
- Too short or vague: “We send texts to customers.”
- Describes the company, not the messages.
- Names a different business (the agency, a parent company) without explaining the relationship.
- Describes personal or one-to-one texting instead of business messages (P2P).
- Mentions promotions while the use case is informational, or the reverse.
- Not in English, or contains customer names and phone numbers.
How to fix it
- Answer Twilio's three questions:
Who is sending the message? Who is receiving it? Why are they receiving it?
- Name the registered business. If you trade under another name, say so; HighLevel suggests “We are doing DBA as [Business_Name]”.
- List the message types (reminders, order updates, promotions) and how often you send them.
- Say how recipients opted in, in one sentence. The details belong in the message flow.
- If you are a direct lender, include the words “Direct Lending” even for 2FA campaigns (Twilio).
- Write each field for its own purpose. Copying the same paragraph into several fields triggers Twilio 30911.
Gets rejected
Bright Smile is the best dental office in Austin. Call us today!
Gets approved more often
Bright Smile Dental (Bright Smile Dental PLLC), a dental practice in Austin, TX, sends appointment reminders, confirmation requests and rescheduling notices to patients who opted in on our online booking form or patient intake form. Patients receive about 2-4 messages per appointment. Messages are informational and contain no marketing.
The Campaign Registry accepts 40 to 4,096 characters. Twilio's toll-free equivalent is the “use case summary”, and toll-free reviewers reject summaries that are too generic or describe a different program (30497, 30496).
Check before you resubmit. Every rejection costs days, and often another $15 vetting fee. Paste your description, message flow, samples and policy text into the free preflight check, or generate a consistent set with the campaign builder.
Frequently asked questions
How long should the campaign description be?
At least 40 characters (TCR's minimum). In practice, 2-4 sentences that answer who sends, who receives and why are enough.
Should I mention my opt-in method in the description?
One short sentence helps the reviewer connect the fields. Put the full opt-in details, links and disclosure text in the message flow (call to action) field.
What is P2P and why does it get rejected?
Person-to-person means personal, one-to-one conversation, such as a realtor texting from a personal phone. A2P 10DLC is for business messages sent through an application. Describe the business program instead (Twilio 30912, 30533).
Sources
- Twilio: A2P 10DLC Campaign Onboarding Guide (updated 2026-09-24)
- Twilio error 30886 (accessed 2026-10-03)
- Twilio error 30497 (accessed 2026-10-03)
- Twilio error 30911 (accessed 2026-10-03)
- Twilio error 30912 (accessed 2026-10-03)
- Bandwidth: Proxy Connector vetting rejection reasons (2026-03-17)
- Bandwidth: DCA2 vetting rejection reasons (2026-03-17)
- The Campaign Registry: CSP API OpenAPI spec (accessed 2026-10-03)
- HighLevel: How to get your phone number A2P approved in 2026 (modified 2026-07-30)
Rules change often and providers sometimes disagree; where they do, this page says so. This is general information, not legal advice, and no one can guarantee approval. See the disclaimer.
Related problems
- Twilio 30893, 30496, 30499, 30507, 30537, 30916 · DCA 602 · Proxy 2003, 2005, 8001-8004Use case mismatch: when your samples, description and opt-in disagree
- Twilio 30893, 30538, 30499, 30911 · DCA 602, 603 · Proxy 6012-6014 · TCR SAMPLE_MESSAGESample messages rejected: how to write samples reviewers approve
- MESSAGE_FLOW · Twilio 30909, 30896, 30917, 30924 · DCA 806MESSAGE_FLOW rejection: fix an opt-in the reviewer can't verify
- Twilio 30795, 30799, 30796, 30894, 30918, 30898, 30971 · DCA 603, 710, 711, 713 · TCR BRAND_INCONSISTENCIESBrand registration failed: EIN and legal name mismatch (Twilio 30795)
The Approval Kit adds industry template packs, opt-in and policy page templates, and an agency checklist.