Write the short brief before meeting suppliers.
Describe the business, number of users and locations, who answers first and the most important problem to solve. List the numbers and devices you already use, then identify the requirements that would make the change worthwhile.
Keep requirements distinct from preferences. “Reception must connect a caller to either office” describes a business result. “We like this model of phone” may be a useful preference, but it does not explain whether the system solves the problem.
Give every supplier the same brief so differences in scope become visible. Include the desired decision process and any operational dates that affect a move, while leaving carrier dates to the actual porting review.
Score the things that matter to your team.
Use a simple scale: not addressed, described, demonstrated, and accepted in writing. Leave space for the evidence and any conditions.
| Requirement | Evidence to request |
|---|---|
| Company-wide extensions | Call and transfer between locations and a mobile user |
| Reception and departments | Your main incoming call and no-answer route |
| Queues and announcements | Busy team, waiting caller and no-agent outcome |
| Automated callback | Offer, return call and unanswered callback |
| AI role | Approved business-hours or fallback conversation and human handoff |
| Call recording | Agreed scope, sample playback, reviewer permissions and storage ownership |
| Migration | Number dependencies, cutover plan and acceptance owners |
| Support | Channels, hours, escalation, responsibilities and commercial terms |
Make the demonstration about your difficult call.
Ask the supplier to show the exception your team struggles with, not only a clean incoming call. A busy receptionist, someone away from the desk or an unavailable branch can reveal more than a long feature tour.
If queues matter, listen to the actual announcements and test the configured callback option. If mobile access matters, use the proposed supported app and check availability, incoming calls, transfers and caller ID. If AI matters, ask it something outside the approved scope and request a person.
If recording matters, use a fictional test conversation. Check automatic or on-demand behaviour, the approved caller notice, playback quality and who can listen, download or delete. Sign in as the intended reviewer and a restricted user. Ask who owns retention, capacity monitoring and archives, and include any storage charges in the comparison.
Record what was demonstrated, what still needs configuration and what depends on the selected plan or software version. A statement that a platform supports a feature is different from acceptance of your finished setup.
Compare the proposal and operating relationship.
Ask for recurring service, capacity, numbers, usage, devices, migration, training and optional AI as understandable items. Read the contract term, renewal, cancellation and ownership arrangements.
For a smaller provider, examine the proposed planning and change process: who understands your routing, who coordinates the move and how issues are escalated. For any supplier, check the actual support commitment instead of assuming service quality from company size alone.
The important comparison is the complete relationship and working outcome. A recognizable telecom name and a lower headline price are not substitutes for a clear responsibility map.
Choose the acceptance criteria before the cutover.
Name a business owner and a contact at every location. Agree how you will test numbers, extensions, queues, callbacks, mobile users, schedules and AI routes.
Keep unresolved items visible and decide which prevent launch. Agree the fallback and rollback approach before the move. Once the setup is accepted, retain the routing plan and the support instructions so the business can manage future changes.
Questions buyers ask.
Should we choose the provider with the most features?
Choose the provider that can meet and demonstrate the requirements that matter to your operation. Extra features may add complexity without improving the calls your team handles.
How do we compare a small provider with a large telecom?
Ask both to explain planning, migration, change handling, issue ownership and support terms. Evaluate the named process and evidence rather than assuming that size alone guarantees a better result.
Can we start before knowing every technical detail?
Yes. Start with the business problem, users, locations and current setup. The discovery process should identify the technical details and dependencies that are needed for a dependable proposal.