Twilio Changelog

We're excited to announce that the Update Profile Traits Widget is in Private Beta. Use this widget to take information you learn about a caller during a flow execution and send it to Unified Profiles to update profile trait data. This allows you to enrich profiles to personalize future customer experiences based on their profile traits. 

Visit the Update Profile Traits Widget docs to learn more.

When using the Set Variables widget and Run Subflow widget, parameters are (by default) parsed as strings. Use the `parse as JSON object` option when you know a parameter will be a JSON object. This will allow the variable to be properly interpreted as a JSON object so you can reference its attributes within the Studio flow. 

The `parse as JSON object` option allows you to:

• Set or pass an existing JSON object and reference its members as variables.

• Set a literal JSON string (Liquid reference to a JSON string, or a mixture of JSON and Liquid) and access it as an object. 

Use twilio/catalog to send items and services directly to your customers on WhatsApp and guide them through a transaction

The Make HTTP Request widget configuration now includes a checkbox allowing the request to be made with your Twilio credentials. 

This makes it easy to invoke Twilio APIs that are not available natively as Studio widgets. It is also more secure than embedding your Twilio credentials within the request URL.

To learn more, visit the Make HTTP Request documentation, or try it out now in Studio.

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.