Product changelog and announcements

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.

The Bulk Messaging API is now in Public Beta, enabling product and engineering teams to message at scale. Key features and benefits include:

• Send up to 10,000 messages with a single API request over SMS/MMS and RCS, eliminating the need for custom queuing, rate limiting, and retry logic
  
• Personalize message text, images, rich content, and tags for each recipient using Liquid 
• Schedule bulk sends for a later time
• Send RCS rich content without templates, or continue using your existing Content Templates

This API also offers full JSON support, consistent versioning schemes, and shared primitives that work across Twilio Email and Push Notifications, enabling you to expand to multiple channels with fewer lines of code.

By providing multi-recipient sends, per-request controls and a durable API design, the Bulk Messaging API reduces implementation complexity and can accelerate time-to-scale for teams of all sizes. Check out our tutorial to get started now!

Compliance Toolkit is now Generally Available for Twilio Programmable Messaging customers in the United States. 

Compliance Toolkit helps you automate regulatory compliance by embedding AI-powered safeguards directly into your messaging workflows. It proactively detects possible compliance violations, identifies high-risk recipients, and applies intelligent transmission controls to prevent issues before messages are sent.

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

You can now use the Programmable Messaging API to send and receive SMS in Twilio's Ireland (IE1) region. When using the feature, messages are stored and processed in Twilio's Ireland (IE1) region up to the point they reach Twilio’s connections with telecommunications providers.

This release adds API support in IE1 for:

• Sending SMS messages with phone numbers and alphanumeric sender IDs.
• Receiving inbound SMS messages with webhooks.
• Messaging Services, including webhooks, sticky sender, and country code geomatch.

To learn more and get started, see the Public Beta API docs.