New employees get a laptop, a headset, a login and a calendar full of introductory meetings. What they almost never get is five minutes on how to sound good in those meetings. The result is predictable: first impressions delivered through the wrong microphone, a week of “sorry, can you hear me now?”, and help desk tickets that a short checklist would have prevented. Adding a small audio segment to onboarding is cheap, and it pays back on the first day.
Why this gap exists
Everyone assumes someone else has covered it. IT assumes that video calling is universal knowledge by now. Managers assume IT handled it during laptop setup. The new hire assumes that because they used a different platform at their last job, this one will behave the same way.
It does not quite. Every calling app has its own idea of where device settings live, how muting works, and what happens when a headset is plugged in. People coming from a company that used Zoom or Google Meet are competent callers who simply do not know where Teams keeps things. And people in their first office job may never have used a headset with a boom microphone at all. Neither group will ask, because asking how to use a microphone feels embarrassing in week one.
The handful of things worth teaching
An onboarding audio segment does not need to be long. It needs to cover the few things that cause most of the trouble.
Begin with device selection. Show where the device settings are in Teams, and make the point that speaker and microphone are chosen separately. Hearing the call through a headset does not guarantee the headset microphone is the one in use. Have them read the microphone name out loud once; it sticks.
Next, the test call. Teams can record a short sample and play it back, and very few users know the feature exists. Make it part of day one. A new hire who has heard their own audio knows what “good” sounds like on their equipment, and will notice when something changes.
Then cover mute: the on-screen button, the keyboard shortcut, and the mute button on the headset if it has one. Explain the local convention too. Does your team stay muted in large meetings? Are cameras expected? These norms are invisible to a newcomer and differ from one company to the next.
Noise suppression gets a brief mention: where the setting is, that the automatic mode suits most people, and that your organization may have locked it. Finally, the one-room rule: if several people join the same meeting from the same space, only one device should have audio on, or everyone gets echo.
Give them somewhere to look things up afterwards. Internal wiki pages go stale quickly, so it is reasonable to pair your own notes with Microsoft’s support pages and an independent reference such as MutePoint, which concentrates on Teams audio settings and troubleshooting. The goal is that a new hire with a quiet microphone at 8:55 has a first stop other than panic.
Equipment: decide it for them
Much audio trouble comes from improvised hardware. If the company issues a headset, say so clearly and issue it on day one, not after the first week of meetings on laptop speakers. If it does not, publish a short list of recommended models, ideally ones certified for Teams, since those tend to handle mute syncing and device switching more gracefully.
Remote hires need extra care here. Their environment is unknown: a kitchen table, a shared apartment, a spare room next to a busy street. A decent headset with a boom microphone makes up for a great deal of that, far more than any software setting can. Ship it with the laptop.
Making it part of the process
The format matters less than the consistency. Some teams add a ten-minute slot to the IT setup session. Others assign an onboarding buddy who runs a practice call on the first morning, which has the added benefit of being a friendly first conversation. A short recorded walkthrough works for larger intakes, as long as it is updated when the Teams interface changes.
Whatever you choose, include a real call. Reading about settings does not stick; joining a practice meeting, switching microphones, muting with the shortcut and listening to a test recording does. Ask the new hire to do it again after they first connect to a dock or a meeting room, because that is when things shift.
The payoff for a small investment
Ten minutes of audio basics means new colleagues are heard clearly in the meetings where they are trying hardest to make a good impression. It trims a category of support tickets, spares everyone else the daily troubleshooting ritual, and signals that the company has thought about what working here actually involves.