Twilio Changelog

On 1 June 2021 the Twilio Voice Insights gateway (eventgw.twilio.com) will no longer support TLS 1.0 or 1.1 protocols. The Voice Insights gateway is where Voice SDKs publish events and metrics gathered by the sensors. The Voice Insights gateway will stop offering TLS 1.0 or 1.1 protocols on this date, only the TLS 1.2 protocol will be supported.

To improve discoverability, a new SMS Commands API has been introduced for exchanging machine-to-machine SMS between your applications and your Super SIMs. This new API replaces the existing Commands API. The functionality offered by the SMS Commands and Commands APIs is almost identical with some minor changes to property names.

The Commands API will be removed before Super SIM is released to General Availability in the near future. Please plan to migrate your integrations to use the new SMS Commands API as soon as possible.

You can now integrate Twilio SendGrid with identity and access management platforms that support SAML 2.0 such as Okta, Duo, and Microsoft Azure. Twilio SendGrid SSO integration allows you to securely and centrally manage account permissions, including password requirements, multi-factor authentication, and employee offboarding. Twilio SendGrid SSO provides access to those who need it by mapping new Twilio SendGrid Teammates to users in your SSO Identity Provider (IdP). Please note that each SSO user can access only one account or subuser during the Public Beta.

Visit our documentation for more information on how to access and manage SSO permissions.

We are excited to announce that the Plugins Dashboard and Plugins API are now generally available and covered by Twilio SLA and support plans.

The Plugins Dashboard, powered by the Plugins API, provides visibility and control to admins outside of a developer’s command line interface. The Plugins API provides modern DevOps capabilities to plugin development, including:

• Control which plugins are enabled for your agents
• Track your version and release history as you update Flex
• Quickly revert to a previously known working configuration when troubleshooting agent issues

Review our dashboard guide and migration guide for more details.

Twilio has completed validation of the integration between Flex and Aspect WFM. The following features have been verified and are available for customers of Flex and Aspect:

• Workforce Management
  • Historical data for forecasting
  • Agent schedule creation
  • Real-time adherence

To learn more about Aspect WFM’s capabilities and how to enable it for your application, visit our integration documentation.

This release Flex UI and WebChat UI upgrades Browser Notifications and Markdown to Generally Available. These features improve agent efficiency and customer experience for messaging interactions.

Markdown support allows agents to format Web Chat messages. This can improve the readability of longer messages. Using bold text, italics, or bulleted lists can create structure and emphasis in your agents' messages, and ensure that customers read and understand the message correctly.

Browser notifications help agents respond to tasks that require their attention in a timely manner and not miss any customer interaction when they are not focused on Flex.

To take advantage of these features, visit Flex settings to enable them for your account.

Other notable changes in Flex UI 1.26:

• Error reporting - Flex now reports on errors that are generated within the UI. This will help us continuously improve the quality of the application and get more insights into issues that need troubleshooting. To read more about ways to troubleshoot Flex UI, including how you can opt out of error reporting, visit our Flex docs.
• Transfer directory hidden filters - Now you can programmatically pre-filter the list of agents or queues in the transfer directory. Agents accessing the directory to initiate a call transfer will view and search only within the prefiltered subset. For example, you can choose to only display agents who are available. To learn more about Transfer directory hidden filters, visit our Flex docs.

For more details on this release, please visit the release notes for Flex UI and WebChat UI.

The Plugins Dashboard now enables Flex admins to delete legacy builds of plugins that you have started migrating to the Plugins CLI. This step is necessary to complete a migration, and it ensures you can disable a plugin without accidentally serving the legacy build to your users. Legacy builds are plugins that were added to Twilio Assets prior to the Plugins CLI.

Admins can access the Plugins Dashboard via the Admin UI. Refer to our docs for more details.

Super SIM now offers Distributed Internet Breakouts. Up until now, all traffic from/to an IoT device using Super SIM has been going through the Twilio Mobile Core instance deployed in Ashburn, USA. Twilio now has an additional location in Frankfurt to provide Internet breakout for Super SIM customers in Europe and Africa, with more locations to follow.

Using distributed breakout to the Internet is important to achieve low latency, which opens up new use cases such as adding real time voice/video communications to an IoT device. To make use of the breakout location in Frankfurt, Super SIM customers must configure “de1.super” as the APN (see Super SIM APN configuration). The existing default APN “super”, when used, results in traffic breaking out to the Internet via Twilio Mobile Core in Ashburn, USA.

If you are interested in using the Frankfurt Internet breakout location, please reach out to Twilio support.

Twilio has completed validation of the integration between Flex and Survey Dynamix. Survey Dynamix can capture feedback over post call voice IVR, outbound voice IVR, conversational SMS, Web SMS, email, and web surveys.

To learn more about Survey Dynamix’s capabilities and how to enable it for your application, visit our integration documentation.

The TwiML <Conference> noun and the Conference Create Participant API have been updated to provide a new announcement status callback event. This event will be sent to the provided status callback URL when the announcement to a conference or a participant ends normally or fails due to a Twilio-internal error.

This allows developers to be informed when an announcement has completed and additional call processing instructions can be executed, or when an announcement has failed and a retry attempt is needed.

For more info, see our docs for the <Conference> noun status callback event and for creating a Conference participant.