The Number Porting Playbook That Prevents Cutover Disasters

Every VoIP provider eventually has a port day disaster story. Numbers that go dark for six hours, main lines that route to voicemail during business hours, or a rejection that pushes cutover into the following week. Almost every one of these is preventable with a tighter process. The failures cluster around a small number of root causes, and once you fix those, port disasters become rare enough to be memorable.

Assign a named porting coordinator to every deal above five seats. The coordinator owns the LOA, the CSR request, the FOC date, and the customer communication. If a port is anyone in the operations queue, it is nobody. Ownership is the single highest leverage change you can make. For deals above fifty seats, that coordinator should be on a first name basis with the losing carrier port desk.

Get the CSR from the losing carrier before you write the LOA. Customer service records are the source of truth for billing telephone number, account number, and authorized user. Guessing any of these guarantees a rejection. Ask the customer to request their CSR early, ideally during the contract signing phase, and do not submit an LOA without it in hand.

Match the LOA to the CSR field by field. The business name must match exactly, punctuation included. The service address must match, not the billing address, and not what the customer thinks their address is. Suite numbers, street abbreviations, and the difference between road and drive have all killed ports. Build a two person review step where a second coordinator visually compares the CSR and LOA before submission.

Set the FOC date at least ten business days out for anything over ten numbers. The porting standard is faster on paper, but real world tier two and tier three carriers routinely miss the fast turnaround windows. Give yourself margin so the customer expectation is a smooth cutover, not a race. Under promising and delivering early builds trust that pays off for years.

Communicate the cutover window in the customer's language. Do not say the port will happen between nine and one Eastern on Thursday. Say the phones will ring in the old system until roughly ten am, may briefly not ring, and will start ringing in the new system by lunch. Then confirm the receptionist knows to test both systems. Send a one page cutover briefing to every stakeholder the day before.

Have a rollback plan. If the port fails after the FOC time has passed, the losing carrier can sometimes reverse the port within twenty four hours, but only if you request it immediately and only if the customer has not yet disconnected the underlying service. Never let a customer cancel their old service until the new one has been running cleanly for at least seventy two hours. Put this in writing in the welcome kit.

Document every port. Rejection reasons, root causes, and what changed on the next attempt. Over time this becomes your porting playbook, and it is worth more than any tool you could buy. New coordinators reach competence in weeks instead of months when they can read the history of every port your company has ever run.