If Teams or Zoom audio is broken, do not start by reinstalling the app. Start by proving where the problem lives: user mute, app selection, operating system input/output, browser permissions, headset hardware, Bluetooth weirdness, or network quality.

Use this checklist when someone says “my mic does not work,” “I cannot hear anyone,” or the classic ticket: “Zoom is broken.” It is written for help desk and IT support techs who need a repeatable flow, not a 40-minute guessing session while six people stare at the meeting tile.

Quick answer: test the same audio device in the OS first, then in the meeting app, then in a second app or browser. If the device fails everywhere, troubleshoot hardware or drivers. If it only fails in Teams or Zoom, fix app permissions, selected devices, app cache, or meeting settings.

The 60-second triage questions

Before touching settings, get the scope clear. Audio tickets get messy because everyone uses the same words for different failures.

Ask:

  1. Can you hear other people?
  2. Can other people hear you?
  3. Is this happening in Teams, Zoom, both, or every app?
  4. Are you using built-in laptop audio, USB headset, Bluetooth headset, docking station, or conference room equipment?
  5. Did it work earlier today? What changed?
  6. Are you remote, in office, on VPN, or on guest Wi-Fi?

That gives you the first fork:

SymptomFirst place to check
User cannot hear anyoneOutput device, volume mixer, meeting speaker selection
Nobody can hear userInput device, mute controls, privacy permissions
Audio works in one app but not anotherApp device selection, browser permissions, cache
Audio cuts in and outBluetooth, network quality, CPU load, docking station
Echo or feedbackMultiple open devices, room speakers, bad mic placement

Write the exact symptom in the ticket. “Audio issue” is not documentation; it is a shrug with a ticket number.

Step 1: Check the embarrassing stuff first

This is not insulting. This is efficient.

Check:

  • The user is not muted in the meeting.
  • The meeting host did not mute them.
  • The headset has no physical mute switch enabled.
  • The cable is fully seated.
  • The headset is charged.
  • The laptop volume is not at zero.
  • The correct meeting tab/window is active if using browser audio.
  • The user is not connected to a random Bluetooth device in another room.

Bluetooth is especially good at wasting your life. A laptop may show “connected” to earbuds in a bag, a car in the parking lot, or a headset paired to both phone and laptop. If audio disappears after a few seconds, disconnect Bluetooth and test with wired or built-in audio.

Step 2: Prove the device works outside the meeting app

Do not debug Teams until you know Windows or macOS can see the microphone and speakers.

On Windows:

  1. Open Settings → System → Sound.
  2. Confirm the correct Output device is selected.
  3. Confirm the correct Input device is selected.
  4. Use Test your microphone or watch the input meter move while the user talks.
  5. Open Volume mixer and make sure Teams, Zoom, or the browser is not muted.

On macOS:

  1. Open System Settings → Sound.
  2. Check Output and select the intended speakers/headset.
  3. Check Input and select the intended microphone.
  4. Watch the input level move while the user talks.
  5. Check Control Center for active mic mode or output routing.

If the OS does not see the device, the meeting app is probably innocent. Move to cable, port, driver, Bluetooth, docking station, or headset replacement.

Step 3: Check app device selection

Teams and Zoom can use different devices than the operating system default. That is useful until it is not.

Microsoft Teams

In Teams:

  1. Open Settings → Devices.
  2. Confirm the right Audio devices profile.
  3. Confirm Speaker and Microphone are not set to the wrong monitor, dock, webcam, or Bluetooth device.
  4. Use Make a test call if available.
  5. During a meeting, open device settings and confirm the same selections.

Common Teams trap: the user joins a meeting from a browser tab once, then the desktop app later, and the two sessions have different permissions or devices. Ask which one they are actually using.

Zoom

In Zoom:

  1. Open Settings → Audio.
  2. Test Speaker.
  3. Test Microphone and watch the input level.
  4. Disable auto microphone switching while troubleshooting.
  5. During a meeting, click the arrow beside the microphone icon and confirm the selected speaker and mic.

Zoom makes testing easier than most apps. Use the test buttons instead of guessing.

Step 4: Check privacy and browser permissions

If audio works in the OS but not in the app, permissions are the next stop.

On Windows, check:

  • Settings → Privacy & security → Microphone
  • Microphone access is on.
  • Desktop apps are allowed.
  • Teams, Zoom, or the browser has access.

On macOS, check:

  • System Settings → Privacy & Security → Microphone
  • Teams, Zoom, Chrome, Edge, or Safari is allowed.
  • Restart the app after changing permissions.

For browser meetings, check the browser site permission too. In Chrome or Edge, click the icon beside the URL and confirm microphone permission for the meeting site. A browser can block mic access even when the operating system allows it.

Step 5: Isolate headset, dock, and Bluetooth problems

A lot of video-call audio tickets are not Teams or Zoom problems. They are accessory problems wearing a software costume.

Use this order:

  1. Test built-in laptop mic and speakers.
  2. Test the headset on another USB port.
  3. Test without the dock.
  4. Test a different headset.
  5. Test the same headset on another machine.
  6. If Bluetooth is involved, unpair and re-pair only after a wired/built-in test.

Docking stations deserve special suspicion. They often expose multiple audio devices: monitor speakers, dock audio, webcam mic, headset, and laptop speakers. If the user moves between home and office, Teams may cling to yesterday’s device like it has abandonment issues.

Step 6: Check network and performance only after device tests

Network problems usually sound like choppy audio, robotic voices, delay, or users dropping from calls. They do not usually cause a microphone to be completely missing from device lists.

Check:

  • Is the user on weak Wi-Fi?
  • Are they on VPN when the meeting does not require it?
  • Is CPU or memory pinned during calls?
  • Are cloud backup, browser tabs, or security scans eating bandwidth or CPU?
  • Does audio improve on a phone hotspot or wired network?

If the problem is choppy audio, pair this with the same practical mindset from the VPN troubleshooting checklist and Wireshark network troubleshooting guide. Start with scope and symptoms before reaching for deep packet wizardry.

A reusable Teams and Zoom audio troubleshooting checklist

Copy this into your ticket notes or knowledge base:

  • Confirm exact symptom: cannot hear, cannot be heard, choppy audio, echo, or wrong device.
  • Confirm affected app: Teams, Zoom, browser, all apps.
  • Check meeting mute, host mute, headset mute, and device volume.
  • Confirm OS input/output device selection.
  • Test microphone input level in Windows or macOS.
  • Confirm Teams or Zoom speaker and microphone selection.
  • Check microphone privacy permissions.
  • For browser meetings, check site permissions.
  • Test built-in audio to bypass headset/dock/Bluetooth.
  • Test headset on another port or machine.
  • If audio is choppy, check Wi-Fi, VPN, CPU, and memory.
  • Document the fix in plain English.

What to write in the ticket

Good ticket notes make repeat issues faster. Bad ticket notes create archaeology projects.

Use a format like:

Issue: User could hear meeting audio in Teams, but other attendees could not hear user.
Scope: Teams desktop only. Windows sound settings detected headset mic correctly.
Checks: Verified user not muted, headset mute off, Teams microphone set to monitor mic instead of headset mic.
Fix: Changed Teams Settings → Devices → Microphone to Jabra headset. Test call passed.
Next step: If recurring after dock changes, update headset firmware or reset Teams device cache.

That is useful. “Fixed audio” is not.

When to escalate

Escalate when:

  • The OS does not detect known-good audio devices.
  • Drivers fail repeatedly after reinstall or update.
  • Multiple users in the same location have choppy calls.
  • Conference room hardware fails across devices.
  • Teams or Zoom admin policies appear to block device access.
  • The issue follows a recent MDM, security, browser, or operating system update.

Include what you already tested. Your escalation note should save the next person time, not make them repeat the first 20 minutes.

FAQ

Why does my microphone work in Zoom but not Teams?

Usually because Teams has the wrong microphone selected, lacks OS microphone permission, or is stuck on an old device from a dock, monitor, or Bluetooth headset. Test the mic in the operating system first, then compare Teams and Zoom device settings.

Should I reinstall Teams or Zoom for audio problems?

Not first. Reinstalling is a last-ish step after you prove the OS sees the device, app settings are correct, permissions are allowed, and the problem follows the app rather than the headset or dock.

Why does Bluetooth audio sound bad in meetings?

Bluetooth headsets can switch profiles when the microphone is active, which may reduce audio quality. They can also fight with phones, cars, and previous pairings. For troubleshooting, test with wired or built-in audio before blaming the meeting platform.

What should a new help desk tech learn from audio tickets?

Audio tickets teach the core support habit: isolate the layer before changing things. The same method applies to email troubleshooting, network share troubleshooting, and plenty of interview scenarios in troubleshooting interview questions.

Bottom line

Teams and Zoom audio troubleshooting is mostly disciplined isolation. Start with the symptom, test the OS, test the app, bypass accessories, then look at network and performance. The boring order works.

If you are building real help desk skills, save this checklist and practice explaining each step out loud. For more practical IT support guides, subscribe to the IT Support Group newsletter on the homepage and keep stacking the troubleshooting reps that actually make you useful.