Product changelog and announcements

🔔 Overview: With Audience Size Change Alerts, you can get notified when your audience increases or decreases past a set threshold. During the Public Beta, Audience Size Change Alerts only supports Linked Audiences.

For more information, check out our Audience Size Change documentation.

We’re thrilled to announce that the launch of our completely reimagined Journeys product within Twilio Engage is now Generally Available to all Engage customers. Built from the ground up and based on your valuable feedback, the new Journeys empowers you to deliver more relevant, timely, and seamless customer experiences at every touchpoint.

What’s new in the Next Generation Journeys?

• 🔄 Real-Time Orchestration with Event Triggered Journeys:
  • Automatically trigger and personalize outreach based on real-time customer actions—like cart abandonment, onboarding milestones, and more. No more relying only on drip campaigns. Now, you can react right when it matters.
• 🔎 Richer Personalization with Contextual Payloads & Data Access:
  • Access all the details you need — including important contextual data from your triggering event and subsequent events performed in the Journey (product viewed, cart contents, membership status, etc.) — to simplify the delivery of highly relevant messages, when it matters most.
• 📈 Enhanced Builder Experience with improved Observability & Optimization:
  • Effortlessly map out every customer touchpoint using our intuitive drag-and-drop builder, enhanced with rich activity tracking and comprehensive audit trails. This streamlined approach makes it simpler than ever to analyze, optimize, and scale your customer engagement strategies.

But wait, there’s more! 

• Randomized Split: Unlock dynamic profile routing within Journeys for rapid A/B testing and data-driven analysis, making it easier to optimize engagement and outcomes.
• AdTech Support – Action List Destinations: Build targeted lists or audiences in destination platforms directly from event-triggered Journeys, enabling more precise and impactful engagement strategies.
• Editing & Versioning: Seamlessly update Journeys with new versions—without duplicating or deleting—simplifying workflow management and boosting flexibility.
• Multiple Activations Support: Send up to five different actions per Destination step, whether to the same or multiple locations, cutting down on workarounds and saving Journey step credits.
• Simultaneous Entries: Profiles now launch a new Journey instance with each triggering event, enabling personalized messaging and seamless support for transactional use cases every time an action is performed.
• And More!

This release empowers marketers to move at the speed of their customers—giving you the tools needed to deliver the right message, on the right channel, at the right time.

For more information review our docs and check out this article.

Twilio will disable symmetric RTP for SIPREC connections on June 30, 2025. 

Through leveraging the SIPREC Resource or <Siprec> TwiML instructions, customers can stream the audio of a call to one of Twilio’s available SIPREC partners. In the case of SIRPEC, Twilio is not expecting any RTP from the SIPREC partner or customer as SIPREC is a one-way audio stream to the customer; therefore, Twilio will disable symmetric RTP for SIPREC connections.

For more information, please refer to the docs:

• SIPREC | Twilio
• TwiML™️ Voice: <Siprec> | Twilio

For years, Twilio Voice JS SDK 1.x has helped customers power countless voice calling experiences. But as with any long-standing tool, there comes a time to pass the torch.

Twilio will officially sunset Voice JavaScript SDK version 1.x on September 10, 2025. To continue building [and delivering] seamless voice experiences, customers should migrate to version 2.x before this date. 

Why upgrade?

Voice JS SDK 2.x was built based on customer feedback and real-world cases in mind. Since its release it’s brought meaningful improvements, such as:

• Support for modern JavaScript Frameworks

• Ability to send messages to and receive messages from your backend (User Defined Messages)

• Improved connection handling with automatic recovery without dropping the call

As SDK 1.x begins to wind down, customers may start to experience service degradation or intermittent disruptions. After September 10, 2025, version 1.x will no longer be maintained or supported. 

Migrating early is the best way to ensure uninterrupted service. The Voice JS SDK migration guide makes it easy to get started, and SDK 2.x is the best way to ensure your voice experience stays reliable and up to date.

We’re grateful to the customers who have relied on SDK 1.x and we’re excited for what’s possible with version 2.x and beyond.

 

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.