Formatting phone numbers
Formatting phone numbers means converting a messy column of numbers into one consistent, machine-readable shape — usually the E.164 international standard (a plus sign, country code, then the national number). Sigmera standardizes a phone column entirely in your browser: you set a default region, preview the result, and download a clean file with nothing uploaded to a server.
Last updated: June 2026
What phone-number formatting is
Phone-number formatting is the act of taking the many ways humans write a number — “(415) 555-1234”, “415.555.1234”, “+1 415 555 1234”, “00 1 415 555 1234” — and normalizing them to a single canonical form. The de facto target is E.164, the International Telecommunication Union standard: +[country code][national number], digits only, no separators, 15 digits maximum. A number stored in E.164 is unambiguous anywhere in the world, which is exactly what machines downstream need.
Why it matters
Inconsistent phone formatting is one of the most common reasons a CRM import fails or an SMS campaign under-delivers. Messaging platforms and calling APIs — Twilio, MessageBird, HubSpot, Salesforce — store numbers in E.164 internally and either reject or silently drop numbers they cannot parse. A single column where some rows have a country code and others do not will route some messages and lose the rest, with no obvious error. Inconsistent formatting also defeats deduplication: “+14155551234” and “(415) 555-1234” are the same person but look like two records, so you double-count and double-contact them. Normalizing the column once, up front, prevents all of that.
The edge cases that trip people up
- Missing country codes. A bare national number has no country, so it cannot become valid E.164 without an assumption. The fix is a sensible default region for your list, plus a flag on anything that does not fit.
- Leading zeros and trunk prefixes. Many countries write national numbers with a leading 0 (a “trunk prefix”) that must be dropped when the international country code is added — “020 7183 8750” in the UK becomes “+44 20 7183 8750”, not “+44 020…”.
- The 00 vs + prefix. “00” is the international dialing prefix in much of the world and means the same thing as “+”, so “0044…” should normalize to “+44…”.
- Extensions and junk characters. “x123” extensions, letters spelling a vanity number, and stray text in the cell all have to be stripped or set aside before a number can be validated.
- Numbers stored as numbers. When a spreadsheet treats a phone column as numeric, leading zeros and the plus sign vanish, silently corrupting the data. Phone numbers should always be text.
How to approach it
Decide your target format (almost always E.164) and a default region for numbers that lack a country code. Strip everything that is not a digit or a leading plus, drop trunk prefixes when adding the country code, and convert any “00” prefix to “+”. Then validate length against the region — too few or too many digits means the row needs review rather than a silent guess. Finally, preview the result and export. Because Sigmera does this in the browser, the phone numbers — which are personal data under GDPR — never leave your device, satisfying the data-minimization principle of GDPR Article 5.
In this topic
The tool, guides, and real-world use cases for standardizing a phone column.
Frequently asked questions
- What is the E.164 phone number format?
- E.164 is the ITU international standard for phone numbers. A valid E.164 number is a plus sign followed by the country code and the national number, with no spaces, dashes, or parentheses, and a maximum of 15 digits — for example +14155551234 or +442071838750. Because it is unambiguous and globally unique, it is the format most CRMs, SMS gateways, and calling APIs expect.
- Why do CRMs and SMS tools require E.164?
- An SMS gateway or VoIP system has to route a message or call internationally without guessing the caller's country. Local formats like (415) 555-1234 are ambiguous outside their own country, so platforms such as Twilio, HubSpot, and Salesforce normalize to E.164 internally and reject or silently drop numbers they cannot parse. Storing numbers in E.164 from the start prevents failed sends and duplicate contacts.
- How do I know the country if a number has no code?
- You can't, reliably — a bare '5551234' could belong to any country. The safe approach is to set a default region for numbers that arrive without a country code, based on where your list comes from, and to flag numbers that are too short or too long to be valid for that region. Sigmera lets you pick a default region and shows you which rows could not be confidently formatted.
- Does formatting phone numbers in the browser upload my data?
- No. The formatter runs entirely in your browser using client-side JavaScript, so the file never leaves your device and nothing is sent to a server. This keeps customer phone numbers — which are personal data under GDPR — private by design, satisfying the data-minimization principle of GDPR Article 5.