Twilio Changelog

Upcoming EIN Requirement for US Short Code Campaigns

Starting October 15, 2024, the CTIA and US Short Code Registry will implement an enhanced vetting process for all new US Short Code campaigns. As part of this process, businesses will be required to submit a valid Employer Identification Number (EIN) during the onboarding phase. This change is designed to increase trust and security across the messaging ecosystem by ensuring a direct relationship between the brand and the short code campaign.

Additionally, starting January 15, 2025, the EIN requirement will apply to all short code renewals. Failure to provide the EIN within 60 days of renewal could result in short code suspension until the required information is submitted.

Key Dates to Note:

• October 15, 2024: EIN submission required for all new short code campaigns.

• January 15, 2025: EIN submission required for all short code renewals.

What You Need to Do:

• For new short code campaigns: Ensure you have a valid EIN ready to submit during onboarding after October 15, 2024.

• For existing short codes: Be prepared to provide your EIN when your short code comes up for renewal starting January 15, 2025.

For further details, please review the official CTIA guidelines and Twilio Short Code Onboarding Requirements.

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.