Product changelog and announcements

Content Templates, Content Variables, and rich features from Content Template Builder are now supported in Studio.

Content Templates are currently available on WhatsApp, Facebook Messenger, SMS, MMS, and Google Business Messages. New channels will continually be added. 

Content Templates can be used for generating automated responses to your customers in Twilio supported channels. Content Templates enable the use of rich content and personalization via buttons, media, variables, and channel specific template types to drive greater engagement and streamlined messaging interactions.

Use Content Templates in Send and Send & Reply widgets. Use rich features in the Split widget. 

Variables in WhatsApp and other channels can now be specified using Content Variables via key-value pairs instead of body insertion in a simple deterministic structure.

See our public documentation to learn more.

Studio now supports SSML tags when using Amazon Polly voices in Say/Play and Gather Input On Call widgets.

To enable SSML, select a default Polly voice from the Text-to-Speech Settings in Twilio Console or select one from the Voice dropdown menu on the Studio widget.

Add the SSML tags you wish to use directly in the Text to Say field.

Now you can more easily scale your low-code Voice and Messaging applications with Studio Subflows!

• Reduce complexity when managing large Studio Flows by breaking them down into smaller parts.
  
• Shorten Flow-publishing times by reusing portions of Flows that are common across multiple Flows.
• Increase operational efficiency by handling calls and messages with the most relevant Subflow.

Studio Subflows is now generally available to all Twilio accounts.

To learn more, check out the Subflows docs or try it out in Twilio Console now!

To correctly end an Execution for an inbound Voice call, Studio needs the “hangup” event from the Voice status callback. When that event is not received, the Execution may be left open (or “stuck”) indefinitely.

To address this, Studio now automatically configures the status callback shortly after configuring your phone number for Studio. This ensures the final “hangup” event is always received. With this release, manually setting the status callback is no longer necessary and helps avoid “stuck” Executions for inbound calls.

To learn more, review our knowledge base article.

The Studio REST API v2 with Flow publishing support is now Generally Available. Now developers can create, publish, and manage Flows programmatically -- without having to log in to Twilio Console -- and all with the backing of Twilio's service level agreement.

With the Flows endpoint you can

• Integrate Flow publishing into your CI/CD pipeline to automate Studio deployments
• Programmatically move Flows between accounts or subaccounts
• Create your own custom, branded Studio front-end UI

To learn more, read the announcement on our blog or try the quickstart.

Now you can easily search large Flows and jump to a specific widget in Studio. No more dragging and panning the canvas to find a widget!

To launch the search bar, click the magnifying glass or use the keyboard shortcut CMD + k for Mac and CTRL + k for Windows.

Type a partial name and select the widget from the search results to jump instantly to that widget.

Try it now in Studio!

With Flow publishing support built into the Studio REST API v2, you can now create, publish, and manage your Flows programmatically without having to log in to Twilio Console.

Flow definitions are exposed as JSON schemas and can be easily updated via the Twilio helper libraries and Twilio CLI.

With the new Flows endpoint you can

• Integrate Flow publishing into your CI/CD pipeline to automate Studio deployments
  
• Programmatically move Flows between accounts or subaccounts
• Create your own custom, branded Studio front-end UI

The Studio REST API v2 is now available on all customer accounts.

To learn more, read the announcement on our blog or try the quickstart.

Twilio Studio now supports programmatically ending an active Execution via the REST API and the Twilio helper libraries. This method is useful in cases where a new REST API-triggered Execution needs to override an existing Execution that is already active for the same Contact. Previously active Executions could only be ended via the Console.

To learn more, visit the API documentation for End an Active Execution.

Following the release of Amazon Polly Neural Text-to-Speech voices for the Voice <Say> verb, Studio now supports the same new voices in the Say/Play and Gather Input widgets.

Twilio Functions created via the Serverless API can now be integrated with your Studio Flows through the Run Function widget.

Selecting a Function to invoke in the Flow is easy. For Functions created via the Console UI choose the "Default" service, and for Functions created via the Serverless API choose the Service and Environment where they are deployed.