Evidence · first-party tested/Best AI Meeting Notetakers for Accurate Transcripts, Summaries, and Action Items
Speaker attribution was mostly correct, with nearly all speakers identified by name, but the transcript still showed some misattributed lines, so diarization was not fully reliable for every turn.
What was measured
Speaker Diarization
Correctly attributes who said what across a multi-speaker standup.
decisive for this rankingtransformation
Correctly attributing who said what is part of making the transcript and notes trustworthy in multi-speaker meetings. (3 of 3 judges)
What was given, what came back
Test input: AI Demos Daily Standup — 31 July 2026 · image · group: ai-meeting-notetaker
Input — what we sent
AI Demos Daily Standup — 31 July 2026
A real 25-minute technical engineering daily standup with 14 attendees and about 10 active speakers, used as the single parallel-capture meeting for evaluating AI meeting notetakers on transcription, diarization, summaries, action items, search/chat, and collaboration features.
Why this input is hard
- · Transcription accuracy for real names, tool names, numbers, and technical jargon
- · Speaker diarization across multiple active speakers
- · Robustness to overlapping speech, crosstalk, and rapid turn-taking
- · Join reliability for bot-based and botless capture
- · Summary quality on identical source material
- · Action-item extraction with correct owners and commitments
- · Topic segmentation of standup updates
- · Search and chat grounded in the meeting content
- · Sharing, API, MCP, integrations, plan limits, languages, and privacy feature coverage
Output — unretouched
Also checked on this input — same tool, 7 other criteria
Action-Item Extraction✓ WorkedThe action-item list extracted the real commitments from the call, formatted them as checkbox items with @mentions, and the report says owner assignment was correct with no false positives.Chat with Notes / Ask Questions✓ WorkedThe Q&A interface answered a natural-language question with a grounded response from the meeting record, including the specific date "6th August," and the report observed no hallucinations.Join Method & Reliability✓ WorkedThe bot-based Google Meet join was reliable in the tested call: Notta Bot appeared in the meeting list, admitted/managed normally, and the capture ran through the end of the session without disconnects or plan-limit cutoffs.Search Across Notes◐ MixedSearch works inside a meeting transcript through AI Chat and returns exact timestamps in plain text, but the timestamps are not clickable, and the report says this was not tested across meetings.Summary Quality✓ WorkedThe generated meeting summary was comprehensive and skimmable, with structured sections such as Task & Issue Management and a mindmap-style organization that reflected the meeting flow.Topic Segmentation✓ WorkedThe meeting was segmented into useful topic blocks rather than one blob; the report names three sections, including Task & Issue Management, Individual Progress Updates, and API Benchmarking Task.Transcription Accuracy✓ WorkedNotta’s transcript capture was accurate on the evaluated standup: the report says it correctly captured names, tool names, numbers, and engineering jargon with no significant word-level errors, silent hallucinations, or misheard terms.
Provenance
- Observation
- 089aaaff-2da4-4739-8045-46df7a2f1e6b
- Evidence run
- ace58582-3d1e-48ee-996c-9b3cd03f27a2
- Study
- AI Meeting Notetakers — Capture Accurate Transcripts, Summaries & Action Items From Live Calls
- Research task
- 86baxegnv
- Tested at
- not recorded
- Source
- first-party
- Evidence state
- verified
- Proof shown
- input + output shown
- Cost / latency
- not captured
- Repeat run
- not captured
- Tester
- not captured
The last three rows are honest blanks, not placeholders — our capture has no field for them yet.
Query this
get_evidence({
tool: "notta",
scenario: "ai-meeting-notetaker"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 7 other tools
measured on Speaker Diarization
Fathom◐ MixedFathom separates most speakers correctly in a busy multi-speaker standup, but the report observed one rapid-transition segment where two speakers' lines were merged into a single speaker block.Fellow✓ WorkedThe transcript attributed speaker turns correctly across the standup, with all ~10 speakers labeled by name and no attribution errors or generic labels reported.Fireflies.ai✓ WorkedAttributed consecutive turns to distinct speakers in the transcript, and the report says speaker identification was almost complete with only minor attribution errors.Granola✗ FailedGranola’s default capture does not attribute speakers: the settings panel shows Speaker tags switched off, and the transcript excerpt is a plain text wall with no speaker labels, so diarization is absent unless the user manually enables it.HappyScribe◐ MixedIt identified most speakers, but the report says multiple transcript lines were assigned to the wrong speaker, so speaker-to-statement mapping was not fully reliable across transitions.MeetGeek◐ MixedIt identifies most speakers in a multi-speaker standup, but leaves at least one utterance as "Unknown speaker" and misattributes some lines to the wrong speaker, so attribution is not fully reliable.Otter.ai✗ FailedOtter’s diarization was effectively unusable in this multi-speaker standup: only 1 of about 10 active speakers was identified by name, while the other 9 were left as generic labels or unattributed, which the report summarizes as a 90% failure rate.
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com