Recurring costs
Package subscription, annual commitment, payment schedule, telco service, number rental, call usage, taxes, extra storage and third-party licences.
Buying guide
Compare the complete service, including the carrier and implementation. A software subscription is only one part of the operating cost.
Cost checklist
Package subscription, annual commitment, payment schedule, telco service, number rental, call usage, taxes, extra storage and third-party licences.
Setup, number porting, gateways, handsets, headsets, installation, training and existing contract termination charges.
Renewal, cancellation notice, upgrades, downgrades, refunds if applicable, support hours, escalation and vendor SLA terms.
Capacity
Extensions describe how many staff or endpoints are provisioned. Concurrent calls describe the platform capacity in the published plan. External carrier calls also need sufficient telco capacity. Confirm how the proposed call flow consumes both capacities before purchasing.
Recording & data
Ask what the recording allowance measures, whether it resets, how recordings are retained and exported, what happens at the limit, where data is hosted and who can access it. Backup retention and recording retention are different terms.
Migration
Confirm number eligibility and carrier-dependent timing, assess analog devices, test supported apps and call routing, agree staff training and nominate a cutover contact. Decide how callers reach you during an internet, power or carrier outage.
Next step
Choose the operating model that fits your people, existing equipment and connectivity—not just the lowest advertised subscription. Read the guide →
Number eligibility is checked before a migration is promised. A cloud-phone package does not itself confirm that an existing number can move. Read the guide →
A monthly software rate is one part of your telephone budget. Use the same assumptions when comparing your current service with a proposed cloud PBX. Read the guide →
Staff count explains who needs an endpoint. Peak call demand explains how much conversation capacity the design needs. Read the guide →
A cloud PBX depends on the connection between your staff, supported clients and the service. Test the actual environment before cutover. Read the guide →
A listed capability is a starting point. Confirm the licence, account, implementation and data lifecycle needed by your business. Read the guide →
Use the same call scenarios for every proposal. Ask each supplier to mark an item included, additional work, unavailable or unconfirmed, and identify the configuration demonstrated.
| Call scenario | Answer to record | Acceptance evidence |
|---|---|---|
| Office-hours enquiry | Destination and fallback if unanswered | A test call reaches the agreed person or team |
| Everyone is busy | What the caller hears and where the call goes | Busy-period behaviour matches the written scope |
| Transfer to another team | Transfer method and unanswered destination | Staff complete the transfer on the intended devices |
| After-hours call | Message, destination and next-day handling | The agreed out-of-hours route is demonstrated |
Record the test date, responsible person and unresolved item alongside each answer. These are requirements to assess, not claims that every package includes the functions.
Prepare the capacity questions · Plan acceptance before migration
Use these practical comparisons when defining your requirements: