Product changelog and announcements

Intelligent Alerts is now GA for all Twilio Messaging customers sending SMS traffic. It uses anomaly detection to automatically monitor your messaging traffic for unusual spikes in selected error codes, helping you identify potential delivery issues faster.

The TCPA Known Litigators Check is now available within Compliance Toolkit to help safeguard your messaging by identifying and blocking messages to phone numbers believed to be associated with individuals or entities with a history of filing TCPA-related legal actions. 

This safeguard intelligently filters non-essential communications, such as marketing/promotional messages to phone numbers associated with known litigators, while allowing essential traffic, like transactional alerts, otp, and customer support messages, to reach the recipient. 

When a message is blocked by this feature, Twilio will return Error Code 30640.

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

Consent Management API is now available globally in Public Beta, allowing you to programmatically sync, store, update, and manage end-user consent preferences across RCS, SMS, and MMS channels. This API acts as a centralized source of truth for managing consent preferences, enabling you to seamlessly integrate consent data from external systems like CRMs or web forms directly into Twilio.

Note that consent states updated via this API for a given Messaging Service are automatically enforced across all three unified channels (RCS/SMS/MMS) to ensure compliance, without requiring any code changes.

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

You can now specify the SMS or MMS sender Twilio uses when an RCS message fails to deliver using the new "FallbackFrom" parameter in your /Messages API request. The FallbackFrom sender must be in the same account SID, but does not need to be in your Messaging Service's sender pool.

This can be useful if you need fallback messages to come from a specific number, instead of relying on Twilio's automatic selection. You can also use this to send from one RCS sender representing your brand, with different fallback numbers per department, store, or representative.

For more information, please see our docs.

The Country Code Geomatch feature within Messaging Services now supports RCS in a public beta. If you have distinct RCS senders approved per country, you can add each of them to the sender pool of a single Messaging Service. When you send from that Messaging Service, Twilio will select the RCS sender that matches the country of your recipient’s phone number.

Previously, each Messaging Service supported only one RCS sender, which meant customers sending to recipients in multiple countries had to maintain separate Messaging Services and build their own routing logic. RCS Geomatch removes that requirement.

For more information, see the Messaging Services’ docs.

Twilio Programmable Messaging now supports adding AT&T test numbers to your RCS sender.

You can now prototype and test your RCS sender on all major US carriers.

Once you’re ready to use RCS for production traffic, submit your RCS compliance information and our operations team will guide you through the carrier approval process

Go to Console to get started now.

For more information, see our docs.

Starting March 18, 2026, MMS rate limits for Application-to-Person (A2P) U.S. 10-digit long code (10DLC) numbers are determined by Brand Trust Score and Campaign use case, replacing the previous fixed account-level cap of 1 message per second (MPS).

Twilio Programmable Messaging automatically unifies opt-out management across RCS, SMS, and MMS channels.

When an end-user replies with any opt-out keywords (such as STOP, CANCEL, or UNSUBSCRIBE etc) to an RCS message, Twilio automatically enforces that opt-out for all future SMS or MMS messages sent from that same Sender or Messaging Service. Conversely, opt outs on SMS or MMS will automatically block future RCS messages.

Any attempt to message an opted-out user across these unified channels will now fail and return Error 21610.

This cross-channel compliance is active by default to protect your sender reputation, prevent accidental messaging on fallback channels, and requires no code changes to implement.

For more information, read our documentation.

 

Starting March 23, 2026, we’ll begin rolling out more specific and detailed error codes for US A2P 10DLC Campaign registrations.

These new codes are designed to give you clearer, more actionable feedback when a campaign is rejected or requires an edit - helping you resolve compliance issues faster and get your messaging live.

The existing error codes will still be supported, but these new granular codes provide the specific context needed for rapid troubleshooting.

What’s changing?
Currently, A2P 10DLC rejection messages can sometimes be broad, making it difficult to identify the exact compliance blocker. With this update, you’ll see granular error codes that pinpoint the specific reason. 

These new codes will appear in:

• API Responses
• Event Streams
• Twilio Console (Campaign Details Page)

What this means for you
If you have built custom logic or processes to handle A2P 10DLC registration errors, we recommend reviewing your error mapping.

Updating your tools to reflect these new, specific codes will allow your end-customers and operations teams to respond to rejections with much higher precision.

For a full list of the new codes and their meanings, please refer to the Support Article on Campaign Rejections. 

Twilio Programmable Messaging now supports RCS messaging to Canadian phone numbers.

You can now request RCS Sender approval on available Canadian carriers.

To start sending branded RCS messages using Twilio Programmable Messaging, go to the Twilio Console to create, test and submit an RCS Sender.

Note that while all brands can submit RCS Senders for carrier approval, Twilio cannot provide an SLA or guarantee Sender approval by carriers.

For more information, see our RCS documentation.