International country codes and national phone formats
Understand when a country selector is required, when an explicit + prefix wins, and why formatting is not reachability.
International phone data has two separate questions: what country context applies, and what output format does the destination need? E164Flow uses a country selector or mapped country column for national numbers, while an explicit international prefix takes priority.
How do I start this workflow?
Keep the source file, confirm the phone and country fields, and review the results before choosing the import layout.
- Use E.164 as a compact storage format for international lists.
- Use a local country only for national numbers that lack an international prefix.
- Keep the original value and validation status beside the generated value for review.
How does country context change a national phone number?
Country context tells the parser how to interpret a national input. An explicit international prefix already supplies that context and must not be replaced by an unrelated default.
| Input | Country context | E.164 output or decision |
|---|---|---|
| 020 7946 0018 | GB | +442079460018 |
| 041 123 456 | SI | +38641123456 |
| +39 02 3661 8300 | Explicit +39 | +390236618300 |
| +44 20 7946 0018 | Conflicting SI hint | Keep +44 and review the country mismatch |
The Italian example keeps the zero after the calling code. That is why a global rule such as remove every leading zero is unsafe. The examples illustrate formatting with the application's numbering metadata; they do not check whether those demonstration numbers currently receive calls or messages.
What is the difference between a calling code and a country field?
A calling code is part of an international phone number, such as +44. A country field supplies parsing context, such as GB, for a number that is written nationally.
Keep these two pieces of data distinct in a spreadsheet. A column containing country names or two-letter country codes is not another phone column. Map it as country context, and select the fields that actually contain telephone values separately. E164flow accepts supported names and aliases, including UK for GB and Slovenia for SI.
An ambiguous country name still needs a decision. A broad label such as Korea or Congo does not uniquely identify one supported country. Do not replace a country column with a calling-code column and assume that every value is interchangeable; the importer needs the kind of context its mapping expects.
Should I remove the zero at the start of a national number?
Let the numbering rules and the chosen country determine the conversion. Do not remove zeros from every phone value as a spreadsheet cleanup rule.
In the British example, a national form beginning 020 becomes an international form beginning +44 20. The Italian example behaves differently: +39 02 keeps the zero after the country code. A string operation that looks right for one country can damage valid data from another country.
Keep the original input beside the generated value so those changes can be reviewed. If a zero was already removed by a spreadsheet before import, the formatter cannot reliably establish what the original number was. Check the source record rather than inserting digits until the value looks familiar or reaches a chosen length.
What happens when a country field disagrees with a plus prefix?
The explicit international prefix takes priority. A conflicting country hint can produce a review warning, which should be checked against the source rather than used to rewrite the prefix.
For example, a +44 number with a source country of SI still describes a number with the British calling code. That mismatch may be a valid contact situation, a country field describing something other than the phone, or an error in the source. The converter cannot choose which business explanation is correct.
For mixed-country imports, include such a conflict in your initial sample. Review an empty country cell as well: a complete international number can be interpreted without a default, while a national number needs an appropriate mapped or default country. Do not treat the absence of a warning on another row as proof of ownership or current use.
Are 00 and 011 always safe substitutes for a plus sign?
No. International dialling prefixes depend on the source context. Use the known country and inspect the generated result instead of replacing a fixed digit pattern everywhere.
The converter can handle supported international-prefix forms, including the tested 0044 example and an 011 44 example with US context. A local number beginning with similar digits is a different question. The safe decision depends on what the source actually represents, not just the first two or three characters.
For storage and transfer, an explicit + country-code form avoids carrying a local dialling instruction into another system. If a source has mixed dialling conventions, sample those variations before converting the complete file. Retain the original field so a reviewer can see the difference between the received string and the selected output format.
Where do extensions and non-geographic numbers belong?
Keep an extension separate from the base E.164 number, and do not force a country onto every international service number. The result can describe an endpoint without behaving like an ordinary geographic contact.
E164flow parses supported extension notation and exports a separate extension field. The phone-link output can represent it with the tel: syntax and an ext parameter. That is a different output purpose from placing compact E.164 text in a CRM phone field.
The review result can also distinguish supported non-geographic numbering from a country-specific number. Check the detected result and the destination's requirements instead of filling a missing country with an arbitrary value. A country or service classification is numbering metadata; it does not establish that the endpoint is free to call or accessible from every location.
Which output format should I send to the next system?
Use the format the destination expects. Compact E.164 is a practical storage choice for many international contact lists; a national display or a tel: link serves a different purpose.
E164flow offers E.164, international display, national display, international digits without + and phone-link output. Keep the country context when a national form is required, and use digits-only output only when the receiving system explicitly expects it. Changing presentation does not add evidence that a number is active.
Before importing, compare a small sample in the actual destination. Check the plus sign, any retained zero and the extension field. Use Ready results for the initial reviewed export and investigate warning rows separately. None of these formatting choices supplies consent to contact a person or replaces a reachability check where your process needs one.
Which primary sources support this workflow?
Use the underlying standard or the destination's own documentation when checking a numbering rule or an import requirement.
What should I check before the final import?
Compare a small sample with the source and the destination, then use this checklist to review the complete file.
- Use ISO-style two-letter country codes in a mapped column where possible.
- Review ambiguous country names instead of relying on free text.
- Keep phone extensions separate from the base number.
Start with the data you have.
Use 25 pasted rows without an account, or sign up for the 50-row free workflow with CSV/XLSX and export.