Product changelog and announcements

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

 

At Twilio, we’re always working to make your messaging experience more reliable and transparent. That’s why we’re making some updates to how we handle Alphanumeric Sender IDs.

What’s Happening?

Starting on August 13, 2025, we’re introducing clearer error codes and new message status updates when an Alphanumeric Sender ID isn’t properly registered or authorized in a given country. These updates will help you quickly understand if something needs to be fixed and keep your messages flowing smoothly.

Here are the highlights:

• *New Error Codes

  • 30041: Sent when the Alphanumeric Sender ID isn’t registered or authorized for use.

  • 30042: Sent when the Alphanumeric Sender ID is explicitly blocked because it’s generic or not allowed to be used.

•  What Will Change in Your Logs?

  • Messages with unregistered Alpha Sender IDs will now appear as “Likely-SCAM” in the logs in Singapore and Ireland.

  • Error codes will be clearer and more actionable.

If your Alphanumeric Sender IDs are already registered and approved for your destinations, you’re all set—no action needed! If you see one of these new error codes, that’s your cue to double-check that your Alphanumeric Sender ID is properly set up for the country you’re sending to.

*Note: Error codes are subject to processing fees. For more information on charges on messaging errors, visit our Twilio Help Center article on error code fees.

For questions or help with registering your Alphanumeric Sender IDs visit:

• SMS Guidelines Page

• Twilio Help Center

This powerful new feature automatically analyzes your messaging traffic to identify key opportunities to improve deliverability & engagement. It provides tailored insights—including the potential impact of improvements—and highlights relevant Twilio products that can enhance your messaging performance.

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!

 

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. 

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.

We’re excited to announce a major upgrade to how you monitor A2P 10DLC Brand registration statuses: Twilio Event Streams now supports more granular notifications for key brand registration events.

With this release, you can subscribe to a comprehensive set of status change events for A2P 10DLC Brands via Twilio Event Streams. This enables you to automate workflows, surface issues more quickly, and provide greater transparency to your customers and systems.

Notably, we’ve introduced two new events — brand-registration.brand-verified and brand-registration.brand-vetted-verified — that serve as indicators when a brand is ready to initiate campaign registration.

To learn more about A2P Notifications through Event Streams , check out our guide docs.

 

Event Name	Change		Description
com.twilio.messaging.compliance.brand-registration.brand-registered	Updated		Brand has been successfully submitted and registered. Does not indicate Brand status.
com.twilio.messaging.compliance.brand-registration.brand-failure	Updated		Brand fails registrations.
com.twilio.messaging.compliance.brand-registration.brand-verified	New		Brand has an identity status of Verified.
com.twilio.messaging.compliance.brand-registration.brand-unverified	Updated		Brand failed primary vetting. Now includes detailed error information.
com.twilio.messaging.compliance.brand-registration.brand-vetted-verified	New		Brand has passed secondary vetting.
com.twilio.messaging.compliance.brand-registration.secondary-vetting-failure	New		Brand failed secondary vetting. Includes reasons for failure.

 

Twilio is announcing the end of life (EOL) for outdated versions of the Sync and Chat SDKs. Starting on March 31, 2025, the following SDK versions will no longer be supported, and critical features such as live updates and chat functionality will stop working:

Sync SDK:

• Javaccript: Versions below 0.8.1

• iOS: Versions below 0.8.1

• Android: Versions below 0.8.0

Chat SDK:

• Javascript: Versions below 3.0.0

• iOS: Versions below 2.4.2

• Android: Versions below 4.0.0

SDKs that are not updated by the EOL date may fail to connect to Twilio services and could return errors such as 404 “HOST_NOT_FOUND.”

This change allows Twilio to focus on delivering faster troubleshooting, better guidance when issues arise, enhanced security, and improved performance for applications using supported SDK versions. Upgrading ensures your applications benefit from these improvements and remain operational.

What Do You Need to Do?

To avoid service disruptions, please complete the following steps before March 31, 2025:

1. Upgrade to the Minimum Supported Versions:

   • Sync SDK: Javascript 0.8.1, iOS 0.8.1, Android 0.8.0

   • Chat SDK: Javascript 3.0.0, iOS 2.4.2, Android 4.0.0

2. Test Your Updates:

   • Test your upgrades in a safe environment to ensure everything works as expected before deploying changes live.

For more information on how we support our SDKs, see our SDK version and support documentation, and consider upgrading to the latest versions.