Product changelog and announcements

We are thrilled to announce the ability to edit and retry A2P 10DLC Campaign registrations in Twilio Console. With this update, failed campaign registrations can be edited and resubmitted directly from Console. Additionally, this release introduces new fields for campaign registrations to provide more comprehensive campaign details ensuring the registrations meet compliance standards.

 

For more information on how to edit and retry Campaign submissions and understand the new fields in campaign registrations, please visit our detailed guide at: Troubleshooting and Rectifying A2P Campaigns.

For more general information about the A2P 10DLC product, please visit the Twilio website. 

We are extending an invitation to Twilio Messaging customers to experience advanced capabilities for monitoring their messaging traffic. Our new Intelligent Alerts product monitors for anomalies in outbound messaging traffic in real-time using predictive artificial intelligence. Alerts are categorized to help prioritize events based on their impact on your business. Customers can configure notifications and review prior alerts on the Twilio Console.

Starting February 12th, 2024, we are improving visibility of inbound messages by including redacted One Time Passcode (OTP) messages. Twilio does not generally allow receiving inbound OTP messages on Twilio numbers. This prevents abuse of Twilio numbers. Previously, these inbound messages were filtered before being processed onto your Twilio account. In order to provide better visibility for all inbound traffic, Twilio will allow you to see these messages, but will be redacting the passcode itself and setting a failed status with error code 30038.

Starting February 13th, 2024, as part of out messaging error visibility improvements, we will be rolling out improvements to our console error logs. We are enhancing error coverage to include outbound messaging errors which previously weren't available in the console error logs. Previously, these errors were only accessible through the API, messaging logs and insights, and via message status callbacks. This visibility improvement empowers efficient troubleshooting and full operational transparency and doesn't indicate a decrease in message delivery success.

Learn more about upcoming messaging error visibility improvements.

RCS is an enhancement over SMS, delivering messages over Wi-Fi and cellular with higher encryption security and lower latency, to the default SMS messaging app on Android, Messages by Google. RCS only works on compatible devices and a limited set of countries.

In a gradual rollout starting February 16th, 2024, Twilio Verify will automatically upgrade delivery of Verify OTP messages via RCS instead of SMS whenever possible; and if it exhibits the same or better performance. See Verify RCS to learn more.

Effective January 31, 2024, messages sent from toll-free numbers pending verification will be blocked. Only fully verified toll-free phone numbers will be eligible to send messages. 

Blocked messages will return Error 30032 (any message sent from a restricted or pending TFPN) or Error 30007 (if spam/unwanted on a verified TFPN), and are subject to messaging fees.

These verification efforts, along with increased message filtering, help Twilio combat spam and create a trusted messaging ecosystem for you and your customers.

You may use our Twilio Console or API options to submit toll-free phone numbers for verification.

For more information, please check out our guide Toll-Free Message Verification for US/Canada.

The United Kingdom (UK) regulators are enforcing new Know Your Customer (KYC) requirements and guidelines for UK long codes. Twilio will collect KYC information through Regulatory Compliance (RC) bundles either in Console or through our API.

We previously announced that the Notify product would end of life (EOL) on April 25, 2024. Notify will now EOL on December 31, 2025, in order for Twilio to provide an alternative solution for the current Notify product. Note that this EOL doesn’t affect other push notification use cases powered through other Twilio products such as Verify, Voice, Conversations or Engage.

We will update you via our Twilio Blog as soon as we have an alternative solution for the current Notify product. We have also prepared a migration guide and recommend reaching out to our support team with any questions.

The Compliance Embeddable is a React application you can i-frame into your existing web portal / application so you can collect business information directly from your end customers via self-service

Twilio is committed to streamlining the A2P 10DLC campaign registration process and providing transparent feedback on issues that might arise during registration. To enhance this experience, we are rolling out three new error codes that will convey more specific reasons for registration setbacks, enabling you to quickly address and resolve these issues.

New Error Codes:

• Error 30907: Encountered when there is a validation issue with the website URL provided.
• Error 30908: Returned when a Campaign registration lacks a compliant privacy policy.
• Error 30909: Issued for unverifiable Calls to Action (CTA) within the Campaign registration.

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