Product changelog and announcements

We've released two new granular roles for the Twilio Console: Messaging Insights & Intelligence Admin and Messaging Insights & Intelligence Viewer. These roles give access to only the Messaging Insights and Intelligence pages.

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. See the complete list of roles here.

Warehouse Enrichment for Journeys Destination Sends

Destination Sends from the new version of Journeys now support enriching outbound payloads with warehouse data, allowing you to add entirely new fields or update key data with the latest and greatest from your source of truth.

Here's how it works. Within a journey:

1. Add a Destination Send step, select your destination and action

2. Click the Entity properties tab

3. Select the entity from your data graph to join to and the join key

4. Select the entity properties to include

Just make sure on the Data Graph > Edit Data Graph that your entity is enabled for Linked Events. All workspaces with access to Engage Foundations are provisioned with access to 1 entity and 1 million rows. If you need more, contact your account team.

Auto-Instrumentation: The End of Manual Tracking

You can now capture, create, and publish events without touching code.
Auto-Instrumentation lets you move at the speed of your business, not your release cycle.

Why It Matters

Manual event tracking slows down product and marketing teams. Each new event usually means a Jira ticket, a sprint slot, and a release window.

Auto-Instrumentation removes that bottleneck. It lets non-engineers define new events in minutes instead of waiting weeks for an app update.

Teams that adopt Auto-Instrumentation see:

• Faster campaign launches and A/B test setups

• Cleaner, more consistent data

• Less engineering overhead and context switching

How It Works

1. Replace the original Segment SDK with the Signals SDK in your website or mobile app (Swift or Kotlin).

2. Enable Auto-Instrumentation in your Segment source settings (Settings > Advanced > Auto-Instrumentation).

3. Turn on Debug Mode on web, iOS, or Android.

4. Interact with your app — Segment records every click, navigation, and API call as interactions.

5. Open the Event Builder in your workspace to:

   • View captured interactions

   • Combine them into Event Rules

   • Map event properties or traits

   • Preview and Publish directly — no deploys needed

Once published, the SDK automatically emits those events through your standard Segment pipelines: Protocols, Destinations, Audiences, Journeys, and Warehouses.

Pro tip: You can verify your event firing in real time from the Source Debugger.

Demo video

Example Use Cases

• Marketing teams can instrument new funnel events instantly — no sprint cycles required.

• Product managers can track onboarding or feature usage without waiting for the next deploy.

Availability

Auto-Instrumentation is now in Public Beta for all workspaces.
Enable it today from your Segment workspace:

Source → Settings → Advanced → Auto-Instrumentation → Toggle On

Then update your SDKs and start capturing your first signals.
 

Read the full setup guide › 

Related Blog: Auto-Instrumentation: The End of Manual Tracking

We’ve expanded the capabilities of alerts and notifications in Flex. You can now send supervisors notifications about important contact center metric changes over email, or use a custom webhook to integrate your other business messaging platforms. In addition, we’ve made multiple APIs available for setting up alerts and thier associated configurations for notifications. 

To learn more, see Alerts for contact center metrics, Notifications API, and Alerts API.

Data Residency for SMS (EU) is available in Private Beta. 

Private Beta participants can now send and receive SMS with message data processed and stored in the Twilio Ireland (IE1) region, keeping personal data in Europe.

Access is limited. Contact your account representative or submit this form to request access.

New real-time assist features for Agent Copilot are now available in Flex. As agents interact with customers in their contact center, Agent Copilot can now automatically suggest responses to agents to save time. 

Agents can also search questions in Agent Copilot, which uses uploaded knowledge sources, such as help center articles, to find relevant answers. Admins can choose which sources to upload in Console, or developers can use the new Knowledge API to upload sources programmatically.

To learn more about Agent Copilot, see Agent Copilot for administrators.

Real-Time Transcriptions for Video is now Generally Available (GA). This HIPAA eligible feature allows 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. For pricing information refer to the Twilio Video Pricing page. 

Developers can choose from various speech models and supported languages to ensure their use case needs are met. In addition, this release adds the Deepgram nova-3 monolingual speech model. 

To start using Real-Time Transcriptions, upgrade your Video Client SDK and review the detailed setup instructions in our developer documentation. A reference implementation of on-screen captions using real-time transcriptions is available here.

We are excited to announce the Private Beta release of our Phone Number Provisioning Status API for Voice Integrity, as well as US Basic and Enhanced Branded Calling.

This API enables customers to programmatically check the carrier-level provisioning status of phone numbers associated with the above Voice Trust products. By providing detailed carrier insights, the API empowers users to understand whether their numbers are successfully provisioned, pending, or rejected by each carrier.

If you would like to participate in this Private Beta, please contact your account representative.

We’re excited to introduce the Branded Calling APIs in Private Beta, expanding our Voice Trust capabilities with full programmatic control.

If you currently use the Console to verify brands and configure branded calls, these APIs extend that workflow - enabling you to register brands, submit compliance details, and assign phone numbers directly via API. This is intended to provide a faster, more seamless way to onboard customers and scale Branded Calling across your applications.

Join the Beta

Interested in early access to these APIs and docs? Reach out to your Twilio account representative; they'll guide you through eligibility and next steps. Spots are limited, so connect soon!

Twilio Communications APIs now support OAuth 2.0 authorization.

Using OAuth 2.0, short lived access tokens can be generated which have scoped access to certain APIs making them more secure than Auth tokens and API keys.