Product changelog and announcements

The new Twilio Console acts as a hub for all of your communication channels, sender compliance documentation, and billing. With smart recommendations, centralized compliance and brand information, and a simplified billing and account model, you can scale multi-channel experiences with less friction.

Conversation Orchestrator is now generally available, unlocking Twilio's Conversation Layer for customer interactions across channels. Conversation Orchestrator creates a unified view of customer conversations, whether they happen over Voice, SMS, WhatsApp, RCS, or Chat (via Conversations (classic) API). Conversation Orchestrator natively resolves Customer Particiapant addresses (e.g. phone numbers) to an Identity on the Profile in Conversation Memory. This foundation powers Conversation Intelligence, Conversation Memory, and Twilio Agent Connect with a complete picture of every customer interaction.

This release includes:

• Core conversation primitives: Conversations, Communications, and Participants resources provide the building blocks for representing any customer interaction, with full API support for creating, reading, updating, and managing conversation state
• Omnichannel support: One unified conversation model works across Voice, SMS, WhatsApp, RCS, and Chat, eliminating the need to stitch together data from separate channel silos
• Passive and Active ingestion: Choose how Conversations form and Communications flow into them. Ingest existing Twilio messaging and voice traffic automatically, or create conversations explicitly via API/TwiML when your application needs full control
• Intelligent conversation grouping: Configure how traffic groups into conversations, by:
  1. Customer Profile: Recognize the same Customer Participant across channels and devices. This is the default grouping.
  2. Participant Addresses: Omnichannel on same number/ address (ie sms and voice)
  3. Address and Channel: Every new channel makes a new Conversation
• Customer-centric identity: Customer Participants are automatically linked to persistent identities that follow them across channels. When adding Participants, they may be added using addresses or Profiles
• Conversations (classic) API compatibility: Bridge existing Conversations (classic) API services to Conversation Orchestrator, gaining access to Memory and Intelligence features while your application continues to work unchanged

Read the announcement blog post for the full story, or get started with the Conversation Orchestrator documentation.  

Email is now available as a native channel in the Twilio platform. Set up, configure, and try email from the Twilio console, using your existing Twilio account structure, API keys, procurement and billing.

Twilio Email includes:

• The Mail Send API

• Automated domain authentication

• Suppression management

• Email logs

• Subaccount management for segmenting email traffic

 

Coordinating email alongside other Twilio-powered actions such as the Bulk Messaging API has never been easier.

To get started, navigate to the Email section in the Twilio Console under products and services. For API integration, see the Twilio Email documentation.

Compliance Toolkit is now Generally Available for Twilio Programmable Messaging customers in the United States. 

Compliance Toolkit helps you automate regulatory compliance by embedding AI-powered safeguards directly into your messaging workflows. It proactively detects possible compliance violations, identifies high-risk recipients, and applies intelligent transmission controls to prevent issues before messages are sent.

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

 

DigiCert, the Certificate Authority that issues the public TLS certificates Twilio uses, has pushed back the timeline for removing the Client Authentication Extended Key Usage (EKU) extension from their certificates to March 1, 2027. With the extended timeline, we're revisiting our response to this change. 

You can now use the Programmable Messaging API to send and receive SMS in Twilio's Ireland (IE1) region. When using the feature, messages are stored and processed in Twilio's Ireland (IE1) region up to the point they reach Twilio’s connections with telecommunications providers.

This release adds API support in IE1 for:

• Sending SMS messages with phone numbers and alphanumeric sender IDs.
• Receiving inbound SMS messages with webhooks.
• Messaging Services, including webhooks, sticky sender, and country code geomatch.

To learn more and get started, see the Public Beta API docs.

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.