Changelog

Elastic SIP Trunking - Pass on 603+ Reason Header Information

Thu, 23 Apr 2026 00:00:00 -0400

Flex UI 2.17.0 is now available

Tue, 21 Apr 2026 14:30:00 -0400

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.

Twilio Java Helper Library Major Version Release 12.x.x

Tue, 21 Apr 2026 01:00:00 -0400

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.

Intelligent Alerts for Twilio Messaging is now Generally Available

Tue, 21 Apr 2026 01:00:00 -0400

Twilio Node Helper Library Major Version Release 6.x.x

Mon, 20 Apr 2026 00:00:00 -0400

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.

Transit CallerID Sunset: Migrate to Verified CallerID or Immutable Call Forwarding Before May 31, 2026

Mon, 13 Apr 2026 01:00:00 -0400

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.

Consent Management API is in Public Beta

Thu, 09 Apr 2026 14:30:00 -0400

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.

TCPA Known Litigators Check is now available in Compliance Toolkit

Thu, 09 Apr 2026 14:30:00 -0400

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.

Specify your SMS fallback sender when sending RCS messages

Thu, 09 Apr 2026 03:00:00 -0400

You can now specify the SMS or MMS sender Twilio uses when an RCS message fails to deliver using the new "FallbackFrom" parameter in your /Messages API request. The FallbackFrom sender must be in the same account SID, but does not need to be in your Messaging Service's sender pool.

This can be useful if you need fallback messages to come from a specific number, instead of relying on Twilio's automatic selection. You can also use this to send from one RCS sender representing your brand, with different fallback numbers per department, store, or representative.

For more information, please see our docs.

Country Code Geomatch now supports RCS (Beta)

Thu, 09 Apr 2026 03:00:00 -0400

The Country Code Geomatch feature within Messaging Services now supports RCS in a public beta. If you have distinct RCS senders approved per country, you can add each of them to the sender pool of a single Messaging Service. When you send from that Messaging Service, Twilio will select the RCS sender that matches the country of your recipient’s phone number.

Previously, each Messaging Service supported only one RCS sender, which meant customers sending to recipients in multiple countries had to maintain separate Messaging Services and build their own routing logic. RCS Geomatch removes that requirement.

For more information, see the Messaging Services’ docs.

ConversationRelay Payment Card Industry (PCI) Compliance

Thu, 09 Apr 2026 02:00:00 -0400

Twilio ConversationRelay now supports Payment Card Industry (PCI) compliant Voice workflows when configured with PCI-compliant TTS (text-to-speech) and STT (speech-to-text) providers. Please refer to Twilio's Responsibility Matrix to see a list of PCI-compliant TTS/STT vendors and for further information. To learn more about ConversationRelay please see the docs.

AT&T phone numbers can now be added as RCS test devices

Thu, 09 Apr 2026 00:00:00 -0400

Twilio Programmable Messaging now supports adding AT&T test numbers to your RCS sender.

You can now prototype and test your RCS sender on all major US carriers.

Once you’re ready to use RCS for production traffic, submit your RCS compliance information and our operations team will guide you through the carrier approval process

Go to Console to get started now.

For more information, see our docs.

OAuth for Twilio APIs is now in GA

Mon, 06 Apr 2026 14:30:00 -0400

Twilio Communications APIs now support OAuth 2.0. Upgrading to OAuth 2.0 makes your applications more secure than using traditional API keys or Auth tokens. Here is why:

Short-lived tokens: OAuth 2.0 generates short-lived access tokens instead of static, long-lasting credentials.
Scoped access: Each token only works with the specific APIs it was issued for, so a compromised token doesn't expose everything.

A2P 10DLC campaign registration will require privacy policy and terms & conditions URLs starting June 30, 2026

Mon, 06 Apr 2026 02:00:00 -0400

Starting June 30, 2026, PrivacyPolicyUrl and TermsAndConditionsUrl will be required fields when registering a new A2P 10DLC campaign via the Twilio Messaging REST API. Campaign creation requests that don’t include both fields will be rejected during campaign review.

Branded Calling Insights: Canada, United Kingdom, & Germany

Sun, 05 Apr 2026 14:30:00 -0400

Branded Calling Insights for Canada, the United Kingdom, and Germany are now live in the US1 region.

Verify Events: Message Status Event Stream V2 released with new Tags parameter

Wed, 01 Apr 2026 19:00:00 -0400

V2 of Verify Message Status events is now available. This version adds a "tags" parameter to the event stream. By including key-value pairs in your Start New Verification request, you can now pass custom metadata through to your stream for better tracking. Check out the Message Status Stream guide to get started.

Verify Events: Verification Stream (all versions) will no longer provide updated message delivery status or error code information

Wed, 01 Apr 2026 19:00:00 -0400

New customers subscribing to the Verification Event stream will no longer provide updates on the delivery_status for each send_code_attempt and its value will be set to a static status of SENT. The error_code attribute will also be removed from each attempt. To obtain updates on message delivery status, new subscribers should now use the new Message Status Event Stream.

Verify Events: Verification Event Stream V3 released with new Tags parameter

Wed, 01 Apr 2026 19:00:00 -0400

Verify Event's Verification stream has a new version 3 that includes a new "tags" parameter in each attempt. This set of custom tags will appear in the event stream when you include a key value pair in the tags parameter of the Start New Verification request. To learn more, please visit our Verification Status Stream guide.

Twilio integration with Salesforce Service Cloud Voice is live on AppExchange

Tue, 31 Mar 2026 14:30:00 -0400

We’re excited to announce that Twilio’s integration with Salesforce Service Cloud Voice is GA and listed on the AppExchange.

This release comes with the following enhancements:

External Call Transfers: Agents can now transfer calls to external phone numbers.
Supervisor Barge & Listen: Supervisors can now monitor live calls and “barge in” to assist agents during critical customer interactions.
Toggle Real-Time Transcription: Administrators can enable or disable real-time transcription based on specific privacy requirements or workflow preferences.

To learn more about setup, please see the setup guide.

Voice Insights: Trust & Engagement Insights and Reports API (GA)

Tue, 31 Mar 2026 03:00:00 -0400

Voice Insights Trust & Engagement Insights and its companion Reports API are now Generally Available. This combined release provides a comprehensive solution for managing outbound calling health and campaign ROI.

Trust & Engagement Insights offers a specialized Twilio Console dashboard to detect behaviors triggering spam labeling, identify blocked calls, and optimize dialing windows with a best-time-to-call heatmap. Users can quantify campaign effectiveness through a visual engagement funnel and measure the ROI of trust investments like Branded Calls.

The Reports API serves as a zero-infrastructure companion, allowing you to programmatically retrieve these same aggregated metrics—per account or per phone number—with a single call. By outsourcing data processing to Twilio, you can accelerate decision-making and reduce operational costs by up to 90%.

Key Benefits:

Holistic Health: Monitor Trust & Engagement scores to proactively mitigate spam labeling and blocks.
Performance Optimization: Use heatmaps and human-answer rates to refine dialing strategies.
Programmatic Access: Use the Reports API to build custom dashboards or integrate metrics into your own internal tools.
ROI Attribution: Compare branded vs. unbranded call performance to justify trust product investments.

These features are available exclusively as part of Voice Insights Advanced Features.

Learn more in our Trust & Engagement Insights and the Reports API documentation.

Twilio SCIM API

Sun, 29 Mar 2026 19:00:00 -0400

Twilio SCIM API is now Generally Available (GA). You can now automate user provisioning and deprovisioning directly from your Identity Provider (IdP), keeping Twilio access in sync as your team grows and changes.

Connect your IdP to Twilio using the SCIM 2.0 standard by creating an OAuth application in the Twilio Admin Center. Use the access token to manage users via the SCIM API endpoints—create new Twilio users, update user details, and deactivate access automatically.

Create a new OAuth application using the authorization code grant type with the required SCIM scopes.
Use the access token to manage users via the SCIM API endpoints—create Twilio users, update user details, and deactivate access automatically
Okta is supported out of the box; Azure AD and Google Workspace require custom setup.

To learn more about the SCIM API, please check our docs.

Add a Flex Instance to existing Twilio account or subaccount

Thu, 26 Mar 2026 14:30:00 -0400

We are excited to announce that Flex instances can now be added to any existing Twilio account or subaccount. Key features include:

Reuse existing resources: You can now add Flex to any existing (non-Flex) Twilio account. This allows you to leverage existing phone numbers and Studio flows without the need for time-consuming resource migrations.
Subaccount support: Flex instances can now be deployed within Twilio subaccounts. This is ideal for managing distinct Flex environments for:
- Regional or departmental deployments: Separate instances for different countries or regions or departments like sales or support.
- SDLC environments: Clear separation between Dev, Staging and Production.
- Tenant isolation: ISVs can provide strict data and configuration isolation for end-customers within a multi-tenant architecture.

Flex SDK is GA

Thu, 26 Mar 2026 01:00:00 -0400

We are thrilled to announce that the Flex SDK has officially moved to GA. The Flex SDK enables embedding Twilio Flex contact center capabilities into any web application. This release includes:

The SDK is now significantly more lightweight.
This version requires a minimum Node.js version 20.
Bug fixes and enhancements.

For details, see the Flex SDK docs.

Detect entity context changes with data freshness for Linked Audiences in Segment

Thu, 26 Mar 2026 01:00:00 -0400

In Segment, Linked Audiences now supports data freshness detection for Identify events. When you configure an activation with the new "Profile enters or exits audience or entity values changed" trigger, Segment detects changes to entity context data between runs and emits an Identify event for affected profiles — even if their audience membership hasn't changed. This keeps enrichment values up to date in Braze, Customer.io, and AWS S3, making it easier to power time-sensitive journeys like past-due reminders, onboarding sequences, and abandoned cart campaigns.

To learn more, see our Linked Audiences docs.

Create entity-based Linked Audiences in Segment

Thu, 26 Mar 2026 01:00:00 -0400

In Segment, you can now choose to build entity-based Linked Audiences, explicitly scoped to entities such as accounts, businesses, or households. Once users select the activation target upfront, the builder dynamically adapts, ensuring conditions, operators, and validations match user expectations for that specific entity. When you preview your Linked Audience, you'll see the count of audience members who meet the criteria and a sample of matching entities.

To learn more, see our Linked Audiences docs.

Configure Part of Audience to import audience conditions in Segment

Thu, 26 Mar 2026 01:00:00 -0400

In Segment, when building an audience based on audience membership, you can use existing audiences as criteria for creating new audiences. You can include or exclude profiles based on their membership in other audiences, allowing you to generate more specific audience segments. You can configure your conditions with:

Import audience conditions: This copies the conditions from the referenced audience and generates a combined SQL query. The audience runs independently, even if you disable the original audience or update it later. Use this option when you need the freshest compute result, since this eliminates the Profile Sync delay (about 1 hour).
Use audience membership traits: This references the original audience membership traits, so it may take extra time to update if that audience needs to recompute. Use this option if the base audience membership doesn’t need to be recomputed every time, in order to save on compute costs.

To learn more, see our Linked Audiences docs.

RCS support now available in Studio

Wed, 25 Mar 2026 01:00:00 -0400

Twilio Studio now natively supports RCS (rich communication services) for both outbound and incoming message flows. This means you can now build and automate rich, branded, and interactive messaging experiences directly within Studio, leveraging all the benefits of RCS—such as rich media, card crousels, and webviews—without the need for workarounds or custom integrations.

For configuration details and best practices, see our documentation:

Start Conversation widget now available in Studio

Thu, 19 Mar 2026 01:00:00 -0400

Studio now includes the Start Conversation widget, which enables Studio flows to initiate a two-way Twilio Conversation without requiring custom code or direct API calls. This widget creates a Conversation with a single participant and configures Studio to continue the flow when inbound messages are received.

Note that this widget is only for outbound/REST API triggered flows. Inbound flows already support Twilio Conversations without the Start Conversation widget.

For more information, see our Start Conversation widget docs.

Increased MMS rate limits for A2P 10DLC Phone Numbers in the U.S. starting March 18, 2026

Tue, 17 Mar 2026 02:00:00 -0400

Starting March 18, 2026, MMS rate limits for Application-to-Person (A2P) U.S. 10-digit long code (10DLC) numbers are determined by Brand Trust Score and Campaign use case, replacing the previous fixed account-level cap of 1 message per second (MPS).

Twilio Now Supports Unified Opt-Outs across RCS, SMS, and MMS channels

Sun, 15 Mar 2026 14:30:00 -0400

Twilio Programmable Messaging automatically unifies opt-out management across RCS, SMS, and MMS channels.

When an end-user replies with any opt-out keywords (such as STOP, CANCEL, or UNSUBSCRIBE etc) to an RCS message, Twilio automatically enforces that opt-out for all future SMS or MMS messages sent from that same Sender or Messaging Service. Conversely, opt outs on SMS or MMS will automatically block future RCS messages.

Any attempt to message an opted-out user across these unified channels will now fail and return Error 21610.

This cross-channel compliance is active by default to protect your sender reputation, prevent accidental messaging on fallback channels, and requires no code changes to implement.

For more information, read our documentation.