Product changelog and announcements

Twilio will now support RCS Title and description text in twilio/card. We will support backwards compatibility 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

Mappings editor improvements is now Generally Available!

These enhancements make creating mappings easier, faster, and more intuitive - empowering you to build data mappings with greater flexibility and efficiency. We've revamped the mappings editor to include the following features:

• 🔍Streamlined search: we’ve consolidated the mappings editor to a single, intuitive search bar, making it easier to find, select, and create event properties

• 💊Copy-and-paste pills: you can now copy-and-paste event property pills directly within the input field, eliminating repetitive manual selections

• ⬇Smart dropdown interaction: clicking a pill in the input field automatically opens the dropdown with the selected pill highlighted, improving usability

• ✅ Static value support: in addition to strings, you can now create static values as boolean, number, or null types, providing greater control over data types in mappings

• 📍Combine event properties with strings: you can create dynamic mappings by combining event properties with static strings for more flexible data structures

For example, you will now be able to:

• Search for properties using a single, unified search bar

• Copy a pill like {{properties.email}} and paste it in the mappings editor

• Combine properties with strings, e.g., User: {{properties.name}} to create custom outputs

• Cclick a pill to instantly access its dropdown options for quick edits

• Define static values like true, 42, or null directly in the mappings, instead of only string values like "true"

For more information, check out our docs.

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.

We're announcing updates that improve the visibility of WhatsApp voice call metrics in Voice Insights, for customers using the WhatsApp Business Platform with Twilio. Here's a detailed rundown of the new updates:

Voice Insights API Updates:

• Call Summary API & Eventstream: A new parameter, call_type: "whatsapp", has been introduced to distinguish WhatsApp calls. Metrics for these calls are accessible within the carrier object of the Call Summary API.

• Call Events & Call Metrics APIs:Customers can track and analyze WhatsApp RTP stats and call progress events through the Call Events and Call Metrics APIs.

Voice Insights Console Updates:

• Call Logs Page: Within the Insights Summary tab, customers can now view metrics and track call progress events for individual WhatsApp calls.

• Call Insights Dashboard: On the Call Insights Historical View page, customers have the added functionality to filter dashboard data by the "whatsapp" call type.

For more information, please refer to the Voice Insights reference docs.  

The Object Editor now supports dot notation, allowing you to create nested objects and arrays in destination fields, enabling more complex and structured data mappings. This allows you to map flat event properties and profile traits to nested structures in the destination payload.

• Nested Objects: Use dot notation (e.g., info.name) to create nested object fields.

• Arrays: Use array index notation (e.g., info.[0].name) to create arrays with nested objects.

What changed? Previously, you could only create flat objects and arrays like this:

{
 "name": "{{properties.name}}",
 "email": "{{properties.email}}",
 "address": "{{properties.address}}"
}

Now, with dot notation, you can create nested objects and arrays using index notation:

{
 "info.name": "{{properties.name}}",
 "info.email": "{{properties.email}}",
 "details.address": "{{properties.address}}"
}

{
 "info.[0].name": "{{properties.name}}"
}

which will produce the following structure in the destination payload:

{
 "info": {
 "name": "John Doe",
 "email": "john.doe@example.com"
 },
 "details": {
 "address": "123 Main St"
 }
}

{
 "info": [
 {
 "name": "John Doe"
 }
 ]
}

Existing mappings that include literal dots or array notation in keys (e.g., info.name as a single key) will continue to function as literal keys. To differentiate these from the new nested object syntax, literal keys containing dots or array symbols will be enclosed in double quotes in the Object Editor UI. For example:

• Old mapping: info.name (interpreted as a single key)

• New representation in UI: "info.name" (to preserve it as a literal key)

When editing existing mappings, the UI will automatically display double quotes around keys that contain dots or array symbols to avoid unintended conversion to nested objects. New mappings using dot notation without quotes will be interpreted as nested structures.

For more information, check out our docs.

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.