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.

We’ve extended the end-of-life (EOL) date for the legacy version of Flex Single Sign-On (SSO) from June 2025 to January 15, 2026. This extension comes directly in response to customer feedback and the momentum we’re seeing with migrations. Our goal is to give every team the time they need for a smooth, stress-free transition.

Here’s what customers need to do next: 

• Customers using legacy Flex SSO now have until January 15, 2026, to complete migration to the enhanced SSO.

• After this date, logins via the legacy flow will no longer be supported

Need a hand?

Here are some helpful resources to help customers migrate: 

• Enhanced and Legacy SSO Twilio documentation

• Flex SSO URL Migration Guide

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

• The option to turn on a default Flex ringtone for incoming tasks and the ability to configure different sounds based on task channel using the new SoundManager API.

• Spell-check functionality in the email editor.

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.13.0.

We're thrilled to announce a major update to our Data Graph: the launch of our visual, no-code Data Graph builder.

With this release, creating and managing your Data Graph is more intuitive than ever. Our new editing experience empowers you to add entities and relationships with a simple point-and-click interface and easy-to-use dropdown menus—no coding required. This streamlined approach opens up Data Graph editing to a wider range of users.

The new visual builder is now the default way to edit your Data Graph, but power users who still prefer working with raw configuration code – or who wish to copy the code into version control – can seamlessly switch between the no-code and code-based editors at any time.

Ahoy!

​​On May 8, 2025, Twilio sent an advisory to some customers outlining an upcoming change to the Twilio Verify V1/Authy API endpoints. This change, initially planned for June 16, 2025, would stop accepting GET requests that include a request body. The goal is to enhance security and better protect against smuggling attacks.

To ensure a smooth transition and give customers more time to update their integrations, Twilio is extending the deadline for this change to January 15, 2026.

What customers need to do:

• Update any GET requests that include a request body to either remove the body or use the correct HTTP method (such as POST).

• If third-party integrations are involved, confirm with those providers to ensure they are aware of and preparing for this change.

Thank you for building with Twilio! 

–Team Twilio

 

Description: Linked Audiences customers can now activate list-based action destinations—ideal for advertising and ROAS campaigns.

You can now activate data using Actions List Destinations including key adtech platforms like Google and Facebook Custom Audiences. This helps improve return on ad spend by leveraging your complete first-party data relationships for more precise audience targeting.
 

Full list of supported Destinations:

• Facebook Custom Audiences (new)
• Marketo Static Lists (new)
• Google Conversions
• TikTok Audiences
• Klaviyo
• Amazon AMC
• Display & Video 360
• First-Party DV360

For more information, check out our docs.

Twilio has officially ended support for TLS 1.0 and TLS 1.1 protocols on Elastic SIP Trunking and Programmable Voice SIP interfaces.

Twilio will end-of-life (EOL) its Twilio Engage Premier product on December 15, 2025. Existing customers will continue to have full access to Engage Premier until that date, and Twilio will continue to provide support throughout the transition period.

After December 15, the following features will no longer be available:

• Multichannel campaign delivery (Email, SMS/MMS, Push, WhatsApp)
• Marketing Engagement Analytics
• Subscription Management

Twilio Engage Foundations—including Audiences, Connections, Journeys, ID Resolution, and CustomerAI Predictions—will continue to be supported as part of Segment’s CDP offering.

Customers may choose to transition to Twilio SendGrid Marketing Campaigns for email-first needs or explore one of Twilio’s preferred ISV partners—Airship, Attentive, Bloomreach, Braze, Customer.io, Insider, Iterable, and Klaviyo—for broader multichannel marketing capabilities.