HyperCloudSoft · Singapore
Extensions and simultaneous calls: size both.
Staff count explains who needs an endpoint. Peak call demand explains how much conversation capacity the design needs.
Extensions do not describe peak demand
An extension identifies a user or endpoint in the phone-system design. Twenty extensions can serve a team of twenty, but that number does not tell you how many calls happen together. Shared phones, multiple devices and staff roles also need review before provisioning.
Use the published capacity language
The CP10–CP90 office tiers publish concurrent calls. CPSC packages publish simultaneous conversations and unlimited extensions. Confirm how your proposed internal calls, transfers, queues and external calls consume capacity; do not infer a per-leg counting rule from a plan label.
External carrier capacity is a separate dependency. Having sufficient PBX capacity does not purchase carrier lines or establish the number of external calls your telco service can carry.
A worked office example
CP20 lists 20 extensions and 8 concurrent calls at SGD 79/month. If the requirement is 20 extensions and 12 published concurrent calls, CP30 is the next standard tier meeting both allowances: 30 extensions and 12 calls at SGD 119/month. Both rates require annual commitment and exclude telco and external calls.
This example compares published PBX allowances only. A specialist must still confirm carrier sizing and the exact use of capacity in the intended call flow.
Describe your busiest period
- Which staff or teams answer incoming calls?
- How many outbound calls overlap with incoming calls?
- What happens to callers while they wait, transfer or reach voicemail?
- Do remote sites and internal calls share the same proposed capacity?
- How much growth should the agreed design allow?
If the answers are unknown, request an assessment rather than buying from staff count alone. Compare capacity tiers or use the plan finder for a provisional starting point.
Discuss your requirements
Record demand before selecting capacity
Observe representative busy periods rather than selecting a package from headcount alone. Use a separate row for seasonal peaks or planned growth. Leave unknown values unconfirmed rather than entering zero.
| Observation | What to record | Question for the supplier |
|---|---|---|
| People and endpoints | Staff, shared phones and working locations | How will extensions be provisioned? |
| Busy-period calling | Time window and observed overlapping activity | How does the proposed PBX count this activity? |
| External calling | Inbound and outbound overlap | What carrier capacity is required separately? |
| Waiting and transfers | Observed queue and transfer behaviour | Does this change the required platform capacity? |
| Growth assumption | Proposed increase and confidence in the estimate | What should be reviewed before demand increases? |
Agree how the resulting design will be tested. An unlimited-extension allowance does not replace workload assessment. Keep personal caller information out of this planning worksheet.
Discuss call-centre requirements · Check the calling environment