Skip to content
Illustration: an open laptop with a browser dialer, a smartphone on a stand with a softphone app and a corded desk phone side by side on one desk, all showing the same number and ringing in turn.

Web dialer vs softphone vs desk phone: which should you use?

Web dialer, softphone or desk phone? Our plain answer for small teams, plus what really decides call quality and which of the three can reach 911.

If you work from a laptop and want to make business calls today, use a web dialer. There’s nothing to install and almost nothing to maintain. Need your business number on your mobile? Get a softphone app. And if people sit at the same desk all day, or a front desk has to reach 911 with an exact address, put desk phones on those desks.

That’s our short answer. The labels matter less than you’d think, though. In practice, two things separate a web dialer, a softphone and a desk phone: how your calls sound, and what happens when someone dials 911.

What each option is

A web dialer

A web dialer, or browser-based dialer, is a web page that places calls. You sign in, allow the microphone and dial. Underneath, it runs on WebRTC, a set of standards that lets a web page capture audio and stream it without plug-ins or other software (MDN). Your provider’s servers then connect the call to the phone network.

Browser support isn’t something to lose sleep over. WebRTC works in Chrome, Edge, Firefox and Safari, including Safari on iOS since version 11, and Can I use counts about 97% of browsers in use as supporting it.

Encryption comes with the standard. RFC 8827 requires every WebRTC audio stream to be secured with SRTP, and plain, unencrypted audio isn’t allowed. That protects the stretch between your browser and the provider.

The catch? The dialer lives in a tab. It only works while that page is open, and it shares your computer with everything else you have running.

A softphone app

A softphone is an installed program that acts as a phone, on a computer or a mobile. The word even turns up in the SIP standard, RFC 3261, for a SIP application on a PC. Softphones usually speak SIP, the protocol that sets up, changes and ends calls. A SIP app or phone registers with the provider’s server when it starts, then again at regular intervals, so the server knows where to send incoming calls.

They come in two kinds. Your provider’s own app needs only a sign-in. A general SIP app needs a server address, a username and a password from your provider, and settings such as codecs are yours to get right. Our advice: use the provider’s app unless you have a clear reason to tinker.

Encryption is where softphones get less predictable. SIP servers must support TLS, but RFC 3261 only strongly recommends that phones and apps be able to start it. So ask your provider whether your calls are encrypted, and how.

A desk phone

A desk phone, or IP phone, is a handset with its own keypad that plugs into your network. Many are SIP phones, which work like a softphone built into hardware: they register with the provider’s server and ring when a call arrives (RFC 3261).

They bring chores with them. Each handset needs a network connection and power. Someone has to set it up, too: either you enter the provider’s details, or the provider configures the phone for you. Firmware updates land on each phone.

Once several phones share one system, US rules call it a multi-line telephone system (MLTS). The definition is broader than the name suggests. It covers network-based systems such as VoIP and Centrex as well as an on-site PBX (47 CFR 9.3).

Web dialer vs softphone vs desk phone, side by side

Web dialer Softphone app Desk phone
Setup time Minutes: sign in, allow the microphone Minutes per device; longer for a general SIP app Order, cable and set up each handset
What you install Nothing beyond a current browser An app on each computer or phone A handset on each desk, with network and power
Cost beyond the phone service A headset A headset, and some apps are paid A handset per person
Works on Any computer with a current browser The computers and phones the app supports That one desk
Call quality depends on Your network, headset and computer Your network, headset and device Your network and the handset
IT effort Almost none Installs, sign-ins and settings on each device Network ports, power, setup and 911 configuration
Updates Arrive when you reload the page App updates on each device Firmware updates on each phone
Emergency calls Depends on the service; some cannot call 911 Depends on the provider; location rules apply On a multi-line system, direct 911 dialing and location are required
Best for Solo sellers and small teams on laptops Calling from a mobile, or working without a browser tab Fixed desks, reception, people who want a handset

If nobody on your team does IT, read the “IT effort” row twice.

What decides call quality

Whatever you call with, three things under the label decide how it sounds: the network, the codec and what you speak into.

The network

An internet call travels as a stream of small packets. Three things go wrong with them.

Delay is the one you notice mid-conversation. ITU-T Recommendation G.114 treats one-way delay of up to 150 ms as acceptable for most uses, and more than 400 ms as unacceptable for general network planning. Past about 200 ms, people start talking over each other. Cisco’s guide to delay in packet voice networks has the detail.

Jitter is subtler. It’s variation in when packets arrive. The receiving end holds packets in a buffer so it can play them out evenly, and packets that arrive too late for the buffer are thrown away. You hear that as dropouts (Cisco on jitter).

Then there’s packet loss. A lost packet is missing sound. A good codec hides small losses, and heavy loss still breaks up the call.

Bandwidth is rarely the problem. For wideband speech with Opus, MDN suggests 16 to 20 kbps, and G.711 uses 64 kbps (MDN). Either fits easily on a normal broadband line. What hurts is a connection that’s busy or unstable.

Here a desk phone has a real edge. It’s usually on a cable and does nothing but calls. A laptop on Wi-Fi shares its connection with everything else, and an Ethernet cable wins back most of the difference. If you call from a laptop, that cable is money well spent.

The codec

The codec turns your voice into data and back. For WebRTC, browsers must support two: Opus and G.711 (MDN).

Opus is the flexible one. It scales from 6 kbit/s narrowband speech to 510 kbit/s fullband stereo music, and it’s built for imperfect networks. The clever part is how it treats speech that matters most, such as the start of a word. That speech can be encoded again at a lower bitrate and added to a later packet, so if the original packet is lost, the receiver can fall back on the copy. Both details come from RFC 6716, which defines Opus.

G.711 is the telephone standard from 1972: 8,000 samples a second, 64 kbps, and a voice band of 300 to 3,400 Hz. MDN’s audio codec guide describes it as the highest quality encoding that can pass through the public telephone network.

That last point should set your expectations. When you call an ordinary phone number, the far end of the call is on the phone network, whichever option you use. A better codec on your side mostly helps the call survive a shaky connection. Don’t expect it to make the other person sound better than a normal phone call.

Softphones and desk phones agree on a codec with the other side as each call starts, through the offer and answer exchange SIP uses (RFC 3264). Which codecs are on offer depends on the app or phone and on your provider. Ask.

What you speak into

On a computer, a wired headset is the biggest improvement you control. Our guide to cold calling from the browser covers headsets, microphone permission and the rest of the setup. A desk phone gets this right by design: the handset keeps the microphone at your mouth and the speaker at your ear, which is part of its appeal.

Emergency calls: where the options differ most

This is general information about US rules, not legal advice. Check with your provider, and if you run your own phone system, with a lawyer.

The three options split hardest here. Ask every provider the same question before you sign up: what happens when someone dials 911?

Desk phones on a multi-line system

The FCC’s MLTS page sets out two federal laws that apply to multi-line systems made, sold or installed after February 16, 2020.

Kari’s Law requires that every phone on the system can dial 911 directly, without a prefix such as 9. Where the system can do it, a 911 call must also send a notification to a central point, such as a front desk or a security desk, where someone is likely to see or hear it.

Section 506 of RAY BAUM’S Act requires a dispatchable location with each 911 call. That means a validated street address, plus details such as a suite or floor number. Fixed phones on the premises have had to send it automatically since January 6, 2021. For phones that move around the site, and devices used off-site, the date was January 6, 2022: automatically where technically feasible, otherwise from a location the user updates or other location information.

These duties fall on whoever makes, sells, installs, manages or operates the system (FCC). If you set up and run your own phones, that includes you, so read the FCC’s page before you plug them in.

Softphone apps

If your softphone comes from what the FCC calls an interconnected VoIP provider, the provider must send location information with 911 calls (FCC). For an app you can use from more than one place, that means automated dispatchable location where technically feasible. Failing that, the provider can use a Registered Location (an address you give before service starts and can update at any time) or other location information. As a last resort, it can route the call to a national emergency call center.

These providers also have to tell you, in plain language, when 911 may not work or may be limited. The rule’s examples include moving your device, a broadband failure and a power cut (47 CFR 9.11). That covers desk phones on VoIP service too. An internet phone needs both internet and power.

Web dialers

Some web dialers can’t call 911 at all. KNOQRA is one of them, and we’d rather say so plainly here than have you find out on a bad day. If you use one, make sure everyone who works with it knows, and has another phone within reach that can call for help.

How to choose

Working alone from a laptop and want to start calling today? Use a web dialer. If you need your business number on your mobile, put a softphone app on your phone. Where several people share one phone system, or someone staffs a front desk, go with desk phones, on a system set up for direct 911 dialing and dispatchable location.

If you want little or no IT work, pick a web dialer or your provider’s own softphone app. If you need 911 from the same tool you call with, rule out any service that can’t dial it. And if your connection drops or stutters, fix that first. All three options here run over the internet.

You also don’t have to pick just one. Say you run a three-person recruiting firm. You make your call blocks from a laptop, a colleague covers reception, and you’re often out seeing clients. A web dialer for the call blocks, a mobile in your pocket and a desk phone at reception can work side by side. Skip the desk phone altogether if nobody sits at a fixed desk.

Where KNOQRA fits

Full disclosure: KNOQRA is ours, and it’s a web dialer. It sits inside a browser-based workspace for calls, SMS and WhatsApp, built for solo sellers and small teams. You call from the browser in the Desk at app.knoqra.app, with nothing to install, one seat and no contract.

The numbers you buy in KNOQRA are US and Canada numbers, available once a check of you or your business is approved; every request is reviewed, so approval isn’t automatic. From them you can call 220 countries, and each country’s rate is on the call rates page. Before every call, you see an estimate.

One limit matters for this choice: KNOQRA cannot call 911 or other emergency numbers. If you need that, keep a phone that can. KNOQRA also has apps for iPhone and Android on the same number. Otherwise, see how the browser dialer works, or compare plans and pricing.

Sources

  1. MDN: WebRTC API
  2. Can I use: WebRTC peer-to-peer connections
  3. RFC 8827: WebRTC Security Architecture
  4. RFC 3261: SIP, Session Initiation Protocol
  5. RFC 3264: An Offer/Answer Model with the Session Description Protocol (SDP)
  6. 47 CFR 9.3, 911 requirements: definitions (eCFR)
  7. Cisco: Understanding Delay in Packet Voice Networks
  8. Cisco: Understanding Jitter in Packet Voice Networks
  9. MDN: Codecs used by WebRTC
  10. RFC 6716: Definition of the Opus Audio Codec
  11. MDN: Web audio codec guide
  12. FCC: Multi-line telephone systems, Kari's Law and RAY BAUM'S Act 911 direct dialing, notification and dispatchable location requirements
  13. FCC: Dispatchable location for 911 calls from fixed telephony, interconnected VoIP, TRS and mobile text service
  14. 47 CFR 9.11, E911 service for interconnected VoIP (eCFR)

Fees and rules change: check the source before you rely on a number. This post is general information, not legal advice.

Apple, the Apple logo and iPhone are trademarks of Apple Inc., registered in the U.S. and other countries. App Store is a service mark of Apple Inc., registered in the U.S. and other countries. IOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used under license. Android, Google Play and the Google Play logo are trademarks of Google LLC.

Start with one conversation.

Create your account in a minute. Calls and texts on one number, with every conversation in one place.