Twilio Changelog

Twilio has enabled automatic roaming GLL call handling for Programmable Voice SDKs from our Umatilla/us2 edge location.

Twilio now allows you to pass additional SIP headers as part of an outbound SIP call.

Twilio is introducing the Operator, OperatorType and OperatorAttachment Resources for the Voice Intelligence API, now available in public beta.

The Activity Skills Filter plugin lets you map an agent's status to their skills and enables custom order status in the status selector.

Effective August 1, 2024, Twilio will transition to a unified deployment model for Flex plugins, discontinuing direct deployments through Twilio Functions and Assets. You will need to use the Flex Plugin Builder (Plugins CLI) for all plugin deployments and modifications. This update simplifies maintenance and upgrades across the platform.

Starting April 1, 2025, any legacy plugins that have not been migrated to the new system will stop working within the Flex UI. It’s crucial that you migrate your plugins before this date to avoid any disruption in service. 
Updated 25-Sept-2024: Previously, this changelog entry stated that non-migrated legacy plugins would stop working on November 20, 2024. The deadline has been extended to April 1, 2025.

Previously, Flex plugins could be directly deployed and modified via Twilio Console or the Serverless Toolkit, allowing flexibility in management but varying in standardization.

These changes are aimed at enhancing security and manageability without impacting system performance. We encourage you to follow these steps to ensure a seamless transition:

• Identify your legacy plugins: Review your Flex custom plugins to determine which of your deployments are considered legacy plugins. 
• Install the Flex Plugin CLI: If you haven’t already, use the Twilio CLI documentation to install the Twilio CLI on your local machine. Then, install the Flex Plugins CLI to ensure you have the necessary tools for migration. 
• Follow the migration guide: Our Flex plugins migration guide outlines all necessary steps to reinstall your plugins without impacting your ongoing operations. 

The Make HTTP Request widget configuration now includes a checkbox allowing the request to be made with your Twilio credentials. 

This makes it easy to invoke Twilio APIs that are not available natively as Studio widgets. It is also more secure than embedding your Twilio credentials within the request URL.

To learn more, visit the Make HTTP Request documentation, or try it out now in Studio.

TaskRouter now enables agents to place outbound calls from any queue, whether or not they are a member of that queue. This update enhances TaskRouter’s adaptability and functionality for diverse operational needs.

Effective May 14, 2024, TaskRouter no longer performs backend validation to confirm that an agent is a member of a queue before allowing them to place an outbound call from it. This change improves contact center flexibility by accommodating a wider range of use cases, such as agents who are assigned to multiple queues or who are temporarily assisting in a different queue. 

Previously, TaskRouter required agents to be a member of a queue in order to place a call from that queue. 

This change does not impact system metrics or statistics.

Webchat 3.0’s newest feature, allowed origins, boosts chat widget security by only accepting messages from pre-determined websites. 

Starting May 14, 2024, you can use the Allowed origins field  in your Webchat 3.0 deployment key settings to specify up to 10 trusted URLs where your customers can initiate a chat. Once specified, chat sessions are only accepted from the trusted URLs that you entered. Webchat will reject chats from any URLs that are not listed in the Allowed origins field.

If you have already created a deployment key for Webchat 3.0, you must take action to prevent disruption. By August 15, 2024, you must update your deployment key for your existing Webchat 3.0 widget.

We’re excited to announce that you can now download the Twilio Flex CTI connector directly from the Salesforce AppExchange. For full configuration details, see Integrate Flex with Salesforce. For those already using the Salesforce integration, no action is required.