Twilio Changelog

We are officially ending support for the Epic Conference functionality in Programmable Voice. This was a long-running beta program that allowed developers to create a Voice Conference with up to 1000 participants. It did not prove to be as useful to developers as first envisioned and so we are ending support effective today.

Our standard Programmable Voice Conference provides flexible support for multi-party voice use cases with up to 250 participants. Additional details are available here.

The Twilio Debugger now reports on uncaught exceptions or console.error messages that are triggered from the Flex UI or Flex Plugins. In addition to the Debugger, these notifications can also be consumed via the Debugger Webhooks and Alert Triggers.

You can enable the Debugger Integration on the Pre-Release Features Page in the Flex Admin UI. Learn more about how to use the integration by visiting our End User Guide.

This release of Flex UI introduces minor fixes for chat interaction, a new Action for updating agent activity, and UI performance improvements.

For a full changelog, visit the Flex UI release notes.

You can now record voice calls in Flex with two distinct channels, one per party in the conversation. This allows call center managers and quality supervisors to focus on just the customer or just the agent when analyzing calls. The voice player within Flex Insights will separate both channels and highlight who was talking during the conversation.

Visit our documentation for details on enabling and accessing these recordings.

POST request for Twilio <Pay>, once it has successfully tokenized or created a charge, includes the following updates:

• A new parameter called ProfileId - the identifier of the customer object to which the collected payment method is associated. Depending on your connector, this can be used as a token. This value was previously in the PaymentToken parameter if your <Pay> connector is CardConnect, Stripe, or Chase.
• An updated value in the PaymentToken parameter (depending on your connector) - the tokenized value of the payment method.

These changes provide you context and transparency on the value being returned by your selected <Pay> connector when the payment method is tokenized.

If you are already using <Pay>, these changes will not impact you right away. Learn more about the ProfileId, PaymentToken, and their values by <Pay> Connector here.

With the new Play action, you can use pre-recorded audio in addition to text-to-speech to interact with callers. This is especially useful if you have a well-defined IVR script and need to use pre-recorded voices for reasons related to brand and experience. Learn how to use Play in the docs.

The Twilio CLI lets you access all of Twilio’s APIs through the command line to do things like buy and provision phone numbers, send messages and handle incoming calls. It also has a unique plugin model that makes it easy to extend its functionality that we’ve leveraged to build the Autopilot Plugin. You can use it to manage your Autopilot bots, CRUD Tasks, Fields and Webhooks, and add Samples and Field Values directly from a .csv file. Learn how to use the Autopilot Plugin for the Twilio CLI in the docs.

Collect's Prefill feature intelligently skips questions asking for information the user has already provided in the utterance invoking the task. Prefill can be enabled separately on each question by setting the prefill attribute to the Field Name expected. Learn how to use Prefill in the docs.

When building an IVR with Autopilot, you can now provide callers the option to use DTMF alongside speech to interact with the bot. This is especially useful if they need to provide a long numerical sequence like a bank account number in their response, or need to confirm the data the bot has collected. You can use the Listen and Collect actions to add DTMF support to your Autopilot IVRs. Learn more about using DTMF with Listen and Collect in the docs.

TaskRouter no longer immediately deletes tasks if they pass the final step in a workflow without an accepted reservation. After the Workflow Timeout event, these tasks will now transition to Canceled, and the relevant events are being emitted via the TaskRouter REST API Events Resource.

To learn more about the lifecycle of a task, refer to our documentation on task state and workflow execution.