Product changelog and announcements

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.

To support compliance and improve campaign approval rates, Twilio is introducing new fields during U.S. A2P 10DLC Campaign registration.

What’s Changing?

When registering a Campaign, you must now provide:

• Privacy Policy URL – A valid, publicly accessible link to your privacy policy
• Terms & Conditions URL – A valid, publicly accessible link to your service terms.

These are now dedicated fields in the registration flow.

Console Updates

In the Twilio Console, you’ll see new fields in the Campaign registration form where you can enter your Privacy Policy and Terms & Conditions URLs directly.

API Updates
For programmatic registrations, these fields are now supported:

• Setup: Values can be passed during the Campaign create request. Providing the specific request header during the Campaign create call will return these fields in the API response.
• Recommendation: While the API currently allows flexibility, we highly recommend including these links in all new registration requests to avoid potential vetting failures.

Why This Matters
Previously, this information was required and  requested within the Message Flow description.
Providing dedicated, direct links ensures your Campaigns get approved faster and reduce the risk of rejection.

To learn more about U.S. A2P 10DLC registration, please review our documentation and Support article on Campaign approval requirements.

To improve message reliability and security, we are updating the Toll-Free Verification process to require business registration numbers.
Starting February 17, 2026, a business registration number for all business types expect sole proprietorships will be required for all new Toll-Free submissions.

These fields are available now in Console and API. 
To learn more about  business registration number requirements check out our Toll-Free Verification API Docs and Support Article. 

To maintain compliance with industry standards for platform integrity, all 527 organizations using toll-free numbers for political messaging must now provide a Campaign Verify (CV) Auth Token.

February 17, 2026 - All new political Toll-free verifications from 527 organizations require a valid CV Auth Token to register and a CV Auth Token needs to be added to existing verifications.
January 7, 2026 - Support for CV Auth Tokens launched in Twilio Console and API

To learn more about Campaign Verify Token requirements check out our Toll-Free Verification API Docs and the Campaign Verify FAQ

Template editing is live for all Content API users today. You can now update existing templates (text, variables, rich content) directly via the API without needing to recreate or version manually. Editing a template does not change its Content Sid.

Why it matters

• Faster copy tweaks and fixes
• Consistent messaging template changes across channels
• Retain the same Content Sid when sending templates

How it works
Use PUT /v1/Content/{ContentSid} to update any existing template.

To learn more about editing your Content Templates, see our docs page here.