## Why Phone Number Format Decides Whether a Text Arrives An SMS campaign can have the right audience, the right offer, and the right send time, and still fail on something as small as a missing country code. A number saved as `07700 900123` means one thing to a person in London and nothing at all to an SMS gateway that has no idea which country the contact lives in.
A number saved as `0049 30 1234567` carries a dialing prefix that only makes sense when someone is calling from inside a particular network. A number saved as `+44 (0) 7700 900123` mixes an international prefix with a domestic trunk digit that should never be sent. People are very good at reading these numbers. Messaging systems are not.
Providers and carriers route texts by country code and national number, so anything the system has to guess about is a chance for a failed message, a text routed to the wrong country, or a duplicate contact that gets two copies of the same offer. The standard that removes the guesswork is E.164, the international numbering format defined by the ITU.
This guide explains what E.164 looks like, why local formats break bulk sending, how trunk prefixes and international dialing prefixes cause most conversion mistakes, how to handle lists that mix countries, and a practical workflow for normalizing numbers before your first send. ## What E.164 Actually Is E.164 is the ITU-T recommendation that defines the international public telephone numbering plan.
In practice, when messaging teams say "E.164 format" they mean a number written like this: `+447700900123` That string has three parts: - A leading plus sign, which stands in for whatever international dialing prefix the caller would use. - A country code of one to three digits, such as `1` for the North American Numbering Plan, `44` for the United Kingdom, `49` for Germany, or `972` for Israel.
- The national significant number, which is the subscriber number without any domestic trunk prefix. There are no spaces, dashes, parentheses, or dots, and the full number, country code included, is at most 15 digits long. Every number in the world that can receive a call or text has one E.164 form, which is why it works so well as a storage format.
Two people can write the same number ten different ways, but if both versions are converted correctly, they produce the same E.164 string. ### Display format and storage format are different jobs E.164 is a storage and transmission format, not a display format. Nobody expects a customer to type `+447700900123` into a signup form or read it on an invoice.
A good system accepts the way people naturally write numbers, converts them to E.164 for storage and sending, and formats them back into a readable national or international style when a human needs to see them. Keeping those jobs separate avoids a common trap: storing whatever the user typed and trying to clean it up at send time.
By then the context that made the number understandable, such as the country of the signup form, the user's billing address, or the sales region, may already be lost. ## Why Local Formats Break Bulk SMS Local formats are written for a caller who already knows where they are. A bulk sender does not have that context for every row in a spreadsheet, so local formats create several distinct problems.
### The country is missing A number like `052-123-4567` is a valid Israeli mobile number when dialed in Israel. In a list that also contains customers from the UK, Germany, and the United States, nothing in the string says it is Israeli.
A system that assumes the wrong default country will either reject it, convert it to a number that does not exist, or in the worst case convert it to a real number belonging to someone else. ### Trunk prefixes get kept by mistake Many countries use a domestic trunk prefix, most often `0`, when dialing within the country. The UK mobile number `07700 900123` becomes `+44 7700 900123` internationally, and the leading `0` disappears.
If a conversion simply glues `+44` to the front of the local string, the result is `+4407700900123`, which is not a valid UK number. ### International dialing prefixes look like digits When people write numbers for international callers, they sometimes include the exit code of their own country instead of a plus sign. In much of Europe and in Israel the exit code is `00`, so a German number might arrive as `0049301234567`.
In the United States and Canada the exit code is `011`, so the same number could arrive as `011 49 30 1234567`. Unless the exit code is recognized and stripped, the resulting number is wrong. ### Formatting characters and notes sneak in Spreadsheets collect everything people type: spaces, dashes, dots, parentheses, `ext. 204`, `(mobile)`, `call after 5`, or two numbers in one cell separated by a slash. Some of these can be cleaned safely.
Others, like extensions or multiple numbers, mean the row needs a decision before it can be sent. ### Duplicates hide behind different formats `+44 7700 900123`, `07700900123`, and `0044 7700 900123` are the same phone. Without normalization they look like three contacts. That inflates list counts, can send the same message three times to one person, and makes opt-out handling unreliable, because a STOP recorded against one version may not match the others.
## The Trunk Prefix Problem in Detail The trunk prefix causes more conversion errors than anything else, so it is worth understanding how it varies.
### The common case: drop the leading zero In the UK, Germany, France, Israel, Australia, and many other countries, a domestic number starts with `0`, and that `0` is removed in the international form: | Written locally | Country | E.164 | | --- | --- | --- | | `07700 900123` | United Kingdom | `+447700900123` | | `030 1234567` | Germany | `+49301234567` | | `06 12 34 56 78` | France |
`+33612345678` | | `052-123-4567` | Israel | `+972521234567` | The examples above are illustrative formats, not real subscriber numbers. ### The exception: countries that keep the zero Not every country follows that rule. Italy is the best-known example. Italian landline numbers begin with `0`, and that `0` stays in the international form, so a Rome number written `06 1234 5678` becomes `+39 06 1234 5678`.
A blanket "strip the leading zero" rule would break every Italian landline in your list. ### North America works differently again The North American Numbering Plan, which covers the United States, Canada, and several Caribbean countries, uses the country code `1`. Domestically, people often dial a leading `1` before the area code for long-distance calls. A number written `1 (415) 555-0123` therefore already contains its country code, while `(415) 555-0123` does not.
A converter that adds `+1` to the first version produces an invalid number. ### Some mobile numbers change shape internationally A few numbering plans change more than one digit between local and international form. In Argentina, for example, mobile numbers written domestically with a `15` prefix are written internationally with a `9` after the country code and without the `15`. A generic rule cannot handle cases like this.
A maintained numbering library that knows each country's plan can. The lesson is simple: do not write your own string rules for trunk prefixes. Use a well-maintained phone number library that carries per-country metadata, keep it updated, and let it decide what to strip. ## Choosing the Right Default Country Conversion only works when the system knows which country a local number belongs to.
There are several good sources for that answer, in rough order of reliability: 1. **A number already in international form.** If a number begins with `+` or a recognized exit code followed by a valid country code, the country is already known, and that number should be preserved rather than reinterpreted. 2.
**The signup context.** A form on a country-specific site, a country selector next to the phone field, or a checkout with a billing country gives strong evidence for every number captured there. 3. **Account or CRM fields.** A country, region, or address field in the same row is usually a better signal than a global default. 4.
**List-level evidence.** If a list came from a single market and nearly every number that can be checked fits one national plan, that plan is a reasonable default for the rest. 5. **A single global default.** This is the weakest option and should only be used when the list truly comes from one country. When those signals disagree, or when a number is valid in more than one country's plan, treat the row as ambiguous.
It is better to set a small number of rows aside for review than to send a promotional text to a stranger because a guess happened to produce a valid-looking number. ### Mixed-country lists Lists from events, marketplaces, affiliates, and international ecommerce often mix countries. The cleanest approach is to split the list by country evidence first, then normalize each group with
Related Articles
Double opt-in filters out typos, bots, and signups in someone else's name. Learn when to use it for email and SMS and how to keep real signups.
Most email A/B tests crown winners that don't last. Learn how to test one variable at a time, pick a metric and guardrails before you send, size your sample, split your list
Invalid email addresses quietly tax every campaign. They waste sends, distort analytics, increase bounce rates, and can push mailbox providers to distrust...
Blended list metrics hide weak signup sources. Tag every entry point, score it on validation, bounces, complaints, and clicks, and fix or pause the ones that hurt.
Opted-in subscribers are only as safe as the proof behind them. Learn which consent fields to store for every email and SMS contact, how to capture them at each signup point
Bots, list bombing, and fake leads quietly poison email and SMS lists. Learn how to spot form abuse and block junk at capture with layered, low-friction checks.
Your suppression list protects deliverability, budget, and consent. Learn what belongs on it for email and SMS, how to record and match entries, and how to apply it on every send
Every year, 22.5% of email addresses become invalid. Learn how bounce management, suppression lists, proactive validation, and re-engagement campaigns keep your contact data clean
Explore SESender
SESender brings audience preparation, contact validation, sender and provider controls, scheduling, delivery tracking, and campaign reporting into one workspace. Review the current product and pricing information before deciding whether the platform fits your messaging workflow.
Explore the platform or review pricing.