Saying “can everyone hear me?” at the top of a meeting is not a test. It tells you that some sound is reaching someone, and nothing about whether you are clear, echoing, clipped or sitting on a bed of hiss. A proper test means recording yourself the way others will hear you, listening back critically, and knowing what each flaw sounds like. It takes about three minutes, and you only need to repeat it when something in your setup changes.
Why the level meter is not enough
The little bouncing bar in your settings window confirms that the microphone is alive and roughly how loud it is. The meter moves just as happily for a laptop mic picking up a hollow, echoing room as it does for a clean headset. It cannot show you distortion, a filter chewing on your consonants, or the fact that the app has quietly selected your webcam’s microphone instead of the one on your desk.
Nor can you judge by ear as you talk. You hear your own voice largely through the bones of your head. The only reliable method is to capture the signal after the app has processed it and play it back.
Three ways to hear what others hear
Most platforms include a built-in check. Zoom has a test speaker and microphone function in its audio settings that records a few seconds and plays them back, and it offers a test meeting you can join alone. Teams provides a test call feature that records a short message and replays it. Google Meet and Webex have their own pre-join or settings-based checks. Menu locations move around between versions, so look in the audio or device settings of your current client. If Zoom is your main platform, the steps to test your audio before a Zoom meeting are laid out in order, including what to do when the test itself fails.
The second method is a solo recorded meeting. Start a meeting with only yourself, record for a minute, and open the file. This is the most faithful option because it uses exactly the same processing chain as a real call.
The third is a friendly colleague. Ask them to describe what they hear, not to reassure you. “Fine” is not feedback. “A bit distant and I can hear the road” is.
Say the right things during the test
Counting to five reveals very little. Give the recording something to work with. Speak two or three full sentences at your normal meeting volume. Include a line heavy in p, b and t sounds to expose popping, and one with plenty of s sounds to expose harshness. Go quiet for five seconds so you can hear the background on its own. Say one sentence louder than usual. Then produce your typical noises on purpose: type a line, shuffle paper, set a mug down.
What to listen for on playback
Use headphones for the playback, since laptop speakers hide most faults. Then work through the recording with specific questions in mind:
- Level: is your voice comfortably loud without anyone needing to turn you up, and consistent from sentence to sentence?
- Distortion: does the loud sentence crackle or go fuzzy? That is clipping, and it means the input gain is too high.
- Room: do you sound close and dry, or distant and boxy, as if speaking in a bathroom?
- Background: what can you hear in the silent gap? A steady hiss, a hum, a fan, voices?
- Filter artifacts: are first syllables missing, do word endings fade, does the voice warble or sound underwater?
- Handling noise: did the typing, the mug or the cable brushing your shirt come through as thumps?
Each fault has a usual remedy. Clipping calls for lower gain or a little more distance. A boxy room calls for a closer microphone and softer surroundings. Hiss often comes from gain set too high on a distant mic. Missing syllables and warbling suggest too much noise suppression, or two filters stacked on top of each other. Thumps mean the microphone shares a surface with your keyboard and wants a stand, an arm or a headset.
Do not forget the listening side
Half of call audio is what you hear. Play the test tone through the output you intend to use and confirm it comes out of the headset, not the laptop speakers, since sound from open speakers is a classic source of echo for everyone else.
Retest when something changes
You do not need to do all of this every morning. Run the full check when you get new equipment, after a major update to your meeting app or operating system, when you move to a different room, and before any call with real stakes. On ordinary days, a ten-second glance is enough: right microphone selected, right speaker selected, mute state as you expect. The recording told you the setup is good. The glance confirms it is still the setup you tested.