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

# Porting Numbers: Inbound

> Transfer phone numbers you already own into Invoca — typically a two-to-five week process requiring a signed Letter of Authorization.

If your organization already owns toll-free or local phone numbers you'd like to use with Invoca, you can transfer (port) them into your account. Standard port-in requests take about two to five weeks depending on your previous carrier; requests for more than 200 numbers may take longer.

Invoca assesses a service fee for porting in numbers. We strongly recommend contacting your Invoca Account Manager to discuss pricing and billing before submitting a port-in request.

## Submitting a port-in request

Local and toll-free number requests must be submitted separately.

1. Draft a Letter of Authorization (LOA) permitting Invoca to transfer and manage your numbers. Reach out to your account team or [support@invoca.com](mailto:support@invoca.com) for the correct LOA template (local or toll-free). Your LOA must be signed and dated within 30 days of submitting your request.
2. List your phone numbers and their intended campaign URL in a porting spreadsheet. Reach out to your account team or [support@invoca.com](mailto:support@invoca.com) for the porting template. Required fields are Number to Port and Campaign URL; optional fields include description, media type, detected destination, and any other marketing data to apply.
3. Reach out to your account team or [support@invoca.com](mailto:support@invoca.com) to open a ticket with the subject and description "Request to port-in phone numbers," Case Reason "Number Management," and Sub-Category "Porting Numbers."
4. Attach your completed LOA and porting spreadsheet to the ticket, then submit.

Our telecom operations team will process your request and keep you updated. If you need to port in both local and toll-free numbers, repeat these steps for each.

**Requirements to get started:**

* An internal porting project owner to handle communication with Invoca
* The current RespOrg controlling the number
* A completed Letter of Authorization, matching what your current carrier has on file and signed within 30 days
* An Invoca campaign to place static numbers in once ported

## Losing carrier considerations

To prevent delays or rejections, request a Customer Service Record (CSR) from your current carrier before starting. If porting local numbers, also obtain the Account PIN associated with them.

Invoca depends on your current carrier (the RespOrg) to confirm LOA details and complete the port. The LOA must match the losing carrier's records exactly, or the request is rejected — if rejected, you have 10 business days to respond before the case is closed and you'll need to start over.

**Common reasons for rejection:**

* Billing address mismatch
* Customer/business name mismatch
* Authorized name and signature mismatch
* Account with the losing carrier on hold due to non-payment
* Numbers on a bundle account that the carrier won't allow to port out individually
* A PIN is required for number release

A corrected request is resubmitted as a new order, which increases the total time to port.

Numbers ported into Invoca count against your contractual number allotment for billing purposes. For example, if your platform is contracted for 1,000 numbers and you port in 700, that's 70% of your contractual allotment.

## Where to go next

* [Numbers & Destinations Overview](/s/article/numbers-destinations-overview)
* [How to Port UK Numbers Into Invoca](/s/article/port-uk-numbers-into-invoca)