Use case mismatch: when your samples, description and opt-in disagree
Short answer
Everything in the registration has to describe the same program: the use case, the description, the samples, the opt-in wording and your website. If you send promotions, the use case must be Marketing or Mixed. The use case can't be changed once a 10DLC campaign exists, so a wrong one means a new campaign.
What you'll see
| Where | Code | Wording |
|---|---|---|
| Twilio (10DLC) | 30893 | “Campaign vetting rejection - Inconsistency between Sample Message and Use-case” |
| Twilio (toll-free) | 30496 | “Toll Free verification rejection - Use case and use case summary inconsistent” |
| Twilio (toll-free) | 30507 | “Toll Free verification rejection - Opt-in does not match use case” |
| Twilio (both) | 30537 | “Business model does not match the messaging use case” |
| Twilio (10DLC) | 30916 | “Campaign rejected: Use case mismatch between lead generation and lead nurture” |
| Telnyx, Bandwidth | 602 | Samples, description or CTA inconsistent with the selected use case |
| Bandwidth Proxy, Infobip | 2003, 2005, 8001-8004 | Description vs use case mismatch; undeclared use case; site or campaign shows charity, political, cart reminders or several use cases, but the declared use case differs |
Text in curly quotes is the provider's wording; the rest is our summary.
Why it happens
- Account Notification or Customer Care selected, but samples include discounts or “come back” offers.
- One-time passcodes in samples without the 2FA use case.
- Opt-in wording says “marketing messages” while the use case is informational, or the reverse (30507).
- The use case doesn't fit the business; HighLevel's example is
A pizza restaurant using an appointment or confirmation reminder use case
. - Abandoned-cart reminders filed as informational. The Proxy vetting partner requires Marketing (8003).
- Lead generation selected for follow-ups to existing leads, or the reverse (30916).
How to fix it
- List every kind of message you'll send. If any of them promote anything, choose Marketing, or Mixed for marketing plus informational.
- Low-volume senders with several message types can use Low Volume Mixed if their provider offers it.
- Rewrite the samples and the opt-in wording to match the use case exactly.
- On toll-free, select every category that applies (Twilio has 14 and no “Mixed”) and give one sample per category.
- If the 10DLC use case is wrong, create a new campaign. The Campaign Registry doesn't let you change it after creation.
A known conflict: cart reminders
T-Mobile's code of conduct says abandoned-cart reminders belong under an informational use case, but the Proxy vetting partner's code 8003 requires Marketing. Filing them as Marketing, with a double opt-in and one reminder per cart within 48 hours, is the safer path.
Check before you resubmit. Every rejection costs days, and often another $15 vetting fee. Paste your description, message flow, samples and policy text into the free preflight check, or generate a consistent set with the campaign builder.
Frequently asked questions
Can I change the use case of an existing campaign?
No. The Campaign Registry doesn't allow changing a campaign's use case after creation. Create a new campaign with the right use case, which means another vetting fee.
Do reminders with a small promo line count as marketing?
Yes. Any promotional content makes the program marketing. Either remove the promo line or register as Mixed with separate marketing consent.
What is the difference between lead generation and lead nurture?
HighLevel's description: lead generation is initial outreach, and lead nurture is ongoing engagement with existing leads. Third-party lead generation (collecting leads to sell or share) is prohibited outright.
Sources
- Twilio: A2P 10DLC Campaign Onboarding Guide (updated 2026-09-24)
- Twilio: Toll-Free Verification Onboarding Guide (updated 2026-09-24)
- Twilio error 30496 (accessed 2026-10-03)
- Twilio error 30507 (accessed 2026-10-03)
- Twilio error 30537 (accessed 2026-10-03)
- Twilio error 30916 (accessed 2026-10-03)
- Bandwidth: DCA2 vetting rejection reasons (2026-03-17)
- Bandwidth: Proxy Connector vetting rejection reasons (2026-03-17)
- The Campaign Registry: CSP User Guide (July 2026)
- HighLevel: How to get your phone number A2P approved in 2026 (modified 2026-07-30)
- T-Mobile Code of Conduct v2.2 (November 2020 (latest public))
Rules change often and providers sometimes disagree; where they do, this page says so. This is general information, not legal advice, and no one can guarantee approval. See the disclaimer.
Related problems
- Twilio 30893, 30538, 30499, 30911 · DCA 602, 603 · Proxy 6012-6014 · TCR SAMPLE_MESSAGESample messages rejected: how to write samples reviewers approve
- Twilio 30886, 30497, 30910, 30911, 30912 · Proxy 2002, 2006 · DCA 506 · TCR CAMPAIGN_DESCRIPTION_OR_ATTRIBUTESCampaign description rejected (Twilio 30886): who, to whom, and why
- Twilio 30951, 30932, 30468, 30916 · DCA 708 · Proxy 7002Rejected for lead generation or affiliate marketing (Twilio 30951, DCA 708)
- Twilio 30925, 30923, 30931, 30913, 30475, 30551, 30556 · DCA 803 · TF 1401-1407Opt-in checkbox rejections: pre-checked, required or bundled consent
The Approval Kit adds industry template packs, opt-in and policy page templates, and an agency checklist.