# Porting requests

Porting requests are used to submit existing phone numbers for transfer to DIDWW.

A porting request groups one or more phone numbers together with the information, documents, and end-user details
required for carrier review and approval.

## How porting requests work

After a porting request is submitted, DIDWW reviews the request details and verifies that all required information and
documents are provided.

The porting request progresses through its own lifecycle, while each phone number within the request is tracked
separately through the Porting Numbers workspace. Depending on the country, number type, and carrier requirements,
additional information or corrected documents may be requested before the request can continue.

Before a request can be submitted, DIDWW may require end-user details, a completed Letter of Authorization (LOA), the
latest invoice from the current carrier, the current carrier account number, or additional supporting documents. The
exact requirements depend on the country and number type selected during request creation.

```
        ---
config:
  layout: dagre
---
flowchart LR
    create(("&nbsp; Create New &nbsp; <br> &nbsp; Porting Request &nbsp; ")) --> pending["Pending"]
    pending --> start(("&nbsp; Start Porting &nbsp; <br>Request"))
    pending -.-> requires_changes(("Porting Request<br>Requires Changes")) & cancel(("&nbsp; Cancel Porting &nbsp; <br> &nbsp; Request &nbsp;"))
    start --> process1["In Process"]
    process1 --> foc(("Porting Date<br>Confirmed (FOC)"))
    process1 -.-> cancel
    foc --> process2["In Process"]
    process2 --> completed["Completed"]
    cancel --> cancellation_pending["Cancellation Pending"]
    cancellation_pending --> confirm_cancel(("&nbsp; Confirm &nbsp; <br> &nbsp; Cancellation &nbsp; "))
    confirm_cancel --> canceled["Canceled"]
    requires_changes --> changes_required["Changes Required"]
    changes_required --> cancel & resubmit(("Resubmit Porting<br>Request"))
    resubmit --> pending

     create:::customer
     pending:::status
     start:::staff
     requires_changes:::staff
     cancel:::customer
     process1:::status
     foc:::staff
     process2:::status
     completed:::completed
     cancellation_pending:::status
     confirm_cancel:::staff
     canceled:::canceled
     changes_required:::status
     resubmit:::customer
    classDef status fill:#f9e6dc,stroke:#ff5c1a,stroke-width:2px,color:#1f2d3d
    classDef staff fill:#fff4cf,stroke:#ffb000,stroke-width:2px,color:#1f2d3d
    classDef customer fill:#d7ecfb,stroke:#008ce3,stroke-width:2px,color:#1f2d3d
    classDef completed fill:#d0f0ec,stroke:#00a99d,stroke-width:2px,color:#1f2d3d
    classDef canceled fill:#f6d6df,stroke:#e83f6f,stroke-width:2px,color:#1f2d3d
```

## How-to guides

**Create porting request**

Create a porting request, upload required documents, and submit it for processing.

[Create porting request](create-porting-request.html)

**Resubmit porting request**

Update required information and resubmit a request in **Changes Required** status.

[Resubmit porting request](resubmit-porting-request.html)

**Cancel porting request**

Cancel an entire porting request before it is completed.

[Cancel porting request](cancel-porting-request.html)

**Cancel specific number porting**

Cancel selected numbers inside a porting request.

[Cancel specific number porting](cancel-specific-number-porting.html)

**Resolve Action Required status**

Resubmit numbers that require additional information or corrected documents.

[Resolve Action Required status](resolve-action-required-status.html)

## Related resources

**Porting requests reference**

Look up request statuses, filters, and table fields.

[Porting requests reference](porting-requests-reference.html)

**Number porting**

Understand porting requirements, timing, and cancellation basics.

[Number porting](../index.html)

**Porting numbers**

Understand individual porting numbers inside requests.

[Porting numbers](../porting-numbers/index.html)

On this page