Product changelog and announcements

The conference_participant field in the Voice Insights Call Summary is being removed from the REST API and Event Streams August 1, 2026. This field pre-dated Conference Insights and had limited accuracy due to the complexity of conference call flows. It is currently only populated for calls eligible to participate in a Twilio conference; all others return attributes: null. After removal, all calls will uniformly return attributes: null. Use the Conference Insights API or Conference Insights Event Streams for conference data going forward.

Twilio recently made improvements to our platform to increase RCS delivery and improve fallback consistency.

The time for a recipient’s device to confirm delivery before an RCS message’s status is updated to "undelivered" or a fallback SMS / MMS is sent, no longer depends on how long a message is queued within Twilio. Consequently, when messages queue within Twilio (as expected when sending large marketing campaigns) Twilio’s native fallback-to-SMS feature now ensures messages to RCS-capable devices are always attempted to be delivered on RCS, and no longer will fall back prematurely.

In addition, to optimize our platform by balancing successful RCS delivery with timely message resolution (whether that results in a native SMS / MMS fallback or a timely "undelivered" status), the amount of time given to devices to confirm delivery has been updated. As a result, you may notice messages falling back to SMS / MMS or an RCS message’s status updating to undelivered faster or slower than before.

No code changes are needed to take advantage of these optimizations. However, you may guide this behavior by ensuring you are using the "ValidityPeriod" parameter. Though the "ValidityPeriod" parameter continues to only apply to messages queued within Twilio’s platform, it is used to inform Twilio of how time-sensitive the message is and when a faster fallback or failure signal is needed. For time-sensitive messages, like OTPs or appointment reminders, it’s recommended to use a shorter value than the 10-hour default, like 30 seconds or 15 minutes. For customers sending RCS without Twilio's native fallback feature, these optimizations also ensure the message’s status moves to "undelivered" when it is no longer likely to be delivered, rather than waiting hours (or days) for it to inevitably expire.

Consent Management API is now Generally Available allowing you to programmatically sync, store, update, and manage user consent preferences globally across RCS, SMS, and MMS channels.

As of June 30, 2026, Consent Management APIs can now support healthcare use cases that may contain protected health information (PHI) for organizations that are subject to the Health Insurance Portability and Accountability Act (HIPAA). Twilio will sign Business Associate Addendums (BAA) with covered entities and business associates for HIPAA Eligible Services. Learn more about how to build on Twilio for HIPAA compliance.

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

As of June 30, 2026, Compliance Toolkit can now support healthcare use cases that may contain protected health information (PHI) for organizations that are subject to the Health Insurance Portability and Accountability Act (HIPAA). Twilio will sign Business Associate Addendums (BAA) with covered entities and business associates for HIPAA Eligible Services. Learn more about how to build on Twilio for HIPAA compliance.

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

Twilio Conversation Relay handles the real-time complexity of voice AI interactions - transcription, turn-taking, interruption handling, speech generation - so that your app logic stays focused on the conversation itself. We've published a reference component for the Twilio Voice React Native SDK to show how that works end-to-end on mobile.

Twilio is launching the Private Beta for Compliance Embeddable for US A2P 10DLC.

The Compliance Embeddable is a white-label, self-service solution that integrates seamlessly into an Independent Software Vendor’s (ISV) application portal. With the Compliance Embeddable, end customers can independently complete both brand and campaign registrations while Twilio handles the underlying regulatory infrastructure behind the scenes. 

Featuring fully customizable styling and data pre-filling, the Compliance Embeddable simplifies end-user registration, reduces internal development overhead, and streamlines onboarding workflows.

Sign up for the Private Beta to get started.

With Enhanced RBAC we have introduced more granular roles called built-in roles, which provide access to specific Twilio products including Messaging, Studio, Phone Numbers etc. You can find the complete list of new roles here.

These roles can be assigned at the organization, account or subaccount level, unlike the general roles which can only be assigned at the account level.

Twilio is announcing its public beta availability of Call Forwarding with Caller ID preservation. Twilio Elastic SIP Trunking customers who would like to preserve & retain the caller ID from the incoming trunking origination call in their outgoing trunking termination (forwarded) call for context about their customers can now use this feature. Twilio Programmable Voice already has support for this functionality via CallTokens.

New Unified Typing Indicator API experience:

You can now send typing indicators across RCS, WhatsApp (WA), and Apple Messages for Business (AMB) using a streamlined consistent integration with JSON payloads.

Smart Channel Behaviors:

• RCS: Displays a typing indicator for up to 20 seconds (or until the message delivers) to reduce perceived wait times.
• WhatsApp: Automatically marks the referenced message as read and displays the indicator for up to 25 seconds (or until delivery) using the required messageId.
• Apple Messages for Business (Private Beta): Support for Typing indicators is available! Please note that AMB access is currently restricted as it is in private beta. How to use typing indicators on AMB is available in our beta documentation. 

💡 Need more time? For longer workflows, you can send additional typing indicator requests to extend the duration before the default timeouts hit.

See our public documentation here:

• RCS
• WA

Studio and TaskRouter are now available in Private Beta in Twilio's Ireland (IE1) region. With this release, your application's Studio and TaskRouter data is processed and stored in IE1, providing EU data residency and control over where your contact center routing and workflow automation data lives.

You can learn more on Studio and TaskRouter as well as other Regional products on our Regional product and feature availability page. To request Private Beta access, contact your account team.