10DLC by provider · Bandwidth · Critical
Bandwidth 10DLC rejected: Opt-in language does not match the use case
Your Bandwidth registration came back rejected and it points to opt-in language does not match the use case. Bandwidth did not make that call. Here is what the reason means and exactly how to fix it.
Bandwidth showed your A2P 10DLC campaign as rejected, and the reason maps to "Opt-in language does not match the use case". The part that trips people up: Bandwidth did not decide this. It submitted your brand and campaign to The Campaign Registry (TCR) and the carriers, they returned the rejection, and Bandwidth is relaying it back to you.
That is good news for the fix. Because "Opt-in language does not match the use case" is a carrier and TCR requirement rather than a Bandwidth rule, the correction is the same no matter which provider you registered through: Sample messages or call-to-action describe a message type the campaign did not register for (e.g. marketing content on a 'customer care' campaign).
Where Bandwidth shows this rejection
Bandwidth shows brand and campaign registration status in its Dashboard (and via the Dashboard API), including the reason for a rejected registration. That reason comes from TCR or the carriers.
Bandwidth is the messenger, not the decider
As a direct carrier-connectivity provider, Bandwidth passes registry and carrier decisions straight through. Treat the rejection text as the carriers' words: it maps to one of the known 10DLC rejection reasons, and that is what you fix before resubmitting.
The fix
Make the CTA, the declared use case, and the sample messages describe the same thing. If you send marketing, register a marketing campaign and say so at opt-in.
Same rejection, different provider?
The reason is identical no matter who you registered through.
Common questions
Did Bandwidth reject my 10DLC campaign for opt-in language does not match the use case?
No. Bandwidth submitted your campaign to The Campaign Registry and the carriers, who returned the rejection. Bandwidth relays the reason. You resolve the underlying issue and resubmit through Bandwidth. The fix here: Make the CTA, the declared use case, and the sample messages describe the same thing. If you send marketing, register a marketing campaign and say so at opt-in.
Can one 10DLC campaign cover reminders and marketing?
Not under one generic opt-in. Reminders and marketing are different consent types. If you send marketing, the opt-in has to say so and you generally register a marketing use case, separate from a transactional reminders campaign.
How do I resubmit after a Bandwidth rejection?
Correct the issue, then resubmit the campaign for review through Bandwidth. Every resubmission is re-reviewed and re-review typically takes one to four weeks, so fix every problem before you resend rather than resubmitting to test it.