Product changelog and announcements

The Twilio Video JavaScript SDK now supports Samsung Browser, the third most popular mobile internet browser globally with over 1 billion installs. This adds official support for millions of Android users on Samsung Galaxy devices who use Samsung Browser as their default browser and expands the reach of Twilio Video. 

To use Twilio Video with Samsung Browser, upgrade your application to the latest version of the Video JavaScript SDK. See the JavaScript SDK changelog for additional details and review the supported browsers documentation for the full browser compatibility matrix.

Studio now includes the Resume Conversation widget, which allows outbound Studio flows to connect to an existing Twilio Conversation. This widget fetches an existing Conversation, lists its participants, and configures Studio to continue the flow when inbound messages are received.

Note that this widget is designed for REST API triggered flows. Only one Conversation can exist per execution.

For more information, see our Resume Conversation widget docs.

Starting 23rd April 2026, Twilio will start passing on the “Reason” header for Elastic SIP Trunking outbound calls (Trunking Termination calls) that are rejected by Carriers based on Network Analytics with a SIP error response 603 Network Blocked.

We’re excited to announce that Flex UI 2.17.0 is now available. This release includes a number of enhancements and bug fixes.

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

Intelligent Alerts is now GA for all Twilio Messaging customers sending SMS traffic. It uses anomaly detection to automatically monitor your messaging traffic for unusual spikes in selected error codes, helping you identify potential delivery issues faster.

We released a new major version of the Twilio Java Helper Library on April 21, 2026. This release adds JDK 21 build and test support, bringing official compatibility with the latest Java LTS runtime. The library continues to support Java 8 and above; no runtime upgrade is required.

We're releasing a new major version of the Twilio Node Helper Library. To keep our customers' integrations secure, we're dropping support for Node.js versions 14 through 19, all of which have reached end of life and no longer receive security updates from the Node.js foundation.

Starting May 31, 2026, Twilio will begin sunsetting the Transit CallerID feature. Customers currently using Transit CallerID to present a different phone number than the one they're calling from will need to migrate to an alternative before this date.

The TCPA Known Litigators Check is now available within Compliance Toolkit to help safeguard your messaging by identifying and blocking messages to phone numbers believed to be associated with individuals or entities with a history of filing TCPA-related legal actions. 

This safeguard intelligently filters non-essential communications, such as marketing/promotional messages to phone numbers associated with known litigators, while allowing essential traffic, like transactional alerts, otp, and customer support messages, to reach the recipient. 

When a message is blocked by this feature, Twilio will return Error Code 30640.

Learn more about this feature and how to enable it in our documentation.

Consent Management API is now available globally in Public Beta, allowing you to programmatically sync, store, update, and manage end-user consent preferences across RCS, SMS, and MMS channels. This API acts as a centralized source of truth for managing consent preferences, enabling you to seamlessly integrate consent data from external systems like CRMs or web forms directly into Twilio.

Note that consent states updated via this API for a given Messaging Service are automatically enforced across all three unified channels (RCS/SMS/MMS) to ensure compliance, without requiring any code changes.

Learn more about this feature and how to enable it in our documentation.