Twilio Error 30886: Fix an Invalid Campaign Description
Updated
Short answer: Error 30886 means your A2P 10DLC campaign failed vetting because the campaign description does not clearly explain the messaging program. Rewrite it to say who sends the messages, who receives them and why, using the registered business name, and make it match your use case and sample messages. Then edit and resubmit the same campaign. It is not an EIN error: too many brands on one EIN is error 30898.
What error 30886 means
Twilio's title for this code is "30886: Campaign vetting rejection - Invalid Campaign Description". The error page says:
"Your A2P 10DLC campaign was rejected during vetting because the Campaign Description field does not clearly explain the messaging program. Describe who is sending the messages, who receives them, and why the messages are being sent. Make sure the description matches your selected campaign use case, sample messages, and registered brand details."
Twilio defines the field as "A detailed description of the purpose of the messaging Campaign. Must be between 40 and 4096 characters." Its own example is one sentence: "This Campaign will send weekly marketing messages about sales and offers from Acme Sandwich Company to end customers who have opted in".
Common causes
Twilio lists six:
- "The campaign description is too vague or incomplete."
- "The description does not explain who the sender is, who the recipients are, and why they are receiving messages."
- "The description does not align with the selected campaign use case."
- "The description does not match the sample messages, brand name, website, or other registration details."
- "If you are registering on behalf of customers, the description identifies your ISV or platform instead of the actual business sending the messages."
- "The description includes personal information instead of a general summary of the messaging program."
The fifth one catches agencies. When you register a client's campaign, the description names the client's business, not your agency or the software you send through.
How to fix error 30886
- Say who sends, to whom and why. "Rewrite the campaign description so it clearly states the sender, the intended recipients, and the purpose of the messages." Make it "specific enough to describe the real messaging program."
- Match the rest of the registration. "Verify that the description matches your selected use case and your sample messages."
- Name the real business. "Use the actual registered business or brand name in the description. If you are an ISV with a direct offering, say that clearly in the description."
- Take out personal details. "Remove personal information and keep the description focused on the messaging program."
- Declare direct lending. "If your business is a financial institution engaged in direct, first-party lending, include Direct Lending in the description."
- Edit and resubmit the same campaign. "Update the failed campaign and resubmit it for review. Create a new campaign only if the selected use case is wrong or the failure is tied to the associated brand rather than the campaign details." Twilio's troubleshooting guide explains why: "The vetting fee is only charged once per Campaign, at its first vetting decision, and resubmitting keeps that fee from being charged twice."
Weak and better descriptions
The brands are made up. Each better version names the sender, the recipients and the purpose.
| Problem | Weak | Better |
|---|---|---|
| No sender, recipients or purpose | We send texts to our customers. | Acme Dental sends appointment reminders and rescheduling links to patients who book a visit online or at the front desk. |
| Names the platform, not the business | Our marketing software sends texts for local businesses. | Bright Path Realty sends new listing alerts and showing confirmations to home buyers who sign up on its website. |
| Personal information | Reminders for Maria at 555-0100 about her cleaning. | Acme Dental sends cleaning reminders to patients who are due for a visit. |
| Does not fit the Marketing use case | Order status updates for shoppers. | Acme Outdoor Gear sends sale announcements and discount codes to shoppers who sign up for text offers. |
If you use HighLevel
HighLevel files this code under "Invalid Campaign Description": "Campaign description does not thoroughly explain the purpose of the campaign or description does not match the use case." Its correction: "Verify that the campaign description is accurate and detailed. If you are an ISV registering a direct offering to your customers, please indicate that in the campaign description. Resubmit campaign for review."
For Manual Setup, HighLevel says the Use Case Description should "Explain who sends the messages, who receives them, what messages are sent, and how contacts opt in." Chat Widget Setup fills the description in for you. If your company has an EIN but texts under another name, HighLevel suggests adding the sentence "We are doing DBA as [Business_Name]" in the Campaign Use Case.
Not an EIN problem
Error 30886 is about the description. A campaign rejected because one EIN is behind too many brands gets a different code: 30898, "Campaign vetting rejection - Excessive EIN". See Twilio error 30898.
Related codes
| Code | Twilio title | What it means |
|---|---|---|
| 30497 | "Use case summary is incomplete or unrelated to the messaging" | The summary is "too generic, incomplete, or describes something unrelated to the selected messaging use case". It applies to toll-free verification and A2P 10DLC |
| 30894 | "Campaign vetting rejection - Invalid Brand Information" | The brand on the campaign is not the business that actually sends the messages |
| 30893 | "Campaign vetting rejection - Inconsistency between Sample Message and Use-case" | The samples do not match the use case. See A2P sample messages |
| 30911 | "Campaign rejected: Duplicate template text; each field must be unique" | The same or nearly identical text appears in several fields |
How to avoid it next time
- Choose the use case and draft the samples first, then write the description to match them.
- Name the business exactly as registered, and say who receives the messages and why.
- Precheckly's Pro plan ($29 a month) includes 10 A2P registration pre-checks a month. Each one checks whether the description says who receives the messages, why, and how they opted in, along with your website, privacy policy, opt-in flow and samples. See pricing.
For a longer guide with more examples, see how to write an A2P 10DLC campaign description. For other rejection codes, see the list of A2P 10DLC error codes.
Sources
- 30886: Campaign vetting rejection - Invalid Campaign Description, Twilio
- A2P 10DLC - Gather the Required Business Information, Twilio
- Troubleshooting and rectifying Campaigns, Twilio
- 30898: Campaign vetting rejection - Excessive EIN, Twilio
- 30497: Use case summary is incomplete or unrelated to the messaging, Twilio
- 30894: Campaign vetting rejection - Invalid Brand Information, Twilio
- 30893: Campaign vetting rejection - Inconsistency between Sample Message and Use-case, Twilio
- 30911: Campaign rejected: Duplicate template text; each field must be unique, Twilio
- Campaign Rejection Reasons and Resolutions, HighLevel
- A2P Campaign Registration: Step by Step Guide and FAQs, HighLevel
Not legal advice. Carrier rules and provider documentation change, so check the linked sources before you rely on them.