RegistrationToll-freeIn effect

Toll-free verification now needs privacy policy and terms URLs

New toll-free verifications without both public URLs are rejected.

Published , updated

What changed
New toll-free verification requests must include a public privacy policy URL and a public terms and conditions URL. Both pages must contain the SMS disclosures: program name, message frequency, "Message and data rates may apply", HELP and STOP instructions, and a statement that opt-in data is not shared for marketing. Consent must not be bundled with other agreements, and consent checkboxes must be unchecked by default.
Who is affected
Businesses and platforms that submit new toll-free verifications. Existing verifications do not need to be sent again.
When
Effective . Announced .
What to do
Add the SMS disclosures to your privacy policy and terms pages before you submit. This matches what Twilio requires for 10DLC campaigns since 30 June.

Toll-free numbers do not use The Campaign Registry. Each number goes through toll-free verification before it can send business traffic. From 15 September 2026, a new verification request must link to a public privacy policy and public terms and conditions.

The terms must contain the SMS disclosures: the program name, what the program sends and how often, "Message and data rates may apply", HELP and STOP instructions, support contact details, and a statement that carriers are not liable for delayed or undelivered messages. The privacy policy must say that SMS opt-in data is not shared with third parties for marketing.

Reviewers also check the opt-in flow. Consent must be for the SMS program only, the disclosure must be next to the phone number field, and the consent checkbox must not be checked by default.

These are the same disclosures that carriers look for in 10DLC campaign reviews.

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.