Product changelog and announcements

You can now delete WhatsApp message templates in the Twilio Console. To delete a message template, click on the template name on the WhatsApp Message Templates page and then click “Delete” at the bottom on the page. Per WhatsApp guidelines, you may not reuse the name of a deleted template for 30 days after deletion.

Customers registering for U.S. A2P 10DLC should use the new name “Proxy” instead of the old name “Conversational” when registering for campaigns of this type. This change is applicable in the A2P wizard in the console as well as ISV APIs (Create Campaign Use Case step). ISV API customers need to update their API integration.

This name change is to better represent the campaign type, which is meant for proxy/pooled numbers supporting personalized services and non-exposure of personal numbers. Some customers had incorrectly registered campaigns as Proxy/Conversational which should’ve been registered as Customer Care.

You can read more about the Proxy campaign use case here.

Customers can now view the reasons for their brand registration failures in the A2P wizard in the console or via the ISV APIs for US A2P 10DLC. In the A2P Wizard in the Twilio console, brand failures will result in an error screen with reasons for the failure and instructions to fix your brand registration before you can move forward. The GET Brand API call returns the failure reasons for ISVs registering their customers via API. You can review the failure reasons and API details here and reduce the likelihood of your brand registration failing by following the brand registration best practices here.

Customers registering for their Primary A2P Brand for US 10DLC traffic automatically get their brand vetted by carriers through a process called Secondary Vetting. This vetting costs $40 and was being covered by Twilio till Sept 30. The Secondary Vetting fee will now be passed through to customers and reflect in customer bills as the waiver has ended.

Note Starter Brands and Starter Campaigns continue to remain free of charge.

Businesses can now move their existing WhatsApp Business API phone numbers to the Twilio platform at any time whether they were previously registered through a different Business Solution Provider or directly with Facebook. Upon a successful migration, the transferred number retains its display name, messaging limit tier, quality rating, and Official Business Account status. High quality message templates on the account that it was previously registered on will also be copied over to the new account on Twilio.

For more details on how to move WhatsApp numbers to Twilio, please take a look at this support article.

Twilio MMS 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.

A subset of 5 A2P 10DLC Special Use Case campaigns require additional carrier approvals immediately following registration. These 5 post-approval use cases are now available for registration. Once a campaign information is submitted, it will remain in “review” until carriers grant approval on the campaign.

The special use cases that require carrier post-approval and are now available for registration via the Console and ISV APIs are:

• Agents; franchise; local branches
• Proxy (formerly Conversational)
• Emergency
• Social
• Sweepstakes

You can read more about these in our support article or API docs.

Businesses around the world can now send promotional or marketing template messages with the Twilio API for WhatsApp. Prior restrictions requiring notifications be related to specific transactions no longer apply. Businesses can now engage with their customers in new and exciting ways to drive better business outcomes such as sending timely renewal reminders, product upgrade offers, back in stock alerts, sale notices, promotional coupons, and much more!

For more details on how to send these messages using Twilio, please take a look at our documentation.

ISV customers registering their customers' US 10DLC Brands and Campaign Use Cases have full functional parity between the API and console registration experience for Starter and Standard.

Customers can now use the Trust Hub console to register Starter and Standard Brands and Campaign Use Cases. Illustrated screenshots and guidance on which brand type to choose for your customers is provided in the documentation.

ISV Customers with a registered US A2P ISV Brand can now test their API integrations with Twilio by registering Mock Brands and Campaigns. The Mock Brand and Campaign API allows you to develop and test applications against Twilio’s A2P Brand and Campaign APIs without incurring any A2P 10DLC related fees.

Mock brands and mock campaigns are created similarly to brands and campaigns registered against the non-mock A2P APIs. Any campaign registered alongside a Mock Brand will automatically be considered a Mock Campaign and will not allow Messages to be routed on US A2P routes. And Mock Brands and campaigns expire after 30 days. These are some important restrictions and considerations to keep in mind when you’re using this API, with detailed explanations available in this guide.