ProviderTwilioAnnounced

Twilio adds more specific 10DLC rejection codes on 9 December

Rejected campaigns can return new error codes that your code must know.

Published , updated

What changed
From 9 December 2026, Twilio plans to return more specific error codes when a 10DLC campaign registration is rejected. The codes cover the campaign description, the opt-in flow, and the Privacy Policy and Terms and Conditions pages. Twilio also maps the existing error 30569 to 10DLC rejections.
Who is affected
Twilio customers and ISVs that register 10DLC campaigns through the API or the Console.
When
Effective . Announced .
What to do
Add the new codes to the code that maps rejection reasons to messages for your customers before 9 December.

Twilio returns an error code when a 10DLC campaign is rejected. Since March 2026 these codes name one problem each. Twilio now adds more of them.

From 9 December 2026, new codes say what is wrong with the campaign description, the opt-in flow, or the Privacy Policy and Terms and Conditions pages. Examples: the description does not name the registered business, a sign-up form has no phone number field, or the Privacy Policy page does not load. Error 30569, a missing message and data rates disclosure, now also applies to 10DLC.

Some fixes need a new campaign with a different campaign type, not a resubmission. If your code shows a generic message for unknown codes, customers will not see the fix.

Related

Catch 10DLC violations before a carrier does

Moderation API checks every message against the campaign it was registered under. Start with a free backtest on 30 days of your traffic.