Product changelog and announcements

Error codes for campaign reviews are now available on the Console. With this latest update, customers can view the reason for campaign rejection with an error code and description directly within the Console and through the US App to Person (A2P) Campaign Resource.

For a detailed list of all error codes please visit Twilio Error and Warning Dictionary. To learn more about these error codes, please read the Twilio support article.

Twilio’s self-service Toll-Free verification tooling is now in Public Beta. Customers who are looking to submit toll-free phone numbers for verification can now do so directly within Messaging Compliance API or Twilio Console without going through Support or Sales.

With Toll-Free verification tooling, you can:

• Submit a new US or Canadian toll-free phone number for verification
• Utilize customer profiles for a Toll-Free verification that were created in other compliance programs like A2P 10DLC, STIR/SHAKEN, etc
• Get a list of toll-free verification records, including status and rejection reason (if rejected). Historical verifications submitted manually through CSV process are available for most toll-free numbers.
• Re-submit a rejected verification (if rejection type is allowed to resubmit)
• Subscribe to Event Stream’s webhook for toll-free verification events

Learn more about Toll-Free verification with Twilio docs:

• Messaging Compliance API documentation
• Toll-Free Verification within Twilio Console
• Toll-Free Message Verification overview
• Required Information for Toll-Free verification
• Toll-Free Verification for ISVs
• Information and best practices for using Toll-Free SMS and MMS in the US and Canada
• Forbidden Message Categories for SMS and MMS in the US and Canada
• What are the differences between long codes (A2P 10DLC), short codes, and Toll-Free numbers for messaging to US/Canada?”

Please register your +1 10DLC numbers as soon as possible to avoid impact to your traffic

Requiring HTTP authentication for stored media is now considered industry best practice, and it will be enforced by Twilio. Effective July 31, 2023, Twilio will enforce HTTP Basic Authentication for Programmable Voice and Programmable Messaging Media.

Twilio has released error codes for campaign review process. With this latest update, customers can easily identify the reason for campaign rejection with an error code and description through US App to Person (A2P) Campaign Resource. For a detailed list of all error codes please visit Twilio Error and Warning Dictionary.

To learn more about these error codes, please read the Twilio support article. Additionally, be sure to check out our code samples and API guidelines in Twilio docs. We hope that these updates will help make your messaging experience with Twilio even smoother!

We previously announced that the Notify product would end of life (EOL) on October 23, 2023. We’re now extending the EOL deadline; the new EOL date for Twilio Notify is April 25, 2024. After this date, any requests made to the Notify API will fail.

We hope this extension will provide you with enough time to transition to alternative options. To assist you in this process, we have prepared a migration guide and recommend reaching out to our support team with any questions.

Twilio now supports a Sole Proprietor registration option for US 10DLC messages via the Console and APIs.

When users reply to a specific WhatsApp message, Twilio now passes additional context to the WhatsApp Sender’s webhook URL. The OriginalRepliedMessageSender and OriginalRepliedMessageSid parameters will include information about the previous message the user replied to. If you need the content of the original message, you can use this API to fetch the Message Resource.

Note that only message replies to messages sent within the last 7 days will contain this additional context. Incoming message replies to messages sent over 7 days ago will still be delivered, but will lack this additional information.

For more information about this and other inbound message parameters, please refer to this page.

Twilio is making changes to Geo-Permissions in the Twilio Console to better differentiate traffic being sent to both Israel and Palestine. Palestine, which previously was only +970 will now include Palestinian networks operating with +972 prefixes. If you enabled geo permissions for Israel and/or Palestine, then we have updated your selection based on the corrected prefixes.  Israel will no longer send traffic to +97256 and +97259 since these two prefixes are associated with Palestinian Jawwal and Wataniya cellular communication company.

If needed, you can enable or disable SMS Geo Permissions to any country at any time in Twilio Console by following the steps in this Support Article.