Twilio Changelog

We’ve made a key improvement to Authentication+ to support programmatically triggering a new 2FA verification email for A2P 10DLC Brand registrations that have failed. 

Alongside the endpoint, we’re introducing a set of dedicated 2FA error codes that surface precise failure reasons and point you to the fastest remedy, so your users can complete brand verification with fewer support tickets and less manual work.

To learn more about Authentication+, check out our Support Article and Twilio API Docs.
 

Twilio will now support RCS Title and description text in twilio/card. We will support backwards compatability to ensure no existing templates fail to deliver based on channel limitations. 

No changes will occur in WA translations. 

• Twilio supports RCS title via the title field in twilio/card
  • Up to 200 characters for RCS title
  • Twilio will translate twilio/card title to description if twilio/card title is greater than 200 characters
• Twilio supports RCS description with the body field in twilio/card
  • twilio/card subtitle will also be appended onto the body to form RCS description

Voice Recording Storage billing behavior is changing to improve accuracy and will provide daily usage metrics.

Real-Time Transcriptions are now available in Public Beta, allowing you to access the transcribed text from participants in your Video Group Rooms and provide on-screen captions for accessibility. You can opt in to transcriptions on a per-Room basis via the REST API or enable it by default on all Rooms via the Twilio Console configuration.   

Real-Time Transcriptions leverages the scale and programmability of the Twilio Communications Platform. You can choose supported languages and speech models, and control when transcriptions start or stop in each Group Room. The feature is available in the latest JavaScript, iOS, and Android SDKs.

To start using Real-Time Transcriptions, upgrade your Video Client SDK and review the detailed setup instructions in our developer documentation.

With Enhanced RBAC we are introducing 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.

We can assign these roles at organization, account or subaccount level unlike the current general roles which can be assigned only at the account level.

Studio now supports the ability to shorten links within your message body when using the Send Message and Send & Wait For Reply widgets. You can also shorten links to track customer engagement with click events.

Effective July 15, 2025: Twilio SendGrid launched data residency within the EU for email. This enables you to keep all email event data such as opens, clicks, bounces, and unsubscribes, and email recipient emails within the EU, giving you control over where your customer data lives. This is important as email event data, which includes recipient email addresses and engagement history data is considered personally identifiable information. 

Before, when you sent an email through Twilio SendGrid, it was handled by our global API. That meant your email and the data it generates is processed through our global infrastructure and stored in data centers around the world.

With Data Residency for Email (EU), the flow is different. Emails sent through the EU API are processed within the EU region, and recipient personal data and email event data is stored in EU-based systems. This gives businesses more control over where their data is stored and helps meet regional compliance standards without compromising performance or deliverability.

WhatsApp Business Calling for Twilio Programmable Voice is now available.

Twilio SendGrid now supports multi-account access, enabling Twilio Login users the ability to access multiple SendGrid accounts through a shared SendGrid and Twilio credential. This is built into the existing teammate invitation workflow and allows admins to invite an existing email that already have access to other SendGrid accounts. Invited teammates can easily switch between accounts from a new account selection page—no need to sign in and out each time nor manage separate credentials for each account.

This update streamlines multi-account management and improves security, making it easier to work across departments or business units within SendGrid.

All ID fields specified in the Twilio Content Content APIs such as in Twilio cards will be returned in Button Payload in a uniform way.

We will return the exact payload specified without 64 bit encoding to align button behavior.  

To specify a Button Payload, pass in an ID field into the button actions array within a button object. Examples can be found in the Twilio docs. Button Payloads will be returned in the inbound webhook. Billing may apply. To learn more see our docs here.