Product changelog and announcements

Compliance Toolkit is now available in Public Beta, allowing you to use Artificial Intelligence and machine learning to help manage compliance obligations with respect to certain local regulatory or compliance requirements.

To start using Compliance Toolkit, Opt in through the Twilio Console and review the detailed setup instructions in our developer documentation.

 

We’ve made an important update to A2P 10DLC Phone Number Registration events in Twilio Event Streams — now including the Messaging Service SID in all related events.

With this enhancement, you can directly identify which A2P Campaign a phone number is associated with by referencing the messaging_service_sid field in the 2.0 schema version. This improves traceability and helps streamline debugging, monitoring, and automation workflows tied to number registration.

The following Event Streams now include the messaging_service_sid field:
- com.twilio.messaging.compliance.number-deregistration.pending
- com.twilio.messaging.compliance.number-deregistration.successful
- com.twilio.messaging.compliance.number-registration.pending
- com.twilio.messaging.compliance.number-registration.successful

To learn more about A2P Notifications through Event Streams , check out our guide docs.

We’ve made a key improvement to Authentication+ to support programmatically triggering a new 2FA verification email for A2P 10DLC Brand registrations that have failed. 

Alongside the endpoint, we’re introducing a set of dedicated 2FA error codes that surface precise failure reasons and point you to the fastest remedy, so your users can complete brand verification with fewer support tickets and less manual work.

To learn more about Authentication+, check out our Support Article and Twilio API Docs.
 

Error Code	Message	Description
21736	Domain Ownership Could Not Be Verified	The domain used in the brand contact email could not be independently verified.
21737	2FA Verification Expired	The 2FA verification link or token expired before being used.
21738	2FA Email Undeliverable	The verification email could not be delivered to the brand contact.
21739	2FA Verification Failed or Timed Out	The verification process was not completed.
21740	Invalid Brand Contact Email Domain	The domain used for the brand contact email is not acceptable for Authentication+ (e.g., gmail.com).
21741	2FA Code Expired	The verification code was not entered in time.

Studio now supports the ability to shorten links within your message body when using the Send Message and Send & Wait For Reply widgets. You can also shorten links to track customer engagement with click events.

All ID fields specified in the Twilio Content Content APIs such as in Twilio cards will be returned in Button Payload in a uniform way.

We will return the exact payload specified without 64 bit encoding to align button behavior.  

To specify a Button Payload, pass in an ID field into the button actions array within a button object. Examples can be found in the Twilio docs. Button Payloads will be returned in the inbound webhook. Billing may apply. To learn more see our docs here. 

 

 

Meta Pricing Changes for WhatsApp Messages: Effective July 1, 2025

Starting July 1, 2025, Meta will shift from 24-hour conversation-based pricing to a new model that charges per template message delivered. Pricing will vary by template type (Marketing, Authentication, or Utility) and may also be subject to volume-based tiers in some regions. 

This update applies to all WhatsApp messages, including those sent through Twilio Verify.

Twilio will continue to pass through Meta’s updated charges without adding any additional fees. No action is required, but customers may notice billing changes starting July 1, 2025, based on message type and volume. 

We haven’t listed the Meta fees directly in this email because they vary by region and message type. For more information, check out Twilio’s Notice: Changes to WhatsApp’s Pricing (July 2025) Help Center article or Meta’s Pricing updates on the WhatsApp Business Platform docs page.

We can’t wait to see what you build!

–Team Twilio

 

At Twilio, we’re always working to make your messaging experience more reliable and transparent. That’s why we’re making some updates to how we handle Alphanumeric Sender IDs.

What’s Happening?

Starting on August 13, 2025, we’re introducing clearer error codes and new message status updates when an Alphanumeric Sender ID isn’t properly registered or authorized in a given country. These updates will help you quickly understand if something needs to be fixed and keep your messages flowing smoothly.

Here are the highlights:

• *New Error Codes

  • 30041: Sent when the Alphanumeric Sender ID isn’t registered or authorized for use.

  • 30042: Sent when the Alphanumeric Sender ID is explicitly blocked because it’s generic or not allowed to be used.

•  What Will Change in Your Logs?

  • Messages with unregistered Alpha Sender IDs will now appear as “Likely-SCAM” in the logs in Singapore and Ireland.

  • Error codes will be clearer and more actionable.

If your Alphanumeric Sender IDs are already registered and approved for your destinations, you’re all set—no action needed! If you see one of these new error codes, that’s your cue to double-check that your Alphanumeric Sender ID is properly set up for the country you’re sending to.

*Note: Error codes are subject to processing fees. For more information on charges on messaging errors, visit our Twilio Help Center article on error code fees.

For questions or help with registering your Alphanumeric Sender IDs visit:

• SMS Guidelines Page

• Twilio Help Center

This powerful new feature automatically analyzes your messaging traffic to identify key opportunities to improve deliverability & engagement. It provides tailored insights—including the potential impact of improvements—and highlights relevant Twilio products that can enhance your messaging performance.

Accept PIX Payments on WhatsApp with Twilio/pay
Move from conversation to conversion with native in-chat payments

We’re excited to announce support for PIX payments on WhatsApp using Twilio/pay templates. You can now guide customers through completing a financial transaction directly in WhatsApp.

Use Content Templates with Twilio/pay to:

• Send Order Details messages with a PIX copy code button that opens the user’s banking app

• Send Order Status updates as payment progresses through stages like pending, shipped, or completed

• Display itemized order summaries, expiration details, and total amounts—all within a single message

To enable this, your business must:

• Have a valid WhatsApp sender in Brazil

These templates support variables for payment ID, merchant name, itemized details, and expiration. Rich metadata can be passed to payment processors, with updates automatically sent to users through Order Status messages.

Ready to embed seamless checkout into your messaging flows?
Explore the docs to get started:
twilio/pay