How to Write an A2P 10DLC Campaign Description
Updated
Short answer: The campaign description tells reviewers who sends the messages, who receives them and why. Twilio requires 40 to 4,096 characters, and the text must match the use case you select, your sample messages and your brand registration. A vague description is its own rejection reason, error 30886.
What the description must say
Twilio's registration docs give the rule in one sentence: "The description should include who the sender is, who the recipients are, and why messages are being sent to the recipients."
The field itself is "A detailed description of the purpose of the messaging Campaign. Must be between 40 and 4096 characters." Twilio adds: "This description must align with the us_app_to_person_usecase". That is the use case you pick, such as Marketing or Account Notifications.
The Campaign Registry (TCR) explains why clarity matters: "This field should paint an accurate picture so that everyone in the campaign chain can see and understand exactly how this campaign will be used. Lack of clarity can result in campaigns being rejected."
When the description falls short, Twilio returns error 30886, "Campaign vetting rejection - Invalid Campaign Description". The campaign was rejected "because the Campaign Description field does not clearly explain the messaging program."
Twilio's good and bad examples
Twilio's onboarding guide shows one description that works:
Messages are sent by {Brand Name} to patients with upcoming appointments. Messages include appointment reminders, rescheduling options, and post-visit care instructions.
And one that does not: "We send texts to people." Twilio's note on it reads "Too vague, no brand, no recipient info, no purpose".
The good example answers three questions in two sentences. The sender is the named brand. The recipients are patients with upcoming appointments. The purpose is reminders, rescheduling and care instructions.
A pattern you can follow
Write two or three plain sentences:
- Who sends: start with "Messages are sent by" and your brand name as registered.
- Who receives: the people and their link to you, such as customers who booked a visit or members who signed up for offers.
- Why: the kinds of messages they get, in everyday words.
Examples for three common use cases. The brands are made up:
| Use case | Example description |
|---|---|
| Account Notifications | Messages are sent by Acme Plumbing to customers who booked a service visit. Messages include visit confirmations, technician arrival windows and invoice reminders. |
| Marketing | Messages are sent by Acme Fitness to members and visitors who signed up for text offers. Messages include class promotions, membership discounts and event announcements. |
| Customer Care | Messages are sent by Acme Outdoor Gear to shoppers who contact its support team by text. Messages include answers to order questions, return instructions and updates on open requests. |
Each one names the sender, says who receives the messages and lists what they will get. Each is well over the 40-character minimum.
Keep it consistent with the rest of the registration
Reviewers read the description next to everything else you submit. Twilio's onboarding guide says: "Your campaign description also needs to match the campaign type you selected and your sample messages." It also says: "Double-check that your campaign description matches your brand registration."
Three rejection codes come from inconsistency:
- 30893: the campaign was rejected "due to inconsistencies between the sample message and the intended use-case of the campaign." The sample messages guide covers the fix.
- 30916: the submission "does not describe a single, consistent use case", for example one that mixes lead generation and lead nurture.
- 30911: the campaign "reuses the same or nearly identical text across multiple registration fields." HighLevel says the same: "Each field (description, sample messages, message flow) must contain unique content."
So write the description fresh. Do not paste your opt-in description or a sample message into it.
Special cases
- Software vendors and agencies. Register the business that sends, not yourself. Twilio's example: "If you provide software for dentists, don't register your software company. Register the specific dental practice that's actually sending the messages."
- A different brand name in HighLevel. If your company has an EIN but your messages use another brand name, HighLevel suggests adding the sentence "We are doing DBA as [Business_Name]" in the Campaign Use Case.
- Direct lending. Twilio says first-party lenders must write "Direct Lending" in the description, "even if you're only sending OTP/2FA messages."
- A website that is not live yet. Error 30891 lists "Lack of proper indication in the campaign description if the registration pertains to a pre-launch website" as a cause. If your website only works in some regions, Twilio asks you to "indicate this in the campaign description and provide a link to a screenshot."
- Personal data. "Please don't include any Personal Identifiable Information (PII) in the Campaign Description field. Publicly available info like brand names and phone numbers is fine."
- Language. Twilio rejects a campaign "when campaign registration fields include non-English content." That is error 30910.
- Personal messaging. Error 30912 applies when "the campaign details describe personal or peer-to-peer messaging instead of business messaging sent from an application to a person."
Checklist before you submit
- It names your brand exactly as registered.
- It says who receives the messages and why.
- It lists the kinds of messages in plain words.
- It is between 40 and 4,096 characters.
- It matches the use case you selected and your samples.
- Its text is not copied from another field.
- It has no customer names or phone numbers.
- It is in English.
Precheckly's Pro plan, at $29 a month, includes 10 A2P registration pre-checks a month. Each one reviews the campaign description together with your website, privacy policy, opt-in flow and samples, with an AI review and suggested rewrites.
For the other reasons a campaign fails, see why A2P 10DLC campaigns get rejected. If the brand behind the campaign failed instead, see A2P brand registration failures.
Sources
- A2P 10DLC - Gather the Required Business Information, Twilio
- A2P 10DLC Campaign Onboarding Guide, Twilio
- 30886: Campaign vetting rejection - Invalid Campaign Description, Twilio
- 30893: Campaign vetting rejection - Inconsistency between Sample Message and Use-case, Twilio
- 30916: Campaign rejected: Use case mismatch between lead generation and lead nurture, Twilio
- 30911: Campaign rejected: Duplicate template text; each field must be unique, Twilio
- 30891: Campaign vetting rejection - Invalid Website URL, Twilio
- 30910: Campaign rejected: A2P 10DLC campaigns must be submitted in English, Twilio
- 30912: Campaign rejected: A2P 10DLC is for application-to-person messaging only, Twilio
- Resources and FAQ, The Campaign Registry
- CSP User Guide, April 2026, The Campaign Registry
- A2P Campaign Registration: Step by Step Guide and FAQs, HighLevel
- A2P Campaign Rejections, Required Fixes & Vetting Errors, HighLevel
Not legal advice. Carrier rules and provider documentation change, so check the linked sources before you rely on them.