I Was on a Call With More AI Notetakers Than Humans

Last updated: 2026-08-29

I was testing multiple AI meeting assistants at once. Other people on the same call had their own assistants joining too. There were more AI notetakers than humans.

It was funny. It was also a snapshot of where work is headed. Everyone wants the meeting captured. The visible bots can be distracting, and they can create resistance from attendees. Choose the tool on purpose. Don’t add another bot by default.

Does this sound familiar to you?

Brooks described the common meeting notes graveyard. Transcripts and summaries pile up in your inbox. They’re technically searchable. You rarely review them or act on them. Brooks uses meeting recordings mostly to find information later. Search is useful. My own inbox fills with summaries I often skim or ignore.

Searchability is a reactive, level-one use case. You captured the meeting so you can go looking if you need something. I stopped there for a while too.

The real productivity leak is the failure to convert discussion into accountable action. You can have a decent meeting. Someone promises a follow-up. Then two months later you’re on another call discussing the same issue, because nothing left the room as a task with an owner and a deadline. Brooks connected this to a common corporate pattern: people discuss problems repeatedly because nothing leaves the meeting in an actionable format.

AI meeting assistants can extract who promised what by when and push those tasks into a project management system. Decisions. Owners. Deadlines. Automatic task capture. That’s the meeting system I want you to build.

Ask first

Brooks has a simple etiquette rule.

Ask first.

A simple “Are you okay if I use an AI notetaker for this call?” can reduce discomfort, especially in a sensitive one-on-one, medical, legal, coaching, or confidential conversation.

Brooks does not mind being recorded. He still appreciates being asked. I’ve noticed that people may behave differently when an assistant is present. A bot that shows up unannounced is a rough way to start a call.

Copy that sentence. Ask it before the assistant joins. If they say no, leave it out.

Bot, local recorder, or built-in platform

There’s a tradeoff between invisible local recording tools and visible meeting bots.

Visible bots join the call. That meeting with more notetakers than humans is what you get when everyone adds a bot by default.

Tools that record computer audio without joining can reduce meeting friction because no bot enters the call. Brooks noted that local transcription can be better for privacy. The limitation is weaker speaker identification. You may not get clean labels for who said what. You still need legal and ethical consent. Quiet recording is still recording.

The third option is the built-in meeting platform. If the tool you already meet in can capture the conversation, you may not need another assistant at all.

So which one do you actually need for this meeting?

Bot-based assistant

Use this when you want speaker identification and automations, and everyone on the call is okay with a bot joining.

Local recorder

Use this when you want less friction and more privacy, and you can live with weaker speaker labels.

Built-in meeting platform

Use this when capture is already sitting inside the tool you meet in, and another assistant would just add noise.

Get the work out of the transcript

A strong AI meeting assistant should update the systems where work actually happens. Instead of leaving action items inside a transcript, connect the assistant to a task manager, a CRM, a project management app, or team chat so the output lands where people already execute.

I used to treat these as summary tools. Hit record, get a recap, maybe skim it. Now I look for assistants that can trigger automations through built-in integrations or an automation platform. The summary is a stop along the way. The work has to arrive in the system you already open.

After every important meeting, run this checklist:

1. Transcript

You have a record of what was said.

2. Summary

Skim this so you don’t have to replay the whole call.

3. Actions

Who promised what, and by when.

4. System update

Push those actions into the task manager, CRM, project tool, or team chat.

5. Human review

Read what the assistant created. Confirm the owners, the dates, and the wording. Then let the tasks live in the tool, not in the notes.

Two setups worth doing first

CRM after client calls

Sales and client-facing professionals often avoid admin work even when it helps them. Brooks said CRM hygiene has been a long-running pain point in software and sales teams. How many follow-ups are sitting in your head instead of in the CRM?

An assistant can detect new contact details, meeting notes, buying timelines, and follow-up commitments, then update the CRM or create a reminder automatically. I’ve used this to update a contact’s location, add call notes, and create a 30-day follow-up task.

Stop relying on memory after client calls. Let the assistant catch the details. You review them. The CRM stays current.

A content bank from conversations you already have

AI meeting assistants can become a content and customer-insight engine. I use transcripts to automatically capture testimonials, customer pain points, research insights, and personal stories into a searchable content bank. Later, that bank supports newsletters, podcast outlines, and posts.

Someone mentions an interesting story or a testimonial casually, in the middle of a meeting. You don’t scramble for a notebook. The assistant captured it. You store it. If you create content or talk to customers all week, you’re sitting on this material already.

Your next meeting

Pick one recurring meeting this week. Before it starts, ask: “Are you okay if I use an AI notetaker for this call?” After it ends, run the checklist. Get the owners and deadlines out of the notes and into the tool you actually work from.

One meeting. One pipeline. Start there.