Product changelog and announcements

A faster, more reliable, and user-friendly way to port US local numbers now available in Public Beta. This does not impact the previous experience "Port a Number" which can continue to be used.

Starting September 30, 2025, customers will have the option to add Business Registration Numbers (BRNs), like Employer Identification Numbers (EINs), when they set up new Toll-Free verifications.

This update helps Twilio keep messaging safe, trusted, and reliable for everyone. For now, adding a BRN to new Toll-Free verifications is optional, but we’re giving early notice so you (and your customers) can get a head start on gathering the right info. By January 2026, a BRN will be required for all new Toll-Free verifications, so it’s a good idea to start preparing now 

If you ever run into trouble submitting your Toll-Free Verification with a BRN, we’ve got your back. Check out our New Policy API Onboarding documentation to help you with error code details and step-by-step guidance to make fixes as painless as possible.

We're excited to announce that we have made updates to the existing Compliance Report to now include Toll-Free & Regulatory Compliance Information.  Compliance information from all 3 programs (A2P, Toll-Free & Regulatory Bundles) can be downloaded from one singular report on demand and can be accessed on the download page located on Twilio's Console.

Introducing the Regulatory Compliance API Private Beta

We're launching the Regulatory Compliance API Private Beta, aimed at improving the Twilio compliance onboarding API experience.  This Private Beta is opt-in, and we're inviting interested customers to express their interest. 

Capabilities of the Regulatory Compliance API Private Beta include:

• Fewer Calls to Create Bundles: The new API (v3) simplifies the process of creating Regulatory Compliance Bundles by reducing the number of requests needed. Unlike the v2 API, which requires multiple steps per requirement (ex: Authorized Individual, a Business Address, and a Business Name), the new API consolidates these into a single request. With more complex registrations, the benefits are greater.

• Improved Error Codes: Errors are now surfaced in the API and error dictionary allowing for a more programmatic approach to error handling and less time troubleshooting. 

• Single Call to Fetch Bundle Details: Getting bundle details is simplified into a single request.

**Important Note:  Private Beta access is limited and the Twilio Product team will reach out to interested customers regarding access. More information is available here to learn more about Twilio’s general Beta Guides.

Easily verify if you can port-in your desired US local phone numbers to bring Voice and Messaging capabilities from your current carrier to Twilio.

The new area code overlays below will be introduced in select regions between April and May 2025. While Twilio doesn’t control these rollouts, we’re here to keep you in the loop.

What You Need to Know:

• These overlays will introduce new area codes in regions where existing ones are running out of numbers.

• Twilio may not have numbers available in every affected region.
  
  

The Compliance Embeddable is a white-label React component designed to seamlessly integrate into an ISV's web application as an iframe. This product enables ISVs to securely collect compliance information from their customers and send it directly to Twilio, streamlining compliance and shortening customer’s time-to-market. For ISVs, the Compliance Embeddable serves as a great alternative to manually collecting information from customers, and requires less development work compared to integrating with the Twilio Toll-Free Verification APIs and building their own UI.

The Compliance Embeddable is offered for free and is now available in Public Beta. Please follow the instructions in Twilio Docs to get started.

UPDATE: This change is anticipated to be made on January 6th, 2025
___________________________
To improve the experience for purchasing long codes in the United Kingdom, we have added more digital verification capabilities to vet business registration information. 

Improved digital verification capabilities allow the following improvements to the Regulatory Compliance Policies for the United Kingdom:

- Documents are no longer required for Businesses that are not registered in the UK Companies House. Previously, documents were required when users selected “Other” or non-UK registration authorities such as EIN for US based companies. 

- Emergency Address is no longer required during RC Bundle creation. However, users placing outbound calls must still add their emergency address SID to their Phone Number(s) as part of Phone Number configuration. 

While the Regulation Resource API response will reflect these changes in requirements, for API integrations leveraging the v2 Regulatory Compliance API, documents and Emergency Addresses will still be accepted and can be used to assist verification.

This set of APIs will help you automate the Porting process to bring your numbers from your current carrier to Twilio

We're excited to announce the new Bundle Clone API, allowing developers to quickly duplicate approved regulatory bundles between accounts without the need to be re-approved.

With the Bundle Clone resource, developers can reuse compliance information across Twilio accounts. The resource creates a copy of a twilio-approved regulatory bundle against another account within the same organization. The new regulatory bundle is automatically set to the twilio-approved status, enabling you to start provisioning phone numbers in the new account immediately.

This is particularly useful for ISV customers that want to more quickly assign numbers to themselves, or customers that want to move resources between their accounts.