A2P 10DLC Campaign Description Examples by Use Case
Most A2P 10DLC guides tell you the rules. This page gives you the thing you actually want: full campaign description examples that pass carrier / TCR review, by use case — each annotated with why it works, and each with a one-click scan so you can compare yours.
Guidance only — A2PCheck is independent and not affiliated with Twilio, The Campaign Registry, or any carrier, and we can't guarantee approval.
Scan your campaign description
Paste your description — or load an example below — and get a readiness verdict against the checks carriers and TCR apply. Free, no signup.
What a description that passes includes
Carriers and The Campaign Registry read the description as a factual account of your program. A strong one answers five things:
- Who you are — the brand/business name, matching your website and samples.
- Who you message and how they opted in — the audience plus where and how they gave consent (quote the consent language).
- What you send — the message types and content (offers, codes, alerts), not a vague 'updates'.
- How often — a frequency (e.g. '~4 messages per month' or 'only when triggered by the user').
- Opt-out & help — STOP/HELP handling, and reachable privacy policy / terms URLs.
Weak vs. strong
Rejected-shape
We send marketing messages to our customers.
- One vague sentence — no audience, no content detail, no frequency.
- Doesn't say how people opt in or quote any consent language.
- No brand, links, or message types for a carrier to verify against your site and samples.
Approved-shape
Promotional SMS campaign for Brightleaf Coffee customers who opt in at brightleafcoffee.com/sms or at checkout. Subscribers receive about 4 marketing messages per month with new-product launches, seasonal offers, and limited-time discount codes. Every message includes the brand name, opt-out wording, and a message-and-data-rates disclosure.
- Names the brand, the opted-in audience, and the content (launches, offers, discount codes).
- States frequency (~4/month) and includes the message-and-data-rates disclosure.
- Describes exactly where and how people opt in — and quotes the consent language.
Examples by use case
The right description depends on your TCR use case. Each example below is a full, carrier-friendly description you can adapt — click Scan this example to run it through the checker. Pair it with the sample message checklist and opt-in flow examples.
Marketing promotions
MARKETINGOpt-in promotional offers and sale alerts.
Promotional SMS campaign for Brightleaf Coffee customers who opt in at brightleafcoffee.com/sms or at checkout. Subscribers receive about 4 marketing messages per month with new-product launches, seasonal offers, and limited-time discount codes. Every message includes the brand name, opt-out wording, and a message-and-data-rates disclosure.
- Names the brand, the opted-in audience, and the content (launches, offers, discount codes).
- States frequency (~4/month) and includes the message-and-data-rates disclosure.
- Describes exactly where and how people opt in — and quotes the consent language.
Two-factor auth
TWO_FACTOR_AUTHOne-time passcodes for login verification.
Transactional one-time-passcode (OTP) messages sent by Vaultline to verify a user's identity when they sign in or change account settings. Messages are triggered only by an explicit user action on our website or app and contain a short numeric code that expires in 10 minutes. No marketing content is ever sent on this campaign.
- Declares it transactional OTP only: 'No marketing content is ever sent on this campaign.'
- Explains the trigger — codes go out only in response to a user-initiated login or settings change.
- Notes the code expiry, reinforcing that the messages are genuinely security-related.
Customer care
CUSTOMER_CARETwo-way support replies and ticket updates.
Two-way customer-care messaging for Northwind Appliances. After a customer contacts support or schedules a repair, our team replies by SMS with ticket updates, appointment confirmations, and answers to their questions. Messages are conversational and only sent to customers who have an open support request or have texted us first.
- Describes two-way support tied to an existing ticket or a customer who texts first.
- Makes clear messages only reach customers with an open request — no cold outreach.
- Quotes the opt-in consent shown on the support request form.
Account notifications
ACCOUNT_NOTIFICATIONReceipts, shipping, and account alerts.
Transactional account notifications from Harbor Bank for customers who opt in. Messages include payment confirmations, low-balance alerts, statement-ready notices, and profile-change confirmations. These are non-promotional alerts tied to activity on the customer's own account.
- Scopes messages to activity on the customer's own account (payments, balances, statements).
- Labels them non-promotional, matching the ACCOUNT_NOTIFICATION use case.
- Explains enrollment inside online banking with an explicit, unchecked-by-default consent box.
Fraud alerts
FRAUD_ALERTSuspicious-activity warnings with a reply prompt.
Time-sensitive fraud and security alerts from Harbor Bank. When our systems flag a potentially fraudulent transaction or login, we text the affected customer so they can confirm or deny the activity. Messages are triggered by suspected fraud only and ask the customer to reply YES or NO; they never request passwords, PINs, or full card numbers.
- Ties every message to detected suspicious activity and a YES/NO reply.
- States it never asks for passwords, PINs, or full card numbers — a strong carrier trust signal.
- Describes opt-in during account setup, quoting the consent statement.
How to adapt these for your campaign
Replace the placeholder brand, URLs, frequency, and consent wording with your real details — and make sure every claim in the description is actually true on your website and in your samples. Carriers reject descriptions that don't match the rest of the submission. When it's ready, run a free pre-scan and fix any Red findings before you register. Still getting turned down? See why descriptions get rejected.
Frequently asked questions
Can I copy these campaign descriptions word for word?
Adapt them — don't submit them verbatim. Swap in your real business name, URLs, message frequency, and the exact consent language from your own opt-in. Carriers cross-check the description against your website and sample messages, so it has to be true for your business.
How long should a campaign description be?
Long enough to answer who you message, why, what you send, how often, and how they opted in — usually three to six sentences. A vague one-liner is the single most common reason descriptions get rejected.
Does the description have to mention opt-in / consent?
Yes. Describe where and how people consent to your texts and quote the consent language they agree to. Descriptions that don't show a clear, explicit opt-in are routinely rejected.
Is the campaign description more important than the sample messages?
They're reviewed together and must match. A strong description paired with off-tone or non-compliant samples still fails. Line them up with the sample message checklist before you submit.