Twilio Changelog

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.

We’ve expanded Twilio Events to include support for Flex Teams events. Now, any actions taken on Flex Teams, whether through the API or Twilio Console, are published as audit events in Twilio Audit Insights. No configuration is needed—Flex Team events automatically appear in your Event Stream and logs.

This update provides a single source of truth for team activity and simplifies troubleshooting, auditing, and compliance reporting. You can also integrate Flex Teams events with your existing observability or compliance workflows. 

For full details, see Events resource.

Starting September 30, 2025, customers will have the option to add Business Registration Numbers (BRNs), like Employer Identification Numbers (EINs), when they set up new Toll-Free verifications.

This update helps Twilio keep messaging safe, trusted, and reliable for everyone. For now, adding a BRN to new Toll-Free verifications is optional, but we’re giving early notice so you (and your customers) can get a head start on gathering the right info. By January 2026, a BRN will be required for all new Toll-Free verifications, so it’s a good idea to start preparing now 

If you ever run into trouble submitting your Toll-Free Verification with a BRN, we’ve got your back. Check out our New Policy API Onboarding documentation to help you with error code details and step-by-step guidance to make fixes as painless as possible.

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 July 14, 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

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