How Many Telephone Lines or Concurrent Calls Does a Business Need?

Worked SIP capacity examples

These examples illustrate a method, not a fixed purchasing recommendation. Confirm how the proposed PBX and provider count call legs before selecting capacity.

Business example	Observed or planned overlapping demand	Planning implication
Small office with 12 employees	Three inbound conversations and two outbound calls at the same moment	Five external call legs before any allowance for queues, forwarding or growth
Medium office with 60 employees	Ten inbound conversations, four outbound calls and three connected waiting callers	Seventeen external call legs before agreed headroom
Contact centre with 20 agents	Twenty active customer conversations and eight connected callers waiting	Twenty-eight external call legs; agent count alone understates demand

For the medium-office example, suppose the business also expects three additional overlapping calls after a planned recruitment round. The starting requirement becomes twenty call legs before any further justified contingency. The provider and PBX licence must both support the agreed design; their capacity tiers and counting rules may differ.

Check the busiest interval rather than adding peaks from departments that never overlap. Also consider capacity on any fallback route. More channels cannot compensate for too few available agents, so review waiting times and staffing alongside the trunk limit.

Use the SIP channels, DDI numbers and extensions guide to identify forwarding and queue paths, then compare the resulting capacity in our current SIP trunk pricing and included services.

Businesses often ask how many telephone lines they need, but modern systems are usually sized by concurrent calls rather than by one physical line per employee. The right capacity is the highest realistic number of calls that must be carried at the same time, with a sensible allowance for peaks and growth.

There is no dependable ratio that suits every organisation. A 50-person professional office may have fewer simultaneous calls than a ten-person appointment team. Good sizing begins with evidence from the business itself.

Telephone lines, channels and concurrent calls

A traditional analogue line normally carries one call. Digital and SIP services use channels or capacity that can carry several calls over shared connectivity. A concurrent call is one active call at a particular moment, whether inbound, outbound or—in some licensing models—internal.

Extensions and telephone numbers are different. A business may have 100 extensions and 40 direct-dial numbers but need only 15 external calls at once. Conversely, a smaller call-handling operation may require capacity close to its user count during campaigns or service incidents.

When reviewing business phone system capacity, define exactly which call types consume a channel or licence. Supplier terminology is not always identical.

Start with call records

Use call-detail records from the current system where available. Look at busy periods across several representative weeks, not only daily averages. Record the maximum simultaneous inbound and outbound calls, queue demand, abandoned calls and occasions when callers received busy treatment.

Include exceptional but foreseeable events: Monday-morning demand, invoice runs, appointment reminders, marketing campaigns, weather disruption, deadlines and service outages. A capacity plan that covers an average day but fails at the moment customers most need help is not adequate.

Estimate when data is unavailable

If the old system cannot provide reliable reports, interview each team. Ask how many people make or receive calls during their busiest half hour, how long calls last and whether staff work in queues. Observe reception and customer-facing departments rather than relying solely on headcount.

A basic worksheet can list departments down one side and peak inbound, outbound and internal calls across the top. Combine overlapping peaks, then apply a measured contingency. Avoid multiplying every team’s individual worst case if those peaks never happen together.

Allow for queues, conferences and internal calls

Queued callers may consume capacity while waiting. Conference calls can use several call legs, and forwarded calls may use both an inbound and outbound channel. Some PBX licences also count internal calls or calls to voicemail and other services.

Confirm the design with the chosen provider. A managed business SIP trunk should be configured with enough channels for the agreed traffic profile, but extra capacity should have an operational justification.

Consider call length and working style

Teams making short transactional calls create a different traffic pattern from advisers holding long consultations. Remote and mobile users may place calls through the business platform, increasing central capacity even though they are not in the office.

Outbound diallers, contact-centre integrations and automated reminders can create sudden bursts. These functions should have explicit limits so they do not prevent ordinary customer calls.

Build in growth without excessive waste

Allow for planned recruitment, new sites, campaigns and service changes over the contract term. Capacity should not be so tight that one additional team causes congestion, but buying for an undefined maximum can waste money.

Ask how quickly capacity can be increased and whether it changes licence, hosting or trunk charges. A scalable service may justify a smaller initial margin when upgrades can be implemented quickly and safely.

Capacity and resilience are separate

Twenty channels on one unavailable route provide no service. Consider whether inbound and outbound traffic can fail over, how numbers are rerouted and whether alternative connectivity has enough bandwidth. Resilience design should include likely failure modes rather than simply doubling the channel count.

A repeatable sizing method

• Collect peak concurrent-call data across representative periods.
• Add queue, conference, forwarding and automated-call requirements.
• Confirm which call types count under the proposed service or licence.
• Model known growth and exceptional operational peaks.
• Add a proportionate contingency and agree monitoring thresholds.
• Review capacity after launch using actual reports.

What happens when capacity is exhausted?

The result depends on the platform and call direction. New outbound calls may be rejected, while inbound callers may hear busy treatment or follow an alternative route. Queued calls can also occupy capacity, so a sudden increase in waiting callers may affect the ability to place other calls.

Agree alarms and reporting before this occurs. A provider should be able to identify when usage repeatedly approaches the configured limit and discuss whether the cause is growth, a one-off event or an inefficient call flow. Capacity increases should be controlled changes rather than emergency guesses.

Review capacity after migration

The initial estimate should be tested against live data after employees have settled into the new system. Compare peak concurrency, queue wait, abandoned calls and failed attempts with the assumptions used in the design. Remote working, new applications and changed opening hours can alter demand.

Schedule a review after the first month and again before renewal. Reducing clearly unused capacity may save money, while early expansion can prevent avoidable busy periods. Keep the method and evidence so future decisions remain consistent. When budgeting for a managed system, compare your peak calls and user count with our Hosted 3CX package capacities and monthly prices; both limits need to fit.

The answer is therefore not “one line per employee”. It is enough concurrent capacity for real peak traffic, plus a justified margin and a route for expansion. I.T Communications can review call records and design the PBX and SIP capacity together. Ask our team for a practical capacity review.