Guides › Error 30886

What error 30886 means and how to fix it

Last checked against official sources: November 3, 2026. Carrier rules change, so check the source links before you resubmit.

What it means

Twilio's page for 30886 titles it "Campaign vetting rejection - Invalid Campaign Description." HighLevel lists it as "Invalid Campaign Description" too. In plain terms, the reviewer read your campaign description and couldn't get a clear picture of the texting program: which business is sending, who is on the receiving end, and what the messages are for.

The description is the first thing a reviewer reads, and they check everything else against it: the use case you picked, your sample messages, your brand name and your website. If the description is thin, or tells a different story from the rest of the registration, this code comes back.

Why it usually happens

• The description is one short, generic line, such as "We send texts to our customers."
• It doesn't say who the sender is, who receives the messages, or why they're getting them.
• It describes a different kind of messaging from the use case you selected, for example promotions under an account-notification use case.
• It doesn't match the sample messages, the brand name or the website.
• An agency or software platform registered it under its own name instead of the actual business doing the texting.
• It contains personal details, like a customer's name or number, instead of a general summary of the program.

How to fix it

1. Name the real sender. Use the business name exactly as it's registered on the brand, not your agency or software vendor.
2. Say who receives the texts, such as customers who booked an appointment or members who joined a loyalty list.
3. Say why they get them: the specific kinds of messages, like reminders, order updates or occasional offers.
4. Say how those people agreed in a few words (for example, an optional checkbox on the booking form), so the description lines up with your message flow.
5. Check it against the use case and samples. Every message type you mention should show up in your samples, and nothing in the samples should be missing from the description.
6. Write it fresh. Don't paste the same text into the description, message flow and samples, since reusing text across fields can trigger a separate rejection.
7. Leave out personal information and keep it to a general summary of the program.
8. If you're a platform texting your own customers directly, say that plainly in the description.
9. Edit and resubmit the rejected campaign rather than deleting it. A brand-new campaign means a new vetting fee and a fresh wait.

Example campaign description (made-up business)

Maple Street Dental sends appointment reminders, scheduling confirmations and occasional recall notices by text to patients who opted in by ticking an optional, unticked SMS box on the online booking form at maplestreetdental.example/book, or by asking front-desk staff to sign them up. Messages are sent only by Maple Street Dental about the patient's own visits. Patients can reply STOP to opt out or HELP for help at any time.

Maple Street Dental is fictional. Swap in your real business, audience, message types and sign-up method, and describe only what you actually do.

Questions and answers

Next step

Run your rejection text through the free checker to confirm nothing else was flagged. If you'd rather not rewrite the fields yourself, our approval packets cover the description, samples, opt-in wording and policy text. Carriers make the final call, so we can't promise approval, but we revise free until it goes through.

Sources

• Twilio: Error 30886
• HighLevel: Campaign rejection reasons and resolutions (30886)
• Twilio: Troubleshooting and rectifying A2P campaigns
• Twilio: Gather the required business information

TextApproved is independent and not affiliated with Twilio, HighLevel or any carrier. This guide is not legal advice.