Evidence · first-party tested/Best AI Meeting Notetakers for Accurate Transcripts, Summaries, and Action Items
The bot joined the Google Meet call and stayed connected through the full meeting capture with no visible dropout or mid-call disconnection.
What was measured
Join Method & Reliability
Bot-in-call vs. botless/local capture, and reliability of joining Zoom, Meet, or Teams.
decisive for this rankingcapability
A meeting notetaker must reliably get into the call or capture it locally; if it cannot join or record consistently, it cannot do the job at all. (2 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, 8 other criteria
Action-Item Extraction◐ MixedIt extracted the real action item about updating logs, but owner attribution was wrong because the misheard name cascaded into the action item and showed 'Nadine' instead of 'Mahreen.'Chat with Notes / Ask Questions✓ WorkedAI chat answers a meeting question with a grounded transcript-backed response, returning that the call was scheduled for '6th August' and explicitly indicating it is reading the transcription.Search Across Notes⚠ StruggledThere is no dedicated transcript search UI, so direct keyword lookup across notes is not available from the transcript view and is only routed indirectly through AI Chat.Speaker Diarization◐ 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.Summary Quality✓ WorkedThe meeting summary is structured into skimmable topic sections rather than one blob, with headings like 'Tool testing & publishing' and 'Access, tracker & expiries.'Summary Quality◐ MixedThe summary can hallucinate a person name: the report says it substituted 'Nadine' for 'Mahreen' in a summary bullet, creating a false team-member attribution.Topic Segmentation✓ WorkedIt breaks the standup into logical topic sections that reflect meeting flow, instead of presenting the notes as a single undifferentiated block.Transcription Accuracy◐ MixedOn this ~25-minute multi-speaker standup, HappyScribe captured the vast majority of names, tools, and jargon correctly, and the report records only 1–2 misheard words.
Provenance
- Observation
- 45f5aaac-5c02-4796-8e1c-058a8fce59c8
- 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
- observed
- 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: "happyscribe",
scenario: "ai-meeting-notetaker"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 7 other tools
measured on Join Method & Reliability
Fathom✓ WorkedThe bot joined Google Meet successfully and stayed connected for the full ~25-minute call, with no mid-call disconnections or plan-limit cutoffs.Fellow✓ WorkedThe bot auto-joined via Google Calendar integration and stayed connected for the full meeting capture without drops or disconnections, including the late closing portion of the call.Fireflies.ai✓ WorkedUsed a bot-based Google Meet join: the Fireflies notetaker appeared in the People panel, and the recording player showed it still present in a 23:40 capture, matching the report’s claim of uninterrupted full-call capture.Granola✓ WorkedThe botless desktop capture recorded the full ~25-minute meeting end-to-end without visible dropouts; the transcript reaches the call’s closing lines, indicating uninterrupted capture rather than a mid-call failure.MeetGeek✓ WorkedThe bot successfully joined a Google Meet call and the report says it captured the full ~30-minute meeting with zero disconnections or data loss.Notta✓ 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.Otter.ai✓ WorkedOtter’s bot joined Google Meet successfully and stayed connected through the full ~25-minute call with no mid-call dropout or ejection, so the meeting was captured end to end.
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com