Beyond the Feature List: The Hidden Work of a UK VoIP Switch

A VoIP demonstration is designed to impress. Calls follow staff across devices, voicemail arrives as email, queues report in real time and the system integrates with a CRM. For a UK SME, those features can be genuinely useful. But the feature list is not where most migrations fail. The difficult work lies in the unglamorous details: listing every number, mapping every call route, preparing staff for different handsets and testing the service before the old one is switched off.

Procurement therefore needs to look beyond the monthly price and the demonstration. A VoIP switch is part purchase, part operational project and part change programme. The supplier that wins on features may not be the one that manages porting, support and cutover well.

Features are the easy part

Most reputable providers can offer call groups, auto-attendants, voicemail-to-email and softphone apps. Differentiation often appears in support hours, porting experience, contract flexibility and how much help is included. Those are the areas that determine whether the migration is calm or chaotic.

Before comparing quotes, build an inventory. List every telephone number, including the main number, direct dial ranges, fax lines and any numbers used for alarms or payment systems. Record hunt groups, reception routes, out-of-hours messages and call recording requirements. Note which handsets, headsets and cabling are in use, and whether staff rely on desk phones, mobiles or computers. Include any integrations with CRM, helpdesk or accounting systems.

This inventory does more than support a tender. It exposes assumptions. A business may discover that a number it thought was unused is connected to a lift phone, a security system or a card terminal. Those details matter before porting, not after.

Number porting is a project, not a request

Porting is often treated as an administrative step. In practice, it is a scheduled operational event with dependencies. The losing provider must release the numbers, the gaining provider must coordinate the port, and the business must know what will happen to each service during the change.

UK SMEs should confirm which numbers are being ported, the requested date and time, and what happens to any numbers not being ported. Check contract notice periods with the existing supplier. Do not cancel the old service before the new one is working. Ask how the supplier handles port rejection, partial ports and emergency access.

A common mistake is to port the main number first because it feels symbolic. It is usually safer to port secondary numbers or a test range first, provided the supplier supports that approach. The main number should move when the routing, handsets and support are ready.

Routing deserves a diagram

Call routing is where business logic becomes visible. Who answers first? What happens after five rings? Which calls go to voicemail and which must reach a person? How are calls handled at lunchtime, out of hours and during holidays? What happens if the broadband fails?

Ask the supplier to document the proposed call flows in plain language. Test them with real scenarios rather than accepting a verbal assurance. A route that works in a demonstration may behave differently when the receptionist is on holiday or when a queue overflows.

Continuity also needs a plan. If the office broadband fails, can calls divert to mobiles? Can staff use a softphone on a mobile network? Are emergency calls handled correctly? These questions should be answered before cutover, not during the first outage.

Staff habits change more slowly than systems

The technology may switch in an afternoon. Habits take longer. Staff who have used the same handset for years need time to learn transfer, hold, conferencing and voicemail. Receptionists need to understand new queue behaviour. Managers need to know how to access reports.

Training should be practical and role-based. A short all-staff session is useful, but champions in each team can answer everyday questions. Provide a one-page guide for common tasks and a clear route for support. If headsets or handsets are changing, let staff try them before the cutover date.

Test before you trust

Acceptance testing is the point at which procurement becomes operational. Agree in advance what “working” means: inbound calls, outbound calls, transfers, voicemail, queues, call recording, emergency access, integrations and remote working. Test from different networks and devices. Check that caller display and number presentation are correct.

Choose a cutover time that gives room to recover. A Friday afternoon switch leaves little support time before the weekend. A midweek morning may suit some businesses better, provided key staff are available. Keep the old system accessible for a short period where possible, and confirm how rollback would work.

Contract terms should reflect the project

The contract should cover service levels, support hours, porting responsibilities, training, acceptance testing and what happens if the service does not meet the agreed standard. Check termination rights, number porting rights at the end of the contract and how data such as call recordings will be returned or deleted.

A VoIP migration is not difficult because the technology is mysterious. It is difficult because it touches numbers, routines and customer expectations. UK SMEs that treat it as a procurement and change project, rather than a simple equipment swap, are more likely to keep talking throughout the change.