International Calling From UK: Country Codes & Dialling Guide

International CallingCountry CodesUK Business Guide

Call overseas numbers correctly from the UK, understand when to use + or 00, avoid leading-zero mistakes, and keep international contact data clean across mobiles, CRM systems and business VoIP platforms.

Focus: correct international diallingIncludes: E.164, CRM & VoIP governanceUpdated: 
The core dialling pattern
+ or 00→Country code→International-format number
USA +1India +91France +33Germany +49Ireland +353UAE +971Australia +61China +86
Built around current ITU numbering rules and UK business workflowsCountry-code facts come from ITU numbering resources; business recommendations separate dialling, data quality, VoIP permissions, caller ID and commercial control.
How we research guides →
DialUse + or 00, then the country code

The digits after the country code must follow that destination’s international numbering rules.

Do not guessLeading-zero rules vary by country

Dropping a domestic 0 is common, but not universal. Italy is an important exception for geographic numbers.

Business dataStore one canonical format

E.164-style storage reduces ambiguity across CRM, mobile, VoIP and API workflows.

Fast answer

1. How Do You Call an International Number From the UK?

From the UK, an international call normally starts with the UK international prefix 00 or a + on devices and systems that support it, followed by the destination country code and the destination number in international format. The critical step is applying that country’s own national-prefix rules correctly.

UK caller→+ or 00→Country code→National significant number

A useful mental model is to separate three things:

  • International access: how your device or network enters the international telephone network.
  • Country code: the one-, two- or three-digit code that identifies the destination numbering area.
  • National significant number: the digits that identify the destination within that country’s numbering plan.
The safe rule

Do not mechanically copy the number exactly as it is written for domestic use. Convert it using the destination country’s international format. A domestic trunk prefix is often removed, but some numbering plans keep a leading zero as part of the internationally significant number.

This page focuses on the broad international-calling process. Country-specific child guides will own detailed rules for individual destinations as they are published.

Lookup

2. Common Country Codes for Calls From the UK

Country codes identify the destination country or numbering zone before the national number is dialled. The table below covers the destinations in the approved CompareVoIPService international-calling cluster plus several common UK business destinations. It is a practical shortlist, not a substitute for the ITU’s complete country-code register.

DestinationCountry codeTypical UK startPlanning note
United States+1+1 … / 001 …Part of the North American Numbering Plan; +1 is shared.
Canada+1+1 … / 001 …Shares country code +1 with the USA and other NANP territories.
India+91+91 … / 0091 …Use the Indian number in international format after +91.
Australia+61+61 … / 0061 …Domestic trunk 0 is normally omitted internationally.
Ireland+353+353 … / 00353 …Domestic trunk 0 is normally omitted internationally.
United Arab Emirates+971+971 … / 00971 …Confirm mobile vs geographic structure before normalising data.
Pakistan+92+92 … / 0092 …Domestic trunk 0 is normally omitted internationally.
South Africa+27+27 … / 0027 …Domestic trunk 0 is normally omitted internationally.
Spain+34+34 … / 0034 …No blanket leading-zero removal rule is needed for ordinary numbers.
France+33+33 … / 0033 …Domestic trunk 0 is normally omitted internationally.
Germany+49+49 … / 0049 …Domestic national prefix 0 is normally omitted internationally.
Italy+39+39 … / 0039 …Important exception: geographic numbers use 0 as a significant leading digit.
Portugal+351+351 … / 00351 …Use the full international national number after +351.
Netherlands+31+31 … / 0031 …Domestic trunk 0 is normally omitted internationally.
Poland+48+48 … / 0048 …Use the national significant number after +48.
China+86+86 … / 0086 …Check landline area-code and mobile format separately.
Belgium+32+32 … / 0032 …Domestic trunk 0 is normally omitted internationally.
Switzerland+41+41 … / 0041 …Use the destination number in current international format.
Sweden+46+46 … / 0046 …Domestic trunk 0 is normally omitted internationally.
Denmark+45+45 … / 0045 …National numbers generally do not use a trunk prefix.
Norway+47+47 … / 0047 …Use the national number after +47.
Singapore+65+65 … / 0065 …Use the national number after +65.
New Zealand+64+64 … / 0064 …Domestic trunk 0 is normally omitted internationally.
Japan+81+81 … / 0081 …Domestic trunk 0 is normally omitted internationally.

Country codes can be shared. The best-known example is +1, which covers the United States, Canada and other territories within the North American Numbering Plan. The digits after +1 determine the specific numbering area.

Dialling prefix

3. Should You Use + or 00 When Calling Abroad From the UK?

In the UK, 00 is the standard international prefix used before a country code. The + symbol is a portable international representation supported by mobile phones and many cloud systems. For stored contacts and business data, + format is usually cleaner because it is not tied to one country’s exit prefix.

FormatBest useExample to FranceImportant limitation
00Manual dialling from the UK0033 …00 is an international access prefix, not part of the E.164 number itself.
+Mobiles, contacts, CRM, VoIP, APIs+33 …The device/network interprets + when placing the call.

The distinction matters when data moves between countries or systems. Saving a contact as 0033… encodes the UK’s access method into the stored number. Saving it as +33… records the destination in a more portable international form.

Business default

Use +country-code format for canonical contact storage unless a specific application requires another representation. Let the calling platform handle the local dialling prefix rather than embedding UK-specific 00 into every record.

Critical accuracy

4. Do You Always Remove the Leading 0 From an International Number?

No. Removing a domestic leading 0 is a common international-dialling rule, but it is not universal. Many countries use 0 as a national trunk prefix that disappears after the country code. Other plans treat a leading 0 as part of the internationally significant number. Always follow the destination’s numbering plan.

Common pattern: trunk 0 removed

A French number written domestically with a leading 0 normally drops that trunk digit after +33. Germany, Australia, Ireland and many other destinations follow comparable trunk-prefix logic.

Important exception: Italy

Italy uses 0 to identify geographic numbers within its national significant number. For Italian landlines, that zero remains after country code +39. A blanket “always remove 0” rule would therefore corrupt valid numbers.

This is one of the most important differences between a safe business-number guide and a generic dialling shortcut. A CRM import rule that deletes the first 0 from every non-UK number can silently damage valid data.

When a country page is published in this cluster, it should become the detailed owner for that destination’s mobile, landline and trunk-prefix rules.

Number types

5. Do International Landline and Mobile Numbers Use the Same Format?

Landlines and mobiles share the same high-level international structure—country code followed by the destination’s national significant number—but the digits inside that national number can differ by service. Some countries use area codes for landlines, mobile prefixes for mobiles, variable lengths, or different national-prefix behaviour.

QuestionLandlineMobile
Country code needed?YesYes
May include an area code?CommonlyUsually uses a mobile/service prefix instead
Leading-zero handlingCountry-specificCountry-specific
Tariff can differ?YesYes, sometimes materially
Should CRM store type?Useful when operationally relevantUseful when SMS/WhatsApp/mobile workflows depend on it

A correct country code does not guarantee that the rest of the number is valid. A number can have the right prefix but the wrong length, wrong service range or wrong domestic-to-international conversion. For business systems, validation should therefore be country-aware rather than a single global regular expression.

Canonical format

6. What Is E.164 and Why Does It Matter for UK Businesses?

ITU-T E.164 is the international public telecommunication numbering plan. It defines the structure used for internationally routable telephone numbers, including the country code and national significant number, with a maximum of 15 digits. In business systems, E.164-style storage gives each telephone number a consistent country-aware representation.

Human-readable UK display020 7946 0000
International display+44 20 7946 0000
Canonical storage+442079460000

For geographic international numbers, E.164 separates the country code from the national significant number. The international access prefix—such as the UK’s 00—is not part of the E.164 number.

In practical CRM and API workflows, many organisations store the canonical number without spaces or punctuation while formatting it differently for display. That separation makes deduplication, click-to-call, integrations and validation more predictable.

Worked examples

7. International Dialling Examples From the UK

Examples are useful only when they show the numbering rule behind the conversion. The table below illustrates common patterns: removing a domestic trunk prefix, preserving a significant leading zero where required, and handling a shared country code. The numbers are formatting examples, not a directory of real businesses or subscribers.

DestinationDomestic-style exampleInternational-format exampleWhat changed?
France01 23 45 67 89+33 1 23 45 67 89Domestic trunk 0 removed.
Germany030 …+49 30 …National prefix 0 removed.
Australia02 …+61 2 …Domestic trunk 0 removed.
Ireland01 …+353 1 …Domestic trunk 0 removed.
Italy landline06 …+39 06 …Leading 0 retained as significant.
USA(212) …+1 212 …+1 added; no UK-style trunk zero to remove.
Canada(416) …+1 416 …Shares +1; area code identifies numbering area.
India mobile0 + mobile routing context may appear domestically+91 + national mobile numberUse the current Indian international format rather than copying domestic prefixes.

For production systems, do not hard-code the examples above as universal transformation rules. Use country-aware validation or a maintained telephony library/provider service, particularly when importing mixed-country datasets.

Address books

8. How Should a UK Business Save International Phone Numbers?

A business address book should store enough context to dial the number correctly from different devices and locations. The cleanest approach is usually one canonical international form plus separate metadata for country, contact type and display preferences. Avoid storing local-only strings whose meaning depends on the employee remembering the destination country.

Normalize the number

Convert the supplied number to a validated international representation rather than saving whatever formatting the contact typed.

Keep the country explicit

Store country as structured data where possible. Do not infer it forever from free-text notes or staff memory.

Separate display from storage

A CRM can display spaces for readability while retaining one canonical value for matching and integrations.

Preserve the source

For high-value imports, retaining the original user-entered value can help investigate failed conversions or ambiguous records.

A number field should normally be treated as text, not a mathematical value. Telephone numbers can contain a leading plus sign and may have significant zeros. Storing them as integers risks stripping formatting information and leading digits.

CRM & integrations

9. How Should International Numbers Be Formatted in a CRM?

CRM phone data should support matching, click-to-call, imports, APIs and automation without forcing every integration to reinterpret local formats. A practical design is to normalize to a canonical international number, keep country metadata where useful, and validate numbers before automations or outbound diallers rely on them.

CRM field / controlRecommended roleWhy it matters
Canonical phoneInternational +country-code representationSupports matching, dialling and API consistency.
CountryStructured ISO/country fieldSupports validation and reporting.
Phone typeMobile / landline / work / otherUseful for channel and workflow rules.
Original inputOptional audit fieldHelps investigate ambiguous conversions.
Validation statusValid / invalid / unverifiedPrevents automation from assuming every formatted string is callable.

If your phone system is linked to the CRM, use the VoIP CRM Integration guide for the broader workflow around click-to-call, caller matching, automatic logging and activity history.

VoIP controls

10. How Should International Calling Be Controlled in a Business VoIP System?

International calling should be treated as a permissioned business capability, not an automatic entitlement for every user. Good controls define who may call abroad, which destinations are permitted, what happens outside normal patterns, and who can change those rules. This reduces both accidental cost and avoidable misuse.

Default-deny where sensible

Users who never need international calling do not need unrestricted access to every destination.

Allow by role or destination

Sales, procurement or support teams can receive the permissions they actually require rather than blanket access.

Protect administration

Restrict who can change dial plans, trunks, forwarding rules and international permissions.

Monitor abnormal use

Review sudden destination, duration or volume changes and ensure billing alerts are configured where the provider supports them.

The exact controls vary by platform. When evaluating a business phone system, include international calling permissions in the requirements rather than discovering after go-live that the feature is either blocked or too broadly enabled.

Caller identity

11. What Happens to Caller ID on International Business Calls?

Caller ID on international calls depends on the originating platform, carriers and destination networks. UK businesses should use valid, controlled presentation numbers and avoid assuming any UK number can be presented from any overseas route. Current Ofcom guidance puts increasing emphasis on accurate CLI data and blocking spoofed UK identities from abroad.

For ordinary business operations, that means caller ID should be part of the telephony design:

  • decide which authorised business number each team should present;
  • confirm the provider supports that CLI on international routes;
  • test how the number appears in key destination countries;
  • avoid unsupported workarounds that make a call look as if it originated from a different identity;
  • document exceptions where overseas staff or contact centres legitimately originate calls.
Why this matters in 2026

Ofcom has strengthened guidance around calls arriving from abroad that present UK numbers, including landline and mobile identities. International caller-ID design therefore needs provider-supported routing and accurate CLI data, not arbitrary number presentation.

Commercial control

12. How Do You Control the Cost of International Calling?

International calling rates can vary by destination, number type, provider, plan and bundled calling zone. A business should therefore treat overseas calls as a separate cost category. Do not assume a plan described as “unlimited” or “inclusive” covers every country, mobile network, special range or international route.

Cost questionWhat to verifyWhy it matters
Destination rateCountry + landline/mobile/special rangesRates can differ within the same country.
Bundle coverageExactly which countries and number types are included“International minutes” may cover only selected zones.
Connection feesPer-call charges as well as per-minute ratesShort calls can become disproportionately expensive.
Fair-use policyCaps, excluded destinations and overage rulesInclusive plans can still generate usage charges.
Billing alertsThresholds and anomaly notificationHelps surface unexpected spend earlier.

Use the VoIP Pricing and Hidden Costs guide to review the broader commercial model around licences, calling, numbers, hardware, add-ons and contract terms.

Operating model

13. A Practical International Calling Governance Model for UK Businesses

The strongest business setup separates telephone-number data, calling permissions, cost control and caller identity instead of treating “international calling” as one switch. A small amount of governance prevents avoidable billing surprises, failed CRM automations and caller-ID problems while still giving legitimate teams fast access to the destinations they need.

Define business destinations

List the countries and number types genuinely required by sales, support, suppliers and operations.

Normalise contact data

Use country-aware international formatting so the same contact works across mobile, CRM and VoIP systems.

Set user permissions

Grant international access based on role rather than enabling every user by default.

Control caller identity

Use provider-supported CLI policies and test presentation on important routes.

Model the rates

Check the actual landline/mobile destinations your team calls instead of comparing only headline plan labels.

Review exceptions

Investigate failed calls, unusual spend, repeated manual prefixes and rejected CRM numbers as signals that the design needs correction.

Avoid these

14. Common International Calling and Number-Formatting Mistakes

Most international calling failures are not caused by the country code alone. They come from mixing domestic and international formats, applying one leading-zero rule to every country, storing numbers inconsistently, or enabling calling without the right permissions and tariffs. These mistakes become more expensive when repeated across a CRM or dialler.

MistakeWhy it failsBetter approach
Saving 00 in every CRM numberEmbeds a UK-specific exit prefix into stored dataStore canonical +country-code format.
Always deleting the first 0Breaks numbering plans where 0 is significant, such as Italian geographic numbersApply country-specific rules.
Using a single regex for every countryNumber lengths and ranges differUse maintained country-aware validation.
Storing phone numbers as integersCan strip + and significant leading zerosStore as text/string data.
Assuming +1 means USA only+1 is shared across the NANPUse the following area code/range to determine destination.
Enabling unrestricted international callingCreates unnecessary cost and misuse exposureUse role/destination controls.
Assuming caller ID always passes unchangedInternational carriers and anti-spoofing rules can affect presentationTest provider-supported CLI routes.
Checklist

15. International Calling Checklist Before You Configure a Phone System

Before enabling overseas calling, confirm the numbering, user permissions, cost model and data workflow together. The checklist below is designed for a UK business preparing a VoIP requirement or cleaning an existing system. It keeps the operational decisions separate from provider marketing and makes later testing easier.

  • List the countries your teams genuinely need to call.
  • Separate landline, mobile and special-range requirements where rates differ.
  • Confirm each destination’s country code and international-format rules.
  • Document exceptions to the usual “drop the 0” pattern.
  • Choose a canonical CRM/contact storage format.
  • Decide which users or roles need international permissions.
  • Confirm caller-ID presentation for key routes.
  • Review international rates, bundle coverage and fair-use rules.
  • Configure spend/anomaly alerts where available.
  • Test calls from desk phone, softphone and mobile app where those channels are in scope.
  • Test CRM click-to-call and contact matching with international records.
  • Record who owns dial-plan, tariff and permission changes after go-live.
FAQ

16. Frequently Asked Questions About International Calling From the UK

These questions cover the points most likely to cause failed calls or inconsistent business data: whether to use + or 00, when a leading zero disappears, how +1 works, what E.164 means, and how to store international numbers safely in CRM and VoIP systems.

What do I dial before an international number from the UK?

Use the UK international prefix 00 followed by the country code, or use + on a mobile or system that supports international + format. Then dial the destination number according to that country’s international numbering rules.

Is + the same as 00?

They serve related purposes but are not literally the same data. 00 is the UK’s international access prefix. + is a portable international notation that a compatible device or calling system interprets when placing the call. For stored contacts, + format is usually more portable.

Do I always remove the first 0 when calling abroad?

No. Many countries use a domestic trunk 0 that is removed internationally, but the rule is not universal. Italian geographic numbers are a well-known exception where 0 is significant and remains after +39. Check the destination numbering plan rather than applying a blanket rule.

What is the country code for the USA from the UK?

The country code is +1. The same +1 code is also shared by Canada and other territories in the North American Numbering Plan, so the following area code helps identify the specific destination.

What is the country code for India from the UK?

India uses country code +91. Use +91 or 0091 from the UK, followed by the Indian number in the correct international format. Avoid blindly copying domestic prefixes into the international number.

What is E.164 phone number format?

E.164 is the ITU international public telecommunication numbering plan. For geographic numbers it combines a country code with the national significant number and allows a maximum of 15 digits. Business systems commonly use a leading + representation for canonical storage.

Should CRM phone numbers include spaces?

For canonical storage and API use, many systems work best with a normalized +country-code value without presentation punctuation. The interface can still display a human-readable version with spaces. Check the requirements of the CRM, phone integration and downstream APIs.

Can the USA and Canada both use +1?

Yes. +1 is the shared country code for the North American Numbering Plan. The next digits, including the area code, determine the relevant numbering area rather than the +1 alone identifying one country.

Can a business block international calls for some users?

Many business VoIP platforms support permissions, dial plans or calling policies that can restrict international calling by user, role or destination. The exact control varies by provider, so include this requirement during selection and test it before go-live.

Does unlimited VoIP calling include international calls?

Not necessarily. International destinations, mobiles, special ranges and countries outside the plan’s calling zone may be billed separately. Check the provider’s current rate card, bundle coverage and fair-use terms for the destinations your team actually calls.

Will my UK caller ID always appear on an overseas call?

Not always. Caller-ID presentation depends on provider support and international routes. Use valid, provider-supported business numbers and test key destinations. Anti-spoofing measures can also affect calls that appear to originate from UK numbers through overseas routes.

What is the safest way to import international contacts?

Keep country information, validate each number against country-aware rules, normalize it to a canonical international form, preserve the original value where auditability matters, and flag ambiguous or invalid records instead of guessing.

Next step

17. Turn International Dialling Into a Controlled Business Requirement

Once the number-format rules are clear, convert them into operational requirements: which countries are needed, who may call them, how contacts are stored, which caller ID should appear, what the expected traffic costs, and how unusual usage is reviewed. That makes international calling testable during procurement rather than an afterthought.

Use the VoIP Pricing and Hidden Costs guide to model international rates within the full commercial picture.

Use the VoIP CRM Integration guide when international number formatting must work with click-to-call, contact matching and automated logging.

For the wider phone-system requirement, continue to the VoIP Buyer’s Guide or the Business Phone Systems comparison when you are ready to move from requirements into platform research.

Sources

Sources & Research Method

This guide uses ITU numbering resources for country-code and E.164 structure, Ofcom for UK caller-identification context, and current CompareVoIPService guides for the surrounding commercial and CRM workflow. Competitor pages were reviewed to identify search intent and recurring mistakes, but the structure, decision frameworks, governance model and wording here are original.

International rates, provider permissions, supported caller-ID behaviour and destination routing can change. Verify provider-specific details before procurement, configuration or large-scale outbound calling.

Bhav Giva, Founder and Lead Analyst at CompareVoIPService.co.uk

CompareVoIPService.co.uk

UK-focused VoIP guidance

About the author

Bhav Giva

Founder & Lead Analyst at CompareVoIPService.co.uk

Bhav Giva is the founder of CompareVoIPService.co.uk, a UK-focused platform helping businesses choose the right VoIP provider with clear, unbiased guidance. With a background in telecom, AI automation, CRM engineering, and digital strategy, Bhav specialises in simplifying complex communication systems and making VoIP decisions transparent, cost-effective, and easy to understand for UK organisations.

Move from dialling to procurement

Make international calling part of the phone-system requirement.

Define the countries, users, number formats, caller identity and cost controls you actually need before comparing platforms. That turns international calling from a hidden tariff line into a testable operational requirement.