Product changelog and announcements

We are excited to announce an enhancement in the Toll-Free Verification process. In our ongoing efforts to streamline and improve the user experience, we’ve updated our email notifications to include extra details like the parent account and the associated phone number. 

Visit our Twilio Docs for more information on Toll-Free Verification Notification Emails.

Effective September 30, 2024, Twilio will begin billing for failed messages in Programmable Messaging.

[Update] For a more in depth description of nuance here please see our help article.

As part of our commitment to transparency and improving message deliverability, we have introduced new features that provide detailed insights into message delivery errors and how to address them. With these enhancements, a failed message processing fee of $0.001 will be applied to messages that terminate in a "Failed" status. This does not affect messages that end in any other status.

Please note that you will not be billed for:

• Failures due to Twilio internal errors (Error codes: 12400, 20500, 20504, 30036, 30103, 30500, 63010, 63012).

• Failures due to Twilio account suspension or fraud detection limits (Error codes: 30002, 30454, 63038, 90010).

• Messages failed by SMS Pumping Protection and Messaging Geographic Permissions (Error code 30450, 21408).

• Meta imposed WhatsApp restrictions beyond a customer’s ability to remedy (Error codes: 63013, 63018, 63021, 63024, 63032).

You will never be billed for errors that are Twilio internal issues, or linked to other products or features. 

 

Why is this happening?

Twilio conducts pre-checks to help you avoid standard termination costs incurred by most CPaaS providers. Processing failures incurs costs for us, and this new fee will help us maintain and improve our services sustainably.

 

What do you need to do?

Review your account’s failed message volume in the Messaging Insights dashboard in Twilio Console to better understand your Twilio integration’s health and the impact of this change. If you see a high rate of message failures, use the messaging insights tool to explore their common error codes and causes. For the vast majority of customers this change will change your bill by less than 1%.

 

Common causes for elevated error rates include:

• Retrying requests to create messages when Twilio’s API responds with a 4xx HTTP status code.

• Invalid numbers in your contact lists (e.g., error codes 21211, 21614, or 21610)

• Other specific error codes that you can review in our error dictionary with potential causes and solutions.

The Certificate Manager for Link Shortening is a feature designed to streamline certificate management tasks for users by delegating them to Twilio. By opting in, you can entrust Twilio with tasks such as requesting SSL certificates and handling subsequent certificate renewals to prevent any interruptions to HTTP traffic. Certificates are issued by LetsEncrypt, a widely used and trusted certificate authority. 

To further simplify onboarding and certificate management, you can also validate your DNS status independently, confirming successful domain and certificate setup.

Read our documentation to learn more about the feature. During Private Beta, this feature is gated behind an account flag. To request enablement of this feature, please fill out this form.

Click Tracking Refinement for Link Shortening is a feature designed to help you gain a full understanding of your users’ engagement from the moment that you send a message all the way down to the individual click. For background, Apple’s and Google’s messaging applications support both automatic link previews (aka bot previews) as well as ‘Tap to load’ link preview functionality, which may lead to confusion around what is considered a real ‘click’, thereby blurring engagement analytics as a result. Twilio’s Link Shortening feature now supports bot preview distinction from human-generated clicks in its click events. This provides you with a highly accurate representation of click through rate (CTR) metrics as well as 100% confidence in the validity of click tracking data.    

Read our documentation to learn more about the feature. During Private Beta, this feature is gated behind an account flag. To request enablement of this feature, please fill out this form.

Twilio is excited to announce the public beta launch of the Intelligent Discovery AI Assistant. This innovative Assistant enhances the Console UI by allowing users to interact with their messaging data using natural language. It offers comprehensive troubleshooting capabilities, provides personalized recommendations, and seamlessly connects to live support agents when necessary.

Twilio Messaging customers can now take advantage of our most advanced messaging traffic monitoring solution, Intelligent Alerts. With the use of anomaly detection models, Intelligent Alerts monitors messaging traffic in real-time looking for abnormal patterns in your error code volumes. Notifications can be configured within Messaging Intelligence pages.

The new Personalized recommendations will analyze your messaging traffic and provide actionable steps to enhance deliverability and performance based on common issues we observe in your messaging traffic. Personalized Recommendations are now available in Public Beta to all Twilio Messaging customers using the Intelligent Discovery AI Assistant in Messaging Insights. 

You can now search, filter, and sort Content Templates based on their language, the type, the date it was created, and the contents within the template!

 

Use these search and filter parameters to easily find and manage your templates. You can use these to quickly identify templates and their approval status using whatever filter is easiest for you prior to sending them out. You can also see what channels the templates are approved to be used for. 

These tools are available on our console UI experience for the Content Template Builder as well as the Content API. To learn more about how you can use these endpoints to manage your content, click here to see our docs.

Multi Sender ID provides Twilio customers with the capability to register multiple Alphanumeric Sender IDs under a single account within the same country. Before now, Twilio customers wanting to use this sender type in registration countries would have to create multiple accounts and manage them independently in order to have multiple active senders in the same country. With the launch of Multi Sender ID in GA, you can utilize the capabilities and reach that comes with using Alphanumeric Sender IDs in a single account - available in over 185 countries globally.

Twilio has enhanced the Console UI to improve end-user usability by adding visibility of phone numbers associated with A2P registrations directly on the Campaign details page. This update introduces a new table that lists all phone numbers linked to a specific Campaign, making it easier to manage and review your numbers.

As an example, you can navigate to this page from Console UI -> Messaging -> Regulatory Compliance -> Campaigns -> Click on the campaign.

Visit our Twilio Docs for more information on A2P 10DLC. For details on confirming A2P registration, see our Support article.