Twilio Changelog

This release of Flex UI introduces an improved troubleshooting experience for Flex UI users. Troubleshooting and fixing any issues starts with understanding their cause and getting additional context about the issues. Users of Flex UI will now be able to get error notifications via a Debugger UI and will be able to download a report with full error descriptions and logs.

We are keeping your runtime up to date with industry standards. In accordance with OpenJS Foundation’s support schedule, Node v10 will no longer be supported after April 30, 2021.A new deployment will be required to make Functions run against the new Node version.

Your currently deployed functions will continue to execute on the existing Node v10 runtime if no changes are made.

Follow theseinstructions to upgrade, test and deploy your codeand ensure a safe transition to Node v12

We recommend that you upgrade to Node v12 even if you’re not planning on making other changes. Test and re-deploy your code with Node v12

If you don’t specify a runtime, we’ll use Node v12 by default if there are no previous builds deployed in the service. If you already have a build deployed in the service, the same runtime will be used to deploy as the last successful deployment until April 30th.

If a Build contains only Assets, then the default Runtime(regardless of the Runtime passed in the Build request or even if Runtime is not passed) will be used automatically for the Build. The default Runtime is Node12 after April 30th.

After April 30th, if you have not deployed using Node v12 already, you would have to deploy using Node v12 at least once to move your code to Node v12.

Currently, the Node version will only change if you explicitly set the Node version via either the UI dropdown in the dependencies tab, by passing runtime using serverless toolkit or by explicitly setting the runtime parameter when creating a Build.

Over the next few weeks, we are gradually rolling out MMS capabilities across our US Toll-Free numbers.

Starting this week, you will see numbers with MMS capabilities appear when you search for US(+1) Toll-Free phone numbers using Advanced Search. If you already own Toll-Free numbers, they will be enabled with MMS capabilities by the end of March as well.

You can send an MMS message on a Toll-Free number by including the MediaUrl parameter in your API request. Pricing information can be found here.

We will share another update once all Toll-Free numbers are generally available for sending and receiving MMS messages from recipients in US and Canada.

In some cases calls placed using the Conference Add Participant API, <Refer>, and <Dial><Sip> Multidial are not being properly billed for Voice Insights Advanced Features usage. We’ll be introducing a fix for new accounts created after February 24, 2021 that will result in these call flows being billed properly. The billing behavior will not change on existing accounts.

Flex Insights provides additional custom data fields for Conversations, Customers, and Agents data sets. You can now attach more data related to your specific business needs to conversations, customers and agents - which you can then use for segmentation, aggregations, and filtering in Historical Reporting.

To learn how you can set custom data fields programmatically, see Enhance your Flex Insights Integration.

The Flex Plugins CLI has been updated to automate one of the most common operations, enabling or disabling a single plugin. Developers can now provide the disable-plugin and enable-plugin arguments in the release and create-configuration commands. This simplifies the release process for developers managing multiple plugins. They no longer need to gather and update configurations for every active plugin. Refer to our CLI documentation for more details on these commands.

Other notable changes:

• Flex plugins no longer need to start with “plugin-”.

Flex Insights now supports detailed intraday reporting of agent workload. Workload reporting enables supervisors and data analysts to see which conversations the agents spent their time working on during the day with 15 minute interval granularity. Workload reporting is especially powerful in contact centers with long conversations that can be leveraged by Workforce Management applications to predict load and monitor schedule adherence. The time spent working on conversations can be filtered and segmented by direction, queue, agents, and all the other attributes available in Flex Insights.

Flex Insights now also reports on how many conversations agents worked in parallel at a specific moment. This gives visibility into how efficiently their time is used in multi-tasking environments. You can also report how much time agents spend idle - handling no conversation during their working hours.

For more information see workload reporting documentation.

In order to enhance security for all of our users, Twilio SendGrid now requires customers on all Essentials plans to use API Key authentication on all API requests and SMTP configurations. Customers must also enable Two-Factor Authentication (2FA) for all users, including teammates. Visit our docs for more information on Upgrading to API Keys and Enabling Two-Factor Authentication. If you did not receive notifications about this change please update your account email address.

HTTP callbacks (webhooks) for inbound WhatsApp messages now include new ProfileName, WaId, Forwarded, and FrequentlyForwarded parameters. The ProfileName parameter contains the WhatsApp sender's profile name and the WaId parameter contains the WhatsApp ID of the contact sending the incoming message. For messages received that have been forwarded or forwarded many times the parameters Forwarded or FrequentlyForwarded, respectively, will appear with the value true.

Twilio’s Programmable Voice <Siprec> TwiML instruction now supports Secure Media encryption using Secure Real-time Transport Protocol (SRTP); this allows customers to encrypt transmission of their SIPREC media stream. Additionally, you can now send traffic to your SIPREC servers from any Twilio Edge Location, which will allow for improved performance internationally.

To get started, pass `secure=true` with the Recording Server SIP URI when configuring Twilio SIPREC connector.

Example

sip:alice@example.com;secure=true

Additionally, you can also select the Twilio Edge Location to use when streaming to your SIPREC servers by specifying the ‘edge’ parameter in the Connector’s Session Recording Server SIP URI.

Example

sip:alice@example.com;edge=frankfurt

More information regarding the ‘secure’ and ‘edge’ parameters can be found in the Programmable Voice SIP documentation.

To learn more about Twilio’s <Siprec> functionality, please check the <Siprec> documentation.