Architecture and ownership
Compare where call control runs, which local components remain, who configures each layer, how changes are handled, and which dependencies belong to the customer or another provider.
Business phone buyer’s guide
Compare the operating system—not only the feature list.
A useful comparison explains how calls should move, what users need, which dependencies remain, who owns each decision, and how the transition will be validated.
Six decisions before features
Start with requirements that can be verified.
A long feature matrix can hide the practical questions that determine whether a system fits the work.
Users and endpoints
Map desk phones, shared devices, desktop/mobile access, and special environments to actual roles. Do not assume every user needs identical equipment or that an unverified device is supported.
Numbers and call handling
Inventory main and direct numbers, extensions, caller identity, schedules, auto attendants, queues where configured, overflow, voicemail, on-call paths, and number-porting requirements.
Connectivity and continuity
Review office reachability, local network and power, traffic prioritization, managed edge, alternate paths, and eligible alternate inbound routing without treating one component as a complete-path assurance.
Operations and support
Confirm administration, change ownership, routine and emergency access, escalation boundaries, and responsibility when an upstream provider is involved.
Migration and validation
Prepare carrier records, future call flows, site readiness, staging, user preparation, cutover ownership, contingency decisions, acceptance tests, and follow-up.
Cloud versus on-premises
Compare responsibility and dependency—not labels alone.
Hosted and on-site systems place call control, equipment, updates, administration, connectivity dependencies, and support responsibilities differently. The conclusion depends on the current environment and approved requirements.
Ask of either architecture
- Which functions run in the provider platform and which remain at each location?
- What local network, power, endpoint, and internet dependencies remain?
- Who administers users, numbers, routing, updates, devices, and changes?
- What happens when a platform, connection, site, device, or power dependency is unavailable?
Do not infer
- That cloud removes local dependencies
- That on-premises removes carrier or support dependencies
- That either label proves uptime, security, compliance, capacity, or cost
- That a deployment model establishes every included feature
Requirements worksheet
Give each role, call path, and dependency an owner.
This worksheet prepares a comparison. It does not select products or approve a design.
People and work
- Users, departments, locations, schedules, and administrators
- Reception, office, mobile, remote, shared, queue, and special roles
- Desk-phone, shared-device, desktop/mobile, cordless, paging, room, and accessibility needs to evaluate
- Volume, concurrency, growth, and capacity questions to verify
Identity and routing
- Main, direct, shared, fax, alarm, entry, and other known numbers
- Normal, after-hours, holiday, no-answer, overflow, voicemail, and on-call behavior
- Outbound identity and emergency-calling requirements
- Porting records, authorization, eligibility, timing, and contingency questions
Locations and dependencies
- Internet paths, local network, Wi-Fi, cabling, power, and equipment
- Quality, managed-edge, and continuity requirements
- Manual recovery, live wired failover, persistent paths, and routing kept distinct
- Customer, Heritage, carrier, vendor, and other provider responsibilities
Operations and transition
- Administration, changes, support, escalation, and evidence ownership
- Messaging, reporting, recording, integration, and AI needs evaluated separately
- Inventory, staging, testing, training, cutover, contingency, and follow-up
- Acceptance criteria and unresolved exceptions
Pricing units and cost drivers
Ask what the unit includes—and what remains separate.
The managed phone-system foundation is generally structured per user/month. Heritage Connect is included for eligible users as a way to access that managed system; it is not free standalone phone service.
Review the complete pricing structureSupport model
Confirm routine, emergency, and provider-dependent handling.
For Heritage, routine support is available by phone, email, or the online ticket form during normal hours. The approved routine hours are Monday–Friday, 9:00 a.m.–5:00 p.m. Eastern.
- Routine accessPhone, support email, and the approved online ticket form during normal hours.
- Emergency accessCall and select the emergency-support option in the automated menu after hours.
- Initial contactThe on-call contact commitment is not a resolution, restoration, or service-level guarantee.
- Shared dependenciesConfirm ownership and escalation when another provider or local component is involved.
Questions for a proposal
Make each answer specific enough to test.
- Which roles, numbers, call paths, locations, endpoints, and optional services are included in this configuration?
- Which facts remain assumptions, dependencies, customer responsibilities, third-party responsibilities, or separate work?
- What records, authorization, site work, connectivity, power, equipment, access, and decisions are required?
- How will normal, exception, continuity, and selected optional workflows be tested and accepted?
- What are the billing units, included items, variable charges, third-party fees, taxes, terms, and change conditions?
- How are routine support, emergencies, changes, escalations, provider dependencies, and unresolved issues handled?
Preparing to transition?
Do not cancel an existing service before the port and cutover plan is confirmed.
Open the Migration GuideNext step
Compare a documented requirement—not a generic bundle.
Bring the worksheet to identify the configuration, evidence, commercial terms, and open decisions that still require confirmation.