Product changelog and announcements

Starting August 10, 2026, the error code returned when an RCS message cannot be delivered to an unreachable end-user device will change from 30036 to 30046.

Error code 30046 (Message delivery not confirmed) gives developers a more accurate signal when an RCS message cannot reach an end-user device. Previously, 30036 (Validity Period Expired) was returned for these failures, pointing to queue and throughput settings as likely causes and making it easy to investigate in the wrong direction. 

With 30046, the failure is correctly attributed to device-side conditions like the recipient's device being switched off, out of coverage, having no internet connection, or being unable to accept the message. This code will also serve as the standard for device-unreachable conditions across RCS and future OTT channels.

WhatsApp Usernames is now supported on the Twilio Platform and Messaging APIs for WhatsApp. WhatsApp now allows users to adopt usernames. A username can optionally mask a user's personal phone number and allows them to interact with businesses through Business Scoped User IDs (BSUID). Twilio exposes this identifier in message webhooks and in Event Streams event data. Meta is releasing this functionality in multiple waves, starting on July 7, with additional countries to follow at later dates. Please check our documentation for the latest rollout schedule.

Consent Management API is now Generally Available allowing you to programmatically sync, store, update, and manage user consent preferences globally across RCS, SMS, and MMS channels.

As of June 30, 2026, Consent Management APIs can now support healthcare use cases that may contain protected health information (PHI) for organizations that are subject to the Health Insurance Portability and Accountability Act (HIPAA). Twilio will sign Business Associate Addendums (BAA) with covered entities and business associates for HIPAA Eligible Services. Learn more about how to build on Twilio for HIPAA compliance.

Learn more about this feature and how to enable it in our documentation.

As of June 30, 2026, Compliance Toolkit can now support healthcare use cases that may contain protected health information (PHI) for organizations that are subject to the Health Insurance Portability and Accountability Act (HIPAA). Twilio will sign Business Associate Addendums (BAA) with covered entities and business associates for HIPAA Eligible Services. Learn more about how to build on Twilio for HIPAA compliance.

Learn more about this feature and how to enable it in our documentation.

Twilio is launching the Private Beta for Compliance Embeddable for US A2P 10DLC.

The Compliance Embeddable is a white-label, self-service solution that integrates seamlessly into an Independent Software Vendor’s (ISV) application portal. With the Compliance Embeddable, end customers can independently complete both brand and campaign registrations while Twilio handles the underlying regulatory infrastructure behind the scenes. 

Featuring fully customizable styling and data pre-filling, the Compliance Embeddable simplifies end-user registration, reduces internal development overhead, and streamlines onboarding workflows.

Sign up for the Private Beta to get started.

New Unified Typing Indicator API experience:

You can now send typing indicators across RCS, WhatsApp (WA), and Apple Messages for Business (AMB) using a streamlined consistent integration with JSON payloads.

Smart Channel Behaviors:

• RCS: Displays a typing indicator for up to 20 seconds (or until the message delivers) to reduce perceived wait times.
• WhatsApp: Automatically marks the referenced message as read and displays the indicator for up to 25 seconds (or until delivery) using the required messageId.
• Apple Messages for Business (Private Beta): Support for Typing indicators is available! Please note that AMB access is currently restricted as it is in private beta. How to use typing indicators on AMB is available in our beta documentation. 

💡 Need more time? For longer workflows, you can send additional typing indicator requests to extend the duration before the default timeouts hit.

See our public documentation here:

• RCS
• WA

The Programmable Messaging API is now generally available for SMS in Twilio’s Ireland (IE1) region. When using this feature, SMS message personal data is stored and processed in the EU up to the point it reaches Twilio’s connections with telecommunications providers.

With this release, the Ireland (IE1) region supports the following messaging features:

• Programmable Messaging API: Send outbound SMS messages using phone numbers and alphanumeric sender IDs.
• Inbound SMS: Receive inbound SMS messages via webhooks configured at the phone number or messaging service level.
• Messaging Services: Manage IE1 sender pools from the Twilio console or via the API. Take advantage of Sticky Sender, Country Code Geomatch, Advanced Opt-Out, and service webhooks in IE1. 
• Messaging Logs and Insights: Analyze and troubleshoot IE1 SMS traffic in the Twilio Console.
• Phone Numbers: Configure phone numbers for use in IE1 using the Twilio Console or the API.

To learn more and get started, see the developer documentation.

Starting May 21, 2026, T-Mobile A2P 10DLC daily message cap warning error codes 30025 (50% threshold), 30026 (70% threshold), and 30027 (100% of the daily limit) are being retired. These error codes will no longer fire in API error logs or webhooks, and the associated proactive warning emails will stop.

Error code 30023, which triggers when traffic hits 100% of the T-Mobile daily cap, is not affected by this change.

What do customers need to do? 

Customers who have webhooks or monitoring configured for error codes 30025, 30026, or 30027 should plan to remove those integrations before  May 21.

Customers who relied on these error codes or warning notifications to monitor daily usage can track T-Mobile message volume through Twilio Messaging Insights. Error code 30023 will continue to fire when traffic hits 100% of the T-Mobile daily cap, so customers can use that as a trigger for monitoring and alerting.

Need a hand?

These resources will help:

• Error code 30023

• T-Mobile Daily Message Limits

• Twilio Messaging Insights

• Traffic Optimization Engine

We are excited to announce that Apple Messages for Business (AMB) is now available in Private Beta on the Twilio platform. This release allows businesses to connect with their customers directly within the native Messages app on iPhone, iPad, and Apple Watch, providing a secure, branded, and highly interactive communication channel.

With Apple Messages for Business, you can go beyond plain text to deliver rich, end-to-end customer journeys with features like:

• Native Entry Points: Meet customers where they already are—integrated natively into Apple Maps, Safari, Siri, and iOS Search.
• Rich Interactive Features: Utilize List Pickers for product selection, Time Pickers for scheduling, and Rich Links for high-fidelity website previews.
• Secure Commerce: Enable seamless, one-touch payments using Apple Pay, authenticated via FaceID or TouchID.
• Branded Experience: Build trust with a verified sender logo and end-to-end encrypted messaging.

To learn more and request access to the beta, visit Twilio's Apple Messages for Business product page.

• Simplify sending and build faster with a single shared API that is compatible with Android, iOS and web browsers 
• Automatically expire stale tokens instead of managing expiration webhooks and token state
• Send up to 10,000 notifications with a single API request and personalize those notifications for each recipient using Liquid
• Schedule notifications for a later time

This API also features shared primitives that make it easy to extend your use case across SMS/MMS, RCS and Email using the Bulk Messaging API and Twilio Email. Request access to the private beta to try it today!

Note that this API is expected to replace Twilio Notify. If you are a Twilio Notify customer, please indicate it in your request for faster access so you can start planning your migration.