Give every number a purpose
Create an internal register with a number label, current provider, country, type, purpose, owner and proposed disposition. Include advertised main lines and less visible secondary numbers. Keep the actual register private; our local tools need only anonymous totals and do not receive telephone numbers.
Separate service from billing
The business you pay may use an underlying carrier. Record both where the provider confirms them. Distinguish a billing account from the number-level details required for porting. A number appearing on a bill does not answer every portability or authority question.
Decide what is outside the order
Mark numbers that stay, retire or require specialist investigation. Confirm the implications for bundles and related services before changing anything. Keep an explicit unresolved category rather than forcing every number into move or cancel. A partial port needs a clearly bounded scope.
A fictional inventory correction
An office initially lists one published number. A bill review reveals a second reception line and a fax dependency. The team assigns the second line to the transfer scope and leaves the fax pending provider confirmation. The corrected inventory changes the plan before any order is submitted.
Reconcile the scope with two records
Compare the proposed number list with an authorised billing record and the business's own list of advertised contact routes. These records answer different questions: what is charged and what customers are told to use. Investigate a mismatch instead of deleting the unfamiliar entry. Add a disposition column with move, retain, retire or unresolved, then total each category. An entry marked retire still needs authority and dependency review; it is not an instruction to cancel automatically. Use stable internal labels so later support notes can refer to the same item without circulating numbers widely. Have a second responsible person confirm the scope where practical. The aim is not a perfect inventory of every system, but a reliable boundary for this particular order.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- CloudTalk porting requests — Merchant documentation · help.cloudtalk.io · Merchant-controlled · checked 2026-09-28
- CloudTalk port preparation — Merchant documentation · help.cloudtalk.io · Merchant-controlled · checked 2026-09-28