Product changelog and announcements

In this version of Flex UI we have updated the Status Report, formerly known as the Debugger UI, to now include a summary of Flex UI's operation status for each user. The Status Report is now available in GA and includes debugger logs, Twilio service status information and whether Flex UI is running in degraded mode.

Find out more about the updated Status Report on the Troubleshooting Flex UI page.

TaskRouter now supports the evaluation of Activity name and SID in Worker expressions for the Worker-list API.

For example, developers can use this to fetch workers in different activities
using GET /Workers?TargetWorkersExpression=activity_name in ['ABC',
'XYZ'] or to fetch workers using a partial name match using GET /Workers?TargetWorkersExpression=activity_name contains 'MNO'.

For more detailed information please refer to the expression syntax documentation and the Worker Resource documentation.

Twilio Flex’s Agent Desktop has been tested in Microsoft Edge, which can now be used as a supported browser for Flex UI versions 1.31.2 and above.

For more information, see the Flex UI Requirements page.

TaskRouter now emits events for Workspace, Workflow, and Activity resources upon create, update, and delete operations.

For more detailed information please refer to the Events
Reference documentation.

Twilio Flex can now be used to develop compliant healthcare applications that contain protected health information (PHI) for organizations that are subject to the Health Insurance Portability and Accountability Act (HIPAA). Twilio will sign Business Associate Addendums (BAA) with covered entities and business associates for HIPAA Eligible Products and Services.

Learn more about how to build on Twilio for HIPAA compliance.

We changed the TaskRouter out-of-box Task Channel’s friendly name from “Programmable Chat” to “Chat”. The unique name “chat” did not change. This is mostly just for information and should not have a significant impact on how you use TaskRouter or Flex.

We are excited to announce that Flex UI 2.0 is now available in Public Beta.

We are excited to announce that Flex Conversations is available in public beta.

Flex Conversations introduces the new async channel platform to easily build SMS/MMS, WhatsApp, and Chat channels in Flex. This release includes:

• Support for Conversations API, the single API to manage all asynchronous channels including SMS/MMS. WhatsApp, and Chat
• New Interactions API to set up and manage inbound and outbound communications
• An open source React based chat application to help you get started with creating and embedding webchat into your website
• Attachment support for all channels that support attachments
• Conversations support in Twilio Studio

Flex Conversations requires Flex UI 2.0. See the Flex UI 2.0 docs for more info and how to perform a migration.

You can read more about this launch on our blog, and if you’re ready to start building, dive into our docs.

In this release of Flex UI, we have introduced a Degraded mode for Flex UI - now Flex UI will initialize with limited capabilities, even if some of the components like SDK’s (TaskRouter, Conversations, Voice or Sync) are down. In case of disruptions in Twilio services, Flex User will be able to login to Flex and perform certain tasks that are still available. For example, in the case of Twilio Voice experiencing an incident, your agent will still be able to handle messaging tasks.

Users will see a notification informing them of a possible disruption in the normal operation of Flex UI and they will be able to download a thorough report with error details and logs.

For more on error handling and reporting, check out our Troubleshooting Flex UI guide.

Twilio has completed validation of the integration between Flex and Lionbridge Language Cloud real-time language translation solution. Using a database of over 110 languages, this integration enables your agents to send SMS, Chat or WhatsApp messages in their native languages, and have customers read them and send return messages in their native languages.

To learn more about Lionbridge capabilities and how to enable it for your application, visit our integration documentation.