4 min tutorial

Troubleshooting

Work through the most common reasons setup is still blocked.

Outcome

You can distinguish between app-not-running, API-disabled, and shortcut-readiness issues.

Numbered steps

1
Check whether the Teams desktop app is running on the same Mac.
2
Confirm Third-party app API is enabled in Teams Settings > Privacy.
3
Re-open MuteCall and compare the visible state against the readiness model.
4
If Teams is connected, confirm at least one mute shortcut is configured before testing again.

What success looks like

You know whether the blocker is Teams not detected, Teams app detected, Teams is connected, or shortcut setup.
You can retry the flow without guessing.
You only need support for issues outside the normal setup path.

If this does not work

Teams not detected means the desktop app is not currently running.
Teams app detected means Teams is open but the local API is still unavailable.
Teams is connected means the app can talk to Teams and the next step is shortcut validation.

Next step

Return to the landing page or download the Mac build.