Product changelog and announcements

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.

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.

Any direct customers who do not already have access to WhatsApp Self Sign-up can now upgrade directly within the Twilio Console. This enables: 

• Faster onboarding register additional WhatsApp Senders in under 5 minutes—including Bring-Your-Own-Number (BYON) WhatsApp Senders (e.g., non-Twilio numbers).

• Access to Meta-provided insights within the Meta WhatsApp Business Manager.

• Ability to add your WhatsApp Sender as the Contact Button to a Facebook page or Instagram account.

• Meta advertising with Click to Whatsapp Ads.

• Self service ability to directly apply for a WhatsApp Official Business Account (blue checkmark) with Meta.

Twilio now offers rich messaging on RCS through the Content Template Builder. You can now create and send rich cards, media, and rich card carousels. Twilio will support more rich RCS functionality in the near future.

When you send a rich content message through Messaging Services, Twilio will automatically deliver RCS rich content to compatible devices. For devices that do not support RCS , Twilio will send the defined fallback via SMS or MMS. You can define a twilio/media or twilio/text type as a fallback within your rich content template. To learn more about how to create and send rich content on RCS see our docs here. If you want to learn more about RCS generally and request access, you can do so here. 

The Compliance Embeddable is a white-label React component designed to seamlessly integrate into an ISV's web application as an iframe. This product enables ISVs to securely collect compliance information from their customers and send it directly to Twilio, streamlining compliance and shortening customer’s time-to-market. For ISVs, the Compliance Embeddable serves as a great alternative to manually collecting information from customers, and requires less development work compared to integrating with the Twilio Toll-Free Verification APIs and building their own UI.

The Compliance Embeddable is offered for free and is now available in Public Beta. Please follow the instructions in Twilio Docs to get started.

We are excited to announce an enhancement to the Twilio Messaging Service that improves the delivery of multimedia content to destinations that do not support MMS. With the updated MMS Converter feature, Messaging Service can now select SMS-only capable senders when sending messages to destinations that convert MMS to SMS links.