Start with the business requirement, not a headline price.
Describe the users, locations, published numbers and calls the system must support. Include reception, queues, internal extensions, mobile applications and any AI role. The same number of people can produce very different calling patterns.
Ask whether the proposal is based on users, concurrent calls, service capacity or a package. Simultaneous calling matters when reception, departments and external transfers are active together. Have the supplier explain the capacity assumption in ordinary business terms.
The purpose of the quote is to show a complete working setup. A lower subscription figure is not a useful comparison if equipment, configuration, number charges or support are omitted.
Separate recurring service from one-time work.
A clear proposal makes the cost categories visible and identifies which assumptions can change the total.
| Category | Questions to ask | Why it matters |
|---|---|---|
| Service and capacity | What package and simultaneous-call allowance are included? | Shows the operating assumptions |
| Numbers and calling | Which numbers, destinations and usage charges apply? | Avoids treating all calls as included |
| Devices and apps | Purchase, rental, provisioning and support? | Separates equipment from service |
| Migration and training | Porting, routing, setup and onboarding scope? | Makes implementation work comparable |
| AI and integrations | Setup, included usage, overage and connection work? | Keeps optional services transparent |
| Call recording | Edition, configuration, storage, retention and archive charges? | Connects the recording purpose with ongoing ownership |
Include the devices and connections people actually need.
List reception devices, staff desk phones, headsets and supported mobile or desktop applications. Ask what can be reused and who is responsible for replacement, updates and troubleshooting.
Review office internet, power and network needs separately. A business that wants resilience may need additional connectivity or an agreed alternate answering destination. Do not assume every necessary network change is part of a phone subscription.
Ask whether numbers, common-area phones, shared reception and new locations change the cost. Confirm currency, taxes, billing frequency and the treatment of equipment delivery or site work.
Scope queues and callbacks in operating terms.
Describe how the team will answer, how callers wait and when a callback is offered. Features such as position announcements and automated queue callbacks depend on the selected edition, version and configuration.
Ask who designs prompts and schedules, configures queue membership and trains the team to manage availability. Include acceptance testing of the busy, no-agent and failed-callback scenarios. A feature name does not show that implementation work has been included.
Price call recording beyond the record button.
If recording is required, include the eligible service edition, setup, expected volume and retention period in the brief. Automatic recording and permission-controlled on-demand use can create different storage and administration needs.
Ask what recording capacity is included, what additional storage or archiving costs, and who manages cleanup, capacity alerts and archived files. Agree who can review, download or delete recordings and who is responsible for exported copies. Storage quotas can stop new recordings, so monitoring belongs in the operating scope. Include a sample-playback and permission test in implementation; transcription is a separately confirmed requirement.
Give AI Receptionist its own cost explanation.
Identify whether AI answers first during business hours, handles overflow, takes after-hours requests or combines these roles. That operating choice affects expected use and setup.
Request the recurring service, usage measurement, included allowance, overage, transfer or forwarding charges, and any knowledge or workflow configuration. Ask how usage is reviewed and what happens when an agreed limit is reached.
For standalone AI on an existing phone system, include compatibility testing and the route back to people. An automated queue callback and an AI-captured request are different workflows and should not be priced as if they are interchangeable.
Compare terms and ownership before deciding.
Read the service term, renewal, cancellation, equipment obligations and number-porting arrangements. Agree support channels, hours, escalation and the responsibilities retained by your business.
Prepare a common brief and ask each supplier to list assumptions and exclusions. If a proposal seems unusually cheap or expensive, compare what is actually being delivered before drawing a conclusion. The right next step is a clear quote and a demonstration of your own call flow, not an invented universal price.
Questions buyers ask.
Is Cloud Phone always priced per user?
No. Packages can use different licensing and service models, including capacity or simultaneous calls. User count remains useful for planning devices, onboarding and access, but ask how the actual proposal is calculated.
Does AI Receptionist cost extra?
It should be identified separately unless the proposal explicitly includes it. Review setup, recurring service, usage and integration or transfer charges rather than assuming it is part of a basic phone plan.
Is call-recording storage included in a phone quote?
Ask the supplier to state the included capacity, retention settings, archive arrangement and any additional charges. Recording availability depends on the selected service and edition. Assign responsibility for monitoring, deletion and exported files rather than assuming unlimited storage.
Can a smaller provider be less expensive?
Possibly, but price depends on scope and terms. Compare the full service, implementation and support model. A closer planning relationship can be valuable without requiring a promise that every quote will be cheaper.