The Use Case Fathom Misses
Fathom is often described as a great free meeting recorder — and it is, under specific conditions. One condition it doesn't always meet: being a participant rather than the host.
On Microsoft Teams in particular, Fathom's bot requires host-level permissions to join and record. If you didn't create the meeting, you may find the bot can't join at all — leaving you with no transcript from precisely the meetings where someone else set the agenda.
Who This Affects
The host requirement sounds niche but it affects a large slice of working professionals:
- Freelancers and consultants who regularly join client-owned calls. The client hosts; you attend. Fathom doesn't work.
- Salespeople in discovery or demo calls where prospects host their own meetings. You need notes on conversations you didn't organise.
- Employees in vendor or partner calls — supplier reviews, customer success check-ins, any recurring meeting run by an external party.
- Junior employees in large team meetings run by managers or directors. Fathom joins only if the person who created the meeting has the right settings.
- Anyone using Teams at an organisation where meeting hosting defaults to the calendar organiser.
The Workarounds Are Awkward
The most common workaround is to ask the meeting host to admit the Fathom bot or to add you as a co-host. This works in practice but creates friction:
- You have to explain to clients or external parties why a bot is joining their meeting
- You have to remember to ask for every relevant meeting
- Some external hosts will decline, leaving you without a transcript
- The conversation itself becomes about your tooling rather than the meeting's purpose
A second workaround — recording the audio yourself locally — bypasses the problem but loses all the AI summary functionality. You just have a raw audio file.
Why It's a Structural Problem
Bot-based meeting tools fundamentally depend on platform permissions. On Zoom, Fathom works well because Zoom's permission model is relatively permissive. On Teams, the permission model is stricter and enterprise-configured — and many organisations have locked down third-party bot access at the tenant level, making Fathom impossible to use regardless of whether you're the host.
This isn't a bug Fathom can fix easily. It's an architectural consequence of how bot-joining works on different platforms.
What the Alternative Looks Like
The cleaner approach is a meeting tool that doesn't depend on bot admission permissions. Beaver joins meetings using your own credentials — it's you in the meeting, with Beaver transcribing alongside you. Whether you're the host, a participant, or a guest, it works the same way. No bot permission requests, no host dependency, no platform-specific compatibility gaps.
Try Beaver free — set it up for your next client call and see the difference.
