WarmLine → First-impression audio checklist
Ritual
The first-impression audio checklist
Ten checks, under four minutes, before any call where the other person decides something about you. Built to be screenshot-ed, printed, or memorized until it's muscle.
The pre-call audio check is ten items and takes less than four minutes once it's routine. It exists because first impressions on calls are formed before your first full sentence lands — from the sound of your "hi, thanks for making time" — and because every item on this list has personally embarrassed someone who skipped it.
Pilots with ten thousand hours still run the walk-around. Not because they've forgotten how planes work — because the checklist catches the one morning something is different. Your version of "something is different" is quieter: an update reset your audio device overnight, a housemate started a laundry cycle, your suppression tool didn't launch at startup. The client experiences all three the same way: as you, sounding off, on the call where you needed to sound right.
The four-minute check
T-minus four minutes — run in order
- Input device is the one you meant. Open your OS sound panel and read the active input's name out loud. The single most common pre-call disaster is the machine quietly switching inputs after a restart, an update, or something else pairing first. Ten seconds; checks the failure that no filter can save.
- Output device too. You can't respond warmly to a question you half-heard through the wrong speakers.
- Level meter dances mid-range. Say your real opener — not "test, test" — and watch the input meter sit upper-middle without pinning. If you changed rooms since yesterday, this is where you find out.
- One suppression layer, exactly one. Built-in on, or your dedicated tool on and the built-in turned down — never both at full aggression. Doubled filters are how you end up sounding robotic on the call that mattered. (Why one layer: see the full guide to sounding professional on client calls.)
- Notifications silenced. Do-not-disturb on the computer and the phone. A Slack ding mid-price-discussion is self-inflicted background noise, and clients can hear you glance at it.
- Close the heat-makers. Quit the browser-tab zoo and anything rendering, syncing, or updating. Fans spin up under load, and a fan is a noise source you started. This matters double on demos — see demo-call audio.
- Network sanity. If video's involved, be near your router or on the wire; if your platform offers a connection test, run it. Packet loss impersonates bad audio, and the client can't tell the difference — "breaking up" is "breaking up".
- Ten-second record-and-listen. Voice memo or your platform's mic test: record your opener, play it back. This is the compressed version of the voicemail self-test, and it's the one item that would have caught most of what the other nine catch.
- Phone silent and out of the mic's reach. Vibration against a desk travels straight into the call.
- Rehearse the composure line. One sentence, ready, for when noise strikes anyway: "Apologies for that — one second while it passes." Saying it once, calmly, and continuing is the professional move. The full incident playbook, scripts included: background noise during a sales call.
Total elapsed time once it's routine: three to four minutes. The first week it'll take six. By week three you'll do items one through five while your calendar reminder is still fading.
The night-before extension
For career-sized calls — the final-round panel you're running, the listing appointment for the biggest house of your year, the renewal that is your quarter — add three checks the evening before, when there's still time to fix what you find:
- Run updates tonight, not tomorrow. The worst time to discover a 20-minute OS update is four minutes before the call. The second-worst is during it, when the restart-nag notification chimes in.
- Full voicemail self-test. The complete version: call your voicemail, deliver thirty seconds of your actual opening, play it back on phone speakers. Judge it like a client would. Four minutes; described fully in the main setup guide.
- Scout the hour. What does your environment sound like at the call's actual hour? The street that's silent at 8 p.m. has a garbage truck at 8 a.m. If tomorrow's hour is noisy, tonight is when you decide on the quieter room — or make sure your suppression layer is up to the job.
From this page’s own rules: the FAQ’s routine-call shortcut, the full ten, and the night-before extension.
Line check
Item four assumes you have a suppression layer worth trusting. If your calls happen where life is loud — kids, cafés, coworking — Krisp is the tool we point client-facing readers to: $8/user/month billed annually, $16 monthly, 7-day trial, prices read on krisp.ai 2026-09-20.
Put Krisp on the checklist once
Referral tag on this button: start a Krisp subscription from it and Krisp pays WarmLine a fee. Your price is Krisp’s ordinary price, nothing added. In a quiet home office? Your platform's built-in suppression passes item four just fine, and it costs nothing.
Checklist questions
Isn't ten items overkill for a routine call?
For a routine call, run items one, four, and five — thirty seconds. The full ten is for calls with a decision on the other end. The skill is knowing which kind of call you're four minutes away from; your pipeline already knows.
What's the one item people skip that burns them?
Item one, the input device. It fails silently, it fails after restarts and updates — exactly when you least expect it — and no downstream software can fix capturing your voice from the wrong microphone across the room. Read the device name out loud. Every time.
Can I automate any of this?
Partly. Set your suppression tool and do-not-disturb to launch at startup, and keep a standing calendar reminder titled with the first three items. But the record-and-listen check resists automation on purpose — its value is that a human (you) hears what the client is about to hear.
This checklist is the four-minute compression of the full professional-sound setup. Seat-specific versions live in the playbooks: demos, phone screens, real estate.