VoIP phone systems for small business

Licensing is per seat, which makes headcount a pricing decision

The dominant commercial model licenses one extension to one named person, and the licence is charged whether or not that person is on a call. That is simple and predictable, and it is also the mechanism by which a phone system's cost grows: hiring adds licences, and seasonal or shift-based staffing adds licences for people who are rarely on the phone at the same time. Call centre platforms answer this differently, licensing concurrent agents instead of named users. The distinction matters at the point where your business has more people who might answer a phone than people who are on one simultaneously, and it is worth establishing which of those two populations you actually have before choosing a model.

• Count named users, then count peak simultaneous callers; they are different numbers.
• Ask what happens to licences for part-time, seasonal or shared-desk staff.
• Check whether common areas and devices such as lobby phones need a licence.
• Confirm which features require a higher edition rather than an add-on.

Emergency calling is a configuration obligation, not a feature

Two federal requirements shape a commercial phone deployment, and both are about getting the right location to the right dispatcher. For multi-line telephone systems, direct dialing of emergency services without any prefix is required, along with notification to someone on site when such a call is placed. Separately, emergency calls must convey a dispatchable location — information precise enough to identify where within a building the caller is, not merely the building's street address. In a multi-site business or one with remote and softphone users, that makes location data a maintained record rather than a one-time field: it has to be correct for each device and stay correct when people move desks, work from home or change floors.

• Confirm direct emergency dialing works with no prefix on every handset and softphone.
• Have the provider state how dispatchable location is supplied, per site and per user.
• Make someone responsible for updating location records when staff move.
• Test the notification to on-site staff, not just the call itself.

Caller authentication and text registration travel with the phone system

Caller identity on the public telephone network is now authenticated rather than asserted, through the framework carriers use to sign and verify calls originating on IP networks. A business whose outbound calls are not signed correctly finds its calls labelled as suspect, which is a deliverability problem before it is a technical one. The same applies to text messages sent from a business number: application-to-person messaging on ten-digit long codes requires brand and campaign registration through the industry registry, and unregistered traffic is blocked or filtered by carriers. Both sit outside the phone system's interface but inside the deployment, and both take time to complete, so they belong in the migration plan rather than after it.

• Ask the provider how outbound calls are authenticated and what the caller sees.
• Register business text messaging before any campaign is scheduled, not after.
• Allow lead time: registration is a review process, not a setting.
• Confirm who owns the registration if you change providers.

Number porting is a project with documents and a schedule

Porting numbers is a governed process with a paperwork trail, and the failure mode is always the same: service is cancelled before the migration is proven. Treat it as a project with an owner. Inventory every number and what depends on it, because the numbers businesses forget are the ones attached to something other than a phone — alarm panels, elevator and emergency lines, fax machines, older point-of-sale equipment and any line a landlord or landlord's contractor maintains. Keep the existing service running until the new configuration is tested end to end, including inbound routing, after-hours behaviour and emergency calling.

• Inventory numbers by what uses them, not by who answered them last.
• Identify numbers serving non-phone equipment before the cutover date.
• Keep existing service active until testing is complete.
• Confirm portability and timing for each number rather than assuming it.

The integrations decide the edition, and the edition decides the price

Most modern phone systems can do most modern telephony. What separates them commercially is integration: whether the contact record appears on screen when a customer calls, whether call activity writes back into the system of record, whether the same platform handles chat and messaging into the same queue as voice. Those requirements generally live in a higher product edition or need a separate integration licence, which is why a quotation built on the base edition can look dramatically cheaper than the system the business actually described. Demonstrate the integration in the edition you are being quoted, using your own system, before signing.

• Name the two or three integrations that genuinely matter operationally.
• Insist the demonstration uses the exact edition being quoted.
• Check whether integration usage is metered separately.
• Ask what breaks if you change your CRM or ticketing system later.

What to gather, and how HighGround helps

Bring a number inventory with current use, a headcount split into named users and peak simultaneous callers, the call flows you cannot afford to miss, the systems the phone system must integrate with, and the current agreement and end date. HighGround sources business communications through the AppDirect catalog and scopes each site separately. Availability, pricing and terms depend on your locations, the providers serving them and the term, so no two deployments price alike. An inquiry places no order and switches no service, and HighGround may receive compensation from a provider on a completed purchase.

• Number inventory with the equipment and systems behind each number.
• Headcount as named users versus peak simultaneous callers.
• The call flows that carry the most revenue or the most risk.
• Current agreement, term and end date.

A multi-site migration is several migrations, run at once

A distributed business does not port one number, it ports a batch, and every site is its own order. The rules are written per order. A simple port — generally a single line without complex switching or network element changes — must be processed within one business day, while anything involving multiple lines, a PBX arrangement or a mismatch in the customer record becomes a non-simple port with a longer clock. Implementation guidance treats a complete and accurate request the losing carrier receives early in the business day as eligible for activation that night, and anything arriving after the daily cut-off as received the next day. The practical consequence is that a project of forty sites moves at the pace of its worst-prepared site, and the sites that stall are the ones whose stored service record no longer matches reality. Reconcile the inventory against what actually rings at each site before the order goes in, because the number nobody answers is the one that gets missed in the cutover — a main line, a fax, or a line a landlord's contractor maintains.

• Confirm the authorised name, service address, account number and PIN on every account before submitting.
• Expect simple ports to move in about a business day; treat multi-line and PBX orders separately.
• Submit before the daily cut-off if same-night activation matters for the cutover plan.
• An interconnected provider must not delay a valid port request or contract away the right to port.

Local breakout and what keeps ringing in an outage

Moving call control to the cloud removes the server from the closet, not the dependency on the building's internet, power and firewall. A hosted platform can be fully available while one office cannot reach it because local broadband, DNS or Wi-Fi failed; an on-premises PBX can keep internal calls running through a WAN outage but loses outside lines unless it has local trunks or a cellular fallback. A design that keeps a site's calling alive when its data circuit dies is usually built on local breakout — sending that site's public calls through a local trunk or gateway rather than funnelling everything back to the cloud or to headquarters. Local breakout buys independence and costs attention: each site then needs its own trunk capacity, emergency address, firewall policy, monitoring and failover plan, so it is a deliberate trade rather than a default. The question to settle before signing is not which platform is more reliable in the abstract, but which failure the business can tolerate at each site, and whether the design answers it.

• For each site, list the primary and backup internet circuit, the demarcation owner and the endpoint UPS runtime.
• Decide what an inbound caller hears when a site's circuit fails, then test it outside business hours.
• Two circuits are not diverse if they share a route or a carrier; ask who owns the last mile on each.
• Confirm what the provider can do on the platform side when it detects a site has gone unreachable.

Who owns the phone system after cutover

A migration ends when the numbers are cut over, not when the system is running. What decides whether the estate stays healthy is who owns each moving part: who adds a user when someone is hired at a branch, who moves an extension when a desk changes, who keeps the emergency address current when a floor is reconfigured, and who maintains the inventory of numbers that are not phones — the alarm panel, the elevator line and the fax at each site. A hosted provider manages the platform; it does not know that a warehouse changed floors. Write the split down per site, name the person who raises changes, and keep the number inventory somewhere the business owns rather than only inside a provider portal, so that it survives a change of supplier. Set the expectation at go-live rather than at the first dispute: what counts as a change, how it is requested, and who carries the cost when a site visit is needed.

• Name the person authorised to raise adds, moves and changes, per site.
• Keep a business-owned number inventory, not a provider-only one you cannot export.
• Assign ownership for emergency-address updates whenever a floor or desk layout changes.
• Agree how change requests are handled and how response times will be measured.

PUT THE OPTIONS SIDE BY SIDE

Your comparison checklist

Common questions