Background noise during a sales call: prevent, net, recover

Somewhere in the middle of your best paragraph, the leaf blower starts. Or the dog. Or a delivery driver leaning on a doorbell like it owes him money. What happens in the next eight seconds decides whether the call lost thirty seconds or lost its momentum, and the difference is almost entirely about what you do — not about the noise.

This is the incident playbook: the three categories of noise, the two layers that stop most of them reaching the client, and the exact words for when one gets through anyway. Written for people selling, scoping, and closing — the calls where a lost thread costs real money.

Three kinds of noise, three different answers

The useful insight is that money and effort should follow the middle row. Predictable noise is solved with a calendar, freak noise is solved with two sentences, and only the probable class is genuinely a software problem — which is also the class that quietly degrades every call you take rather than dramatically ruining one.

Layer one: don't schedule into it

Look at the last month of your own noise complaints and you'll find a pattern with a clock attached. The street cleaner, the upstairs renovation that runs 8 a.m. to 4 p.m., the coworking lunch rush at 12:30, the daily standup that leaks through a thin wall. Move the high-stakes calls out of those windows. It's free, it's permanent, and it takes ten minutes with a calendar.

The self-inflicted case deserves its own sentence: your own machine. A laptop that starts a demo from cold, with thirty tabs and a video call and a screen share, will spin its fans up within minutes, and that fan noise is both constant and close to the microphone. Open your demo materials before the call, not during. The full version of that argument is on demo-call audio.

Layer two: the software net

Your meeting platform ships background-noise suppression at no extra cost, and for a moderate, steady floor it is genuinely sufficient. Turn it on, at its standard setting, and stop there if your calls happen in a quiet room. That recommendation pays us nothing, which is why it comes first.

Where a dedicated layer like Krisp changes the picture is chaotic, changeable noise and platform-hopping. It sits between your microphone and every application, so the cleanup goes with you to whatever platform the prospect's calendar invite chose — which is the structural problem in client-facing work: you don't pick the app, they do. Disclosure: that's an affiliate link, and WarmLine may earn a commission if you subscribe, at no cost to you. The fit assessment, including who should skip it, is on Krisp for client calls.

One rule that prevents most self-inflicted damage: run one suppression layer at a time. If you add a dedicated tool, turn the platform's built-in filter down to its lowest setting. Two filters fighting over the same voice produce the underwater, half-robotic sound that clients interpret as a bad connection — you will have paid money to sound worse.

The flinch is the actual damage

Here is the thing worth internalizing: in most incidents, the noise costs the client less than your reaction to it. You hear it at full volume in your own room. They hear a suppressed, distant version, often while half-reading something else. Then you stop mid-sentence, apologize twice, explain the renovation, apologize again, and ask where you were — and now a two-second event has consumed twenty seconds, broken your own thread, and signalled that you are rattled.

Drawn to the page’s own numbers. The fix is one short line, then back to the thread.

Composure is not a personality trait here. It's a decision made in advance: when noise happens, I will do exactly one thing, and it will be short.

The three scripts

Pick one, say it once, and continue. Read them aloud now so they're available under pressure later.

When to actually reschedule

Rarely, but the threshold exists: when the noise is continuous, when you are repeating yourself more than twice a minute, or when the call's purpose is precision — pricing, contract terms, numbers someone will act on. In those cases, a clean fifteen-minute call tomorrow beats a damaged forty-minute call today, and proposing it reads as seriousness rather than weakness. Say what you're protecting: "This matters too much to do through a drill. Can we take fifteen minutes tomorrow morning instead?"

What you should not do is push through a genuinely broken call because rescheduling feels like losing. A client who spent forty minutes straining does not remember your resilience; they remember that the call was hard work.

Afterwards

Two small moves recover the remaining ground. Send the follow-up summary a little faster than usual and a little more precisely — it quietly repairs anything that was misheard, without ever mentioning the noise again. And add the incident to your own calendar intelligence: if it was predictable, it's now a scheduling rule; if it was probable, it's an argument for the software layer; if it was freak, forget it entirely. That's the whole loop, and it's on follow-up call habits.

Questions about mid-call noise

Should I mute when noise happens?

Only if you're not speaking. Muting mid-sentence to hide a sound creates a worse artifact than the sound: your voice disappears, which reads as a dropped connection and makes the client interrupt to check you're there. Let suppression do its job and keep talking.

Can the client hear it as badly as I can?

Almost never. You're in the room with it; they're getting a suppressed, compressed version through a laptop speaker. This is why the flinch is so expensive — you often draw attention to something they had not registered.

What if the noise is a person — a family member walking in?

Filters are built to protect voices, so a second human voice is the hardest case for any of them. Handle it socially: one short acknowledgment, no explanation of your domestic arrangements, and carry on. Clients are far more tolerant of human life than of being strained at.

Does suppression make me sound worse to compensate?

It can, if it's set aggressively or stacked with another filter. If people start saying you sound distant or robotic, that's over-processing, not noise. Drop to one layer at a moderate setting and test with the voicemail self-test on the main setup page.

Prevent before you recover: the four-minute pre-call checklist catches most of the predictable row before the call starts.