Product changelog and announcements

Twilio now supports new error codes for "Rejected" and "Paused" WhatsApp Templates. With Twilio Alarms, you can now get notified via webhook or email when these and other errors occur.

When a WhatsApp template gets rejected, Twilio surfaces a new error code of 63040 and will include the reason from WhatsApp.

Likewise, if a WhatsApp template is paused due to quality concerns from WhatsApp, Twilio will surface an error code of 63041. The message also contains when it will be unpaused. A template can be paused by WhatsApp when different users report messages sent using that template, or when users block the number after receiving those messages.

Effective today (October 24, 2022), Twilio is ending the sale of Notify. New customers will be unable to use the product.

We intend to end of life (deprecate) the Notify product on October 23, 2023. Existing customers will be supported up until this date, however, no new feature enhancements or rate limit increase requests will be granted.

Other Twilio products that support push notification use cases such as Verify or Conversations are not impacted by this.

We are sincerely sorry for any disruption this may cause and have prepared this Migration Guide to assist with the transition.

We are excited to introduce the new Messaging - Regulatory Compliance section in the Twilio Console! Regulatory Compliance consists of the following screens, which provide enhanced experience to Twilio's US A2P 10DLC customers.

A2P 10DLC Messaging customers with a Tax ID (for example, EIN in the US) can now register a Low Volume Standard Brand in Twilio Console - Trust Hub - A2P Messaging

Twilio has deprecated the ability to register new Starter Brands due to updated registration requirements from The Campaign Registry (TCR). As a result, the option to create or update Starter Profiles or Brands is disabled in the Twilio Console and APIs. API requests to create or update Starter Profiles will fail with error code 22404; API requests to create or update Starter Brands will fail with error code 21726.

Previously registered Starter Brands and Campaigns are subject to new data validation requirements. Any campaigns and brands that do not meet those requirements will be deleted by Twilio on behalf of customers starting Nov 3rd.

Customers with Tax IDs are requested to register for A2P 10DLC using the Low Volume Standard Brand or Standard Brands options.

For more information, please check out our recent blog post which explains the process for new registrations and the criteria for keeping existing registrations.

Link Shortening is now accessible in public beta on the Programmable Messaging API. This functionality enables you to programmatically shorten long links with your own company branded domain without any extra API calls. You can also set up your webhook to receive click events when recipients of the messages click on the shortened link.

Read our API documentation to get started.

Message Scheduling can now be used to develop compliant healthcare applications that 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 Products and Services.

Learn more about how to build on Twilio for HIPAA compliance.

Twilio has implemented an urgent precautionary measure to protect Programmable Messaging accounts created before April 2019 from possible exploitations of their service by automatically disabling unused SMS Geo Permissions. We’re taking this action to protect customers from potential fraud known as SMS Traffic Pumping. Given the rise of fraud in the ecosystem, we want to help ensure that we minimize potential exploits and reduce the risks faced by our customers. Disabling destination countries your business doesn’t serve or uses infrequently is an additional line of defense against fraudulent activity. See this Help Center article for more information on SMS Traffic Pumping Fraud and how to protect your applications from it.

Why only accounts created before April 2019?

Accounts created during and before March 2019 previously had SMS Geo Permissions enabled globally by default. For our customers’ convenience and protection, Twilio will disable SMS Geo Permissions on a one-time basis for country destinations to which messages have not been sent in the 30 day period from 23 July 2022 to 22 August 2022. This one-time action on accounts will begin on 25 August 2022 and end on or before 9 September 2022.

If needed, you can enable or disable SMS Geo Permissions to any country at any time in Twilio Console by following the steps in this Support Article.

Twilio Message Scheduling is now generally available for use!

Message scheduling enables developers to schedule and send an SMS, MMS or WhatsApp for a time in the future, all within a single API call. Iterations since our beta release include adding support for HIPAA Eligibility, enabling a scheduled message to send 15 min in advance (previously 60 min), and increasing the account usage limitations to enable higher volume sending.

For more information, see the Message Scheduling Documentation.

Twilio customers sending messages via US A2P 10DLC can now log into Twilio Console - Trust Hub - A2P Messaging to check whether they have been incurring penalty fees from sending unregistered message segments.