Twilio Changelog

Collect's Confirm feature simplifies programming your bot to confirm the answers it receives from the user during a question answer sequence. Confirm can be enabled separately on each question using the confirm attribute. Learn more about using Collect Confirm in the docs.

Inbound Context lets you add data to the Autopilot Memory before starting a dialogue with the bot. It can help you make the bot experience more personalized and contextual by making information like names, purchase histories, account numbers etc. stored in third-party systems available directly in the bot conversation.

Inbound Context is available on all channels supported by Autopilot:

• SMS
• Voice
• Studio
• Chat
• WhatsApp
• Facebook Messenger
• Alexa
• Google Assistant
• Custom Channel

Test your email content against spam filters, validate hyperlinks, and preview HTML rendering across browsers and devices with Email Testing for Dynamic Templates. Monthly testing credits included for Trial, Pro and Premier plans, with additional credits available for purchase. See our Email Testing documentation for more details.

We've made some improvements to Transactional Templates. We've renamed them to Dynamic Templates since they can be used to build the content for any type of email message sent over our Email API. They can be found in the app’s sidebar navigation under both the new “Email API” navigation item or the “Templates” navigation item. We've also eased ongoing template management by adding thumbnail images and allowing duplication of entire templates as well as the individual versions within a template.

For more, see our blog post about working with Dynamic Templates.

Twilio Elastic SIP Trunking and SIP Interfaces have added support for a new codec, G.711 A-Law, also referred to as PCMA. Twilio now supports both G.711 versions, µ-Law (PCMU) and A-Law (PCMA).

This addition allows customers more flexibility in configuring their SIP infrastructure, especially in countries where G.711 A-Law is the prevailing standard codec. It also makes connecting with their SIP customers easier, as most SIP implementations will support at least one of the G.711 codec versions. Additionally, acceptance of a new codec could conceivably reduce transcoding on customer networks, which in turn could reduce network overhead and improve performance.

Please see our SIP Interfaces documentation for more information

Getting help while editing a Studio Flow just got easier with the release of the embedded help system. Now you can open help pages and search the docs without leaving the editing canvas.

Click any of the help icons throughout the canvas to load the Studio docs in the help window. The help window can be moved anywhere on the canvas that you find convenient or minimized to stay out of your way while you work.

Open a Flow and click the help icon to try it out in Studio.

This release of Flex UI introduces Chat and Messaging Transcripts for Flex Insights. Supervisors can now open a historical chat or messaging conversation from Flex Insights and see its content. While viewing the content, it is also possible to comment and assess these conversations.

Other notable changes:

• New Actions to programmatically send DTMF tones when there is an active voice connection.
• Flex Insights screens are accessible from top-level Flex navigation.
• Flex Insights Player opens directly within the dashboard instead of opening in a separate window. This significantly improves the speed with which you can scan through multiple calls or chats.
• You can now attach references to 3rd-party web content related to conversations – such as CRM records – and open these directly in Flex Insights.

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

Twilio Elastic SIP Trunking and SIP Interfaces have added support for a new codec, G.711 A-Law, also referred to as PCMA. Twilio now supports both G.711 versions, µ-Law (PCMU) and A-Law (PCMA).

This addition allows customers more flexibility in configuring their SIP infrastructure, especially in countries where G.711 A-Law is the prevailing standard codec. It also makes connecting with their SIP customers easier, as most SIP implementations will support at least one of the G.711 codec versions. Additionally, acceptance of a new codec could conceivably reduce transcoding on customer networks, which in turn could reduce network overhead and improve performance.

Please see our Elastic SIP Trunking documentation for more information.

We have updated all Flex projects that use Automatic Updates to Flex UI 1.15.

This Flex UI release 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.

Reminder: You can pin to individual versions of the Flex UI or manage your Automatic Updates within the Flex Admin UI.

Twilio Interconnect has been expanded with a new Interconnect Exchange Installation in Tokyo, Japan.

The new exchange provides customers with connectivity via cross connect, VPN, Bring-Your-Own-MPLS, and the Equinix Cloud Exchange with initial product support for Elastic SIP Trunking, SIP Interface and Voice WebRTC.

Twilio now has two Interconnect Exchanges in the APAC region, one in Singapore and one in Tokyo. This allows APAC customers to set up redundant interconnects from their networks to Twilio adding an additional layer or resiliency while benefiting from the security and consistency of a dedicated interconnect.

Click here for information about Twilio Interconnect and here for documentation.

The new v2 Regulatory Compliance suite, backed by programmatic public APIs and a Console workflow leveraging the intelligence of the Regulatory Rules Engine.

For additional details:

Regulatory Compliance APIs

Getting Started: using the Public API to create new Bundles

Console: Regulatory Compliance Report Getting Started

Getting Started: How to use the Compliance Report