Softphone mic settings: the ten-minute tune-up every app shares

Five settings cause the large majority of "my softphone sounds terrible" complaints, and none of them are inside the softphone's noise feature: the input device, the gain level, microphone boost, automatic gain control, and stacked audio processing. This is the tune-up that fixes them in order, and it applies identically to RingCentral, Dialpad, 3CX, Vonage, Aircall, Zoiper and whatever your company deploys next quarter.

1. 1Input devicethe mic near your mouth, in all three pickers
2. 2Input gainspeech peaks below max; slider in the middle half
3. 3Microphone boostoff
4. 4Automatic gain controlon in exactly one place
5. 5Suppressionone owner per direction

Setting 1 — the input device (start here, always)

The most common softphone audio failure is also the dumbest: the app is listening to the wrong microphone. You talk into a headset; the app transmits the laptop's internal array, which hears the entire room, the fan, and your typing at full arm's-length bloom.

Devices get selected in up to three places, and they can disagree:

• The OS default input. What most apps use unless told otherwise.
• The OS communications default. Windows keeps a second, separate default just for calling apps — the one nobody remembers exists. If your softphone sounds different from your recorder, check this one.
• The app's own picker. Most softphones have one (Dialpad's Hardware Settings, VBC's Settings → Audio, Zoiper's audio device selection). An explicit app choice overrides OS defaults — including yesterday's explicit choice of a device you unplugged.

Why it breaks on Tuesdays: every dock, undock and USB re-plug can re-enumerate audio devices. The OS may fall back to the internal mic; the app may cling to a device ID that no longer exists and grab something arbitrary. After any hardware shuffle, re-check all three pickers. Thirty seconds, saves a support ticket.

Setting 2 — input gain (the middle is your friend)

Gain decides how much the mic signal is amplified before anything else touches it. Two failure modes:

• Too hot (slider near max): your voice clips into distortion, and the room noise floor rides up with it. Once clipped, no downstream filter can repair it — the distortion is welded to your voice.
• Too cold (slider near zero): the far end cranks their volume to hear you, amplifying your noise floor along with your whisper — and someone "helpfully" enables boost, which is worse (next section).

The boring, correct answer: set gain so your normal speaking voice peaks comfortably below the top of the app's level meter — usually the middle half of the slider's range — and adjust distance-to-mouth before touching the slider again.

Setting 3 — microphone boost (just turn it off)

Boost is a blunt extra amplification stage with none of gain's subtlety. It exists for genuinely broken quiet mics, and on anything modern it mostly amplifies hiss and pushes the input into clipping. Zoiper ships it off by default for a reason — per Zoiper's own configuration docs, it's the only audio toggle they default to off. If you need boost to be audible, something upstream is wrong: mic too far, gain misconfigured, or the wrong device selected. Fix that instead.

Setting 4 — automatic gain control (one AGC, not two)

AGC rides your level automatically — lean back, it compensates. Useful, and most softphones default it on. The problems are the edges:

• AGC pumps noise in pauses. When you stop talking, AGC hears "too quiet" and raises the floor — that breathing whoosh callers notice between your sentences. If they mention it, drop gain slightly or disable AGC and set level manually.
• Two AGCs fight. OS-level and app-level AGC both enabled produce slow level see-sawing. Let the softphone own it; disable the OS one.

Setting 5 — stacked processing (the one-owner rule)

Every layer of your chain can process audio: the OS ships "enhancement" processing, browsers apply their own DSP inside WebRTC apps (this is why the 3CX Web Client sounds different from the native softphone), softphones ship suppression, and virtual-device filters like Krisp do it best-in-class. Any one of them is fine. Two of them on the same job is a fault. Stacked suppression is the source of the robotic word-clipping and underwater tails people blame on "VoIP quality" — vendors themselves warn about it, and we walk the evidence in the double-suppression note.

The rule: pick one owner per direction (mic-out, speaker-in), switch the rest off. If you install Krisp, that means the app's suppression toggle goes off; if you rely on Dialpad's built-in, don't run another filter under it.

The ten-minute run-through

1. Pickers (3 min). OS default, OS communications default, app picker — all pointing at the mic near your mouth.
2. Gain (2 min). Speak normally; peaks comfortably below max on the app's meter; slider in the middle half.
3. Boost (10 sec). Off.
4. AGC (1 min). On in exactly one place, preferably the app.
5. Suppression owner (2 min). Decide which single layer removes noise — the app's built-in (see your app's status in the matrix) or a virtual-device filter — and disable the others.
6. Test (2 min). Record or call a colleague while typing with the fan on. Judge by what the far end hears, not what your side sounds like.

The settings that reset themselves

File this under maintenance rather than setup: OS feature updates re-enable enhancement processing they were told to leave off; softphone updates re-default device pickers and occasionally relocate the suppression toggle entirely; and plugging in any new audio-capable USB device can shuffle the default-device order. None of these announce themselves. The cheap defense is the one from the cornerstone guide: write your five settings down once — device, gain position, boost off, AGC owner, suppression owner — and re-run the ten-minute pass after every OS update and every softphone version bump. It's dull. It's also the difference between audio that stays fixed and audio that gets re-diagnosed quarterly.

A note on Bluetooth headsets and "sudden garbage" quality

Software-side because it is one: when a Bluetooth headset's microphone activates, many systems drop the whole connection into a low-bandwidth telephony profile, and suddenly everything sounds like a 1990s cordless phone. That's a profile switch, not noise, and no filter fixes it. If quality craters the instant you unmute, try the headset's dongle instead of native Bluetooth, or a wired connection — or at minimum know that this is a known mode, not your softphone breaking.

After the tune-up, if the room still wins

A correct chain plus a noisy room is where the AI layer earns its keep: Krisp installs as a virtual mic/speaker that any softphone can select, and becomes the single suppression owner across every app at once. 7-day free trial, no card; paid plans from $8/month billed annually (checked 2026-09-20).

Make Krisp the owner → Sponsored line: subscribe through this button and Krisp may pay LineSide a commission. Everything above this banner is free; do it first.

Quick answers

Why does my softphone sound bad only after docking my laptop?

Device re-enumeration: the dock re-orders audio devices and either the OS or the app falls back to the internal mic. Re-check the three pickers (OS default, communications default, app) — it's the first step of the run-through for a reason.

Should AGC be on or off for calls?

On, in exactly one place — preferably the softphone. Turn it off only if callers report a breathing/pumping noise floor between your sentences, then set gain manually.

Do these settings matter if I'm going to install a noise filter anyway?

More, not less. A filter fed a clipped, boosted, wrong-device signal produces clean-sounding garbage. Filters remove noise; they can't repair distortion or substitute for the right microphone being selected.

Next steps: match your app against the built-in noise matrix, or if your "noise" is crackle and stutter rather than room sound, the problem is the line — see VoIP codecs and noise.