Twilio Changelog

We are excited to announce the release of new NPA-NXX phone overlays scheduled for Q4 2024, with all overlays available by December 31, 2024. Twilio does not control these overlays or the deadlines. Twilio is making this information available solely for our customers’ convenience. Twilio may not have available phone numbers in every region where these overlays are released:

Multi Sender ID provides Twilio customers with the capability to register multiple Alphanumeric Sender IDs under a single account within the same country. Before now, Twilio customers wanting to use this sender type in registration countries would have to create multiple accounts and manage them independently in order to have multiple active senders in the same country. With the launch of Multi Sender ID in GA, you can utilize the capabilities and reach that comes with using Alphanumeric Sender IDs in a single account - available in over 185 countries globally.

Twilio releases end-user usability improvements on the Phone Number detail(configuration) page.
As an example, you can navigate to this page from Console UI -> Phone Numbers -> Active Phone Numbers -> Click on the phone number.

The Console UI improvement introduces two new sections/tabs for faster navigation.

1) Properties tab: Contains details about the phone number.
Such as: Friendly Name, Number type, Location, Capabilities. It allows you to edit the friendly name from here and also release the phone number from this tab.

2) Configure tab: Enables configurations related to: routing updates, configuration updates, integrations with messaging services, add/remove emergency address.

No previous functionality has been removed and no action is required.

On May 3rd, 2022 responses to API requests for CSV representation of Incoming Phone Number and Outgoing Caller ID resources for both list and instance will change; specifically the order of the columns may be different.

The order of the columns in the CSV is not defined and may change when new fields are added to the API response. Your application design should be resilient to changes in the order of the columns in the CSV response.

See our docs for more information about how to leverage CSVs with Twilio.

Customers can now keep up with the latest Regulatory requirements by updating their Regulatory Bundles through Public API and Console using the new action required compliance information update experience. The new compliance information update workflow allows customers to continue provisioning new phone numbers for a specified amount of time while updating a Bundle Copy and submitting to Twilio for review.

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.