Error 30886: Campaign Description Rejected
Your campaign description did not clearly say who sends the messages, who receives them and why. Here is how to rewrite it so reviewers approve.
Why Descriptions Get Rejected
What does 30886 mean?
The campaign description is not clear about the sender, the recipients and the purpose, or it does not match the rest of the registration.
What causes it?
A vague description, one that does not match the use case, sample messages, brand or website, or a platform naming itself instead of the business that actually sends.
How do I fix it?
Rewrite it to state who sends, who receives and why, keep it consistent with your use case and samples, and use the registered business name.
Do I need a new campaign?
Usually not. Edit the failed campaign and resubmit. Create a new one only if the use case itself is wrong.
What Does Error 30886 Mean?
Error 30886 means an A2P 10DLC campaign was rejected during vetting because its Campaign Description does not clearly explain the messaging program. Reviewers need to read who is sending, who receives the messages and why they are sent, and to see that this matches the use case, the sample messages and the registered brand. If any part is vague or missing, the campaign fails with 30886.
Twilio lists the usual reasons in its error reference:
- The description is too vague or incomplete.
- It leaves out the sender, the recipients or the purpose.
- It does not match the selected use case.
- It does not match the sample messages, brand name or website.
- A platform or ISV registered for a customer and named itself instead of the business that actually sends the texts.
- It includes personal information instead of a summary of the program.
How Do You Write a Campaign Description That Passes?
A description that passes answers three questions in plain sentences: who sends the messages, who receives them, and why. It names the registered business, says how recipients opted in, and describes the real messages in a way that matches the selected use case and the sample messages word for word in substance.
| Part | Weak | Strong |
|---|---|---|
| Who sends | “We send texts.” | “Riverside Dental (the registered brand) sends texts.” |
| Who receives | “To customers.” | “To patients who gave their mobile number on our booking form and checked the SMS consent box.” |
| Why | “For marketing and updates.” | “Appointment reminders, rescheduling links and replies to patient questions.” |
The example business is illustrative. Use your own registered name and your real program. If you send promotions as well, select a use case that covers them and say so in the description, because a reminder-only description will not support marketing samples.
Our guide to campaign descriptions and sample messages covers the samples side in detail.
How Do You Fix Error 30886 and Resubmit?
To fix error 30886, rewrite the description so it states the sender, the recipients and the purpose, check that it matches the use case and samples, and resubmit the same campaign. Twilio’s guidance is to update and resubmit the failed campaign, and to create a new one only when the use case itself is wrong or the problem lies with the brand.
- Read every rejection code. 30886 often arrives together with 30893 (sample messages) or 30909 (opt-in flow). Fix them all in one pass.
- Rewrite the description with the who, whom and why from the table above, using your registered business name.
- Match the samples. Each sample message should be something the description promises.
- Check the brand details. The name in the description should match the registered brand and your website. See brand identity rejections.
- Financial lenders: Twilio notes that a business engaged in direct, first-party lending should say “Direct Lending” in the description.
- Resubmit the existing campaign rather than deleting it. Our page on rejected A2P campaigns explains resubmission and fees.
What a Good Description Covers
Answer these three questions clearly.
Who Sends
Your registered business name.
Who Receives
Customers who opted in, and how.
Why
The purpose of the messages.
Consistency
Matches use case, samples and website.
We Rewrite and Resubmit
We rewrite your description to match your samples and use case, then resubmit.
Share Your Details
Send us your business details, website and how you text customers.
We Prepare and Submit
We write your brand and campaign and submit them to The Campaign Registry.
Carrier Review
Carriers review your campaign. Most reviews take a few business days.
Get Approved
Link your numbers and start sending compliant texts.
Rejection Fixes Included
Complete A2P 10DLC verification, done for you. $50 for one business, $399 for ten.
Single Verification
$50
per verification, paid once
For one business that needs carrier approval to text its customers.
- Brand registration with The Campaign Registry
- Campaign registration with use case and sample messages
- Opt in, privacy policy and STOP and HELP review
- Fixes and resubmission until approved
10 Verification Pack
$399
10 verifications, $39.90 each
For agencies and multi location businesses verifying several brands. Just $39.90 per verification.
- Everything in Single Verification
- 10 verifications for your clients or locations
- $39.90 each instead of $50, you save $101
- Fixes and resubmission until each one is approved
Registration and carrier fees are charged separately by your SMS provider.
Frequently Asked Questions
Do I need a new campaign to fix error 30886?
Usually not. Twilio’s guidance is to update the failed campaign and resubmit it. Create a new campaign only if the use case you picked was wrong, or if the failure is tied to the brand rather than to the campaign details.
How long should an A2P campaign description be?
Long enough to state who sends the messages, who receives them, how they opted in and why the messages are sent, which is usually a few clear sentences. Length alone does not pass review; a short, specific description beats a long vague one.
Can an agency or platform name itself in the description?
Not when it registers on behalf of a customer. Twilio says the description should name the actual business sending the messages. An ISV with its own direct offering should say clearly that it is the sender.
Should the description include phone numbers or customer names?
No. Twilio lists personal information in the description as a cause of 30886. Describe the messaging program in general terms and keep real customer data out of the registration entirely.
Why was my description rejected when my samples were fine?
Because reviewers check that the parts agree. A clear description that does not match the selected use case, the brand or the website can still fail, as can one that promises less than the sample messages show.
Rejected for 30886?
Send us the rejection and we rewrite your description.
