If you have ever submitted a business number port manually, you already know the rhythm: paper LOAs, mismatched addresses, rejected orders, and a customer asking why their cutover is three weeks out when you promised five days. Learning how to submit a business number port correctly is less about the form itself and more about the upstream prep work that prevents rejection.
This guide walks through the exact LNP process, the FCC rules that shape it, and how the right platform turns a brittle manual workflow into a clean, repeatable digital one. If you are an MSP, telecom reseller, or IT provider submitting ports on behalf of your business customers, the second half of this article is just as important as the first.
TL;DR
- A business number port (LNP) moves existing phone numbers from one carrier to another without changing the digits.
- The FCC requires interconnected VoIP and wireline carriers to honor valid port requests, with simple ports completing in one business day.
- You need a signed LOA, a recent bill or CSR, the BTN, the full list of numbers, and the exact business name and service address on file.
- Mismatched information between the LOA and the losing carrier's CSR is the primary reason port requests get rejected.
- Viirtue's ViiBE platform digitizes the LNP workflow under your reseller brand with e-sign and pre-submission validation, and makes new number ordering fully self-service end-to-end.
- For resellers, branded self-service porting protects margin, prevents churn during cutover, and turns the most painful part of telecom into a competitive advantage.
Why Porting Quality Defines Your First 90 Days
Number portability is one of the foundational pillars of U.S. telecom competition. The Telecommunications Act of 1996 required local exchange carriers to support number portability, and the FCC has extended those rules steadily to interconnected VoIP providers. In 2009, the Commission compressed the porting interval for simple ports to one business day under 47 CFR Part 52, a rule that still anchors the modern porting market.
For resellers and MSPs, that regulatory floor is the easy part. The hard part is operational. A meaningful share of business port requests get rejected on the first submission, almost always because of address mismatches, BTN errors, or signature issues. Each rejection adds 3 to 10 days, and every day of delay is a day your new customer is second-guessing the switch. That is why the first 90 days of a new customer relationship are so heavily shaped by porting quality -- and why it matters which platform you choose to handle it.
Platform-level porting automation has become a real differentiator as a result. Carriers and platforms that win in 2026 are the ones treating LNP as a product, not a back-office chore. Our reseller VoIP porting rules guide covers the regulatory evaluation checklist if you want the partner platform selection angle alongside this execution guide.
Porting is not an afterthought you clean up post-sale. It is the first real operational test of your service delivery, and customers remember a slow or botched cutover for the entire life of the relationship.
What Business Number Porting Actually Is
Local Number Portability (LNP) is the FCC-defined ability of customers to keep their phone numbers when switching from one telecommunications carrier to another within the same geographic area. It applies to wireline, wireless, and interconnected VoIP providers.
A business number port is the operational process of transferring one or more business telephone numbers from a losing carrier to a winning carrier. The customer keeps the same numbers, but routing, billing, and service ownership move entirely to the new provider.
Two practical categories shape how you approach every port order:
- Simple ports. Single-line or small-line ports without complex translations. Under FCC rules, these must be completed within one business day of a valid port request being received.
- Complex ports. Multi-line, PRI, hunt-group, or numbers tied to DSL, alarm circuits, or fax lines. These follow longer industry-standard intervals, typically 7 to 14 business days in practice, and may require additional documentation.
The distinction matters because the documentation you gather, the timeline you commit to, and the steps you follow all shift based on which category applies. Misclassifying a complex port as simple is one of the faster ways to over-promise a go-live date.
FCC Rules That Govern Local Number Portability
The FCC's LNP framework lives inside 47 CFR Part 52 and a series of Commission orders. These are the rules most relevant when you are submitting a business port:
One-business-day porting interval for simple ports. In FCC 09-41, the Commission required all entities subject to LNP rules to complete simple wireline-to-wireline and simple intermodal port requests within one business day of receiving a valid request. That rule remains in effect and sets the floor for any competent reseller's service promise.
Standard data fields for port validation. The FCC adopted a streamlined set of fields a winning carrier may require from the losing carrier to validate a port: account number, telephone number, ZIP code, and (where applicable) a passcode or PIN. Losing carriers cannot demand additional fields outside this set to delay or obstruct the port.
Interconnected VoIP coverage. Interconnected VoIP providers must facilitate LNP for end users and execute valid porting requests without unreasonable delay. This is the rule that makes white label VoIP resale viable and that applies to your business when you operate under a provider like Viirtue.
Anti-slamming protections. Carriers must have documented authorization from the customer before initiating a port. This is the legal foundation of the LOA requirement. An unauthorized port is a "slam," and the FCC treats it seriously. This is also why the LOA process is not optional or informal.
The practical result: if you submit a clean, validated request with data that matches the losing carrier's records, that carrier has very little legal room to delay. If your data is wrong, none of those protections apply -- because the request is not valid under the rules.
The FCC's rules protect you only when the request is clean. A messy or incomplete port request forfeits those protections and puts you back in line behind every other pending order at the losing carrier.
Documents You Need Before You Submit
Most port failures happen before submission, in document prep. Get these right and you eliminate the majority of rejections before they happen.
Recent phone bill (within 30 days). This is the source of truth for account identification. It shows the legal business name, service address, BTN, account number, and the numbers on the account. A bill older than 30 to 45 days may not accurately reflect current account status.
Customer Service Record (CSR). A CSR is the official account snapshot from the losing carrier, showing exactly how the account is registered: authorized contact, billing address, service address, BTN, and all telephone numbers. The winning carrier validates your LOA against this record. Request the CSR from the losing carrier in writing -- you are legally entitled to it. If the CSR and the bill disagree on any field, use the CSR.
Letter of Authorization (LOA). The LOA is a legal document granting the new carrier permission to act on the customer's behalf to transfer phone numbers. Every field must match the CSR: business name exactly as it appears (including LLC, Inc., or DBA suffixes), service address, BTN, full list of numbers to port, requested port date, and a signature from an authorized party.
List of telephone numbers in 10-digit format. Every number to be ported, verified against the CSR. Numbers tied to different underlying carriers may require separate LOAs even if they bill on the same account.
Account PIN or passcode (if applicable). Some carriers, particularly wireless providers and modern VoIP platforms, require an account security passcode to release numbers. Collect this from the customer up front -- not after the first rejection.
How to Submit a Business Number Port (Step by Step)
This is the workflow that produces clean ports in production, whether you are running it manually or through a platform like ViiBE.
Step 1: Confirm the business is ready to port. Verify the customer is not under an active contract penalty that would generate early termination fees. Confirm that any DSL, alarm, or fax services on the porting lines will be handled separately. Make clear to the customer that they must not cancel service with the losing carrier until the port is confirmed complete.
Step 2: Request a CSR from the losing carrier. Pull the official account record before you touch the LOA. This single step eliminates the majority of rejections, because you will see the exact legal business name, service address, and BTN the losing carrier has on file -- and you can match the LOA to it precisely.
Step 3: Complete the LOA using CSR data, not memory. Match the business name character for character, including punctuation, abbreviations, and entity suffixes. Use the service address, not the billing address, unless they are identical on the CSR. List every number in 10-digit format. Treat this as a copy-paste exercise from the CSR, not a form to fill from the customer's verbal account.
Step 4: Get the LOA signed by an authorized party. The signer must appear on the CSR as the authorized contact or account holder. Collect a legible signature with a date. E-signatures are accepted by virtually all carriers and are faster and more reliable than scan-and-email workflows.
Step 5: Submit the LOA, CSR, and recent bill to the winning carrier. Include the requested port date. Setting the requested date at least three weeks out gives you buffer for the FOC process and avoids panic if the first submission triggers a minor correction request.
Step 6: Wait for the FOC. The Firm Order Commitment is the losing carrier's official confirmation of when the port will execute. Once you receive the FOC, you can confirm the exact cutover time with the customer and begin pre-staging the new service.
Step 7: Pre-stage the new service before cutover. Configure extensions, devices, call flows, voicemail, and routing in the new platform so the switch is instant when the FOC date arrives. If the new service is not ready at cutover, you create a service gap that is entirely avoidable.
Step 8: Cutover. On the FOC date and time, numbers translate to the new carrier. Test inbound and outbound on every ported line. Confirm voicemail, auto-attendants, and hunt groups are routing correctly. Only after you have confirmed everything is working should the customer close out the old account.
Step 9: Document and archive. Store the signed LOA, FOC, and completion confirmation. These records support compliance, audit, and any future dispute resolution if a number is ever contested or wrongly ported away.
Steps 2 and 3 -- CSR pull and LOA completion -- are where nearly all port rejections originate. If you spend extra time anywhere in this workflow, spend it here. The rest of the process is mostly waiting.
The Most Common Reasons Port Requests Get Rejected
Every reseller submitting ports on behalf of business customers will encounter rejections. Most of them are preventable. Here is what causes them and how to stop them before submission.
| Rejection Reason | Root Cause | How to Prevent It |
|---|---|---|
| Name mismatch | LOA uses DBA; CSR shows legal entity | Pull CSR first; mirror the name exactly |
| Address mismatch | LOA shows billing address; CSR shows service address | Always use the service address from the CSR |
| BTN mismatch | Wrong billing telephone number listed | Confirm BTN directly from the CSR |
| Missing or invalid signature | Illegible signature or wrong signer | Use e-signature; verify signer is on the CSR |
| PIN or passcode missing | Account has a security passcode that was not collected | Ask the customer for their PIN during intake |
| Numbers on different underlying carriers | Numbers on one bill are served by multiple carriers | Split into separate LOAs per underlying carrier |
| Past-due balance on the account | Losing carrier blocks release pending payment | Have the customer resolve the balance before submitting |
Scroll to see full table if needed on mobile.
The consistent thread across all of these: the CSR is the ground truth. Every field on the LOA should be a verified copy from that document, not from the customer's memory or the most recent invoice header. Resellers who build that habit into their porting intake process see dramatically fewer first-submission rejections.
How Viirtue's LNP and Number Ordering Workflow Removes the Pain
Most resellers describe porting as the single worst part of running a VoIP business. Viirtue rebuilt that experience from the ground up inside ViiBE, the proprietary quote-to-cash platform included with every Viirtue white label VoIP partnership.
What changes when you run the LNP process through ViiBE:
Branded, mobile-first customer experience. When you initiate a port order in ViiBE's self-service porting workflow, the platform auto-generates the LOA pre-populated with your reseller branding -- your logo, your company name, your contact details. Your customer receives a clean, mobile-friendly e-sign request they can complete from any device in under two minutes. They never see Viirtue's name.
Pre-submission validation. ViiBE flags mismatches in required fields before you submit to the carrier, not after the losing carrier rejects the order. BTN alignment is surfaced during setup so the most common jeopardy trigger gets caught in the workflow rather than in a rejection notice three days later.
Digital LOA with e-signature. No printing, no faxing, no scanning. The signed LOA is captured, time-stamped, and stored for audit. The document vault in ViiBE holds porting artifacts, LOAs, invoices, and compliance records attached to the customer account record where they belong.
Wizard-driven number entry and auto-submission. Enter the numbers, and ViiBE walks you through the workflow. Once the customer completes the e-sign, the automation takes over -- from document assembly to carrier submission -- without additional manual steps on your end.
Fully self-service number ordering alongside the port. Need DIDs staged before cutover? New number ordering in ViiBE is end-to-end automated and self-service: search inventory by area code or rate center, reserve, and provision new numbers without a ticket or a wait. Extensions, routing, and call flows can be configured and ready before the FOC date arrives.
The compliance layer is built in. Because Viirtue operates as a carrier-class platform, FCC LNP rules, validation requirements, and telecom tax handling are part of the platform architecture, not add-ons you configure manually. You do not need to be a telecom regulatory specialist to run a compliant porting practice under your brand.
For a deeper look at exactly how the ViiBE porting workflow is structured for resellers, the self-service porting guide covers BTN alignment, scheduling controls, and the full digital LOA flow step by step.
Viirtue vs. Manual Porting and Generic Wholesale Carriers
If you are evaluating platforms based on porting capability, the operational differences between a manual workflow, a generic wholesale carrier, and a purpose-built reseller platform like Viirtue are substantial. Here is what that comparison looks like across the dimensions that matter for MSPs submitting ports at volume.
| Capability | Manual Process | Generic Wholesale Carrier | Viirtue ViiBE |
|---|---|---|---|
| LOA generation | Word doc template, filled manually | PDF template you complete | Auto-generated, pre-populated, branded |
| Customer signature | Print / scan / email | DocuSign add-on, billed separately | Native mobile e-sign, built in |
| Reseller branding | Manual rebrand of each document | Carrier's brand visible to your customer | Fully white labeled to your brand |
| Pre-submission field validation | None -- errors caught post-submit | Manual carrier review after submission | Automated validation before submission |
| New number ordering | Separate portal, often manual | Separate portal or ticket | Self-service, end-to-end automated |
| FCC compliance handling | Your responsibility entirely | Partial | Built into platform architecture |
| Billing and tax integration | None -- separate tools required | Add-on tools, additional cost | Native in ViiBE billing |
| End-customer portal access | None | Carrier portal, not your brand | Branded end-customer portal included |
Scroll to see full table on mobile.
The combination of a proprietary white label VoIP platform, integrated LNP automation, branded self-service number ordering, and native VoIP billing means resellers run a single system rather than stitching together three or four tools that each add cost and surface area for error.
How to Submit a Business Number Port and Build a Repeatable Practice Around It
Number porting will never be glamorous, but it does not have to be the most painful part of your week. The fundamentals have not changed: CSR-driven LOAs, careful field matching, FCC-aware timelines, clean documentation, and a pre-staged new service ready before cutover. What has changed significantly is the tooling available to resellers who take business number porting seriously as an operational discipline.
Resellers running a manual porting workflow in 2026 are absorbing the cost of rejections, customer friction, and delayed billing in a way that compounds quickly at scale. Every rejected port is a delay in your first invoice. Every slow cutover is a customer who remembers the rocky onboarding when their renewal comes up. Every branded LOA your customer signs under your company's name, rather than a generic carrier form, is a small but real signal that you are running a real business -- not acting as a pass-through for someone else's platform.
If porting is currently a bottleneck in your business, the FCC porting rules guide for resellers and the ViiBE self-service porting walkthrough both go deeper on the platform and regulatory layer. And if you want to see how native LNP, number ordering, telecom billing automation, and a full white label stack work inside a single platform built for MSPs, becoming a Viirtue white label partner is where that conversation starts. The Viirtue partner program is built for MSPs and IT providers who want margin ownership, brand control, and infrastructure that handles the operational complexity so you can focus on growth.
FAQ: How to Submit a Business Number Port
How long does it take to submit a business number port?
Filling out a clean LOA takes 10 to 20 minutes if you already have the CSR and recent bill in hand. Carrier processing after submission ranges from one business day for simple ports to 7 to 14 business days for typical business ports, and longer for complex multi-carrier or PRI orders.
What is the difference between an LOA and a CSR?
The LOA (Letter of Authorization) is the customer-signed permission slip authorizing the new carrier to port the numbers. The CSR (Customer Service Record) is the losing carrier’s official account record that the LOA must match. You need both: the LOA grants authority, the CSR validates accuracy.
Can I port a business number while keeping the same phone service running?
Yes. The whole point of LNP is no service interruption. Numbers stay active on the losing carrier until the FOC date, then translate to the winning carrier at cutover. Do not cancel service with the losing carrier until the port is confirmed complete.
What happens if my port request is rejected?
The winning carrier will return a rejection code (mismatch, missing PIN, address error, etc.). You fix the issue, resubmit, and the clock restarts. Each rejection typically adds 3 to 10 days, which is why pre-submit validation matters so much.
Do FCC rules require my current carrier to release my numbers?
Yes. Under FCC rules, a losing carrier cannot refuse a valid port request from a customer in good standing. They can require you to settle past-due balances, but they cannot use that as a generic blocker if the account is current.
Can I port toll-free numbers the same way?
No. Toll-free numbers are managed under a separate system (RespOrg changes) and must be submitted on their own LOA, separate from local numbers.
How does Viirtue's LNP workflow help resellers specifically?
Viirtue’s ViiBE generates a branded LOA, sends a mobile e-sign link to your customer under your company’s name, validates the data before submission, and provisions new DIDs self-service, all inside the same platform that handles your quoting, billing, and tax compliance. Your customer experiences your brand, not Viirtue’s.
Is number porting different for VoIP providers?
The legal framework is the same: interconnected VoIP providers are bound by FCC LNP rules. The mechanics are slightly different because VoIP carriers use their own number management systems, but for the end customer and reseller, the process looks identical: LOA, CSR, FOC, cutover.
