Desktop app
Bluetooth headsets
Why we don't recommend pairing a Bluetooth headset to your laptop's built-in Bluetooth, what to use instead, and the common pitfalls when you do use Bluetooth.
We don't recommend pairing a Bluetooth headset directly to your laptop's built-in Bluetooth. We don't support customers who hit audio issues on built-in Bluetooth either. The fix is always "use something else", and the time spent troubleshooting the underlying conflict is time you don't get back.
What we do support:
- A wired connection (USB or 3.5 mm).
- A manufacturer USB dongle, for example a Jabra Link 380, paired with the matching Jabra headset.
- A DECT headset (dedicated voice radio, designed for office calling rather than music).
This article covers why built-in Bluetooth produces such poor call audio, and the common pitfalls if you're using Bluetooth via a manufacturer dongle.
Why built-in Bluetooth doesn't work well for calls
Built-in PC Bluetooth has to share airtime with everything else nearby: your wireless mouse, your keyboard, other Bluetooth speakers, your colleague's headset two desks away. Computers handle this by going first-come-first-served, which means call audio drops, robots out, or cuts off entirely when the radio gets busy.
A manufacturer dongle (such as the Jabra Link 380) is a tiny Bluetooth radio dedicated to your headset. It plugs into a USB port on your computer and talks only to your headset.
Compared to your laptop's built-in Bluetooth:
- The dongle's radio isn't shared with your mouse, keyboard, or other paired devices.
- The dongle exposes integrated answer / end / mute buttons in Cradle when paired with a supported Jabra model. Built-in PC Bluetooth doesn't.
If your headset came with a dongle, use it. If it didn't, the headset isn't a good fit for Cradle calls on its own. Pair it with a wired alternative or look at a DECT headset.
Pitfall 1: the "double connection"
The most common Bluetooth issue we see is Windows remembering the headset on two paths at once: via the dongle (correct) and directly via built-in PC Bluetooth (wrong). Audio goes down one path while Cradle is listening on the other, and you get silence.
To check on Windows:
- Press the Windows key and type Bluetooth and other devices settings.
- Look for both the dongle (for example, Jabra Link 380) and the headset by name (for example, Jabra Evolve 2 65) in the device list.
- If you see both, remove the one with the headset's name. Keep the dongle.
On macOS, open System Settings → Bluetooth and disconnect (or remove) the headset entry. The dongle isn't a Bluetooth device on the Mac side; it's a USB audio device, so it won't appear in this list.
Pitfall 2: motion detection and auto-sleep
Many modern Bluetooth headsets have a motion sensor. If you sit very still, or if the headset is laid down on your desk for a moment, the firmware decides you're not wearing it and powers down the radio to save battery. The next sound, whether that's an incoming ring or you starting to speak, gets missed.
If you find audio cuts when you move your head, or there's a delay answering, open Jabra Direct (or your headset manufacturer's app) and disable Motion detection and Auto sleep.
Pitfall 3: your mobile phone is paired to the same headset
A lot of Bluetooth headsets support pairing to two hosts at once: your work computer (via the dongle) and your mobile phone (via Bluetooth). It's a useful feature on paper. It also means a text-message notification on your phone can steal audio focus mid-call and silence your Cradle call.
Three ways to handle it:
- Unpair the headset from your phone while you're at your desk.
- Put the phone on Do Not Disturb during calls.
- Move the phone out of Bluetooth range (a few metres is enough).
Pitfall 4: thinking the headset is "broken"
A surprising number of "my Bluetooth headset just stopped working" tickets are firmware bugs that disappear after a firmware update. The Jabra Link dongle and the headset itself both have firmware, and both get updates.
Run Jabra Direct once a month and accept the updates it offers. Most of the obscure Bluetooth audio issues we see in support disappear after this.