August 18, 2026
How Many Phone Lines Does My Office Actually Need?
How many phone lines a business needs is a question that outlived its own unit, which is why offices overbuy. A line was a copper-era bundle of one call path and one number. Those are separate purchases now: concurrent call capacity, and phone numbers. A ten-person office typically needs five or six of the first, two or three of the second.
Why "lines" stopped being one thing
On a copper installation, a line was physical. One pair of wires carried one conversation and had one number attached. Two simultaneous calls meant ordering two lines, and each came with its own number whether you wanted it or not.
Hosted phone systems unbundle that. Numbers are records pointing at a destination. Capacity is how many conversations the system carries at once. Neither requires the other, and buying them together is now a habit rather than a constraint — an expensive one. An office that ordered eight copper lines in 2009 tends to ask for eight of something in 2026, without anyone asking whether eight conversations ever happened at the same time.
The four quantities you are actually planning
Separate these before you count anything. They are different numbers, and conflating them is the entire problem.
Quantity | What it counts | Typical size for 10 people |
|---|---|---|
Extensions | People and places that need to be reachable | 12–14 |
Devices | Physical and software endpoints; one extension can be on several at once | 12–18 |
Concurrent call paths | Simultaneous conversations with the outside world at peak | 5–6 |
Phone numbers (DIDs) | Numbers published or routed to a destination | 2–3 |
Only the third one is what "lines" used to mean. It is almost always the smallest number in the table, and it is the one people inflate.
How do you calculate concurrent call capacity?
Use peak-hour arithmetic rather than headcount, from two inputs your call history already holds.
Multiply the calls in your busiest hour by the average call length in minutes, then divide by 60. That is your load. Provision enough paths to absorb it comfortably.
A busy front desk. Sixty calls in the busiest hour, averaging three minutes. 60 × 3 = 180 minutes of talk in a 60-minute window: a load of 3. Eight paths puts the chance of a caller finding everything busy under 1%. Five puts it around 11% — one caller in nine rejected during your busiest hour.
A professional office. Twenty calls in the busiest hour, averaging four minutes. 20 × 4 = 80 minutes, a load of 1.33. Five paths puts blocking under 1%.
Two observations. Capacity requirements grow much more slowly than call volume, because calls overlap less than intuition suggests. And the last couple of paths do most of the work — going from 5 to 8 in the first example cuts blocking by more than a factor of ten.
Without call history, count the phones that ring on your main number and the people making outbound calls at the same time of day, then add headroom. After a month, call reporting gives you the real peak-hour figures.
A rough estimate when you have no data
Derived from the arithmetic above, assuming a typical office worker is on an external call something like 15% of the working hour:
Staff who use the phone | Suggested concurrent paths |
|---|---|
5 | 3–4 |
10 | 5–6 |
15 | 6–8 |
25 | 9–12 |
These are starting points, not rules. Two things move them. A dedicated phone role — reception, intake, dispatch, scheduling — pushes the number up, because that person is on the phone most of the hour. A team doing field work or heads-down analysis pushes it down.
Bandwidth is rarely the constraint. Eight concurrent calls need roughly 800 kbps each direction. VoIP network requirements covers the specifics; the short version is that quality problems come from jitter and SIP ALG, not from running out of megabits.
Do internal calls use capacity?
No. Extension-to-extension calls stay on your own phone server and never touch the public network, so they consume no external call paths.
That matters for offices with heavy internal traffic — a clinic where the front desk calls back to the exam rooms twenty times an hour, or a shop where the counter calls the bays. All of it is invisible to capacity planning.
One clarifier, since it gets counted as a line by mistake: an extension registered on a desk phone, a browser web phone, and a desktop app at once is still one extension. One Signal extension can register on several devices at the same time, and they all ring together. Devices are not capacity.
How many phone numbers do you need?
Fewer than most offices buy, and for entirely different reasons than capacity.
Buy a number when it needs to be published separately or routed differently: a main number, a second location that wants a local presence, a department with its own printed number, a legacy number still receiving calls.
Buying numbers for capacity is the copper-era reflex and it does nothing. Ten numbers pointed at the same auto attendant do not increase how many callers can be connected at once. Call paths determine that.
Each number carries a monthly charge, so unused ones are drag on the bill. Adding phone numbers and number strategy covers what to keep, how many phone numbers a small business should have works through the cases, and toll-free or local covers that choice.
What happens when all your paths are busy?
The caller gets a rejection — the worst outcome your phone system can produce, worse than a long hold and worse than voicemail, because neither of you learns anything.
Size capacity so this is rare, and put a call queue in front of it. A queue holds callers with music and position information rather than turning them away, absorbs bursts that exceed your answering capacity, and records the wait so you can see what happened. Live queue status shows who is logged in, who is waiting, and how long. Call queue setup covers configuration.
A queue does not replace capacity. It converts a rejected call into a managed wait, which is a better place to stand while deciding whether to add paths or add people.
What overbuying costs you
Money, and the wrong diagnosis. Excess paths and unused numbers are recurring charges against capacity nobody uses — waste, usually fixable in one conversation. Misattribution costs more: offices that buy extra capacity to solve missed calls usually find the calls were never blocked. They rang a group nobody was in, hit an after-hours route at 4:45 because the timezone was wrong, or landed in a voicemail box nobody checks. Read your call history before buying more of anything.
Frequently asked questions
How many phone lines does a business need?
Fewer than headcount, and the modern equivalent is concurrent call paths rather than lines. A ten-person office typically needs five or six; twenty-five people typically need nine to twelve. Calculate from peak-hour volume and average call length instead of staff count, since offices with a dedicated phone role need meaningfully more.
What is the difference between a phone line and a phone number?
A phone number is a routable address that points calls at a destination. A call path is capacity for one simultaneous conversation. Copper bundled them; hosted systems do not. Ten numbers pointed at one auto attendant do not let ten people talk at once, and one number can support as many simultaneous calls as you provision.
How do I calculate concurrent call capacity?
Multiply calls in your busiest hour by average call length in minutes, divide by 60, and provision enough paths to absorb that load with headroom. Sixty calls averaging three minutes is a load of 3, which needs about 8 paths to keep blocking under 1%. Call reporting gives you both inputs after a month.
Do internal calls use up call capacity?
No. Extension-to-extension calls stay on your own phone server and never reach the public network, so they consume no external call paths. A clinic where the front desk calls the exam rooms constantly can ignore that traffic entirely when sizing capacity. Multiple devices on one extension are also not capacity.
What happens when all my call paths are busy?
The caller is rejected without reaching your system, which teaches neither of you anything. Size capacity so this is rare, and place a call queue in front of your answering team so bursts become a managed wait with music and position information rather than a failed call. The queue's reporting then tells you whether to add paths or people.
If you want to know what your actual peak looks like, we can size it from your current call volume rather than guessing. Bring a recent bill or a month of call history and we will work it out with you.