An icon of a right arrow Back to all releases

Programmable Messaging | Aug. 20, 2024

Twilio Will Bill For Failed Messages Starting September 30, 2024

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

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 (Error code 30450).

  • 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:

Messaging GA