Twilio Changelog

The Messaging area in the Flex Console is fully overhauled, both in terms of design as well as backend implementation. This improves usability and aesthetics of the Administrator experience, as well as fixes some long-standing issues.

Find the new UI under Flex > Manage > Messaging.

Notable changes include:

• The UI is restructured between multiple tabs for easier navigation and reduced clutter. Find the improved version of "Unregistered numbers" in the SMS Numbers tab.
• All Addresses (aka Flex Flows) can be created via the Create Address form. Additionally, SMS Addresses can be created via the SMS Numbers tab.
• WebChat addresses can now also be created via the UI.
• When creating new SMS Addresses, phone numbers can now be searched (by entire number or by partial search).
• The new UI is not affected by the issue of registered numbers sometimes showing up as unregistered.

It is now possible to edit the addional website, business vertical, and about fields for your WhatsApp Senders within the Twilio Console.

1. Click here or navigate to Messaging > Senders > WhatsApp Senders.
   
2. Click "Edit Sender" on the sender you wish to update.
3. Under "Business Profile Information", you may now add or update the additional website, business vertical, or profile about fields.

Now you can more easily scale your low-code Voice and Messaging applications with Studio Subflows!

• Reduce complexity when managing large Studio Flows by breaking them down into smaller parts.
  
• Shorten Flow-publishing times by reusing portions of Flows that are common across multiple Flows.
• Increase operational efficiency by handling calls and messages with the most relevant Subflow.

Studio Subflows is now generally available to all Twilio accounts.

To learn more, check out the Subflows docs or try it out in Twilio Console now!

This release of Flex UI includes Real-Time Queue Monitoring GA. This feature displays real-time metrics that are useful for managing queues during the day. We have added new default metrics - number of handled customers, number of abandoned customers, and SLA. The SLA shows the percentage of waiting customers that were connected to an agent within a desired target time. Developers can programmatically add additional metrics to extend this dashboard.

The Call Log for all Voice Products now has a multi-use search bar that can search for SIP Call ID, CallSid, and now TrunkSid. Isolate calls associated with a particular trunk by entering your TrunkSid into the Call Log search bar.

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

This release of Flex UI includes native outbound dialing and Dialpad being Generally Available. The Generally Available release of outbound dialing brings improvements in quality and reliability and solves several known limitations that include:

• Improved and more granular error reporting when an outbound call fails
  
• Flex agents can no longer place concurrent outbound calls
• Recordings are no longer stopped when an outbound call is transferred

For more information, refer to the Flex Dialpad documentation. For more details on this release, please visit the release notes for Flex UI.

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

It is now possible to do a configure per-service webhooks in the Conversations. With this feature, you can control the effects of webhooks in a particular Conversation Service. This means you can include different metadata in the URLs or even trigger different behavior for different services.

Explore the per-service webhooks documentation and give it a try!

The Workforce Management Real-Time Adherence Feed (WFM RTA Feed) is designed for partners to monitor and report on the activity of agents within a Flex contact center. Events from this feed can be used to generate a real-time snapshot of agent status.

The WFM RTA Feed is now Generally Available, and it can be used alongside historical reporting in Flex Insights to support workforce management integrations to Flex. Review our WFM RTA Feed documentation for details on getting started with the feed and the event data.

Runtime Handler version 1.2.1 introduces access to headers and cookies for incoming requests to Twilio Functions through the new event.request object. Visit our documentation to learn more about this feature.

You can use this version today by setting @twilio/runtime-handler to use version 1.2.1.

For new projects and those that don't specify a specific Runtime Handler version, we'll be rolling out version 1.2.1 over the coming weeks as the new default version.

Check out our docs to learn more about specifying which Runtime Handler version to use.

We are excited to announce the availability of 24 hour participant durations for video rooms.

You can now configure the Maximum Participant Duration for any Twilio Video room type. This value is set at the time of room creation, and upon reaching the limit, a participant will be disconnected from the room.

The default value for maximum participant duration is 4 hours. You can change this value either through the Console under Rooms Settings to make it the default for Ad-hoc rooms or as a configurable parameter via the REST API upon room creation.

For more information on configuring the maximum participant duration, view the participant duration documentation. If you are composing room recordings of participants with long durations, you may want to review the composition size limitations.