The desk phone is not dead. It is just increasingly difficult to justify. A physical handset that only works in one building, needs firmware updates, and occasionally decides to stop registering for reasons nobody can immediately explain — it made sense when everyone was in the office five days a week. The world has moved on somewhat since then.
The shift toward WebRTC softphones has been building for a while, but hybrid working gave it a proper shove. This piece covers why UK businesses are making the switch, what to actually look for in a softphone solution, and what the migration process tends to involve in practice.
What is a WebRTC softphone, in plain terms?
A softphone is a phone that runs as software — on your laptop, desktop, or mobile — rather than as a lump of plastic on your desk. Calls travel over your internet connection using VoIP.
WebRTC is the technology layer that makes this work natively in browsers and apps without plugins, without complex manual configuration, and without the quality issues that plagued early internet voice calls. Audio is encrypted end-to-end by default. The connection adapts to network conditions automatically. And critically, it works the same whether your team member is at their desk in Manchester or on their kitchen table in Edinburgh.
Why the switch is happening now
The hardware cost is hard to ignore
A decent IP desk phone runs anywhere from £80 to £200 per unit. Multiply that across a team, factor in replacements when devices get dropped or simply age out, and the number adds up. A WebRTC softphone runs on a laptop or mobile your team already owns. The per-user subscription cost is a fraction of the hardware equivalent — and there is nothing to physically manage.
The office is no longer the default
A desk phone is tied to a desk. If your team splits time between the office, home, and client sites — which describes most UK businesses in 2026 — a fixed handset creates gaps. Someone works from home on a Friday and misses a call. Someone is on-site with a client and unreachable. A softphone follows the person, not the building. The extension number stays consistent, call history syncs across devices, and the experience is the same wherever they are.
Modern provisioning removed the friction
Older SIP softphones required users to manually enter server addresses, authentication credentials, NAT settings, and codec preferences. For non-technical staff this was a genuine barrier to adoption, and it often needed IT involvement for every new device.
Modern WebRTC softphones are provisioned centrally. An administrator sets up the connection once; users log in and the device configures itself. That shift has removed most of the friction that previously made softphone rollouts painful.
What to look for when choosing a solution
It should work with what you already have
If you run an Asterisk or FreeSWITCH PBX, you should not have to replace it to use a softphone. Look for a solution that supports standard SIP registration and can bridge your existing infrastructure to modern WebRTC clients. Ripping out your PBX to accommodate a softphone is solving the wrong problem.
Mobile needs proper push notifications
A softphone that only receives calls when the app is actively open is not a replacement for a desk phone — it is a downgrade. You need push notification support on iOS and Android so that incoming calls arrive even when the app is backgrounded or the screen is locked. This is a technical detail that has an outsized impact on whether people actually trust the system day-to-day.
Call recording should be a first-class feature
For a significant portion of UK businesses — financial services, legal, insurance, customer-facing teams — call recording is not optional. It is a compliance requirement. Make sure any solution you consider handles recording at the softphone level and gives you access to those recordings in a usable format.
Credentials should never touch the browser
WebRTC enforces end-to-end media encryption by default, which is one of its genuine advantages over older VoIP implementations. But pay attention to how signalling is handled too. A well-built solution keeps SIP credentials server-side and authenticates clients using short-lived tokens — so there are no passwords sitting in browser storage or visible in client-side code.
How Siperb handles the transition
Siperb is built around the idea that your existing PBX infrastructure should be an asset, not an obstacle. Rather than replacing Asterisk or FreeSWITCH, Siperb sits between your current system and your users — acting as a WebRTC proxy and provisioning layer that your PBX does not need to know anything about.
Existing extensions, dial plans, and SIP trunks stay in place. Users get a consistent softphone experience on web, desktop, and mobile. Provisioning is handled centrally. Incoming calls are delivered via push notification on mobile even when the app is not in the foreground. Call history and recordings are synchronised across devices.
For businesses that have invested in their telephony infrastructure but want to move away from physical handsets without a full system replacement, that is a considerably less disruptive path.
What the migration actually looks like
For most small and medium UK businesses, the transition is more straightforward than it sounds. In broad terms:
- Audit your current setup — PBX type, number of extensions, call recording requirements
- Run a pilot with a small group before rolling out to the whole team
- Configure your PBX connection once — typically under an hour
- Provision users centrally — devices configure themselves on first login
- Keep desk phones available during the transition if the team needs the reassurance
The desk phone served its purpose well. But the combination of hybrid working, WebRTC technology, and sensible provisioning tools has quietly removed most of the reasons to keep it around. For UK businesses looking to simplify their communications setup and reduce hardware overhead, a WebRTC softphone is the practical answer.
Siperb · siperb.co.uk · Helping UK businesses make the move to modern voice communication
Leave a Reply