Twilio Changelog

Customers associating emergency addresses with their phone numbers don’t have to set EmergencyStatus to Active in the IncomingPhoneNumbers resource of the Phone Numbers API. Attempting to set the EmergencyStatus to Active or Inactive will be ignored, and will not have any effect on the enablement or disablement of emergency calling.

When fetching an Incoming Phone Number, a new parameter EmergencyAddressStatus is returned with the registration status of the emergency address with the values registered, unregistered, pending-registration, pending-unregistration, registration-failure, and unregistration-failure.

Voice customers with US and Canada phone numbers should provide their accurate physical address to comply with the FCC and CRTC E911 rules. If you make a 911 call from a US or Canada phone number without a registered emergency address, Twilio will pass through a $75 fee per 911 call for the call to be delivered to a national emergency location center where a trained agent will ask for the emergency location.

For additional information, check our SIP Trunking and Programmable Voice documentation.

We have updated the experience when searching for and buying numbers in Console. In addition to refreshing the overall look at feel, we've streamlined the filters available when searching and made updates to provide more helpful guidance when numbers are not available.

You can now manage a Phone Number’s Messaging Service assignment from the Phone Number’s configuration page in Console.

If a Messaging Service assignment is important to the success of your Phone Numbers’ messaging use-case (such as A2P messaging with US local 10-digit long codes) and if the Messaging Service is configured to defer SMS handling to the Phone Numbers' configuration: you can now assign a Messaging Service while also configuring the Phone Number to handle messaging with Flex, Studio, Functions or TwiML App.

You can determine whether the Messaging Service is handling or deferring message handling with the Phone Number from the Phone Numbers’ instance page in Console.

Twilio is releasing Deletable Regulatory Objects to make regulatory information management easier. This new functionality allows customers to delete unwanted Regulatory Bundles, Supporting Documents, and End-Users from the Twilio web Console and the Public API.

Policy updated as of September 28, 2020

Twilio anticipates significant spikes in provisioning of US-based phone numbers as we approach November's 2020 U.S. election. Due to the finite capacity of the U.S. messaging ecosystem, we're implementing a Heightened Awareness Period (HAP) from October 2, 2020until November 4, 2020.

Our goal for this short-term policy is to ensure that all customers have fair access to a secure and reliable network.During this Heightened Awareness Period, the following limitations will apply:

• A maximum of 1,000,000 additional 10-digit long code phone numbers can be added to customers' existing accounts within the +1 country code. These numbers are available on a first-come, first-served basis, with inventory being added regularly.

For more information see this FAQ.

Twilio is releasing RC Reusable Objects to allow customers to reuse previously uploaded identity and supporting documentation. This enhancement will reduce the time they spend creating Regulatory Bundles and makes Phone Number provisioning via the Twilio Console a more efficient process.

Twilio’s Evaluations API resource is in public beta so you can receive transparent feedback to understand the evaluation and failure reason(s) of your Regulatory Bundle via API.

Resources:

• Evaluations Public API Resource Reference
• Evaluations Public API Blog Post

The Regulations API is moving to Public Beta. The Regulations API resource allows users to programmatically fetch the Regulations for a given phone number’s country, type, and the end-user type. The Regulations API is in sync with the Regulatory Guidelines webpage and is continually updated.

For additional details:

• Regulations Public API
• Regulatory Guidelines
• Getting Started: Creating a new Regulatory Bundle

Provisioning new phone numbers with identity regulations through the Twilio /IncomingPhoneNumbers API now requires an approved BundleSid. End-users will be required to include the proper documentation for regulated phone numbers, which are most phone numbers outside the US and Canada. API calls to provision regulated phone numbers that do not include a compliant BundleSID that is valid for the phone number will fail with error code 21649.

For additional details:

• Blog post on this change
• Phone Number Regulatory FAQ

The new v2 Regulatory Compliance suite, backed by programmatic public APIs and a Console workflow leveraging the intelligence of the Regulatory Rules Engine.

For additional details:

Regulatory Compliance APIs

Getting Started: using the Public API to create new Bundles

Console: Regulatory Compliance Report Getting Started

Getting Started: How to use the Compliance Report