New Toll-Free Verification Requirements Take Effect September 15—And the Compliance Gap With 10DLC Keeps Narrowing

Effective September 15, 2026, businesses submitting new Toll-Free Number (TFN) verifications will be required to include direct links to their Privacy Policy and Terms & Conditions pages.

This is an industry-level change to Toll-Free verification standards—not a single provider's policy. Every messaging provider will enforce it, because none of them get to opt out of it.

On its own, the update is straightforward. Publish two compliant pages, link them directly, submit. But the reason it matters has less to do with the requirement itself and more to do with the direction it points: the compliance distance between Toll-Free and 10DLC is shrinking, and it has been shrinking for three years straight.

If you migrated to Toll-Free to get out from under 10DLC registration, this is the moment to look at that decision again.

What's Changing?

Beginning September 15, 2026, every new Toll-Free verification submission must include publicly accessible URLs for:

• Privacy Policy
• Terms & Conditions

The requirement applies regardless of how the verification is submitted, including:

• Toll-Free Verified Sender Form
• Bulk Verification File
• Verification API (updated September 14)

Existing Toll-Free verifications are not required to be resubmitted under the new rules.

What Needs to Be Included?

Simply having a Privacy Policy or Terms & Conditions page is no longer enough. Both pages must contain specific messaging-related disclosures and be directly accessible via the submitted URLs.

Terms & Conditions should include:

• Brand or program name
• Description of the messaging program
• Message frequency disclosure
• "Message and data rates may apply" language
• HELP and STOP instructions
• Customer support contact information
• A direct link to the Privacy Policy
• A statement that carriers are not liable for delayed or undelivered messages

Privacy Policy should clearly explain:

• What customer information is collected
• How that information is used
• That SMS opt-in data and mobile information are not shared with third parties or affiliates for marketing or promotional purposes

Opt-In Flows Are Part of the Review

The update also reinforces existing expectations around consent. Businesses should confirm that:

• The opt-in experience matches the messaging use case submitted for verification
• Consent is collected specifically for the SMS program, not bundled with unrelated agreements
• Required disclosures appear adjacent to the phone number entry field
• Consent checkboxes are unchecked by default
• Message frequency, HELP, STOP, and "Message and data rates may apply" disclosures are clearly presented

If that list looks familiar, it should. It is effectively the same standard 10DLC campaign registration has been held to since the beginning.

The Bigger Picture for Toll-Free Messaging

When 10DLC registration deadlines first hit, a lot of businesses were told to solve the problem by moving their traffic to Toll-Free. Several large vendors made that recommendation at scale—not because Toll-Free was the better channel for those use cases, but because it was the fastest way to keep messages flowing past a deadline.

It worked as a band-aid, but it was never a strategy.

Two things have happened since:

The cost gap didn't go away. Toll-Free carries higher per-message rates and higher carrier fees than 10DLC. Businesses that migrated under deadline pressure absorbed a permanent COGS increase. In most cases, it's still sitting in their unit economics today, quietly compounding with volume.

The compliance gap closed anyway. Toll-Free verification requirements expanded on January 1, 2026, and are expanding again on September 15. Each round pulls Toll-Free closer to the 10DLC standard: campaign-level scrutiny, opt-in flow validation, and now publicly accessible legal documentation. The trajectory is not subtle. These two frameworks are converging, and the endpoint is that they look substantially the same.

So the businesses that migrated to avoid compliance work are now paying more per message and doing the compliance work.

Related reading: Toll-Free Messaging Verification: What Changed on January 1, 2026

The Right Question Isn't "Which Is Easier." It's "Which Number Should Your Customer See?"

Telgorithm has argued this since we started, and nothing about the last two years has changed it:

Choose your number type based on how your customer wants to be reached.

If your customers respond better to a local presence—if a familiar area code is the difference between a read and an ignore—then 10DLC is your channel, and the registration work is simply the cost of doing business well.

If your use case genuinely calls for a national, brand-level identity, Toll-Free is a legitimate and often excellent choice. National consumer brands, support and service lines, and organizations without regional footprints frequently belong on Toll-Free. Nothing here argues against that.

The problem was never Toll-Free, the problem is around why Toll-Free was chosen. 

Related reading: 10DLC versus Toll-Free: Get the Facts Part 1

If You Migrated Under Deadline Pressure, Re-Run the Math

A short reassessment is worth doing before the September 15 change lands:

• Why are you on Toll-Free? If the honest answer is "because we had to move fast in 2023," that's a legacy decision, not a current one.
• What is it costing you? Compare your blended Toll-Free per-message and carrier fee load against 10DLC for the same volume. At scale, the delta is rarely trivial.
• What compliance work are you avoiding? After September 15, less than you think—and the trend line says that number keeps shrinking.
• Does your number type match your customer relationship? Local business, local customers, local number. That's usually the whole analysis.

For some businesses the answer will be to stay on Toll-Free, and that's a good outcome. It means the channel is chosen deliberately. For others, it will surface a migration that's been overdue since the deadline that caused it.

Before You Submit a New Toll-Free Verification

Use this checklist before September 15:

• Create dedicated, publicly accessible Privacy Policy and Terms & Conditions pages
• Confirm both pages include the required messaging disclosures
• Verify your opt-in flow accurately reflects your messaging program
• Include HELP, STOP, message frequency, and "Message and data rates may apply" disclosures
• Ensure Privacy Policy and Terms & Conditions URLs point directly to the appropriate pages

Compliance Is an Operating Process, Not a Registration Task

The broader lesson of the last two years is that messaging compliance doesn't get simpler by switching lanes. It gets simpler by building it into how you operate — validating the full customer journey, not just the submission form.

That's the part Telgorithm handles for the software platforms and businesses we support: verification and registration submitted correctly the first time, compliance requirements monitored as they change, and number type recommendations based on your use case rather than the nearest deadline.

Talk to our team about whether your current number strategy still fits your business.