Product changelog and announcements

Twilio now supports sending one tap and zero tap authentication templates on WhatsApp.

One tap autofill lets your customers authenticate by clicking a button in WhatsApp that triggers an activity that opens your app and delivers the password or code to it.

Zero tap authentication templates allow your users to receive one-time passwords or codes through WhatsApp without having to leave your app. If the zero-tap process fails, the code is still delivered in the WhatsApp chat.

More information on how to configure your existing authentication or new templates to support this functionality can be found in our documentation. 

We're announcing updates that improve the visibility of WhatsApp voice call metrics in Voice Insights, for customers using the WhatsApp Business Platform with Twilio. Here's a detailed rundown of the new updates:

Voice Insights API Updates:

• Call Summary API & Eventstream: A new parameter, call_type: "whatsapp", has been introduced to distinguish WhatsApp calls. Metrics for these calls are accessible within the carrier object of the Call Summary API.

• Call Events & Call Metrics APIs:Customers can track and analyze WhatsApp RTP stats and call progress events through the Call Events and Call Metrics APIs.

Voice Insights Console Updates:

• Call Logs Page: Within the Insights Summary tab, customers can now view metrics and track call progress events for individual WhatsApp calls.

• Call Insights Dashboard: On the Call Insights Historical View page, customers have the added functionality to filter dashboard data by the "whatsapp" call type.

For more information, please refer to the Voice Insights reference docs.  

WhatsApp Business Calling for Twilio Programmable Voice is now available.

We’ve made some changes to help keep Verify traffic secure and your customers protected.

As of June 20, 2025, the “WhatsApp Fallback to SMS” toggle in Messaging Services is no longer supported for Twilio Verify customers. This toggle wasn’t designed to work with Verify, and we’ve identified a potential fraud risk when the two are used together.

To make things easier and safer, we’ve automatically migrated impacted customers to Verify’s own WhatsApp fallback to SMS solution. This ensures fallback SMS messages are protected by Fraud Guard and sent using Twilio-managed phone numbers for reliable delivery.

What this means for customers

• No action is needed. The migration has already happened behind the scenes.

• If a customer prefers to use their own SMS sender, or would like to turn off fallback entirely, our Support team is happy to help.
  
  

We know changes like this can raise questions, and we’re here to support you. This update is all about keeping traffic secure and making sure Verify works exactly as expected—without surprises.

Meta Pricing Changes for WhatsApp Messages: Effective July 1, 2025

Starting July 1, 2025, Meta will shift from 24-hour conversation-based pricing to a new model that charges per template message delivered. Pricing will vary by template type (Marketing, Authentication, or Utility) and may also be subject to volume-based tiers in some regions. 

This update applies to all WhatsApp messages, including those sent through Twilio Verify.

Twilio will continue to pass through Meta’s updated charges without adding any additional fees. No action is required, but customers may notice billing changes starting July 1, 2025, based on message type and volume. 

We haven’t listed the Meta fees directly in this email because they vary by region and message type. For more information, check out Twilio’s Notice: Changes to WhatsApp’s Pricing (July 2025) Help Center article or Meta’s Pricing updates on the WhatsApp Business Platform docs page.

We can’t wait to see what you build!

–Team Twilio

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. 

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

On April 1st, 2025, the WhatsApp Template Console Tab and Templates API will be deprecated. As part of the deprecation Twilio will implement brownouts for the product from April 1 to April 21. After April 22 WhatsApp templates sent with the legacy WhatsApp Templates product will no longer be able to be sent.

Customers will start to see 63016 errors if they continue sending templates without making the necessary changes. Sending WhatsApp templates using the body parameter will be deprecated. Customers need to migrate to Content Template Builder (formerly known as Content API and Content Editor) and change their how they send templates to use Content Sid and Content Variables to avoid a disruption.

Your Content Templates can be found in the Content Template Builder in Twilio console.

More information about the deprecation can be found in this support article.

What’s Changing?

Starting April 1, 2025, Meta will block all WhatsApp marketing messages sent to U.S. phone numbers (+1 area code). Messages sent using a WhatsApp marketing template to U.S. recipients after this date will fail with error code 63049.

This change affects all businesses using WhatsApp marketing templates to engage with U.S. customers. Meta has not provided a timeline for re-enabling this use case, so you should explore alternative channels to maintain customer engagement.

What You Need to Do

To continue reaching U.S. customers with marketing messages, we recommend transitioning to SMS or MMS using Twilio’s Programmable Messaging API. These channels provide reliable, direct engagement to keep your marketing campaigns running smoothly.

Twilio previously sent email communications that we plan to end of life (EOL) the WhatsApp Templates page in console at the end of Q1'2025. Customers will need migrate to Content Templates and change the way the way they send templates to use Content Sid and Content Variables instead of using the body parameter.

To further inform customers, from February 12, 2025 onwards, Twilio will start to publish warnings (63052) when customers use the Legacy WhatsApp Templates product to send templates. Templates sent will continue to be delivered until April 1, 2025 but the template matching logic using body will no longer work after that.

To learn more about the EOL process as a whole and how to migrate, please see this support article here.