Can You Use an AI Notetaker When You Are Not the Host?

The short answer

Sometimes, and almost never through the meeting platform's own note taking feature. If the call belongs to someone else, the built in AI notes on Zoom, Google Meet and Microsoft Teams are administered by that someone else. They decide whether the feature exists on the call, whether you are allowed to turn it on, and whether the output ever reaches you. None of those three are settings you can change from your side of the call.

This matters far more than it sounds, because of who ends up asking the question. Consultants, fractional executives, salespeople, agency leads and founders doing partner and investor calls spend most of their week as a guest. Their own team's meetings are the small part of the calendar. The calls with the highest stakes, a client escalation or a diligence session, are the ones held on the other company's link.

The advice you usually find is about etiquette, and it says to ask the host first. That is reasonable and it is covered below, but it answers a different question. What follows is the mechanical answer, per platform, from each vendor's own documentation, so you can tell before you buy which calls a given tool will actually cover for you.

Zoom: the host starts it, you can only send a request

Zoom's documentation for Meeting Summary with AI Companion is direct about the control. Only the meeting host and co-host can start or stop the meeting summary through the in-meeting controls. As a participant you get one move, which is to ask. If no in-meeting AI feature is active, any participant can request that it be started, and the host receives an in-meeting request to approve or ignore.

There is a second catch on the output. Zoom states that participants must be signed in to their Zoom account during the meeting to receive the summary automatically, and that unauthenticated users will not receive an email summary because no email address was associated with their presence in the meeting. If you joined a client's call from a browser without signing in, which is what most people do when the link opens in the wrong place, you were never in line to receive anything.

So on a client's Zoom, your practical position is that you can raise your hand mid-call and hope, and that a distracted host declining a popup is the end of it. A workflow that depends on the other party pressing a button is not a workflow.

Google Meet: the organizer's plan decides, and the file lands in their Drive

Google Meet's take notes for me feature has three separate gates and a guest is outside all of them. First, licensing: the feature requires an eligible Google Workspace edition or Google AI plan, and Google's own troubleshooting section names the organizer specifically, saying the meeting organizer must have the Workspace edition that includes take notes for me. Your own subscription does not travel to their meeting.

Second, who may start it. Google's FAQ says the meeting organizer and participants internal to the host's organization can start or stop notes, and that when host controls are enabled, only the meeting organizer, hosts and co-hosts can do so. An external guest is not in either group. Being on the invite is not the same as being inside the organization.

Third, where the output goes. The notes document is generated after the meeting and saved in the meeting organizer's Google Drive. Access is set by a sharing menu that Google says is only visible to hosts and co-hosts, and one of its options is to share the notes with hosts and co-hosts only. The host can leave your name on the invite and still keep the record. That is a defensible choice on their part, and it means the call you were paid to attend can leave you with nothing.

Microsoft Teams: a guest cannot record at all

Teams is the clearest case, because Microsoft publishes a table of who can start and stop a recording. The meeting organizer can. A person from the same organization can. A person from another organization or company cannot. A guest cannot. An anonymous participant cannot. There is no request flow to fall back on and no setting a guest can flip.

Recording is the foundation the AI layer sits on, so this is not only about video. Microsoft also notes that organizers with Teams Premium or a Copilot license can choose who is allowed to record and transcribe, with options that narrow it to organizers and co-organizers, or to nobody at all. A security-conscious client can close the feature for everyone in the room, themselves included.

The output follows the same pattern as Meet. The recording is processed and saved in the meeting organizer's OneDrive for Business, and Microsoft's own note says guests and external attendees can view the recording only if it is explicitly shared with them. If you are the outside party on a Teams call, you are not a participant in that record, you are a possible recipient of it.

The bot route has a second gate, and it is not the host

The usual answer to all of the above is to bring your own notetaker, which for most tools means a bot that joins the call as a participant with a name like Otter or Fireflies. That moves the problem rather than solving it, because a bot is a participant and participants are governed. It can sit in a waiting room nobody is watching, or be turned away by a policy that requires everyone to be signed in to a company account.

It can also be stopped a level above the host. Cornell's IT documentation states that Read.ai and Fireflies.ai are currently automatically blocked from joining Cornell Zoom meetings, and that hosts do not need to do anything for the block to apply. The person you are meeting may be happy for you to take notes and still have no ability to let your bot in. Universities were early and public about this, and enterprise security teams have been arriving at the same place, usually because a bot recording a call with outside parties creates an obligation the company never agreed to.

There is also the version of this that costs a deal rather than a record. A bot named after your notetaker appearing in the participant list of a first call with a cautious buyer is a conversation about your tooling that you did not plan to have, at the exact moment you wanted to talk about their problem.

The three ways this fails for a guest

Put together, a guest-heavy calendar runs into three distinct failures, and tools that claim to handle non-host meetings often only address one of them. Worth checking each one separately when you evaluate.

• You cannot start capture. The platform feature is host-only or organization-only, and your request can be ignored or missed.
• You cannot get the output. Capture happened, the file lives in the organizer's Drive or OneDrive, and sharing is a decision you do not control.
• Your own tool is refused entry. A bot is subject to waiting rooms, authentication rules and tenant-level blocks set by an admin you will never meet.
• The quieter fourth one: your record has holes in the shape of your best clients. Whichever calls were on somebody else's strict platform are simply missing when you go looking a month later.

The part nobody else administers

One link in the chain is not controlled by the other side, which is the audio arriving at your own computer. A notetaker that captures on your machine does not ask the host for anything, does not appear in the participant list, and does not care which platform the meeting is on, because nothing is installed on theirs. The permission model stops being someone else's setting and becomes your own decision, which is the right place for it if you are the person accountable for the follow up.

This is how Driffle is built. It runs as a Mac app that captures the meeting audio on your side, so a client's Zoom, a prospect's Teams call and a partner's Meet link all produce the same kind of record, and a guest appearance is treated no differently from a meeting you scheduled. Nothing joins the call and no extra name shows up for anyone else in the room.

The specifics, so you can check them against your own setup: Driffle is a direct download for Mac on Apple Silicon and needs macOS 14.4 or later, Windows and Intel Mac builds are request only at the moment, and capture happens on your Mac while transcription and summarising run in Driffle's own cloud account, with no training rights on your work. If you need a Windows machine covered this quarter, that is a real gap and worth knowing before a trial rather than after.

Why this matters more after the call than during it

The reason to care about coverage is not tidiness, it is that a guest's record is the only record they have. When the client's own notes live in the client's Drive, your version of what was agreed in July is whatever you personally retained.

That is also where a per-meeting notes tool stops being enough. The question you need answered six weeks later is rarely about one call. It is closer to what this client asked us to stop doing, or when the scope changed and who was in the room, and answering it means reading across a dozen conversations at once. Driffle keeps meetings, decisions and commitments in one memory you can question later, so the follow up you owe comes from the record rather than from your recollection of the record.

For anyone billing by engagement, that continuity is the whole asset. Clients change platforms, hosts change settings, and your history should not develop gaps every time either of those happens.

Being able to is not the same as being allowed to

Everything above is about capability. It is not permission, and it would be dishonest to present local capture as a way around the host's wishes. The reason those platform controls exist is that people on a call have a reasonable expectation about who is keeping a copy.

The norm being set by institutions is explicit about this. Fordham's IT advisory tells staff to refrain from using AI note-taking tools if they are not the session's host, and if they still want to, to speak to the host beforehand and then inform all participants if the host agrees. Recording law also varies by where the participants are, and some jurisdictions require consent from everyone rather than just you, so treat that as a question for your own counsel and not for a vendor's marketing page.

In practice the workable version is simple and takes one sentence at the top of the call: say you keep notes for your own follow up, say the record is yours and not shared with anyone outside your team, and stop if anyone objects. That is a much easier sentence to say when the answer to what joins the call is nothing, and when the honest answer to who has a copy is you.

A test worth running during a trial

Most evaluations get run on internal meetings, where you are the host and everything works. That tells you almost nothing about the calls you bought the tool for. Point the trial at the awkward cases instead.

• Take notes on a call you did not organize, on the other party's platform, without asking them to change a setting.
• Do it on the strictest client you have, the one whose security team blocks things, and see whether the record exists afterwards.
• Check what the other participants saw. Ask someone you trust whether anything appeared in the participant list or the chat.
• Wait two weeks, then ask across several of those meetings at once, not for one summary. A tool that can only return the call you name is a filing cabinet.
• Confirm the record is yours if the client's tooling changes next quarter, and that you can get it out.

Where this leaves you

If you host most of your meetings, the platform features are genuinely fine and you should use what you already pay for. If you are a guest on other people's calls all week, you have been evaluating tools on the wrong meetings, and the honest answer to the question in the title is that the platform's own notes will keep failing you precisely where the money is.

The fix is to stop asking the other side for permission to remember your own work, and to pick capture that runs where you are. If your week looks like that, Driffle is a free download for Mac at driffle.ai/download.