Invalid Campaign Description

Why This Rejection Happens

The description field of your campaign was either too short, too vague, or completely irrelevant to the actual messaging content. Vetting agents read this to understand *why* you are texting. A description like "Test" or "Messages" is an automatic failure.

• "Test campaign" or "Platform testing."
• "Marketing messages" (Too vague; explain *what* marketing).
• Description says "2FA" but samples show "Pizza Coupons."
• Word count is too low (< 10 words).

Root Cause Analysis

Primary Triggers

• The "Lazy" Submission: Filling out the form quickly and writing "notifications" does not give the carrier enough context to approve traffic.
• Inconsistency: If the description contradicts the sample messages or the Use Case selected, it is marked as invalid.

Good vs. Bad Descriptions

Bad (Rejected):

Good (Approved):

Step-by-Step Remediation

Follow the Formula

Who + What + Why.
Who: "[Brand Name] sends..."
What: "...appointment reminders and billing alerts..."
Why: "...to customers who purchased our services."

Update TCR Profile

Log in and edit the "Campaign Description." Ensure it is at least 15-20 words long and specific to your content.

Pre-Resubmission Checklist

• My description mentions the Brand Name.
• My description matches the sample messages provided.

Fix It Faster

Generate a perfect description.

Details Matter

A detailed description proves you are a legitimate sender with a plan.

What reviewers check for code 30886

Code 30886 is reported as "Invalid Campaign Description". The campaign description must explain, in plain language, who is sending, who receives the messages, what the messages are for, and how recipients opted in. Reviewers reject descriptions that are vague, copied from marketing copy, written about the platform instead of the brand, or inconsistent with the use case.

Where code 30886 comes from

Code 30886 is one of the brand and campaign registration errors Twilio returns in its 30xxx error range when vetting fails. Other CSPs report the same underlying problem under their own reason codes, so the remediation below applies on any platform. It is marked High severity: it blocks approval, but it is fully fixable by correcting the submission and resubmitting.

Campaign description

Rejected:

We send texts to customers.

Approved:

Lakeview Residential is a property management company. We send maintenance updates and community notices to customers who opt in on our website or at checkout by checking an unchecked SMS consent box. Messages include the brand name, frequency and opt-out instructions. We do not share numbers or send third-party content.

Fix and verify before resubmitting

1. Start with the brand name and its business: "Lakeview Residential is a property management company that..."
2. State who receives messages (existing customers, patients, members, subscribers).
3. List the message types and their purpose.
4. Explain the opt-in method and where it happens.
5. Keep it factual, 40 to 120 words, and consistent with samples and use case.
6. Resubmit with a note that references code 30886 (Invalid Campaign Description) and lists each change made.

Sample resubmission note

Many CSPs let you add a note for the reviewer when you resubmit. A short, specific note shows what changed and speeds up the second review. Example for Lakeview Residential:

Lakeview Residential corrected the deficiency reported as code 30886 (Invalid Campaign Description). Changes made: start with the brand name and its business: "Lakeview Residential is a property management company that..."; state who receives messages (existing customers, patients, members, subscribers); list the message types and their purpose. All URLs, keywords and auto-replies were re-tested from an external network before this resubmission, and the campaign text now matches the live opt-in exactly.

Common mistakes that keep code 30886 coming back

• Describing the messaging platform rather than the business.
• Writing one sentence with no opt-in information.
• Listing message types that are not in the samples.

Related rejection codes

• Code 2002: Campaign Description Unclear
• Code 2131: Verbal Script Missing STOP Instructions
• Code 2128: Opt-in Form Missing HELP Instructions
• Code 2127: Verbal Script Missing STOP Instructions
• Code 2126: Opt-in Form Missing STOP Instructions
• Code 2124: Verbal Script Missing Frequency Disclosure

Frequently asked questions about code 30886

How long should the description be for code 30886?

Long enough to answer who, whom, what and how: usually three to five sentences.

Can I reuse the same description for several campaigns?

Only if they are truly identical; otherwise reviewers see a mismatch with the samples.

Legal Disclaimer: Code 30886 is a data quality error. It ensures the carrier understands the nature of the traffic traversing their network.

© 2025 MyTCRPlus. All rights reserved.