Product changelog and announcements

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.

Over the next few weeks, we are gradually rolling out MMS capabilities across our US Toll-Free numbers.

Starting this week, you will see numbers with MMS capabilities appear when you search for US(+1) Toll-Free phone numbers using Advanced Search. If you already own Toll-Free numbers, they will be enabled with MMS capabilities by the end of March as well.

You can send an MMS message on a Toll-Free number by including the MediaUrl parameter in your API request. Pricing information can be found here.

We will share another update once all Toll-Free numbers are generally available for sending and receiving MMS messages from recipients in US and Canada.

HTTP callbacks (webhooks) for inbound WhatsApp messages now include new ProfileName, WaId, Forwarded, and FrequentlyForwarded parameters. The ProfileName parameter contains the WhatsApp sender's profile name and the WaId parameter contains the WhatsApp ID of the contact sending the incoming message. For messages received that have been forwarded or forwarded many times the parameters Forwarded or FrequentlyForwarded, respectively, will appear with the value true.

Customers can now view the time taken by Twilio to process their messages via the Latency report visible in the Programmable Messaging Insights console.

Message latency is calculated as "Time Twilio sent the message - Time customer made message request API call." Customers can also view the limits applied to their individual senders, messaging services, and accounts via Modals in the Insights report.

This blog contains details about the product and this new guide explains how applications can be built to handle scale from the beginning.

As your messaging volumes grow, you can now monitor the latency introduced in sending messages using the Latency Report in Messaging Insights. This can be particularly helpful in high-traffic times like promotions for Black-Friday, or emergency notification situations. The Latency Report is available to all Messaging Customers at no cost via the Messaging Insights console.

As part of the effort to increase transparency on Messaging Latency, there is now a new guide for scaling and two new filters available as part of Insights - latency buckets and time-ranges of 5-minutes and 4 hours. The blog with this announcement is available here.

Deleting a Message log will now automatically remove any Media objects associated with that message whenever applicable. For media objects that are associated to multiple messages, Twilio will continue to store a copy until all messages refering to the media object are deleted. This allows a more intuitive experience when customers issue delete requests on messages containing media. The change will apply to all messaging channels supporting media including MMS, WhatsApp and Facebook Messenger.

More details of the changes to message records and media availability and deletion are published here.