State the symptom in one sentence
First describe what participants observe. Do others hear broken speech, do you see a frozen picture, or does the connection disappear completely? Record whether you can still hear everyone else. That distinction is more useful than saying the call is poor. Include time, application and connected equipment.
During a test, ask for one specific observation. Someone might assess whether your voice remains clear while you start sharing a screen. Arrange a short agreed trial using non-sensitive content. Change only one part at a time so the result can be attributed. An important live meeting is not the place for several confusing experiments.
Separate local device behaviour
Check the camera in a local preview and the microphone in a recording. If a problem already appears there, investigate that device arrangement first. Confirm the actual selected source; a connected headset is not necessarily the active input. Check accessible mute switches and camera covers too.
Microsoft's camera troubleshooting includes connections and permissions. Those settings may be managed on a work computer. Ask the responsible IT team about locked options instead of bypassing protective requirements. If a local recording works but only one application fails, record that distinction. It helps narrow the next check to that application.
Work on audio separately
Listen to a short recording made with normal speech. Check microphone direction and whether distance changes considerably during ordinary movement. Quiet or uneven speech may relate to placement. Establish an understandable starting position before altering several automatic filters at once.
For returned speaker sound, test an appropriate headphone arrangement. Recheck selected input and output devices. If two devices in one room join the same meeting, establish which send and play sound. Record the working combination so a later change does not recreate the problem through an unnoticed device selection.
Compare connection and application behaviour
If local audio and video work, examine the call conditions. Does the issue affect every meeting or only particular participants? Are other applications or devices affected simultaneously? Note visible large transfers running alongside the call. One download-speed test does not explain every kind of meeting difficulty.
Where appropriate, compare an approved alternative connection on the same computer. Do not change network, camera and meeting software together. If the application has a test function or diagnostic view, use its current instructions. Microsoft describes a Teams test-call function in supported versions; check availability in the version actually used.
Use the latest change as a clue
Ask what changed since the last successful call. A new headset, another USB port, a different workplace or an update may offer a starting point. Treat it as a clue rather than a proven cause. Test a reversible change deliberately where permitted and record the result.
If a dock is involved, compare the affected device connected directly to the computer where that connection is suitable. Leave the remaining setup unchanged as far as possible. If direct connection works, investigate the previous route. This does not automatically prove the dock is defective; cables, configuration and the complete combination still need assessment.
Avoid extensive resets as the first experiment. They can remove working settings and make the starting condition harder to describe later. Use such steps only according to official instructions and, where appropriate, with the responsible IT team. A clear fault report containing a few traceable comparisons is often more valuable than a computer subjected to numerous undocumented changes. Note whether a test merely restored service temporarily or continued to work across the previously troublesome activity.
Provide a useful support report
If the cause remains unresolved, prepare a brief account containing device, application, time, exact symptom and comparisons already performed. Include whether local recordings work and whether another connection changes the result. Do not disclose confidential meeting content when it is unnecessary for diagnosis.
Keep an approved temporary alternative available for important meetings, such as the existing working audio connection. Treat it as a workaround while the cause remains uncertain. After a change, repeat the same brief test. A traceable comparison helps establish whether the particular problem has been addressed or simply failed to occur during one conversation.
