A number inventory is an organization’s record of every phone number it holds: main lines, direct inward dialing (DID) numbers, toll-free numbers, fax and alarm lines, and numbers kept in reserve. For each number, it records which provider and account it sits on, which site and person or function it belongs to, what it routes to, what it costs and whether it is being ported. It is a buyer-side working document rather than a formal standard. Providers also use the phrase for their own stock of numbers available to assign, which is a different thing.
At a glance
- Lists every number the organization holds, across all providers, accounts and sites.
- Records type, provider, account, site, assignment, routing, cost, owner and porting status, and optionally how each number relates to emergency calling.
- Makes migrations and ports safer by showing exactly which numbers need to move.
- Finds unused numbers that are still billing, and numbers that can’t be released without breaking something.
- Usually maintained alongside a broader telecom inventory, or as part of a telecom expense management program.
What problem it solves
Phone numbers accumulate. Offices open and close, employees come and go, providers change, and blocks of numbers are ordered “just in case”. Over time, few people know how many numbers the organization has, which carrier each one is with, or what happens when someone dials it.
That causes real problems. Numbers that are billed but unanswered waste money and can miss callers. During a provider change, numbers left off the port request may stay behind, keep billing or be lost entirely if the old account is closed. Stale records also make it harder to check emergency calling, because numbers, users and devices move without anyone updating where they are. A number inventory gives one place to answer: what do we have, where is it and what is it for?
How it works
Collecting the numbers. Start from each provider’s portal or customer service record, invoices and the phone system’s configuration. Include toll-free numbers, which may sit with a different provider than local numbers.
Recording key fields. Typical fields are: the number; type (main, DID, toll-free, fax, alarm, elevator, reserved); provider and account number; billing telephone number; site; what the number is assigned to or routes to; monthly cost; business owner; and porting status. Port-out PINs, if stored, should be handled as sensitive.
Emergency calling. An optional field can note how a number relates to 911, such as which emergency location record or callback number it uses. On many multi-line and cloud phone systems, the emergency location is attached to an extension, user, device or a location detected from the network, rather than to a phone number, and some 911-capable extensions have no public number at all. That location data, ideally a dispatchable location, is usually maintained in the phone system or a 911 service, outside the number inventory.
Reconciling. Compare the three sources. A number on a bill but not configured in the phone system may be a zombie line. A number configured but not on any bill may be on an account nobody is watching.
Keeping it current. Tie updates to the moves, adds, changes and disconnects (MACD) process, so adding, moving or releasing a number updates the inventory. Reconcile in full on a schedule and before migrations, renewals and number ports.
Where it lives. Small organizations often use a spreadsheet. Larger ones may track numbers in a telecom inventory or expense management platform, or rely on their UCaaS provider’s number management, keeping in mind that a single provider’s portal only shows numbers on that provider.
For programs that keep telecom services, numbers and bills under control, see our telecom expense management solution page.
When it matters for buyers
- Moving to SIP trunking or a cloud phone system. The port request should cover every number that needs to move, and nothing that should be released.
- Mergers, acquisitions and office closures. Numbers spread across inherited accounts are easy to lose.
- Cutting telecom costs. Unused numbers and number blocks are a common, low-effort saving.
- 911 compliance reviews. The number inventory helps, but audit every 911-capable endpoint, user and device separately, including extensions without their own number, because emergency location often is not tied to a number.
- Contract renewals. Knowing your number count and types helps compare offers fairly.
Questions to ask vendors
- Can you export every number on our account, with type, site, assignment and monthly cost?
- Where is the emergency location for each user, device and extension maintained, and can we export it to check against our number inventory?
- Will you reconcile our number list against the old carrier’s customer service records before porting?
- How do you handle numbers we want to keep but not use yet, and what do reserved numbers cost?
- Can we hold port-out PINs or port protection on our numbers?
- If we release a number, how long before it is reassigned, and can we get it back?
- Do you report on numbers with no recent call activity?
How it differs from a telecom inventory
A telecom inventory records the services an organization pays for, such as circuits, lines, trunks, wireless plans and their contracts. A number inventory focuses on the phone numbers themselves, which can outlive any single service or provider and move between them through porting. In practice, the number inventory is often a section or companion list of the telecom inventory, linked by provider, account and site.