Product changelog and announcements

Meta has announced they will no longer support the allow_category_change property during template creation. Previously, if set to true in a template creation request, this allowed WhatsApp to update a template’s category to marketing, if they determined marketing to be its category per its content and our guidelines. This is now the default behavior.

When Twilio passes our equivalent parameter into WhatsApp it will no longer prevent reclassifications. We have now unpublished this field from our documentation as it will no longer function. API calls with this field will still submit the template for approval but will no longer prevent recategorizations. 

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!

BigQuery and Redshift Supported as Linked Audience Warehouse Sources - General Availability

Linked Audiences empowers marketers to effortlessly create targeted audiences by combining behavioral data from the Segment Profile and warehouse entity data within a self-serve, no-code interface. With this GA release, the Data Graph now supports both Redshift and BigQuery as a warehouse source.

For more information view our documentation.

Configurable Lookback for Historical Event Data is now available to all users on Business plans. When creating or editing real-time audiences, you can set a lookback window (e.g., “last 90 days”) under Include Historical Event Data to limit how far back event data is processed. Disable it to use only data after creation. This will speed up initial computations by reducing backfill time, while batch audiences continue to include historical data by default.

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.

Audience Consumers is now available to all users on Business plans.

You can view a new Consumers tab on audiences to see a list of audiences that reference it in their definitions. When editing, disabling, or deleting an audience, a warning will appear if it’s referenced by other audiences, showing the count and a link to review them. This will ensure that you understand dependencies and manage audience relationships more effectively. For more information, view our documentation.

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.