How to Prepare Your Phone List for Twilio Campaigns

Why Twilio Is Unforgiving About Phone Data Quality

Twilio is the backbone of SMS marketing for thousands of businesses, from startups sending appointment reminders to enterprises running multi-million message campaigns. But Twilio's API is strict about what it accepts. Send a message to a number that is not in E.164 format and the API returns an error. Send to an invalid number and you still get charged. Send too many messages that fail and Twilio may suspend your account for poor list hygiene.

The fundamental problem is that most phone lists were not built with Twilio in mind. Contact data comes from CRM exports, web forms, trade shows, and purchased lists. Each source formats phone numbers differently, mixes mobile and landline numbers indiscriminately, and contains its own unique set of data quality issues. Importing this raw data into Twilio without preparation is a recipe for failed campaigns and wasted money.

Understanding Twilio's requirements before you import saves time, money, and frustration. The good news is that with the right preparation workflow, you can get any phone list Twilio-ready in minutes rather than hours.

Twilio's Phone Number Requirements

E.164 Format Is Mandatory

Twilio requires all phone numbers in E.164 format. This is not optional and there is no fallback parsing. E.164 format consists of a plus sign, the country code, and the subscriber number with no spaces, dashes, parentheses, or other characters. For United States numbers, this means "+1" followed by the 10-digit number. For UK numbers, it is "+44" followed by the subscriber number without the leading zero.

If your list contains numbers without country codes, you need to determine the correct country code for each number before formatting. Assuming all numbers are US-based is a common mistake that causes international numbers to be formatted incorrectly. Our detailed guide on converting phone numbers to E.164 format covers edge cases for multi-country lists.

Valid Carrier and Line Type

Twilio will attempt to deliver SMS to any number you provide, but it cannot deliver to landlines. You will be charged for the attempt even though the message never arrives. Twilio's Messaging Service can be configured to check line type before sending, but this adds a lookup charge to every message. It is far more cost-effective to remove landlines from your list before importing.

Messaging Service Configuration

Twilio's Messaging Services provide intelligent sender selection, compliance checks, and delivery optimization. When using a Messaging Service, your phone data quality becomes even more critical because the service will flag or reject numbers that would harm deliverability. Setting up a Messaging Service with proper compliance settings protects your account but makes dirty data more visible and more likely to cause import failures.

The 7 Most Common Errors When Importing to Twilio

1. Missing or Wrong Country Code

The number one error is phone numbers without a country code. "5551234567" is ambiguous because it could be a US number, a Mexican number, or match patterns in several other countries. Without the "+1" prefix, Twilio cannot route the message. Equally problematic is applying the wrong country code to international numbers.

2. Formatting Characters (Spaces, Dashes, Parentheses)

Human-readable formatting is the enemy of API compatibility. Spaces, dashes, parentheses, dots, and other separators must be stripped completely. A number formatted as "(555) 123-4567" contains seven characters that will cause Twilio's API to reject it. Even a single trailing space after an otherwise valid E.164 number will cause a failure.

3. Landline Numbers in SMS Lists

Approximately 30 percent of US phone numbers are landlines. If your contact list comes from a source that does not distinguish between mobile and landline (which is most sources), a significant portion of your list will be undeliverable for SMS. You pay for every attempt, and Twilio counts these failures against your delivery metrics.

4. Leading Zeros Stripped by Excel

This is a notorious issue. When you open a CSV containing phone numbers in Excel, it automatically interprets them as integers and strips leading zeros. A UK number like "07911123456" becomes "7911123456" which is then impossible to format correctly without knowing the original country. Countries with leading zeros in their national format, including the UK, Australia, France, and Germany, are particularly affected.

5. Extension Numbers Appended

Business phone numbers often include extensions: "555-123-4567 x200" or "5551234567,200". The extension portion needs to be stripped before formatting for Twilio, as extensions are meaningless for SMS delivery and will cause the number to be rejected.

6. Duplicate Numbers

Sending duplicate messages wastes money and annoys recipients. After format standardization, duplicates that were previously hidden by different formatting become visible. "555-123-4567" and "(555) 123-4567" are the same number, but they look different until both are converted to "+15551234567".

7. Test and Placeholder Numbers

Development teams often use placeholder numbers like "000-000-0000", "555-555-5555", or "123-456-7890" during testing. These frequently make it into production datasets through merged databases or incomplete cleanup. They are guaranteed failures that waste API calls.

Twilio Lookup API vs. Cleaning Beforehand: A Cost Comparison

Twilio offers a Lookup API that provides carrier information, line type, and validation for phone numbers. It is a powerful tool, but it comes at a cost: $0.005 per lookup for carrier information. This seems trivial until you scale it up.

The Lookup API is valuable for real-time validation of individual numbers, such as when a new contact submits a web form. But for batch processing an existing list, it is significantly more expensive than cleaning your data beforehand. A batch cleaning approach handles formatting, deduplication, and obvious invalid numbers without any per-lookup charge, and you only use the Lookup API for the remaining numbers that need carrier validation.

The optimal strategy is a two-stage approach: batch clean your list first to handle formatting, duplicates, and obviously invalid numbers, then use Twilio Lookup selectively for carrier type verification on the cleaned list. This combination minimizes cost while maximizing data quality.

Step-by-Step: Preparing Your Phone List for Twilio

Step 1: Export and Audit Your Current List

Export your phone list from your CRM or database as a CSV. Before any cleaning, audit the data by examining a sample of 100 records. Note the formats present, whether country codes are included, and the mix of mobile versus landline numbers if you can identify them. This audit tells you which cleaning steps you need and sets a baseline for measuring improvement.

Step 2: Strip All Formatting Characters

Remove every non-digit character from your phone numbers: spaces, dashes, parentheses, dots, plus signs (you will add the correct plus sign back later), and any other punctuation. Also strip extensions and any text that follows the base number. This gives you a raw digit string to work with.

Step 3: Apply Country Codes and Convert to E.164

With clean digit strings, apply the appropriate country code based on your data source or a country field in your dataset. For US/Canada numbers, prepend "+1" to 10-digit numbers. For 11-digit numbers already starting with "1", prepend just "+". Validate the resulting E.164 number against the expected length for each country code.

Step 4: Deduplicate

Now that all numbers are in the same format, run deduplication to find and remove repeated numbers. Decide on a merge strategy for duplicate contacts: keep the most recent record, the one with the most complete data, or merge fields from both. After dedup, your list contains only unique phone numbers.

Step 5: Remove Invalid and Non-SMS Numbers

Filter out numbers that are obviously invalid based on length (too short or too long for the country code), known test number ranges (555 area code for US), and numbers that fail E.164 structural validation. If budget allows, use Twilio Lookup on the remaining numbers to identify and remove landlines.

Step 6: Validate Against Suppression Lists

Cross-reference your cleaned list against your opt-out list, Do Not Call registry, and any previous bounce records from Twilio. Remove any matches. This is both a compliance requirement and a deliverability best practice. Twilio provides bounce and complaint data through their API that should feed back into your suppression list.

Step 7: Test with a Small Batch

Before sending your full campaign, test with a batch of 100 to 500 numbers from your cleaned list. Monitor delivery rates, error codes, and any Twilio warnings. A test batch with a 98 percent or higher delivery rate confirms your list is clean. If the test shows issues, investigate the failing numbers before scaling to the full list.

NoSheet's Twilio-Ready Phone Formatting

NoSheet collapses the entire preparation workflow into a single operation. Upload your phone list in any format, from any source, and NoSheet automatically handles E.164 conversion, character stripping, country code detection, deduplication, and invalid number flagging. The output is a clean CSV that Twilio's API will accept without errors.

For teams running recurring campaigns, NoSheet eliminates the repetitive manual work of cleaning phone data before every send. Import your list once, clean it, and export a Twilio-ready file in the exact CSV format that Twilio's API expects. No more wrestling with spreadsheet formulas, no more API errors from bad formatting, and no more charges for messages sent to invalid numbers.

For the complete guide to cleaning CSV data for Twilio, including Messaging Service configuration and campaign setup, see our Twilio CSV cleaning guide.