Product changelog and announcements

We’re introducing a refreshed, easier-to-use Studio canvas in public beta. This update offers a snappier building experience and an updated design with zero impact on your existing flow logic.

What’s new

• High-performance interactions: The new canvas is built for speed, delivering smooth panning, zooming, and dragging especially for workflows with hundreds of widgets.

• Modernized look and feel: We've overhauled the visual interface to align with modern Twilio UX standards, featuring updated node styling, improved spacing, and cleaner typography.

• Safe, side-by-side testing: Explore the new UI with total confidence. This update maintains full feature parity with the classic canvas, ensuring your widgets and flow logic work exactly as they did before.

How to opt in

Ready to try it out? You’ll find a banner at the top of your Studio page with an option to Try Studio’s new canvas. Turning on this option enables the new canvas experience just for you, without affecting the view for the rest of your team. If you need to switch back at any time, turn off the new canvas option at the top of the page to return to the classic canvas.

Feedback

We want to hear from you! Please help us shape the future of Studio by sharing your thoughts about the updated Studio canvas.

RCS Business Messaging now has a redesigned end-to-end compliance registration flow. The new console experience collects all Google and U.S. carrier requirements in one guided session, shows country-level pricing, gives customers visibility into the status of their submission, and accelerates approvals through automated carrier and verification integrations.

Starting June 11, 2026, Node.js v20 support in Twilio Functions will end. Any new Functions that you create or deploy after that date will default to Node.js v22. Existing Functions will keep running on Node.js v20, and will only move to v22 when you choose to redeploy them. 

Starting May 1, 2026, Twilio’s public Certificate Authority will no longer include the Client Authentication Extended Key Usage (EKU) extension in the security certificates they issue.

We’re pleased to announce that Flex UI 2.16.0 is now available. This release includes a number of bug fixes.

For complete details, see the Flex UI release notes for 2.16.0.

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.

Starting in June 2026, WhatsApp will start rolling out usernames, an optional feature that allows users to hide their phone numbers when messaging or calling businesses. When a user adopts a username, their phone number may no longer appear in webhook payloads. Instead, a Business Scoped User ID (BSUID) will be provided in the to and from field, as well as the new ExternalUserId field.

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

We're transitioning TLS certificate management for Twilio's classic HTTP REST APIs from manually managed DigiCert certificates to AWS Certificate Manager (ACM). This change prepares Twilio for industry-wide changes that will reduce maximum certificate lifespans to 47 days by 2029.