Name the symptom, confirm the selected microphone and speaker, test locally, and change one connection or device at a time.
Audio trouble in a call often produces hurried changes: reconnect the headset, switch applications, restart the computer, and move rooms all at once. If the sound returns, nobody knows which change mattered. A simple sequence makes the problem easier to describe and repeat.
This guide covers ordinary consumer and workplace calls. It is not a diagnostic procedure for emergency, medical, broadcast, or accessibility equipment. Use the product’s support instructions and your organization’s approved tools.
Describe what the other person experiences
“Audio is broken” can mean silence, distortion, delay, echo, or intermittent sound. Ask whether the problem affects what you hear, what others hear, or both. Note whether it began after joining the call, connecting a device, or moving to another network.
If privacy permits, use the application’s local microphone meter or test-call feature. A local recording can show whether the microphone reaches the computer before the call service and network become involved. Delete test recordings you do not need, especially if they contain other people’s voices.
Check the selected path
Many computers have several microphones and speakers: built-in hardware, a display, a headset, or a dock. Confirm the selected input and output inside the call application as well as the operating system. A device can be connected without being selected.
Check physical mute controls and application permissions. If a permission was intentionally denied, understand what changing it allows the application to access. For a managed work device, request help rather than weakening a security setting you do not control.
Change one variable
Try one change and repeat the same short test. Disconnect one accessory, select the built-in microphone, or move from a dock to a direct connection. Avoid updating drivers, changing network settings, and replacing hardware in the same attempt.
Use a tiny log:
| Test | Result |
|---|---|
| Local microphone meter | Responded or did not respond |
| Built-in microphone | Clear, distorted, or silent |
| Headset on another port | Result and connection used |
| Same account on another device | Same symptom or different |
The log is evidence for support, not proof of a particular cause.
Consider the room and network separately
Echo and background noise can be physical-room problems even when the device works correctly. Delay and dropouts may involve the connection or call service. Test in a quieter space or on an approved alternate connection, but do not expose confidential calls by moving to an insecure network or public room.
If several participants have the same problem at the same time, check the provider’s official service-status page. An isolated device repair will not resolve a service outage.
Finish with a repeatable setup
Once the problem is resolved, record the input, output, port, and application setting that worked. Remove abandoned changes and confirm the next call can use the same path. A five-line record is more helpful than remembering that “something with the headset” fixed it.
Questions about this article? Contact the publication.
Editorial policy