10DLC by provider · Twilio · Critical
Twilio 10DLC rejected: Opt-in language does not match the use case
Your Twilio registration came back rejected and it points to opt-in language does not match the use case. Twilio did not make that call. Here is what the reason means and exactly how to fix it.
Twilio 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: Twilio did not decide this. It submitted your brand and campaign to The Campaign Registry (TCR) and the carriers, they returned the rejection, and Twilio 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 Twilio 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 Twilio shows this rejection
In the Twilio Console, the campaign's status and the returned rejection reason appear under your Messaging / A2P 10DLC section, on the campaign that failed. The text you see there is the reason relayed from TCR or the carrier.
Twilio is the messenger, not the decider
Note the difference between a registration rejection and a sending error. A rejected campaign is a registration decision you resolve by fixing the package and resubmitting. A send-time error on an unregistered number is a symptom of registration not being complete, not a separate campaign rejection. If you are unsure which you are seeing, the rejection reason text is the tell.
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 Twilio reject my 10DLC campaign for opt-in language does not match the use case?
No. Twilio submitted your campaign to The Campaign Registry and the carriers, who returned the rejection. Twilio relays the reason. You resolve the underlying issue and resubmit through Twilio. 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 Twilio rejection?
Correct the issue, then resubmit the campaign for review through Twilio. 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.