Product changelog and announcements

Twilio Programmable Messaging now supports RCS messaging to Canadian phone numbers.

You can now request RCS Sender approval on available Canadian carriers.

To start sending branded RCS messages using Twilio Programmable Messaging, go to the Twilio Console to create, test and submit an RCS Sender.

Note that while all brands can submit RCS Senders for carrier approval, Twilio cannot provide an SLA or guarantee Sender approval by carriers.

For more information, see our RCS documentation.

To support compliance and improve campaign approval rates, Twilio is introducing new fields during U.S. A2P 10DLC Campaign registration.

What’s Changing?

When registering a Campaign, you must now provide:

• Privacy Policy URL – A valid, publicly accessible link to your privacy policy
• Terms & Conditions URL – A valid, publicly accessible link to your service terms.

These are now dedicated fields in the registration flow.

Console Updates

In the Twilio Console, you’ll see new fields in the Campaign registration form where you can enter your Privacy Policy and Terms & Conditions URLs directly.

API Updates
For programmatic registrations, these fields are now supported:

• Setup: Values can be passed during the Campaign create request. Providing the specific request header during the Campaign create call will return these fields in the API response.
• Recommendation: While the API currently allows flexibility, we highly recommend including these links in all new registration requests to avoid potential vetting failures.

Why This Matters
Previously, this information was required and  requested within the Message Flow description.
Providing dedicated, direct links ensures your Campaigns get approved faster and reduce the risk of rejection.

To learn more about U.S. A2P 10DLC registration, please review our documentation and Support article on Campaign approval requirements.

To improve message reliability and security, we are updating the Toll-Free Verification process to require business registration numbers.
Starting February 17, 2026, a business registration number for all business types expect sole proprietorships will be required for all new Toll-Free submissions.

These fields are available now in Console and API. 
To learn more about  business registration number requirements check out our Toll-Free Verification API Docs and Support Article. 

To maintain compliance with industry standards for platform integrity, all 527 organizations using toll-free numbers for political messaging must now provide a Campaign Verify (CV) Auth Token.

February 17, 2026 - All new political Toll-free verifications from 527 organizations require a valid CV Auth Token to register and a CV Auth Token needs to be added to existing verifications.
January 7, 2026 - Support for CV Auth Tokens launched in Twilio Console and API

To learn more about Campaign Verify Token requirements check out our Toll-Free Verification API Docs and the Campaign Verify FAQ

 

 

Template editing is live for all Content API users today. You can now update existing templates (text, variables, rich content) directly via the API without needing to recreate or version manually. Editing a template does not change its Content Sid.

Why it matters

• Faster copy tweaks and fixes
• Consistent messaging template changes across channels
• Retain the same Content Sid when sending templates

How it works
Use PUT /v1/Content/{ContentSid} to update any existing template.

To learn more about editing your Content Templates, see our docs page here.

Personalized Recommendations are now generally available in Twilio Messaging Insights, turning your messaging data into clear, prioritized actions to improve deliverability and engagement. Powered by your Health Score for Messaging and traffic patterns, recommendations surface the highest-impact optimization opportunities and highlight relevant Twilio products to drive better performance.

We are excited to announce the Private Beta release of Bulk Messaging on the new Communications API, enabling high-volume queuing for SMS, RCS, and WhatsApp.

The Senders API - WhatsApp, is now generally available, providing customers with an automated and scalable way to register, verify, and manage WhatsApp senders (phone numbers) directly through Twilio’s API.

This release allows both Direct Customers and Independent Software Vendors (ISVs) under the Tech Provider Program to automate sender onboarding. With the Senders API, customers can programmatically create, update, verify, fetch, and delete WhatsApp senders — enabling faster setup, improved accuracy, and reduced operational overhead.

The Senders API is especially beneficial for ISVs managing large portfolios of client accounts, helping streamline registration and configuration across subaccounts while maintaining compliance and consistency.

By eliminating manual workflows, customers can scale WhatsApp adoption more efficiently and accelerate time to market. To learn more about the Senders API - WhatsApp and how to integrate it, see our documentation here.

Twilio Health Score for Messaging (formerly known as Deliverability Score) is now General Availability. 

It provides a comprehensive overview of your messaging health, covering deliverability, engagement, latency performance, and more. Your score compares your issues to industry-best-practice benchmarks and identifies your biggest issues,  so you can more quickly and easily take action to improve.  

Key changes with this release include: 

• Daily-updated 7 -day aggregation, so you always have a fresh view of performance  

• Name changed from Deliverability Score to Twilio Health Score for Messaging, reflecting the comprehensive nature of the score  

Remember to sign up for your Twilio Health Score for Messaging weekly email, so you can stay on top of your messaging health.

 

We've released two new granular roles for the Twilio Console: Messaging Insights & Intelligence Admin and Messaging Insights & Intelligence Viewer. These roles give access to only the Messaging Insights and Intelligence pages.

We can assign these roles at organization, account or subaccount level unlike the current general roles which can be assigned only at the account level. See the complete list of roles here.