Twilio Changelog

Beginning today, agents can now leave and pause a task for any Flex Conversations channel, such as SMS or webchat. We’re expanding this functionality from only email tasks to all Flex Conversations tasks. 

Agents can also enter wrap-up after they leave or pause a task, so they can perform final wrap-up activities before completing a task. This ensures that agents have time to document their actions and also provides a more accurate report of their status.   

In addition, administrators and developers can now configure a webhook URL and subscribe to notifications about Interactions API events that occur during conversations. 

Event notifications can provide information about customer interactions or enable developers to trigger additional workflows after certain events. For example, when used with leave and pause functionality, Interactions event notifications enable you to trigger custom logic when a customer responds to a conversation the agent has left.

With SAML-based SSO, users can now automatically join a primary team when they sign in to Flex. In addition, when supervisors sign in to Flex, they can automatically gain oversight of multiple teams as the assigned owner. By using attributes from your identity provider (like Okta), this update simplifies team assignments right from the start. 

To learn more about Flex Teams and how to set up SSO, see Teams in Flex and Configuring SSO and IdP in Flex.

We’re excited to announce that Flex UI 2.12.0 is now available. This release includes:

• A new Flex UI action for Conversations messages that lets you send rich text using a content template and associated variables.

• You can now localize dynamic strings, such as agent status, in custom Flex plugins.

Throughout Flex UI, you'll find feature and UI enhancements, bug fixes, and more. 

For complete details, see the Flex UI release notes for 2.12.0.

Accept PIX Payments on WhatsApp with Twilio/pay
Move from conversation to conversion with native in-chat payments

We’re excited to announce support for PIX payments on WhatsApp using Twilio/pay templates. You can now guide customers through completing a financial transaction directly in WhatsApp.

Use Content Templates with Twilio/pay to:

• Send Order Details messages with a PIX copy code button that opens the user’s banking app

• Send Order Status updates as payment progresses through stages like pending, shipped, or completed

• Display itemized order summaries, expiration details, and total amounts—all within a single message

To enable this, your business must:

• Have a valid WhatsApp sender in Brazil

These templates support variables for payment ID, merchant name, itemized details, and expiration. Rich metadata can be passed to payment processors, with updates automatically sent to users through Order Status messages.

Ready to embed seamless checkout into your messaging flows?
Explore the docs to get started:
twilio/pay

We’re making it easier to troubleshoot Toll-Free Verification (TFV) errors!

Starting May 15, 2025, we’ll begin rolling out more specific and detailed error codes for TFV requests. These new codes are designed to give you clearer, more actionable feedback when a submission doesn’t go through— so you can fix issues faster and keep things moving. 

Don’t worry, the old codes will still be supported— but we think you’ll find these new ones to be more helpful.

What’s changing?

Right now, TFV error messages can be a bit vague. With this update, you’ll start seeing granular error codes that explain why a verification was rejected. These new codes will appear in: 

• API responses

• Webhooks

• Email notifications

• Twilio Console

What this means for you

If you’re a customer that has set up custom logic to handle TFV errors—like mapping them in dashboards or internal tools—be sure to review and update your error mapping to reflect the new codes.

For more details, check out the Twilio API Docs and the Twilio Error Code Dictionary.

We hope this update makes your TFV experience smoother and more efficient. 

Thank you for building with Twilio!

As of April 10, 2025 the Legacy Boku Identity APIs Infrastructure in Europe will be migrated.

We would like to inform you about upcoming changes to Legacy Boku Identity API’s production infrastructure in Europe. These changes will not impact your current service. Our goal is to minimize impact to your current integration to our services. These updates are part of our ongoing commitment to improving performance, scalability, and reliability for all our customers.

If you have whitelisted or hardcorded our IP addresses instead of URLs, please make a note of our new IP addresses. These new IP addresses will take effect once we perform the switchover to AWS cloud services.

Our support team is available to assist you with any questions or concerns at accsec-onboarding@twilio.com.

Thank you for choosing Twilio. We appreciate your partnership and look forward to continuing to provide you with exceptional service.

You can now sign up to receive a weekly email of your [Deliverability Score], so you can track your messaging health and performance. 

The [Deliverability Score] provides a simple, comprehensive view of your messaging traffic and helps you target specific areas for improvement. The new weekly email summarizes your score and provides links to Twilio Console Messaging Insights where you can view score details, identify optimizations, and troubleshoot. 

We're excited to announce that we have made updates to the existing Compliance Report to now include Toll-Free & Regulatory Compliance Information.  Compliance information from all 3 programs (A2P, Toll-Free & Regulatory Bundles) can be downloaded from one singular report on demand and can be accessed on the download page located on Twilio's Console.