Product changelog and announcements

We have begun enabling accounts for improved message creation API error visibility in  SMS logs and Messaging Insights in the Twilio Console as well as when you list messages via the Programmable Messaging API. Full details are available here. When your account is enabled, the banners on those console pages will update to reflect that your account is enabled. Note that accounts will be enabled on a per-account-sid basis over the coming weeks; thus certain sub-accounts may gain access before others.

HTTP callbacks (webhooks) for inbound WhatsApp messages that originate from a Meta Click-to-WhatsApp advertisement now include a new ReferralCtwaClid parameter. This parameter contains the unique identifier generated by Meta representing the WhatsApp message conversation initiated by a user’s ad click. Customers can now use this parameter to integrate their WhatsApp business messaging events with Meta’s Conversions API (see ctwa_clid) to optimize Meta’s ads targeting and performance measurement.

Learn more about how to create Click-to-WhatsApp advertisements with Twilio from our blog post.

Twilio Messaging MaxPrice API parameter will be deprecated starting June 3, 2024. 

 

We are excited to announce an enhancement in the A2P 10DLC Brand registration process. In our ongoing efforts to streamline and improve the user experience, we now have standardized error codes for any failures or issues encountered during Brand registration. These error codes will be directly available through the errors attribute on the Brand. 

With this release, it’s important to note that brand_feedback and failure_reason will be deprecated in an upcoming release.  If you have used these attributes in your integrations, we strongly advise transitioning to the new errors attribute due to its pending deprecation and limited information. 

Check out the updated Brand registration Twilio docs for more information. or a detailed list of all error codes please visit Twilio Error and Warning Dictionary.  

We are thrilled to announce the ability to edit and retry A2P 10DLC Campaign registrations in Twilio Console. With this update, failed campaign registrations can be edited and resubmitted directly from Console. Additionally, this release introduces new fields for campaign registrations to provide more comprehensive campaign details ensuring the registrations meet compliance standards.

 

For more information on how to edit and retry Campaign submissions and understand the new fields in campaign registrations, please visit our detailed guide at: Troubleshooting and Rectifying A2P Campaigns.

For more general information about the A2P 10DLC product, please visit the Twilio website. 

We are extending an invitation to Twilio Messaging customers to experience advanced capabilities for monitoring their messaging traffic. Our new Intelligent Alerts product monitors for anomalies in outbound messaging traffic in real-time using predictive artificial intelligence. Alerts are categorized to help prioritize events based on their impact on your business. Customers can configure notifications and review prior alerts on the Twilio Console.

Starting February 12th, 2024, we are improving visibility of inbound messages by including redacted One Time Passcode (OTP) messages. Twilio does not generally allow receiving inbound OTP messages on Twilio numbers. This prevents abuse of Twilio numbers. Previously, these inbound messages were filtered before being processed onto your Twilio account. In order to provide better visibility for all inbound traffic, Twilio will allow you to see these messages, but will be redacting the passcode itself and setting a failed status with error code 30038.

Starting February 13th, 2024, as part of out messaging error visibility improvements, we will be rolling out improvements to our console error logs. We are enhancing error coverage to include outbound messaging errors which previously weren't available in the console error logs. Previously, these errors were only accessible through the API, messaging logs and insights, and via message status callbacks. This visibility improvement empowers efficient troubleshooting and full operational transparency and doesn't indicate a decrease in message delivery success.

Learn more about upcoming messaging error visibility improvements.

RCS is an enhancement over SMS, delivering messages over Wi-Fi and cellular with higher encryption security and lower latency, to the default SMS messaging app on Android, Messages by Google. RCS only works on compatible devices and a limited set of countries.

In a gradual rollout starting February 16th, 2024, Twilio Verify will automatically upgrade delivery of Verify OTP messages via RCS instead of SMS whenever possible; and if it exhibits the same or better performance. See Verify RCS to learn more.

Effective January 31, 2024, messages sent from toll-free numbers pending verification will be blocked. Only fully verified toll-free phone numbers will be eligible to send messages. 

Blocked messages will return Error 30032 (any message sent from a restricted or pending TFPN) or Error 30007 (if spam/unwanted on a verified TFPN), and are subject to messaging fees.

These verification efforts, along with increased message filtering, help Twilio combat spam and create a trusted messaging ecosystem for you and your customers.

You may use our Twilio Console or API options to submit toll-free phone numbers for verification.

For more information, please check out our guide Toll-Free Message Verification for US/Canada.