Store international phone numbers in E.164 format, then display them in the local format your users expect. That is the safest rule for databases, CRMs, SMS tools, payment systems, and customer support software. E.164 numbers use a leading plus sign, a country code, and a national number, with a maximum of 15 digits under the ITU recommendation [source: ITU].
TLDR: Use E.164 for storage and system-to-system communication, such as +14155552671. Use local dialing formats for human display, such as (415) 555-2671 in the United States or 020 7946 0018 in the United Kingdom. A sales team importing 50,000 contacts can easily lose hundreds of calls or SMS messages if country codes and trunk prefixes are mixed. In one common case, standardizing numbers before an SMS campaign cuts failed sends from about 7% to under 2%.
What E.164 Format Means
E.164 is the international phone number format used by telecom systems. It removes local guessing. A properly written E.164 number has three parts:
- Plus sign: +
- Country calling code: for example, 1 for the United States and Canada, 44 for the United Kingdom, 49 for Germany
- National significant number: the remaining number used inside that country
For example, a New York number may appear locally as (212) 555-0198. In E.164, it becomes +12125550198. A London number written as 020 7946 0018 becomes +442079460018. The leading zero is dropped because it is a local trunk prefix, not part of the international number.
Image not found in postmetaWhy Local Dialing Formats Still Matter
Local formats are not wrong. They are simply made for people, not databases. They reflect how residents expect to read and dial numbers in their own country.
For example:
- United States: (415) 555-2671
- United Kingdom: 020 7946 0018
- Germany: 030 123456
- France: 01 42 68 53 00
These formats often include spaces, parentheses, hyphens, or leading zeros. That makes them easier to scan. Yet those same marks can break imports, search, SMS delivery, and duplicate matching. It drives me crazy that some contact tools accept 020 7946 0018 in one field, reject it in another, then silently export it without the country code. That is how clean lists become messy again.
E.164 vs Local Format: The Practical Difference
The difference is not cosmetic. It affects whether a system can reach the person.
| Use case | Best format | Reason |
|---|---|---|
| Database storage | E.164 | Consistent, unique, and easier to validate |
| SMS delivery | E.164 | Messaging gateways expect international routing |
| Click to call links | E.164 | Works more reliably across devices |
| Website display | Local format | Easier for local customers to read |
| Printed material | Local or international | Depends on the audience |
If your audience is domestic, local display is fine. If your audience is international, show the full international version. A hotel in Paris should not list only 01 42 68 53 00 for global guests. It should show +33 1 42 68 53 00.
The Role of the Plus Sign
The plus sign is not decoration. It tells the phone network or software to use the correct international access method. From the United States, users often dial 011 before an international number. From many European countries, they may dial 00. The plus sign replaces those prefixes.
So +442079460018 means “call the United Kingdom, then this national number.” It does not require the caller to know whether to start with 011, 00, or another international access code.
Common Mistakes When Writing International Numbers
Most errors come from mixing local habits with global storage. Watch for these issues:
- Keeping the trunk zero: +44 020 7946 0018 is wrong. Use +44 20 7946 0018.
- Dropping the country code: 4155552671 may work locally, but not globally.
- Saving punctuation as data: spaces and brackets are fine for display, but not needed for storage.
- Assuming all countries use fixed lengths: numbering plans vary. Some countries have variable length numbers.
- Confusing country code with area code: in +1 212 555 0198, 1 is the country code and 212 is the area code.
How to Format Numbers in Forms and Databases
A good phone number field should separate user comfort from technical storage. Let users enter a familiar number, but normalize it before saving.
- Ask for the country first. A country selector removes much of the guesswork.
- Accept common local formatting. Do not punish users for spaces or brackets.
- Validate against the selected country. Use a trusted phone number library, such as Google’s libphonenumber [source: Google].
- Store the normalized E.164 value. Save +14155552671, not (415) 555-2671.
- Display the local version when useful. Convert it back for readability.
This approach prevents failed campaigns and duplicate records. It also helps customer service teams search consistently. If one agent enters +49 30 123456 and another enters 030 123456, your CRM may treat them as different people unless normalization runs in the background.
How to Write Numbers on Websites and Business Materials
For websites, the right choice depends on who will call.
- Local business, local customers: show the local format, such as (03) 9123 4567.
- International business: show the international format, such as +61 3 9123 4567.
- Support teams: include both if space allows.
For clickable links, use the tel: scheme with E.164. Example:
<a href="tel:+14155552671">+1 415 555 2671</a>
The visible text can include spaces for readability. The link target should stay clean. Expect to waste time on testing if you use local-only links on a global site. Some phones handle them well. Others do not.
Recommended Standard
The most reliable policy is simple:
- Store: E.164, with plus sign and country code
- Transmit: E.164 for APIs, SMS, voice platforms, and integrations
- Display: local format for local users, international format for global users
- Validate: by country, not by one universal length rule
E.164 is the system format. Local dialing is the human format. Treat them as two views of the same number. Once that rule is clear, phone data becomes easier to store, search, dial, and trust.
