Product changelog and announcements

You can now send RCS messages to Rogers phone numbers, completing RCS coverage across Canada’s major carriers.

When requesting RCS Sender approval in Canada, Twilio will now submit the Sender for review across all major carriers, including Rogers. RCS Senders already approved by other Canadian carriers will automatically be submitted to Rogers for review and approval. No action is required.

To start sending branded RCS messages, go to the Twilio Console to create and submit an RCS Sender.

For more information, see our RCS documentation.

We have a new action 'Send Event asynchronously to Data Extension' in the SFMC actions destination live in Private beta with observability.

With this feature, we switch to using SFMC’s asynchronous APIs and deliver data in much larger batches. That allows SFMC to process requests in the background while we send fewer, bigger payloads-This phase is designed to validate the async batch pipeline at meaningful enterprise volumes. You can expect to test audiences as high as close to 40 million profiles range, covering both the initial full sync and ongoing differential updates as your audience membership changes between runs.

With this release- Segment's Delivery Overview shows the outcome of each sync run, displaying the total number of records successfully delivered, records dropped, and the high level reason for any failure at a batch-level (It excludes sample events).

Please get in touch if you interested in the beta.

Starting October 5, 2026, paid support customers can reach Twilio through live chat for help with Segment and all Twilio platform applications and products.

We have gone GA with one of the AWS S3 Actions destination.

AWS S3 Classic destination stored raw Segment logs in your bucket, but standardizing or transforming that JSON for analytics and integrations was left to you. The AWS S3 (Actions) destination handles that upfront, saving engineering time and reducing the complexity of your data pipeline.

The AWS S3 (Actions) destination allows you to store event data as objects in a secure, scalable cloud storage solution. Each event is written to your S3 bucket, organized into a customizable folder structure such as by event type or timestamp. This makes it easy to manage, archive, and analyze data using downstream tools or AWS services.

Public documentation link

TaskRouter and Studio are now available in Public Beta in Twilio's Ireland (IE1) Region, giving you EU data residency and control over where your contact center routing and workflow automation data lives.

Short Code numbers are now supported as SMS senders in Twilio's Ireland (IE1) region for EU data residency. When using this feature, SMS message personal data sent or received via Short Codes is stored and processed in the EU up to the point it reaches Twilio's connections with telecommunications providers.

With this release, the IE1 region supports the following features:

• Short Code senders: Send and receive SMS messages with short codes in IE1. 

• Region Configuration API: Configure short codes for IE1 using the V3 region configuration API.

• Short Codes API: Set IE1 inbound webhook configurations using the ShortCodes resource.

• Messaging Services API: Add short codes to IE1 messaging services using the service ShortCodes subresource.

To learn more and get started, see the developer documentation.

The Segment Conversation Memory Integration is now in GA. You can now sync long-term customer profile data, like identity and lifetime value, from Segment into the sub-second recall of Conversation Memory, enabling both AI and human agents to instantly access unified context during live interactions. This eliminates cold starts, reduces repetitive questions, and delivers highly personalized, continuous customer experiences across all channels.

The integration continuously syncs long-term customer profile data, such as identity and historical traits, from Segment directly into Conversation Memory. Customers configure this transfer using either "Memory Sync" to rapidly import their entire profile database or "Memory Destination" to target specific user cohorts via Segment Audiences. During setup, Segment profile traits and identifiers are mapped to corresponding semantic trait groups within a Memory Store. Once active, trait updates flow in real time, allowing AI or human agents to instantly query the Memory Store for up-to-date customer context during live interactions.

To get started, read the Segment Conversation Memory Integration | Twilio, and browse the Conversation Memory (Actions) | Twilio. 

Tune transcription without touching your code: engine, model, language, and destination live in a reusable configuration, so changing any of them is one update that every subsequent transcription picks up. Results are delivered via webhook or stored downstream in Conversation Orchestrator for persisted storage and Operator analysis. 

Voice Insights now tells you why a carrier blocked your call and how to reach that carrier for redress.

The FCC requires carriers that block calls using analytics to return the reason header to the caller. It names the network that blocked the call and tells you how to contact them: a URL, a phone number, or an email address. Until now a blocked call showed you only a 603 response. Now you can see which network blocked it and petition them directly.

The reason header appears alongside Last SIP Response in the Call Summary, in Twilio Console, the Voice Insights REST API, and Event Streams.

If you are seeing a high volume of 603 responses, confirm your traffic is signed with STIR/SHAKEN and registered with Twilio Voice Integrity before you start filing redress requests.

Learn more in our Call Summary documentation.