A center has 80 agents. How many concurrent calls does it need? “80” may be excessive, while “20” may leave agents without lines during a busy hour. Seats and simultaneous conversations are different numbers.
Measure the actual peak
Take graphs from normal days and the busiest periods. Find the maximum active conversations at once, separating inbound and outbound. Include calls passing through IVR or queues if your system counts them against capacity. Make sure your PBX and provider mean the same thing by “channel” and “concurrent call”; otherwise their numbers cannot be compared.
Find the bottleneck
The limit may be the SIP connection, your PBX, queue rules or available agents. An incoming busy signal does not always mean external channels ran out. Match the failure time to station logs and provider records. If calls connect but audio deteriorates under load, check the agent network separately.
Ask how capacity changes
Confirm the available ceiling for the proposed setup, the cost of increasing it and the time needed to arrange it. If volume is substantial, run an agreed load check under controlled conditions. Do not generate traffic to real player numbers just to test capacity.
Keep busy-hour graphs and failed-call examples after launch. As the team grows, they show what needs changing first. Proton can provide a SIP trunk or cloud PBX, but full-system capacity is not defined by a single tariff item.
Want to test calls in your markets?
Tell us which countries, numbers and call flows matter to your team. We can discuss a pilot with real test calls.
Discuss a call test →