Product changelog and announcements

This new action supports async batch for SFMC destination extensions (Without observability)

Studio now includes a ConversationRelay widget that allows you to connect live voice calls directly to a WebSocket server (that you provide) using Twilio ConversationRelay.

This widget:

• Exposes ConversationRelay configuration options

• Supports custom parameters and voice controls

• Provides Success and Failed transitions for orchestrating session outcomes within Studio flows

For more information, see our ConversationRelay widget docs. 

Starting March 23, 2026, we’ll begin rolling out more specific and detailed error codes for US A2P 10DLC Campaign registraions.

These new codes are designed to give you clearer, more actionable feedback when a campaign is rejected or requires an edit - helping you resolve compliance issues faster and get your messaging live.

The existing error codes will still be supported, but these new granular codes provide the specific context needed for rapid troubleshooting.

What’s changing?
Currently, A2P 10DLC rejection messages can sometimes be broad, making it difficult to identify the exact compliance blocker. With this update, you’ll see granular error codes that pinpoint the specific reason. 

These new codes will appear in:

• API Responses
• Event Streams
• Twilio Console (Campaign Details Page)

What this means for you
If you have built custom logic or processes to handle A2P 10DLC registration errors, we recommend reviewing your error mapping.

Updating your tools to reflect these new, specific codes will allow your end-customers and operations teams to respond to rejections with much higher precision.

For a full list of the new codes and their meanings, please refer to the Support Article on Campaign Rejections. 

Security and reliability go hand in hand, and we want to make sure your applications keep running smoothly while we work in the background to keep things safe.

That’s why on April 8, 2026, the end-user certificate for all Twilio REST API endpoints will be rotated.

Security standards are always evolving, and we want to ensure your Twilio applications are using the strongest protection available.

We're extending the deadline for these changes and customers now have until June 3, 2026, to update their setups with the ciphers listed below. We’ll continue accepting legacy cipher traffic during that window so customer applications keep running without interruption. 

Verify Events now supports message status events in real time, providing information on the message status of verifications. Available message status events include DELIVERED, UNDELIVERED, SENT, READ and FAILED statuses.

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.

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.