Nothing signed into the call, and there were still minutes to read once it ended.

Taking notes without a bot isn't a matter of remembering to write faster — it's a different sequence entirely, where the record of the call comes from the Mac itself rather than from a participant added to the meeting to produce one. This is that sequence, from before the call starts to the minutes that come out the other side.

What replaces the bot, mechanically

Instead of a named participant joining to capture individual audio feeds, Coii AudioNotes reads what the Mac already has access to — the microphone in the room and the audio the call is playing through the speakers — as two separate tracks. Nothing requests access to the meeting itself, which is why there's nothing to schedule and nothing on the roster for anyone to notice.

Step 1 — start recording before you dial in

The recording begins on the Mac, not inside the meeting platform, so the habit that matters is pressing record before joining rather than partway through once the conversation has already started. There's nothing to recover from a minute that happened before the button was pressed.

Step 2 — let the Mac capture both sides on its own

Once recording starts, the microphone and the call's own audio are captured as two separate tracks without any further action — no per-meeting setup inside Zoom, Meet or Teams, and no permission to grant beyond the one-time system prompt macOS asks for the first time a recording includes system audio. The full walkthrough for that permission and the two-track capture covers the mechanics in more depth than this page needs to repeat.

Step 3 — type your own notes during the call, if you want to

This is the step a bot-based tool doesn't really offer in the same way: typing a short note while the call is still happening — a number worth double-checking later, a name to follow up with — feeds directly into the same summary the transcript produces, rather than becoming a second document to reconcile against the transcript afterward.

Step 4 — let the call end on its own

There's no step to trigger once the meeting is over. The transcript has mostly already been built, segment by segment, while the call ran, so ending the call is what starts the write-up rather than what starts the transcription.

Step 5 — read the minutes once they're written

A language model bundled with the app turns the finished transcript, combined with whatever was typed in during the call, into a short set of minutes — decisions, actions and open questions — generated on the Mac itself once the call ends. Nothing about reading them requires logging into a dashboard a bot-based tool would otherwise host on your behalf.

Which tools actually put a bot on the call

Otter, Fireflies, Zoom's own AI Companion and Microsoft Teams' Copilot recap each join a call as a named participant by default, which is how they get a clean, per-participant audio feed to build a transcript from. That's a real design trade, not a mistake on their part — a scheduled bot can join a recurring call without anyone remembering to start anything, which the sequence above doesn't offer. Coii AudioNotes against Otter, Fireflies and Zoom AI Companion cover each comparison in full, including where each of them is genuinely ahead.

What typed notes actually change about the summary

A transcript alone tells the language model what was said. A typed note adds what wasn't said out loud but still matters — a decision that was implied rather than stated plainly, a follow-up that occurred to you mid-call and would otherwise be forgotten by the time minutes get read. The two are woven into one set of minutes rather than kept as a transcript and a separate notes file that somebody has to cross-reference later.

Fixing a speaker label that came out wrong

Speakers are told apart by a voice print — matching each voice against the others already in the recording, rather than reading a name off a meeting platform's participant list, since there was no participant list this method draws from. A label that starts generic can be corrected once, after which the same voice is recognised the next time it shows up in a later call.

Why some teams keep the bot anyway

It's worth naming honestly rather than pretending there's no trade-off: a team running a dozen calls a week, with no consistent habit of remembering to press anything, gets real value from a bot that joins automatically off a calendar. The sequence above trades that automatic scheduling for nothing appearing on the roster and nothing leaving the Mac — a fair exchange for someone who's had to explain a bot to a client once too often, and a genuinely worse one for a team that valued the automatic part specifically.

Taking notes on a call you didn't schedule

Because nothing needs adding to a calendar invite in advance, a call booked five minutes before it starts — a candidate who called back early, a client squeezing in a quick question — gets the same treatment as a recurring weekly meeting. A bot that only joins calls it was told about in advance misses exactly this kind of call more often than either side would like.

What still has to be said out loud

Recording this way changes what shows up on a participant list, not what's required by law or courtesy. Whether the people on the call need to be told is a separate, real question, and the honest answer is that it matters more without a visible bot as a cue, not less — a plain sentence at the start of the call covers it, and the specific rules for a given jurisdiction are a question for your own counsel rather than something this page is positioned to settle.

Finding a note from a call two weeks ago

Notes typed during a call and the minutes generated from it stay attached to that call's own entry in the archive rather than living in a separate running document, so finding one later means finding the meeting it came from — by date, or by searching what was actually discussed — rather than scrolling through an unrelated notes app hoping the right line is still in there somewhere.

What this workflow deliberately doesn't include

There's no calendar integration to configure and no shared workspace where a colleague reads your notes from their own login — recording, typing notes and reading the minutes afterward all happen on the one Mac that was actually on the call. The fuller case for what a bot-free recorder is and isn't built for covers that trade in more depth, including who it genuinely isn't the right fit for.

A note is not the same thing as an action item

Typing "check with legal" mid-call is a note; "confirm the NDA language with legal by Friday" is closer to an action item, and the summary that comes out the other end sorts roughly along that line rather than dumping every typed line into one undifferentiated list. Writing a note slightly more specifically than feels necessary in the moment tends to produce a cleaner set of minutes than a string of one-word reminders does.

What a typed note actually looks like mid-call

It doesn't need to be a full sentence to be useful. "Check the renewal date" or "follow up re: budget" typed in the middle of a call is enough — the language model writing the minutes afterward has the full transcript around it for context, so a short fragment typed in the moment does the job a longer note would, without slowing down the person typing it while the conversation keeps moving.

Recording a call you're presenting in, not just attending

The same sequence works whether you're mostly listening or doing most of the talking. Presenting a proposal on a call still leaves both tracks intact — your own voice on the microphone, the audience's questions and reactions on the system audio track — so the minutes that come out afterward capture the discussion that followed a presentation, not only the presentation itself.

What happens to the notes and the transcript afterward

Once a call ends, the typed notes, the transcript and the finished minutes sit together as one entry in the archive rather than as three separate files scattered across different apps — the recording to play back if needed, the transcript to scan, the notes and minutes to read first. All of it stays on the Mac that made it, across up to three machines on one licence, the same as any other file worth backing up.

A call that runs long, past what was expected

Nothing about this sequence depends on knowing in advance how long a call will run. Recording continues for as long as it's left running, typed notes can be added at any point along the way, and the transcript keeps building the entire time — there's no fixed slot being reserved the way a scheduled bot sometimes implies, and no awkward cutoff if the conversation goes twenty minutes past when it was supposed to end.

How this differs from jotting notes in a separate app

Typing into a plain notes app during a call produces a note with no connection to what was actually said around it — reading it back later means remembering the context yourself, because the app that held the note never had access to the conversation. Typing into the same session that's recording the call means the note and the transcript around it stay linked, which is the difference between a fragment that makes sense alone and one that only makes sense to the person who wrote it, on the day they wrote it.

Notes on a call somebody else is running

None of this requires being the person who scheduled the call. Recording and typing notes works the same whether you organised the meeting or were simply invited to it — the only requirement is that the recording happens on your own Mac, which is on the call the same way it would be for anyone attending. What ends up in the minutes afterward is your own record of the call, not something shared automatically with anyone else on it.

A call with a long stretch of silence in the middle

Not every useful call is continuously talking — a screen share with a long pause while someone reads a document, a wait for a third person to join. Recording keeps running through those gaps the same way it does through conversation, and a typed note dropped in during a quiet stretch — "waiting on legal to weigh in" — ends up timestamped in roughly the same place a transcript segment would be, giving the minutes something to reference from a part of the call that otherwise produced no dialogue at all.

The difference between this and remembering to write things down later

The alternative to typing during the call is trying to reconstruct what mattered afterward, from memory, once the call has ended and the next one has already started. A note typed in the moment doesn't compete with whatever comes right after this call for space in memory — it's already written down by the time the call ends, sitting next to the transcript rather than depending on being recalled accurately an hour later.

What it costs, what it runs on

This entire sequence is how Coii AudioNotes works by default, not a separate mode to switch into — $19, paid once, for three of your own Macs, with a 30-day trial that needs no card and no account to start. It runs on macOS 13 Ventura or later, on Apple Silicon or Intel, with no bot to configure and nothing to schedule before the first call.