The new business-texting rule that quietly kicked in June 30 (and doesn't touch your existing texts)

As of June 30, 2026, any brand-new business text-messaging registration needs a working privacy policy page and a terms and conditions page on your own website, per Twilio's own changelog. If you already send business texts today, nothing changed for you. Twilio says it flat out: "existing registered campaigns are not affected." This only bites the next time you register a new texting line.

Wait, is this an actual law?

No. This is a carrier registration requirement, not a law. The rule lives entirely inside Twilio and The Campaign Registry (TCR), the industry system phone carriers use to vet business text traffic before they'll route it to customers. There's no FCC ruling behind this, no state statute, nothing passed by a legislature. It's closer to a landlord adding a new line item to a lease application than it is to a new law on the books. I'm calling this out because I've already seen people repeat it online as "a new federal texting law," and that's just not what the source says.

What actually changed on June 30?

Two fields, PrivacyPolicyUrl and TermsAndConditionsUrl, are now required on every brand-new business texting registration (per Twilio's changelog). Skip either one and the registration gets rejected on submission, with its own error code: 30933 for a missing privacy policy link, 30934 for a missing terms link. That's the whole change. It's not a shutoff of business texting. It's a gate on new registrations.

Does this touch the texts I'm already sending?

No, and this is the part that keeps getting mangled in the retelling. Twilio's own changelog says it in plain words: "This change applies only to new campaign submissions made after June 30, 2026. Existing registered campaigns are not affected." If your texting is already up and running, you don't have to do anything about this. It matters to a business setting up texting for the first time, or adding a second line, not to one that's already sending.

What actually has to be on those two pages?

Carriers check these pages during review, and they'll bounce a registration for the wrong details, so it's worth getting right the first time (per Twilio's business-info requirements):

• Privacy policy: publicly visible with no login wall, states you don't sell or share customers' phone numbers with third parties, and discloses roughly how often you'll text ("up to 4 messages a month") plus the line "message and data rates may apply."
• Terms and conditions: publicly visible with no login or download wall, and hosted on the same domain as your actual business website. A terms page that redirects to a different domain gets rejected.

What's the actual fix?

Publish a privacy policy page and a terms page on your own site, then hand carriers both URLs the next time you register a texting line. If you don't already have these pages, that's an afternoon of work, not a legal project - state what you collect, state you don't sell numbers, state the messaging frequency and the rate disclaimer, and put both pages live on your own domain before you submit.

Where does this leave a small business?

If you already text customers today, you can stop reading and get back to work. Nothing changed for you. If you're about to set up business texting for the first time, budget an afternoon for the two pages before you register.

If texting is part of a bigger question, like whether your phones and follow-up are actually catching every lead, that's what TaskChad's AI receptionist is built for - it answers, texts, and books while you're on a job. And if you want to see exactly where calls and messages are leaking before you spend a dollar fixing anything, a free Revenue Leak Audit will map it for you.