Letting an AI meeting note taker sit in on your calls

Most comparisons of AI meeting note takers treat the decision as a shopping problem: which tool transcribes best, which summary reads best, which costs least per seat. The harder part shows up on the first call. Something new is in the room, either a named participant in the attendee list or a piece of software running on one laptop, and the people on the call behave slightly differently because of it.

That behaviour change is the real subject. A note taker that produces flawless transcripts and makes two people stop speaking candidly has cost more than it saved. So the useful order is: decide how the tool gets into the call, decide what the team is told, decide where the text lives afterwards, and only then compare plans.

Two ways in, and they are not interchangeable

Every tool in this category uses one of two capture methods, and the choice determines almost everything else.

A bot joins the meeting. The tool dials in as a participant using a calendar connection, appears in the attendee list under a name, and records the stream the conferencing platform sends it. This method works across platforms, captures the call even when the person who set it up leaves early, and keeps working on a phone or a tablet because the recording happens in the vendor's infrastructure rather than on a device. It is also visible to everyone, including clients and candidates, which is either the honest option or an awkward one depending on the meeting.

The device captures audio. The tool runs on one person's machine and records system audio and the microphone, with no extra participant in the list. Nothing announces itself, which makes it the only workable option for in person meetings and for calls where an extra attendee would be odd. The cost is fragility: it captures what that one machine hears, so a dropped connection, a muted headset or a closed laptop takes the record with it.

A third option is already paid for. Conferencing platforms now include transcription and summary features, and in Microsoft Teams the ability to record and transcribe is governed by admin policy and, for the finer controls over who may do it, by a Teams Premium or Copilot licence. Checking what the existing platform already produces is worth an hour before any trial starts, because the answer is sometimes "enough".

Neither capture method is more accurate than the other in any general sense. Accuracy tracks microphone quality, the number of people speaking over each other, and how much jargon and how many proper nouns the conversation contains. A quiet call with a good headset transcribes well through either route. Four people in a meeting room sharing one laptop microphone transcribes badly through both.

What changes in the room

The visible effects are consistent enough to plan for.

People become more careful and slightly more formal. This is not entirely bad. Meetings where something is being recorded tend to produce clearer decisions, because participants restate conclusions for the record. The loss is the half formed idea, the "this might be stupid, but" contribution, and the honest comment about a client or a colleague. Those contributions are where a lot of value lives, and they are the first thing to disappear.

External guests react more strongly than colleagues. A named bot in a sales call or an interview reads as surveillance to some people, and the polite version of that reaction is a shorter, more guarded conversation. The fix is not to hide the recording, it is to say in the invitation that notes will be taken automatically, and to ask rather than announce when the other side is a customer or a candidate.

The third effect is subtle and worth watching: attendance goes up and attention goes down. When a searchable record exists, people join calls they should have skipped and half listen, because catching up later is now possible. A note taker can quietly make meetings larger and worse, which is the opposite of the intent.

The countermeasure is to name the exceptions out loud. Decide which categories of meeting are never recorded, typically one to ones, performance conversations and anything involving a complaint, and write that down somewhere the team can see it. A blanket "everything is recorded" policy produces a chilling effect that no tool setting can undo.

Consent is a setting, not a sentence in the invitation

Announcing the recording is courtesy. Consent is a configuration, and the platforms treat it that way.

In Microsoft Teams, every participant gets a notification in the desktop, web and mobile apps as soon as a recording starts, external participants cannot start a recording themselves, and administrators can require explicit agreement before anyone can unmute or turn on their camera, with the consent result stored in the meeting attendance report. Teams also ties Copilot to recording: turning Copilot off for a meeting turns off recording and transcription as well.

Two practical points follow. First, if a legal or HR requirement exists, the setting is what satisfies it, not a line in the calendar invitation. Second, jurisdictions differ on whether announcing a recording is sufficient or whether agreement is required, and that question belongs with whoever handles contracts and employment matters in the organisation, not with the person evaluating tools. The vendor's own security documentation is a reasonable place to check how data is handled, and a poor place to look for an answer about local law.

What the free tiers let you find out

Free plans in this category are shaped to demonstrate quality and to stop short of covering a real week. The figures below were checked on the vendors' pricing pages on 25 September 2026, and plans change.

Tool	Free tier	Paid entry point
Otter	300 transcription minutes per month, 30 minutes maximum per conversation, 3 file imports in total, 20 AI chat queries per user	Pro at 8.33 USD per user per month billed annually or 16.99 USD monthly, with 1,200 minutes and up to 90 minutes per meeting
Granola	Limited meeting history on the free Basic tier	Business at 14 USD per user per month, with unlimited notes and history; Enterprise at 35 USD

Read the per conversation cap before the monthly total. A 30 minute limit per conversation means a standard one hour project call is truncated halfway, which is the fastest way to learn nothing from a trial. A team with four 45 minute calls a week needs roughly 720 minutes a month for one participant to record everything, which is already past the free monthly allowance above.

Two other limits matter more than headline minutes: how many months of history remain searchable, and whether the transcript can be exported in a form that survives cancelling the subscription. History is what makes recall useful, and it is the first thing a free tier restricts.

The notes are not the point, the tasks are

Every tool in this category produces a decent summary and a list of action items. What almost none of them do is put those items where work actually gets tracked, with an owner, a date and a place to comment.

The failure pattern is easy to recognise. Notes land in a separate tool, someone skims them, nobody retypes the four action items into the board, and by Wednesday the meeting has produced a searchable record of decisions that no one is executing. The record improved. The follow through did not.

Three ways out exist, in descending order of reliability. The tasks are created directly in the project tool during the call, by whoever is running it, with the transcript serving only as a check afterwards. Or an integration writes the extracted items into the board as cards, which works when the integration is real and fails quietly when it is a webhook someone set up once. Or the recording itself sits next to the work, attached to the card or the board it belongs to, so a person reading the task can hear the two minutes that produced it.

That last option is the reason to care whether a project tool can hold meeting video and searchable transcripts alongside its boards, rather than in a separate archive. A search that returns the card and the moment in the call that created it is worth more than a perfect summary in a different application, which is what a combined approach to boards, chat and recordings is for, and what a feature comparison is worth reading with in mind.

One setting that decides most of the value

Automatic recording is the difference between a tool that works and a tool that gets forgotten. If starting the note taker is a manual step, it will be skipped on the calls that run late, which are the calls where a record would have helped most. Both capture methods support scheduling from a calendar connection, and Teams organisers have a record and transcribe automatically option that administrators can allow or withhold.

Automatic capture brings its own problem, which is that it records meetings nobody wanted recorded. A recurring internal catch up that turns into a difficult personnel conversation is now a file with a retention policy. The workable middle ground is to switch automatic capture on per calendar or per meeting series rather than for every event, and to give the people who run those meetings a reliable way to stop the recording mid call. Both halves matter: automatic enough that nobody has to remember, selective enough that the exceptions stay off the record.

Where the text lives, and for how long

Transcripts are unusually sensitive text. A single project call can contain a client complaint, a frank assessment of a supplier and a comment about a colleague's performance, and once that becomes searchable, it is searchable by everyone who can reach the folder.

Retention defaults are the thing to check first, because they are generous by design. In Microsoft Teams, meeting recordings and transcripts are deleted after 120 days by default, the expiry period is an admin policy rather than a per meeting choice, and a recording that is moved out of its original location stops being governed by that expiry at all. Microsoft also notes that this expiry saves storage and does not satisfy compliance requirements, which need retention policies applied properly.

Three questions are worth answering before a rollout rather than after an incident. Who can read a transcript that was created in a meeting they did not attend. What happens to the text when the person who owns the recording leaves the company. And how a specific meeting gets deleted on request, which is a question customers do occasionally ask.

It is also worth knowing what recordings miss. In Teams, whiteboards, annotations, shared notes and content shared through an app are not captured in the recording. For a design review or an architecture discussion, the most important artefact on the screen may be exactly the thing that is absent from the file, so the diagram still needs saving by hand.

What to change first

Pick one recurring meeting, run one capture method for two weeks, and count only one thing: how many of the extracted action items ended up as tracked work with an owner and a date. If that number is low, the note taker is not the constraint and a better summary will not help. Getting the decisions and the recordings to sit next to the tasks is the change worth making, and keeping them on the same boards, as Pinateca does, removes the retyping step that quietly loses them.

Q1. Is a bot that joins the call better than software that records the device?

They fail differently. A bot works across platforms, keeps recording after the organiser leaves, and is visible to every attendee including clients. Device capture adds no participant and handles in person meetings, but loses the record if that one machine drops off or the wrong audio device is selected. Pick the visible option for internal calls and the quiet one for meetings where an extra attendee would be strange.

Q2. Do participants have to agree, or is telling them enough?

That depends on jurisdiction and on the type of meeting, so it is a question for whoever handles contracts and employment matters. Technically, platforms support both: Teams notifies everyone in the app as soon as recording starts, and an administrator can additionally require explicit agreement before a participant can unmute or turn on the camera, with the result recorded in the attendance report.

Q3. How much recording time does a small team actually need?

Count the calls rather than guessing. Four 45 minute meetings a week comes to about 720 minutes a month for a single recording participant, which is more than the 300 monthly minutes on Otter's free tier and inside its Pro allowance of 1,200. Check the per conversation cap as well, because a 30 minute limit truncates an ordinary hour long project call.

Q4. Why do the action items still get missed when everything is transcribed?

Because a summary is not a task. An item with no owner, no date and no place to be commented on is a sentence in a document, and it competes with everything else people read. The fix is structural: create the tasks during the call in the tool the team actually works in, and keep the recording next to those tasks so the context is one click away rather than in a separate archive.