The job, stated plainly
An AI meeting assistant listens to a conversation, writes down what was said, and turns it into something shorter that you can act on. Everything else is variation on those three steps: who joins the call, where the audio goes, what the summary is shaped like, and what happens to the record afterwards.
Most people arrive at this category because they took bad notes in an important meeting, or because they took good notes and missed the meeting doing it. Both are real, and either is enough reason to use one.
Question one: does something join the call?
Most assistants work by sending a bot into the meeting through a calendar integration. It appears in the participant list, everybody sees it, and somebody usually asks what it is. That is a social cost on every external call you take.
The alternative is capturing the audio the meeting is already playing on your machine. Nobody joins, nothing appears, and it works the same on Zoom, Teams, Meet, a phone call on speaker, or a conversation in a room.
It also decides something less obvious: a bot can be locked out. Video platforms control their own participant APIs, and several now ship their own free notetaker. A tool that depends on being admitted as a guest depends on a decision somebody else makes.
Question two: where does the audio go?
Nearly every product in this category uploads the recording and processes it on their servers. That is not sinister, it is just how the software was built, and it is worth knowing because it decides what a security review will find and what happens to the recording if you stop paying.
The alternative is running the speech model on your own machine. It is harder to build and it costs the vendor nothing to run, which is why the products that do it can afford to be free for one person.
Question three: does it tell you who said what?
A transcript without speakers is a wall of text. Separating voices is called diarization, and doing it well, with overlapping speech handled and the same person recognised across different meetings, is the single largest quality gap between products in this category.
Ask specifically whether it recognises a person in a later meeting, not just whether it labels Speaker 1 and Speaker 2 within one recording. Those are very different features and the marketing rarely distinguishes them.
Question four: can anything else read the record?
This is the one nobody asks and the one that matters most in a year. A meeting archive that only its own app can read is a dead end: you cannot ask your coding agent why a decision was made, or have your assistant check what a customer objected to last quarter.
The open answer is the Model Context Protocol, which lets an agent read the record directly. Ask whether the product has an MCP endpoint, or an API that is not shaped entirely around exporting to one CRM.
What to actually do
Record one real meeting with two candidates on the same day and read both transcripts. Accuracy differences are obvious immediately and invisible in a feature list, and speaker labelling either works on your accent, your microphone and your team or it does not.
Then check the price against how much you will use it. Nearly everything here is metered by minutes, which is fine until a fortnight of workshops.

