Can a notetaker bot join a Google Meet or Teams call you don't host?

Yes. A notetaker bot joins a Google Meet or Microsoft Teams call as an ordinary participant, so it does not need you to be the host. It needs what any guest needs: the meeting link, and someone in the call willing to let it in if the meeting holds outsiders at the door. It is visible to everyone in the participant list, and you should say what it is for and get the consent your client and your jurisdiction expect. This guide is for freelancers and consultants who are guests in most of the meetings they attend.

How does a bot get into a meeting it doesn't host?

The same way you do. A notetaker bot is a browser session that opens the meeting link, gives itself a display name, and asks to join. The host installs nothing and changes nothing. If the link works for a human guest, it works for the bot, subject to the same admission rules.

That means the bot needs three things: the link, which it takes from your calendar invite; a name, which the other participants will see; and a route in, which is whatever the organiser's meeting settings allow for a participant from outside their organisation.

What decides whether it gets in on Google Meet?

Two layers, and you control neither.

The first is the organisation's policy. A Google Workspace organisation can decide whether people outside it may join its meetings at all, and whether they must be signed in to do so. If the organiser's company allows no outside participants, the bot cannot join, and neither could you from a personal account. Only the organiser's admin can change that.

The second is the people in the call. Meet usually lets a participant from outside the organiser's organisation join only after someone inside admits them. The bot knocks, like any guest, and waits. If nobody notices the knock, it never gets in and nothing is recorded.

So the practical questions to ask before a meeting with a new client are: does your company allow outside participants, and who will admit the notetaker when it knocks?

What decides on Microsoft Teams?

The lobby. Every Teams meeting has lobby settings chosen by the organiser or their organisation, and they decide who walks straight in and who waits. Some meetings admit everyone with the link; some hold anyone from outside the organisation until an organiser or presenter lets them in; some hold everybody. The bot follows the same route as a guest with the same link.

If the meeting is one where outsiders wait, the bot will sit in the lobby until someone admits it. Tell the organiser in advance: "a notetaker called [name] will be in the lobby at the start; please let it in." That one sentence prevents most failed joins.

Is the bot visible to everyone?

Yes, and it should be. It appears in the participant list under its display name, on Meet and on Teams, for the whole meeting. Anyone who looks will see it, and someone usually asks what it is in the first minute.

Have the answer ready: "That's my notetaker. It records the call so I can send you proper minutes afterwards, and the recording stays in a workspace only I can see. Happy to remove it if anyone would rather I didn't." Say it before they ask if you can.

Do not give the bot a misleading name and do not try to make it look like a person. A visible, plainly named participant is what makes the recording defensible.

Should you tell people, and what about consent?

Tell people twice: once in writing before the meeting, in the invitation or a message, and once at the start of the call. If anyone objects, remove the bot and take notes by hand. A client who says no is not being difficult; they may have a policy, a colleague on the call who was not warned, or a topic they would rather not have recorded.

Consent rules for recording a conversation differ between countries and between companies, and many client contracts have their own clause about recordings. Some places expect every participant to agree, some expect only one, and a company policy can be stricter than either. This guide cannot tell you which applies to you. Check the rules where you and your client are, ask the client what they expect, and put the arrangement in your engagement letter: that meetings may be recorded by a notetaker, who can see the recordings, and when they are deleted.

What do you do if the bot is waiting in the lobby?

Someone inside has to admit it; it cannot admit itself. On Meet, look for the prompt that someone wants to join. On Teams, look for the lobby notification. If you are in the meeting and the organiser's settings allow it, you can admit it yourself. If you have not joined yet, join first and then admit it.

If the meeting has started and the bot is still waiting, admit it late. Recording starts when it gets in, and the minutes before that are not captured, so the notes will begin mid-conversation. Say so when you send them.

Do not send a second bot to fix the first one. Two notetakers in a meeting is the fastest way to make a client uneasy, and the second one is subject to the same lobby as the first.

What happens if it is never admitted?

Nothing is recorded. There is no transcript, no summary and no minutes, and the join is recorded as failed. That is the honest outcome, and it should be visible in whatever tool you use rather than silent. Check after any meeting where you did not see the bot arrive.

If the meeting is still running, you can retry the join. If it has ended, write your own notes from memory while it is fresh, tell the client the notetaker did not get in, and fix the admission for next time: ask the organiser about their outside-participant policy, or agree who will admit the bot.

How TrackHeros does it

The TrackHeros bot joins as a visible participant under the name "TrackHeros Notetaker", which you can change per client (one line, no emoji). It can post an optional short greeting in the meeting chat when it joins, so nobody has to wonder what it is. It joins about two minutes before the start so it is already waiting when the first person arrives; a meeting that started more than ten minutes ago is not chased.

A failed join can be retried with one click, and the app refuses to send a second bot into a meeting that already has one. Auto-join is a three-level setting, per meeting, per recurring series and account default, so a client who does not want recordings can be switched off at the series level and forgotten about; the most specific setting wins and the app shows which one decided.

On Google Meet the bot joins from whichever connected Google account owns the invite, so it arrives with the right identity for that client. Teams meetings are joined from their link, wherever the link was hiding: conference data, the location field or free text in the description, including forwarded Teams invites. Connecting a Microsoft account for calendar sync is not yet available. The details are at /features/google-meet-notetaker/ and /features/microsoft-teams-notetaker/, and the account model at /features/multi-account/.