How to Record Meetings on Zoom, Teams, and Google Meet Without a Bot

You're five minutes into a client call when a new participant joins. "Fireflies.ai Notetaker has joined the meeting." The client pauses. "Who is that?" You scramble to explain that it's just a recording tool — it's fine, totally normal, nothing to worry about. The conversation resumes, but something has shifted. The client is more guarded now. The candid feedback you were hoping for doesn't come.

If you've used a bot-based meeting recorder on Zoom, Teams, or Google Meet, you've probably experienced some version of this. The "who invited the bot?" moment is a recurring source of friction — and it's not the only way to record meetings. There are actually three fundamentally different approaches, and the differences matter more than most people realize.

Three Ways to Record a Meeting

Platform-native recording

Zoom, Microsoft Teams, and Google Meet all have built-in recording features. This is the most straightforward approach, but it comes with significant limitations.

You typically need to be the meeting host (or have host permissions) to start recording. Everyone in the meeting gets notified. The recording is stored in the platform's cloud — Zoom's cloud, Microsoft's cloud, or Google Drive. And the AI analysis is limited to whatever the platform offers, which is usually basic transcription and, more recently, simple summaries.

The biggest limitation? Each platform handles recording differently. Your Zoom recordings live in one place, Teams recordings in another, and Google Meet recordings in a third. If you switch between platforms — or if you attend meetings across all three — there's no unified view of your meeting history.

Bot-based recording

This is how most third-party meeting AI tools work — Otter.ai, Fireflies, tl;dv, and similar products. When you connect the tool to your calendar, it automatically sends a bot to join your meetings as a participant.

The bot appears in the participant list. Most platforms display a recording notification. The bot captures audio (and sometimes video) through the meeting platform's API, then uploads it to the tool's cloud for processing.

The quality of AI analysis is often better than platform-native recording — you get structured summaries, action items, topic detection. But the tradeoff is the bot's presence. It changes the dynamics of the meeting. Participants become more cautious. Clients and external contacts question who's listening. And in some organizations, IT security teams block third-party bots entirely, which means the tool simply doesn't work.

There's also a scaling problem. When multiple people in a meeting use different recording tools, you end up with two or three bots in the same call. It's distracting, it's redundant, and it makes everyone uncomfortable.

System audio recording

The third approach works differently from both of the above. Instead of joining the meeting as a participant or relying on platform features, a system audio recorder captures the audio output from your computer directly — the same audio you hear through your speakers or headphones.

No bot joins the meeting. No notification appears. The tool isn't interacting with Zoom, Teams, or Google Meet at all. It's simply recording what your sound card is playing.

Most system audio recorders also capture your microphone input simultaneously, so both sides of the conversation are recorded. The two audio streams — what you hear and what you say — are combined and sent to AI for transcription and analysis.

How System Audio Recording Actually Works

The technical explanation is simpler than you might expect. Your computer's operating system manages audio through a series of streams. When someone speaks in a Zoom call, that audio travels from Zoom to your operating system's audio subsystem, then to your speakers or headphones.

A system audio recorder taps into that audio stream at the operating system level. It's capturing the same signal that's being sent to your speakers — nothing more, nothing less. If you can hear it, the tool can record it.

Your microphone input works similarly but in reverse. The tool captures the same audio signal that your microphone is sending to the meeting platform.

This means the recorder is entirely decoupled from the meeting platform. It doesn't know or care whether you're on Zoom, Teams, Google Meet, Slack Huddles, or a phone call through your computer. If audio is playing through your system and you're speaking into your mic, it can record both.

It Works the Same on Every Platform

This platform-agnostic quality is one of the most practical advantages of system audio recording. There's nothing to configure per platform, no OAuth permissions to grant, no API connections to maintain.

Zoom — works identically whether you're a host or participant, free or paid plan.

Microsoft Teams — works in regular meetings, channel meetings, webinars, and town halls. No admin permissions required.

Google Meet — works regardless of your Google Workspace tier. No extension needed.

Slack Huddles — works just as well, even though Slack doesn't offer native recording for huddles.

Phone calls via computer — if you take calls through a softphone app or browser-based phone system, those are captured too.

Webinars and virtual events — any audio that plays through your computer is recordable.

The recording experience is identical across all of these because the tool never touches the meeting platform. You start recording, have your meeting, stop recording. The platform is irrelevant.

A Note on Recording Laws and Ethics

System audio recording is powerful precisely because it's invisible. That's a feature, but it's also a responsibility that deserves serious attention.

Recording laws vary significantly by jurisdiction. In the United States, recording laws are set at the state level. Some states (like New York and Texas) are "one-party consent" states — only one person in the conversation needs to consent to the recording, and that person can be you. Other states (like California, Illinois, and Florida) are "two-party" or "all-party consent" states — everyone in the conversation must know they're being recorded.

International laws vary even more. Many EU countries require all-party consent. Canada's federal law requires one-party consent, but provincial laws differ. Australia generally requires all-party consent.

Company policies add another layer. Even in one-party consent jurisdictions, your employer or client may have policies that require disclosure of any recording.

The technology enables invisible recording, but legality and ethics are separate questions. You should always check your local laws and your organization's policies before recording any conversation. When in doubt, disclose. The fact that you can record invisibly doesn't mean you always should.

Why Bot-Free Recording Produces Better Meetings

Setting aside the legal and ethical considerations for a moment — when recording is appropriate and lawful — the absence of a bot meaningfully improves meeting quality.

Conversations stay natural. People don't moderate themselves when they don't see a recording bot. You get candid feedback, honest objections, and real reactions instead of the polished, guarded version.

No interruptions. There's no "who is that?" moment. No fumbling with permissions to let the bot in. No awkward explanation to clients or external stakeholders.

No IT friction. Many organizations block third-party bots from joining meetings for security reasons. System audio recording doesn't trigger those blocks because it never interacts with the meeting platform.

Works when bots can't. Some meeting types — informal Slack huddles, phone calls, webinars where you're an attendee — don't support bot-based recording at all. System audio recording works regardless.

No bot proliferation. In a meeting where three people each use a different recording tool, a bot-based approach means three bots in the call. System audio recording runs locally on each person's machine with zero impact on the shared meeting experience.

The net effect is that meetings feel like meetings again, not performances for the recording bot.

Record Better Meetings Starting Today

The bot-based recording model was an early solution to a real problem — people need better meeting documentation. But it introduced a new problem: meetings that feel different because they're visibly being recorded by a third-party tool.

System audio recording solves the original problem without creating the new one. You get AI-powered transcription, structured summaries, and action items — from a meeting recorder that nobody in the meeting can see.

MeetWave records through system audio on Windows. No bot joins your Zoom, Teams, or Google Meet calls. No notification appears. You just get better meeting notes without changing the meeting itself. Try MeetWave free and see what meeting recording looks like without the awkward bot.