Product changelog and announcements

ISV customers can now view additional brand registration information for any Secondary Brand they are registering for US A2P 10DLC. On the successful registration of an A2P brand, customers can view this additional information when using the GET Brand Registration API.

“russell_3000” is returned ‘true’ by TCR when the brand is verified as a Russell 3000 brand.

“tax_exempt_status” returns the verified tax-exempt status of a US-based nonprofit brand, such as ‘501c3’, as verified by TCR. Otherwise, this is returned as ‘N/A’.

“skip_automatic_sec_vet” is returned 'true' for ISV customers who choose to skip automated secondary vetting for a secondary brand.

You can find more details for these in ISV Onboarding API docs.

ISV customers can now choose to skip automated secondary vetting for any Secondary Brand they are registering for US A2P 10DLC. Twilio continues to recommend secondary vetting because it raises both campaign throughput and daily volume limits beyond minimums allowed by carriers. With automated secondary vetting, customers can maximize throughput and daily limits without extra registration steps.

That being said, we understand that some of our ISV customers may not want to complete secondary vetting for some of their customers based on the additional vetting fees and the usage patterns of those customers. Customers can review the usage limits available to a brand without secondary vetting in throughput for US A2P 10DLC.

This parameter SkipAutomaticSecVet is an optional parameter during brand registration, which can be used to skip secondary vetting for an A2P brand. You can find more details in ISV Onboarding API docs.

A2P 10DLC brand and campaign registration for all 501(c) nonprofit organizations is now available as part of Twilio’s A2P 10DLC Console and ISV API onboarding experience.Nonprofit organizations can register using the Charity / 501(c)(3), Political, or Standard use cases depending on their entity type:

• 501(c)(3) organizations should register campaigns with the Charity / 501(c)(3) special use case. Charity / 501(c)(3) is a reserved use case for 501(c)(3)s to receive discounts on A2P carrier fees.
• 501(c)(4), 501(c)(5), and 501(c)(6) organizations sending messages that are political in nature should register with the Political special use case, or register non-political messaging with standard campaign use cases. The Political use case receives increased messaging throughput on A2P.
• All other 501(c) designations should register their campaigns with standard campaign use cases.

For more details on the Charity / 501(c)(3) and Political campaign use cases, please see this support article on special use cases.

Note: We're still working to enable registration for 527 Political organizations and for the Emergency Special use case.

Messaging Customers are required by U.S. carriers to register for A2P 10DLC. Independent Software Vendors that offer other customers the ability send SMS and MMS need to register themselves as an ISV brand via Trust Hub in the Twilio console and then they can register each customer as a Standard Brand or a Starter Brand. Registered Brands can then register use case campaigns.

Starter Brand registration is now available for all independent software vendor (ISV) customers to register your customers for US 10DLC compliance and send SMS and MMS in the US with 10-digit long codes. Starter Brand registration is intended for customers who send fewer than 3,000 daily SMS segments and MMS messages over 10-digit long codes AND use five or fewer 10-digit U.S. long codes. Twilio is covering the costs for Starter Brand registration and monthly campaign fees.

ISV Customers can read the Starter Brand overview and step-by-step API walkthrough as they prepare to register their customers.

Twilio continues to streamline registration with US Carriers for Long Code Messaging (A2P 10DLC). All A2P brand registrations are now subject to an additional $40 one-time vetting fee. Twilio will automate the vetting process and cover the vetting fee for primary Brands until October 1, 2021 and Secondary Brands created for ISVs until August 21, 2021.

With automated secondary vetting, you will benefit from:

1. Increased daily messaging limits to T-Mobile. See the article ‘T-Mobile daily message limits for long code messaging with A2P 10DLC’ for details.
2. Increased throughput on your campaigns since secondary vetting will ensure accuracy of information and maximizing the TCR Score. See more details in our support article ‘Message throughput (MPS) and Trust Scores for A2P 10DLC in the U.S.’

There is no special action needed from customers to benefit from secondary vetting after this change, it will automatically be triggered for all brands registering for US A2P compliance.

Government agencies are now able to register for US A2P 10DLC.

Government agencies have access to all Standard Campaign use cases today, and will also be eligible for the use case for Emergency Services, once the ecosystem has launched full support for Special Use Cases. See our support article for more info.

All eligible Twilio customers can now start registration for US A2P 10DLC, in the Twilio console or via API. Registering protects and can improve SMS and MMS traffic deliverability and throughput.

To see who should currently register for A2P 10DLC, please refer to this article. In general, customers who send more than 3,000 SMS to the US using Long Code numbers can immediately begin taking action. To start registration, click here or go to Twilio Trust Hub, and select "Go to A2P Messaging".

Quick reply and call to action buttons can now be added to WhatsApp message templates when they are created in the Twilio Console. Buttons make it easy for businesses to streamline customer responses and guide their customers through conversational interactions, or drive them towards desired outcomes to improve engagement. Quick reply buttons let businesses define standard responses that users can tap to send. Call to action buttons trigger a phone call or direct users to a website when tapped.

To learn more about this exciting feature, check out our blog post or try it out for yourself today!

A new option for handling inbound messages on your Messaging Services has been launched. In addition to the previous options, you can now defer to the webhook set on the phone number, allowing each phone number to have a diferent configuration for incoming messages while they are part of the same messaging service.

This lets you utilize the benefits of a messaging service for outbound messages, but have inbound messages routed differently to fit the needs of your business.

You can find this new option in the Integrations section of your Messaging Service and is also available on the Messaging Services API as the property "use_inbound_webhook_on_number": true

Every US(+1) Toll-Free number is now enabled with MMS capability, out-of-the-box. Starting today, you can use Toll-Free numbers to send and receive media messages from recipients in US and Canada.

To learn more about emerging use cases for media messaging, please visit our blog post.