> ## Documentation Index
> Fetch the complete documentation index at: https://help.cloudtalk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# 🇬🇧 UK Number Porting Guide

> UK number porting instructions for CloudTalk

***

> [!NOTE]
>
> This guide outlines the supported number types, required documents, hosting rules, and porting timelines for UK numbers.

## Initial Overview

### Supported Number Types

| **Number Type** | **Example Prefixes** |
| - | - |
| Geographic (Local) Numbers | +441, +442 |
| Mobile Numbers | +447 |
| Non-Geographic (National) | +443 |
| Non-Geographic (Toll-Free) | +44800, +44808 |

### Submit Your Request

Request porting directly in the CloudTalk Dashboard: open **Numbers > Port existing number** and follow the guided steps. All supported number types for this country use the same flow, and you can track your request anytime under **Numbers > Porting requests**.

> [!WARNING]
>
> Looking to port numbers from other countries? See **[Global Porting Coverage](/en/articles/5440566-porting-pricing-and-coverage)**.

### Letter of Authorization

Where an LOA is required, the correct template for this country **downloads inside the Documents step** of your porting request: download it, sign it, and upload it right there. You no longer need a separate template from this guide.

(Other document requirements listed below.)

### Timelines & Pricing

| Number Type | Estimated Duration | Pricing |
| - | - | - |
| Local | \~15–20 business days | **€30.00** per request, **€7.00** per number |
| National | \~15–20 business days | **€30.00** per request, **€7.00** per number |
| Toll-Free | \~15–20 business days | **€30.00** per request, **€8.00** per number |
| Mobile | \~5–7 business days | **€30.00** per request, **€7.00** per number |

> [!WARNING]
>
> ⚠️ Timelines may vary if submitted details do not match your current provider’s records.

***

## Required Documents for Number Porting

The correct **LOA template** downloads inside the **Documents step** of your porting request.

### ✅ Geographic (Local) Numbers

* Signed Letter of Authorization (LOA)

* Recent billing document (issued within the last 3 months, showing number and account holder)

* UK site address matching the number’s registered location

### ✅ Mobile Numbers

* PAC Code (Porting Authorization Code)

  * 9-digit Format: 3 letters + 6 digits (e.g. ABC123456) *- Issued by your current mobile provider*

  * Expiration date of PAC Code with current Provider - *Valid for 30 days by default*

    * *From major carriers like Vodafone or O2 there will be one unique PAC code per number*

    * *If you are moving from another VoIP platform there may be only one PAC code for a whole batch of numbers*

  * *You’ll enter your PAC code in the Verification step of your porting request.*

* Recent billing document (issued within the last 3 months, showing number and account holder)

### ✅ National & Toll-Free Numbers (Non-Geographic)

* Signed LOA (must include **Billing Account Number**)

* Recent billing document (issued within the last 3 months, showing number and account holder)

### Regulatory Compliance (KYC)

UK number porting is subject to identity verification under UK telecom regulations. CloudTalk (via our partner carrier) may request additional documents depending on:

* Whether your company is **UK-based** or **international**

* The **type of number** being ported (mobile, geographic, non-geographic, etc.)

***

## Porting Process Overview

1. **Submit Your Porting Request**\
   Submit your request in the CloudTalk Dashboard under **Numbers > Port existing number**.

2. **Initial Review**\
   Cloudtalk team'll verify number portability and confirm the next steps.

3. **Documentation Collection**\
   Complete and sign the LOA (Letter of Authorization), and provide a recent invoice from your current telecom provider.

4. **Submission to Carrier**\
   CloudTalk submits your request to our partner carrier, who then forwards it to your current provider.

5. **Approval or Rejection**

   * If **approved**, Cloudtalk team will confirm the porting date (typically 2–4 business days in advance).

   * If **rejected**, Cloudtalk team will share the reason and guide you on how to correct and resubmit the request.

***

## Common Rejection Reasons

| **Issue** | **Description** | **How to Fix** |
| - | - | - |
| **Mismatched Account Information** | Details on the LOA don't match what's on file with the losing provider (often the postal code). | Double-check the LOA fields against your provider’s account info. |
| **Incorrect or Incomplete LOA** | Required fields are missing or the signature is typed. | Fill all fields and apply a valid digital or handwritten signature. |
| **Invalid PAC or STAC** | The code for mobile numbers is incorrect or expired. | Request a valid PAC/STAC from your current provider before submission. |
| **Outdated Billing Document** | Invoice is older than 3 months. | Submit a recent invoice issued within the past 90 days. |

***

## On Porting Day

* The number is activated in your CloudTalk account

* Your former provider deactivates the number

* CloudTalk billing begins the same day

* We recommend notifying your previous provider to prevent duplicate charges

***

## SMS Functionality Note

* SMS for **mobile numbers** is activated along with voice

* **Geographic, national, and toll-free numbers** are not SMS capable

***

**Need Help?**

For further assistance, please refer to:

* [CloudTalk Porting Process Overview](/en/articles/2145454-porting-requests-and-process)

* [CloudTalk Recommendations for a Smooth Port](/en/articles/6084486-recommendations-for-a-smooth-port)

Questions about a request you've already submitted? Open it under **Numbers > Porting requests** and click **Open conversation**.


## Related topics

- [🇦🇺 Australia Number Porting Guide](/en/articles/11069749-australia-number-porting-guide.md)
- [🇨🇦 Canada Number Porting Guide](/en/articles/11045800-canada-number-porting-guide.md)
- [🇱🇺 Luxembourg Number Porting Guide](/en/articles/11469487-luxembourg-number-porting-guide.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.