An AI assistant for Teams your administrator does not have to approve
In most organisations the blocker is not the tool, it is the ticket. Anything that joins a Teams call is an app in the tenant, and an app in the tenant is a review. Whisperer never enters the tenant: it runs on your own machine and listens to your own audio.
No tenant app · no admin consent · no bot in the call
- Needs an administrator to allow it organisation-wide
- Gets permissions on your workplace account
- Its access outlives your interest in it
- One policy change and it stops working for everyone
- Nothing is registered in Microsoft 365
- No permissions on your work account at all
- Access is the audio you can already hear
- Uninstalling it removes everything
Honest framing
This is not a way around your company's policy
It is worth being direct about this, because the reasoning above can be read the wrong way. The reason Whisperer needs no administrator is technical: it is a local application, like a notepad or a screen recorder, and there is nothing for a tenant to approve.
Whether your employer is comfortable with an assistant on internal calls is a different question, and it is theirs to answer. If there is a policy, it applies regardless of what the software architecture makes possible.
Setup
Two permissions on your own computer
-
Microphone
Your voice. Teams asks for its own microphone access separately; the two do not conflict and both are needed.
-
System audio
On Windows — where most Teams calls happen — nothing extra is required beyond making sure Teams plays through the default output device. On macOS, the Screen Recording permission.
-
Play, then join
Start the Whisperer session first, then join the meeting. Both speaker labels should appear within the first few lines.
Where it earns its place
Internal calls produce work, not content
A Teams day is mostly standups, planning and reviews — conversations whose value is entirely in what has to happen afterwards. That makes the post-call half of Whisperer the part that matters here.
Limits
Two limits, one of them awkward on Teams
Teams meetings often have half the participants in a conference room on one device. In that setup your laptop microphone hears the room, system audio hears the remote people, and the room itself is not separated by speaker.
A finished recording can be uploaded: the Meetings section takes one file up to 25 MB — mp3, m4a, wav, ogg, flac, aac, plus mp4 and webm, from which the audio track is used. What is missing is bulk upload of a whole archive; and it spends the same minutes a live call does.
Questions
Microsoft Teams questions
Does IT have to approve anything?
Nothing in Microsoft 365. Whisperer is a desktop application and registers no app, requests no Graph permissions and holds no token for your work account. Whether your workplace policy allows it is a separate question from whether it is technically possible.
Does it work with Teams on the web?
Yes. Whisperer captures audio at the operating system level, so the desktop client and the browser client behave the same.
Can it separate five people in a Teams call?
Not individually. There are two streams: you, and everything else the computer is playing. On a group call the transcript separates your lines from theirs, but not theirs from each other.
Will it show up in the meeting or the chat?
No. Nothing joins, nothing posts, and no notification is raised. The meeting looks exactly as it would without it.
What about calls where I am in a conference room?
That is the weakest case for any overlay assistant. If the room is on a single device and you are in it, your microphone picks up the room without separating speakers, and remote participants come through system audio.
Start with the meeting nobody writes up
Pick the recurring internal call that ends with everyone assuming someone else took notes. That is where the difference is largest and easiest to judge.
Related pages