Otter.ai vs Fellow

Agent ops

1. ai-native userAn agent can automatically file each meeting's action items into my project tracker (Linear, Jira, Asana) using the product's API, webhooks, or native automations

   weight 2 · round to Otter.ai
   Otter.ai~partialprobed7/10

   Otter explicitly documents sending action items into JIRA and Asana (and other tools) plus a public API/webhooks tier and a live, OAuth-gated MCP server enabling AI agents to pull meeting/action-item data into workflows. However, Linear is never named, no OpenAPI/API spec is discoverable (404s on all probed paths), and API/MCP/native project-tracker automations appear gated to Enterprise plans with no independent hands-on confirmation that action items sync correctly end-to-end. Missing for 10: explicit Linear support, publicly discoverable API schema, and independent verification of the automation actually filing items correctly.

   • [claimed-docs] “Help your team move faster by sending actions items from meetings into tools they already use, like JIRA, Asana, and others.”
   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Send meeting summaries and action items from Otter to ClickUp to manage everything in one place.”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”

   proof ↗⚑ flag

   Fellow~partialprobed5/10

   Fellow exposes a Developer API (get_action_items, append_note_agenda), webhooks for real-time event notifications, and an MCP server that could be used by an agent to fetch action items and push them elsewhere, giving the building blocks for this automation. However there is no evidence of a native Linear/Jira/Asana integration or documented reference workflow that actually files action items into those specific trackers. Missing for 10: native connectors/integrations to Linear, Jira, or Asana, and a documented example of an agent automatically creating tickets in those tools via the API/webhooks/MCP.

   • [claimed-docs] “List action items with optional filters and pagination.”
   • [claimed-docs] “Webhooks allow you to receive real-time notifications when events occur in Fellow.”
   • [claimed-docs] “Fellow's Model Context Protocol (MCP) Server allows you to ask your AI Assistant about your meetings, without needing to write any code.”
   • [claimed-docs] “pass transcripts to an LLM for tailored recaps and action plans, the API gives you everything you need to make it happen”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Fellow's hosted MCP server https://fellow.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

2. ai-native userAn official MCP server lets Claude or any MCP client query my meetings — search, transcripts, action items — with OAuth, no glue code

   weight 3 · round to Fellow
   Otter.ai~partialprobed7/10

   Otter has an official, live MCP server (mcp.otter.ai) confirmed by a runtime probe returning proper OAuth-gated 401/WWW-Authenticate flow, and docs describe searching meetings, transcripts, action items, and granular permission scoping via Claude/ChatGPT — matching the story closely (otter-docs-16, otter-docs-46, otter-docs-47, otter-docs-35, otter-probe-rt-1, otter-probe-2). However, the same probe notes this MCP/API access is gated to Enterprise workspaces only, meaning many AI-native individual users cannot actually use it without an enterprise contract. Missing for 10: broader/self-serve tier availability, independent third-party (non-vendor) confirmation of the OAuth/query experience beyond the runtime probe, and public documentation of full query capabilities (e.g., exact tool/resource list).

   • [claimed-docs] “Connect Otter.ai meeting transcripts and action items to Claude via MCP. Search, recap, and draft follow-ups without leaving the chat.”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [claimed-docs] “OAuth-authenticated with granular permissions”
   • [claimed-docs] “Your AI assistant can only access meetings you explicitly authorize”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”

   proof ↗⚑ flag

   Fellow✓fullprobed9/10

   Fellow ships an official, documented MCP server enabling any MCP client (Claude, ChatGPT, Cursor) to query meetings — search, transcripts, action items — without writing code, and admins control which tools are exposed; a runtime probe confirms the hosted endpoint is live and auth-gated (bearer/OAuth-style), matching the docs. missing for 10: independent third-party review of the OAuth flow specifics beyond the probe's bearer-token confirmation.

   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?"”
   • [claimed-docs] “Fellow’s MCP Connector works with any AI tool that supports connectors, so you're never locked into one platform”
   • [claimed-docs] “As a workspace admin, you decide which MCP tools your members’ AI assistants can use.”
   • [claimed-docs] “Fellow's Model Context Protocol (MCP) Server allows you to ask your AI Assistant about your meetings, without needing to write any code.”
   • [claimed-docs] “Your favorite AI chatbot like Claude, ChatGPT, or Cursor can now tap directly into your meeting recaps, notes, and action items”
   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?" or "What did we decide in last month…”
   • [probe] “official MCP server documented at https://developers.fellow.ai/reference/mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Fellow's hosted MCP server https://fellow.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

3. ai-native userMy scripts can pull transcripts, summaries, and action items from every meeting through a documented API with self-serve keys

   weight 3 · round to Fellow
   Otter.ai~partialprobed4/10

   Otter documents an 'Otter API & Webhooks' feature in pricing tiers and a Public API for custom integrations, plus a live MCP server for pulling transcripts/summaries/action items into AI tools, but the runtime probe shows the MCP endpoint is OAuth-gated and both API/MCP access are restricted to Enterprise workspaces (contact account manager), not self-serve; no public OpenAPI/swagger docs were found (all 404). Missing for 10: publicly discoverable API reference docs, evidence of self-serve API key generation for individual/non-enterprise users, and independent confirmation of successful script-based pulls.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fellow✓fullprobed8/10

   Fellow documents a REST Developer API with self-serve API key generation (docs-2,15,16) and endpoints for recordings/transcripts, action items, and notes (docs-4,5,6,31), plus webhooks for real-time events. Runtime probe confirms the API/MCP endpoints are live and properly authenticated, not vaporware. missing for 10: no public OpenAPI/swagger spec found (404s), and no independent third-party developer report of building against the API.

   • [claimed-docs] “The Developer API opens that data to you: transcripts, structured notes, and more, all available through standard REST calls.”
   • [claimed-docs] “All API requests must include a valid API key in the Authorization header.”
   • [claimed-docs] “List recordings with optional filters and pagination.”
   • [claimed-docs] “List action items with optional filters and pagination.”
   • [claimed-docs] “Include your API key in the `X-API-KEY` header of every request”
   • [claimed-docs] “Generate a new API key for your application, giving it a descriptive name.”
   • [claimed-docs] “Webhooks allow you to receive real-time notifications when events occur in Fellow.”
   • [claimed-docs] “pass transcripts to an LLM for tailored recaps and action plans, the API gives you everything you need to make it happen”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.fellow.ai/llms.txt # Fellow Documentation > Fellow’s API provides access to meeting notes an…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.fellow.ai/openapi.json, https://developers.fellow.ai/swagger.json, https://develo…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Fellow's hosted MCP server https://fellow.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Fellow
   Otter.ai—none0/10

   No evidence of an llms.txt file or agent-oriented documentation format for Otter.ai; the evidence pack covers MCP server integration and product features but nothing about machine-readable docs for agents to consume directly.

   ⚑ flag

   Fellow✓fullprobed8/10

   A live probe confirms Fellow serves a proper llms.txt file at https://developers.fellow.ai/llms.txt (HTTP 200) summarizing its API for agent consumption, and the broader developer docs (API reference, MCP server docs) are structured for both human and agent use. Missing for 10: no evidence of a companion llms-full.txt or independent third-party confirmation that agents successfully consume this file in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.fellow.ai/llms.txt # Fellow Documentation > Fellow’s API provides access to meeting notes an…”
   • [claimed-docs] “pass transcripts to an LLM for tailored recaps and action plans, the API gives you everything you need to make it happen”
   • [probe] “official MCP server documented at https://developers.fellow.ai/reference/mcp-server”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Otter.ai
   Otter.ai~partialprobed4/10

   Otter offers a Public API, Webhooks, and an MCP server that could be scripted/integrated into automated pipelines (otter-docs-26, otter-docs-40, otter-probe-rt-1), but these are gated to Enterprise workspaces and there's no documentation of a CLI, SDK, or explicit CI/headless workflow support — the API/MCP surface is aimed at chat-tool integration rather than programmatic batch automation. Missing for 10: documented CLI or SDK for scripted/CI use, explicit CI/automation guides, evidence of non-Enterprise API access, and confirmation the API supports full headless operation (uploading, processing, retrieving) without interactive UI.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”

   proof ↗⚑ flag

   Fellow—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Otter.ai—none0/10

   All evidence describes Otter shipping its own MCP *server* so external AI tools (Claude, ChatGPT) can pull Otter's meeting data — this is the reverse of the story, which asks whether a user can plug external MCP servers into Otter so Otter itself can consume their tools. No evidence shows Otter acting as an MCP client consuming third-party MCP servers.

   • [claimed-docs] “ChatGPT, Claude, and other AI chat tools can securely access your meeting knowledge through Otter's MCP Server for deeper analysis and smart…”
   • [claimed-docs] “Connect Otter.ai meeting transcripts and action items to Claude via MCP. Search, recap, and draft follow-ups without leaving the chat.”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fellow—none0/10

   All evidence describes Fellow acting as an MCP *server*, exposing its own meeting data/tools to external AI assistants (Claude, ChatGPT, Cursor) — the opposite direction of this story, which asks whether a user can plug external MCP servers into Fellow so Fellow itself can use their tools. No evidence shows Fellow consuming or connecting to third-party MCP servers.

   ⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Fellow
   Otter.ai✓fullprobed8/10

   Otter documents and ships an official hosted MCP server (mcp.otter.ai) that connects Claude, ChatGPT, and other AI agents to meeting data, with OAuth-based granular permissions, confirmed live via a runtime probe returning a valid OAuth-protected-resource challenge rather than a dead endpoint. Missing for 10: independent third-party (non-vendor) hands-on confirmation of successful agent connection/tool use beyond the auth handshake, and the capability is restricted to Enterprise workspaces rather than universally available.

   • [claimed-docs] “ChatGPT, Claude, and other AI chat tools can securely access your meeting knowledge through Otter's MCP Server for deeper analysis and smart…”
   • [claimed-docs] “Connect Otter.ai meeting transcripts and action items to Claude via MCP. Search, recap, and draft follow-ups without leaving the chat.”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [claimed-docs] “OAuth-authenticated with granular permissions”
   • [claimed-docs] “Your AI assistant can only access meetings you explicitly authorize”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fellow✓fullprobed9/10

   Fellow ships an official, documented MCP Server (developers.fellow.ai/reference/mcp-server) that lets AI assistants like Claude, ChatGPT, or Cursor query meeting transcripts and action items without code, with admin-level tool controls; a runtime probe confirms the hosted endpoint (fellow.app/mcp) is live and properly bearer-gated as documented. missing for 10: independent third-party/community usage reports beyond the vendor docs and the single runtime probe.

   • [claimed-docs] “Fellow's Model Context Protocol (MCP) Server allows you to ask your AI Assistant about your meetings, without needing to write any code.”
   • [claimed-docs] “Fellow’s MCP Connector works with any AI tool that supports connectors, so you're never locked into one platform”
   • [claimed-docs] “As a workspace admin, you decide which MCP tools your members’ AI assistants can use.”
   • [claimed-docs] “Your favorite AI chatbot like Claude, ChatGPT, or Cursor can now tap directly into your meeting recaps, notes, and action items”
   • [probe] “official MCP server documented at https://developers.fellow.ai/reference/mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Fellow's hosted MCP server https://fellow.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Fellow
   Otter.ai~partialprobed4/10

   Otter references a 'Public API' and 'API & Webhooks' as an Enterprise/paid-tier feature (otter-docs-26, otter-docs-40, otter-docs-48), implying programmatic access exists, but no actual API reference, schema, or endpoint documentation is shown, and a live probe found no discoverable OpenAPI/swagger spec (otter-probe-1). The MCP server is real and OAuth-gated (otter-probe-rt-1) but that's a different (agent-tool) interface, not a general-purpose documented public API for driving the product programmatically. missing for 10: published API reference/docs with endpoints and schemas, independent confirmation of working API calls, clarity on which tiers can access it.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms”
   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fellow✓fullprobed8/10

   Fellow ships a documented Developer API with REST endpoints (recordings, action items, note editing), API-key authentication, and webhooks, giving AI-native users a clear path to programmatic control and even LLM-facing MCP integration. missing for 10: a public OpenAPI/swagger spec (probes returned 404) and independent/third-party developer corroboration beyond vendor docs.

   • [claimed-docs] “The Developer API opens that data to you: transcripts, structured notes, and more, all available through standard REST calls.”
   • [claimed-docs] “All API requests must include a valid API key in the Authorization header.”
   • [claimed-docs] “List recordings with optional filters and pagination.”
   • [claimed-docs] “List action items with optional filters and pagination.”
   • [claimed-docs] “Add Fellow Markdown to the end of a note's agenda, leaving the rest of the content in place.”
   • [claimed-docs] “Webhooks allow you to receive real-time notifications when events occur in Fellow.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.fellow.ai/openapi.json, https://developers.fellow.ai/swagger.json, https://develo…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Otter.ai
   Otter.ai~partialprobed7/10

   Otter's MCP server is OAuth-authenticated with granular permissions and explicit meeting-level authorization ('AI assistant can only access meetings you explicitly authorize'), and a runtime probe confirms the endpoint is live and OAuth-gated rather than just a marketing claim. However, this capability is restricted to Enterprise workspaces, and there's no independent evidence of fine-grained scope customization (e.g., read-only vs write, specific resource scoping) beyond vendor description. Missing for 10: independent/hands-on verification of granular scope options, evidence of least-privilege scoping beyond meeting-level authorization, and availability outside Enterprise tier.

   • [claimed-docs] “Your AI assistant can only access meetings you explicitly authorize”
   • [claimed-docs] “OAuth-authenticated with granular permissions”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [claimed-docs] “Otter API & Webhooks”

   proof ↗⚑ flag

   Fellow~partialclaimed5/10

   Fellow supports API key auth and lets workspace admins control which MCP tools an AI assistant can access (fellow-docs-10), which is a coarse form of least-privilege control for agents. However there's no documented granular scoping (e.g., read-only vs write, resource-level permissions, expiry) for individual API keys — Super Admin keys in fact grant broad on-behalf-of access across the workspace, the opposite of least privilege. Missing for 10: explicit API key scope/permission levels, token expiration/revocation controls, and fine-grained per-resource credential issuance for agents.

   • [claimed-docs] “As a workspace admin, you decide which MCP tools your members’ AI assistants can use.”
   • [claimed-docs] “Super Admin API keys can make requests on behalf of any user in the workspace using the `X-On-Behalf-Of` header.”
   • [claimed-docs] “Fellow’s Super Admin API lets designated Enterprise‑plan administrators retrieve, export, and delete data across the entire workspace”
   • [claimed-docs] “Generate a new API key for your application, giving it a descriptive name.”
   • [claimed-docs] “All API requests must include a valid API key in the Authorization header.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Otter.ai
   Otter.ai~partialprobed4/10

   Otter documents a Public API, webhooks, and a live, OAuth-gated MCP server (confirmed by runtime probe) that let developers integrate meeting data into custom workflows, which supports 'building against Otter programmatically,' but no evidence names an official SDK (Python/JS/etc.) or provides SDK-style client libraries — only raw API/webhook/MCP endpoints are documented. missing for 10: explicit official SDK documentation/libraries, code samples, language coverage, independent developer corroboration of SDK usage.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [claimed-docs] “OAuth-authenticated with granular permissions”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”

   proof ↗⚑ flag

   Fellow—none0/10

   Fellow documents a REST Developer API with API-key auth, webhooks, and endpoints for recordings/notes/action items, but no evidence names an official SDK (e.g., Python/JS client library); the openapi.json/swagger probe returned 404 across all standard paths, suggesting no formal spec-based SDK generation either.

   • [claimed-docs] “The Developer API opens that data to you: transcripts, structured notes, and more, all available through standard REST calls.”
   • [claimed-docs] “All API requests must include a valid API key in the Authorization header.”
   • [claimed-docs] “Include your API key in the `X-API-KEY` header of every request”
   • [claimed-docs] “Generate a new API key for your application, giving it a descriptive name.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.fellow.ai/openapi.json, https://developers.fellow.ai/swagger.json, https://develo…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Fellow
   Otter.ai~partialclaimed5/10

   Otter's pricing page explicitly lists 'Otter API & Webhooks' as a feature on paid plans, confirming webhook subscription capability exists, but there is no documentation describing webhook event types, payload schemas, subscription setup, or independent confirmation of usage. missing for 10: webhook event catalog/documentation, setup/configuration guide, and hands-on or independent verification of webhook delivery.

   • [claimed-docs] “Otter API & Webhooks”

   proof ↗⚑ flag

   Fellow✓fullclaimed7/10

   Fellow's Developer API explicitly documents webhooks that deliver real-time HTTP POST notifications when events occur, which directly satisfies the subscribe-to-events story. Missing for 10: a list of supported event types/payload schema, and independent/hands-on confirmation of webhook delivery reliability.

   • [claimed-docs] “Fellow sends an HTTP POST request to the URL you specify with details about the event.”
   • [claimed-docs] “Webhooks allow you to receive real-time notifications when events occur in Fellow.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Otter.ai✓fullprobed8/10

   Otter's AI Chat and meeting summaries generate insights, decisions, action items, sentiment, and follow-ups directly from meeting data (otter-docs-1,3,21,37,34,13), and this is corroborated by a live, OAuth-gated MCP endpoint confirmed via runtime probe (otter-probe-rt-1). missing for 10: independent hands-on validation of insight quality/accuracy (community evidence focuses on privacy/recording concerns, not insight usefulness), and MCP/insight features are Enterprise-gated rather than universally available.

   • [claimed-docs] “Otter AI Chat searches across your meetings and connected apps to instantly answer questions and help you create follow-ups, reports, and co…”
   • [claimed-docs] “Clear next steps are automatically captured and assigned from every meeting.”
   • [claimed-docs] “Otter turns every meeting into a clear summary with decisions, action items, and insights.”
   • [claimed-docs] “Otter's fully customizable, AI-powered meeting summaries automatically extract actionable insights based on meeting purpose and for differen…”
   • [claimed-docs] “Analyze patterns and themes across multiple meetings”
   • [claimed-docs] “Monitor sentiment, engagement, and strategic keywords across customer-facing teams to align messaging and positioning.”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”

   proof ↗⚑ flag

   Fellow✓fullprobed8/10

   Fellow auto-generates AI meeting summaries, action items, decisions, and topic-based minutes for every meeting, plus MCP server and API access to let AI assistants query and reason over that data ('What were my action items this week?'). Runtime probe confirms the MCP server is live and functioning as documented (bearer-gated, not broken). missing for 10: independent third-party review of insight quality/accuracy, and no in-product analytics/dashboard example beyond summaries and action items.

   • [claimed-docs] “You automatically receive a clear meeting summary, suggested AI action items, decisions, and topic-based minutes for every meeting.”
   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?"”
   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?" or "What did we decide in last month…”
   • [claimed-docs] “Your favorite AI chatbot like Claude, ChatGPT, or Cursor can now tap directly into your meeting recaps, notes, and action items”
   • [claimed-docs] “pass transcripts to an LLM for tailored recaps and action plans, the API gives you everything you need to make it happen”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Fellow's hosted MCP server https://fellow.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Otter.ai
   Otter.ai~partialclaimed6/10

   Otter supports background automation scoped to meetings: scheduled auto-join notetakers, automatic transcription/summarization, auto-extraction of action items, and automatic syncing of notes/action items to CRMs, Jira, Asana, Zendesk, Airtable, S3, etc. (otter-docs-17,9,10,28,29,31,4,3,26,40). This is real autonomous background behavior but it is templated around meeting workflows rather than a general-purpose automation/agent builder where a user defines arbitrary triggers/conditions. Missing for 10: evidence of a flexible, user-configurable automation/workflow engine (beyond Zapier/webhooks) and independent confirmation that these automations reliably run unattended without manual re-triggering.

   • [claimed-docs] “Schedule your AI Meeting Notetaker to automatically join all your Zoom, Microsoft Teams, and Google Meet meetings.”
   • [claimed-docs] “Automatically turn meeting takeaways into support tickets or updates in tools like Zendesk and ServiceNow.”
   • [claimed-docs] “Help your team move faster by sending actions items from meetings into tools they already use, like JIRA, Asana, and others.”
   • [claimed-docs] “Otter automatically sends transcripts, summaries, and meeting metadata to Airtable.”
   • [claimed-docs] “Export transcripts, summaries, and metadata directly to your Amazon S3 bucket.”
   • [claimed-docs] “Send meeting summaries and action items from Otter to ClickUp to manage everything in one place.”
   • [claimed-docs] “Key deal details, notes, and next steps automatically extracted from every meeting and synced to your CRM.”
   • [claimed-docs] “Clear next steps are automatically captured and assigned from every meeting.”
   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”

   proof ↗⚑ flag

   Fellow~partialclaimed5/10

   Fellow automatically generates summaries, action items, and decisions in the background after every meeting without manual triggering (fellow-docs-23), and its webhook system plus Developer API let external automations fire in real time when events occur (fellow-docs-3, fellow-docs-17, fellow-docs-31). However, there's no evidence of a native automation/workflow builder, scheduled triggers, or rule-based autonomous actions within Fellow itself — automation would need to be built externally using the webhook/API primitives. Missing for 10: a first-party automation/rules engine, scheduling capability, and hands-on evidence of end-to-end autonomous workflows beyond passive notification/data-access APIs.

   • [claimed-docs] “You automatically receive a clear meeting summary, suggested AI action items, decisions, and topic-based minutes for every meeting.”
   • [claimed-docs] “Fellow sends an HTTP POST request to the URL you specify with details about the event.”
   • [claimed-docs] “Webhooks allow you to receive real-time notifications when events occur in Fellow.”
   • [claimed-docs] “pass transcripts to an LLM for tailored recaps and action plans, the API gives you everything you need to make it happen”
   • [claimed-docs] “The Developer API opens that data to you: transcripts, structured notes, and more, all available through standard REST calls.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Otter.ai
   Otter.ai~partialclaimed6/10

   Otter ships a built-in 'Otter AI Chat' assistant that can search meetings, answer questions, draft follow-ups/reports, and auto-extract action items/summaries, which is genuine in-product task delegation (otter-docs-1,3,21,41). However this delegation is scoped narrowly to meeting-related tasks (not general-purpose), and there's no independent/hands-on evidence validating the AI Chat's actual task-completion quality — community evidence only covers transcription accuracy and privacy issues, not the assistant's agentic performance. Missing for 10: independent hands-on validation of Otter AI Chat's task delegation, broader (non-meeting) task scope, and confirmation the chat assistant reliably executes multi-step actions vs. just answering queries.

   • [claimed-docs] “Otter AI Chat searches across your meetings and connected apps to instantly answer questions and help you create follow-ups, reports, and co…”
   • [claimed-docs] “Clear next steps are automatically captured and assigned from every meeting.”
   • [claimed-docs] “Otter turns every meeting into a clear summary with decisions, action items, and insights.”
   • [claimed-docs] “Instantly auto-generate follow-up emails and next steps for client calls, internal reviews, and more.”
   • [claimed-docs] “Stay on track by automatically turning your meeting notes into simple action items with deadlines.”

   proof ↗⚑ flag

   Fellow~partialclaimed4/10

   Fellow's AI automatically generates meeting summaries, action items, and decisions (fellow-docs-23, fellow-docs-31), which resembles delegated AI task execution, but there is no evidence of a conversational 'built-in assistant' inside the product that a user can direct with arbitrary tasks — the MCP server (fellow-docs-18, fellow-docs-26) instead lets *external* assistants like Claude/ChatGPT query Fellow's data, which is the inverse of a built-in assistant. Missing for 10: an in-app conversational assistant UI, evidence of multi-step task delegation beyond automatic note/action-item generation, and confirmation this assistant runs natively rather than via third-party AI tools.

   • [claimed-docs] “You automatically receive a clear meeting summary, suggested AI action items, decisions, and topic-based minutes for every meeting.”
   • [claimed-docs] “pass transcripts to an LLM for tailored recaps and action plans, the API gives you everything you need to make it happen”
   • [claimed-docs] “Fellow's Model Context Protocol (MCP) Server allows you to ask your AI Assistant about your meetings, without needing to write any code.”
   • [claimed-docs] “Your favorite AI chatbot like Claude, ChatGPT, or Cursor can now tap directly into your meeting recaps, notes, and action items”
   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?" or "What did we decide in last month…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Fellow
   Otter.ai~partialprobed6/10

   Otter AI Chat lets users query meetings, CRMs, and connected apps using natural language to get answers, drafts, and reports (otter-docs-1, otter-docs-11), and this NL interface also works through MCP-connected assistants like Claude/ChatGPT (otter-docs-16, otter-docs-46), confirmed live by a runtime probe. However, evidence is limited to search/chat-style querying rather than broader NL-driven control of the product (e.g., scheduling, settings, workflow actions), and there is no independent hands-on report validating chat accuracy or command breadth. Missing for 10: independent verification of NL Chat's reliability/accuracy, evidence of NL controlling actions beyond querying/summarizing (e.g., configuring integrations, managing recordings via command), and broader command scope beyond meeting Q&A.

   • [claimed-docs] “Otter AI Chat searches across your meetings and connected apps to instantly answer questions and help you create follow-ups, reports, and co…”
   • [claimed-docs] “Find key insights from past calls, documents, and more using natural-language.”
   • [claimed-docs] “Connect Otter.ai meeting transcripts and action items to Claude via MCP. Search, recap, and draft follow-ups without leaving the chat.”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fellow~partialprobed7/10

   Fellow ships an official, documented MCP server that works with AI assistants (Claude, ChatGPT, Cursor) to let users ask natural-language questions like "What were my action items this week?", and a runtime probe confirms the hosted MCP endpoint is live and bearer-gated as documented. However, the evidence shows this is primarily a query/read interface (search meetings, get action items, get transcripts) rather than full natural-language control over write/agentic actions. Missing for 10: evidence of NL-driven write actions (e.g., scheduling, editing notes, assigning action items) executed through natural-language commands rather than just Q&A retrieval.

   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?"”
   • [claimed-docs] “Fellow’s MCP Connector works with any AI tool that supports connectors, so you're never locked into one platform”
   • [claimed-docs] “Fellow's Model Context Protocol (MCP) Server allows you to ask your AI Assistant about your meetings, without needing to write any code.”
   • [claimed-docs] “Your favorite AI chatbot like Claude, ChatGPT, or Cursor can now tap directly into your meeting recaps, notes, and action items”
   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?" or "What did we decide in last month…”
   • [probe] “official MCP server documented at https://developers.fellow.ai/reference/mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Fellow's hosted MCP server https://fellow.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Fellow
   Otter.ai—none0/10

   Otter has a Public API/webhooks and MCP server, so an interactive API reference is a fair ask, but the evidence pack shows no interactive docs or runnable examples — a direct probe for OpenAPI/Swagger specs returned 404s and no docs page with a live API explorer is cited.

   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”
   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”

   proof ↗⚑ flag

   Fellow~partialprobed3/10

   Fellow publishes a structured Developer API reference with per-endpoint pages (recordings, action items, note editing, webhooks) suggesting a ReadMe.io-style docs site, but there is no confirmed evidence of a live 'try it' interactive console or runnable code examples — the openapi.json/swagger.json probe returned 404 across all candidate paths, indicating no public machine-readable spec to power an interactive explorer. missing for 10: explicit runnable 'try it' console evidence, public OpenAPI/Swagger spec, and independent confirmation of interactivity.

   • [claimed-docs] “List recordings with optional filters and pagination.”
   • [claimed-docs] “List action items with optional filters and pagination.”
   • [claimed-docs] “Add Fellow Markdown to the end of a note's agenda, leaving the rest of the content in place.”
   • [claimed-docs] “The Developer API opens that data to you: transcripts, structured notes, and more, all available through standard REST calls.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.fellow.ai/openapi.json, https://developers.fellow.ai/swagger.json, https://develo…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Otter.ai—none0/10

   Otter advertises a 'Public API' and webhooks (otter-docs-26, otter-docs-40, otter-docs-48), but a direct probe for machine-readable spec files (openapi.json, swagger.json, etc.) returned 404 on all candidate paths, and no documentation link to an OpenAPI/Swagger spec appears anywhere in the evidence pack.

   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”
   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”

   proof ↗⚑ flag

   Fellow—none0/10

   Fellow's developer docs use ReadMe-style reference pages but the probe explicitly found no OpenAPI/Swagger spec at any standard location (all 404), and no evidence of a downloadable machine-readable spec is cited elsewhere.

   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.fellow.ai/openapi.json, https://developers.fellow.ai/swagger.json, https://develo…”

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Otter.ai—none0/10

   There is evidence of an Otter public API and an MCP server, but no documentation of API versioning scheme or a formal deprecation policy anywhere in the pack; the openapi probe returned 404s. Missing for 10: versioning scheme documentation, changelog/deprecation policy, migration guides, evidence of stable version lifecycle.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”

   proof ↗⚑ flag

   Fellow—none0/10

   Evidence documents API endpoints, auth, and webhooks, but there is no mention anywhere of API versioning scheme or a documented deprecation policy; an openapi spec probe even 404'd, suggesting no formal versioned spec is published.

   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.fellow.ai/openapi.json, https://developers.fellow.ai/swagger.json, https://develo…”
   • [claimed-docs] “The Developer API opens that data to you: transcripts, structured notes, and more, all available through standard REST calls.”
   • [claimed-docs] “All API requests must include a valid API key in the Authorization header.”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Fellow
   Otter.ai~partialclaimed4/10

   Otter offers API/webhooks, unlimited file import, and cross-meeting search/analysis (e.g., 'analyze patterns and themes across multiple meetings', 'search meeting transcripts across all time periods') that could support automation across many meetings at once, but there is no explicit documentation of a bulk-edit/bulk-delete/bulk-tag operation or batch endpoint for acting on many items simultaneously. Missing for 10: documented bulk edit/delete/tag UI or API endpoints, evidence of batch processing limits/behavior, and independent confirmation that cross-meeting operations scale reliably.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Analyze patterns and themes across multiple meetings”
   • [claimed-docs] “Search your meeting transcripts across all time periods”
   • [claimed-docs] “Import and transcribe unlimited audio or video files”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”

   proof ↗⚑ flag

   Fellow~partialclaimed5/10

   Fellow's Developer API supports listing recordings/action items with filters and pagination (bulk read), and the Super Admin API explicitly allows retrieving, exporting, and deleting data across the entire workspace, which covers workspace-wide bulk read/delete for admins. However, there's no documented endpoint for bulk create/update/write operations (e.g., batch-editing many action items or notes in one call) — missing for 10: bulk write/update endpoints, batch action-item creation, evidence of true multi-item mutation in a single API call.

   • [claimed-docs] “List recordings with optional filters and pagination.”
   • [claimed-docs] “List action items with optional filters and pagination.”
   • [claimed-docs] “Fellow’s Super Admin API lets designated Enterprise‑plan administrators retrieve, export, and delete data across the entire workspace”
   • [claimed-docs] “Build admin dashboards that display data from a specific user's perspective”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Otter.ai
   Otter.ai~partialclaimed5/10

   Otter offers built-in automatic actions (auto-capture of action items, auto-sync to CRM/Zendesk/JIRA/Asana) and lists 'Otter API & Webhooks' and Zapier integration in its pricing page, which would let users build custom event-triggered automations. However, these are fixed, vendor-defined automatic behaviors rather than a documented native interface where users define their own conditional rules; the webhook/Zapier capability is only mentioned as a bullet with no documentation of rule configuration. Missing for 10: a documented rule/automation builder or webhook event catalog showing user-defined trigger-condition-action logic, and independent evidence it works as described.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Salesforce\*, HubSpot\*, Zapier integrations”
   • [claimed-docs] “Automatically turn meeting takeaways into support tickets or updates in tools like Zendesk and ServiceNow.”
   • [claimed-docs] “Help your team move faster by sending actions items from meetings into tools they already use, like JIRA, Asana, and others.”
   • [claimed-docs] “Stay on track by automatically turning your meeting notes into simple action items with deadlines.”

   proof ↗⚑ flag

   Fellow~partialclaimed4/10

   Fellow offers webhooks that fire real-time notifications on events, which can be used to build external automations, but there is no evidence of a native rules/trigger builder within Fellow itself that lets a user define 'if event X then action Y' logic. Missing for 10: a documented in-product automation/rules engine, examples of user-configurable triggers-to-actions, and any built-in action execution beyond webhook delivery.

   • [claimed-docs] “Fellow sends an HTTP POST request to the URL you specify with details about the event.”
   • [claimed-docs] “Webhooks allow you to receive real-time notifications when events occur in Fellow.”
   • [claimed-docs] “pass transcripts to an LLM for tailored recaps and action plans, the API gives you everything you need to make it happen”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Otter.ai
   Otter.ai~partialclaimed4/10

   Otter documents scheduling only in the narrow sense of automatically joining recurring calendar meetings ('Schedule your AI Meeting Notetaker to automatically join all your Zoom, Teams, and Google Meet meetings'), plus webhooks/API/Zapier integrations that could be chained into workflows. There is no evidence of a general recurring-job/workflow scheduler (e.g., scheduled reports, cron-like automation, or repeatable AI-agent tasks beyond meeting attendance). Missing for 10: documented recurring workflow/job scheduling beyond meeting attendance, evidence of cron-like or repeatable automation configuration, independent confirmation of this capability in use.

   • [claimed-docs] “Schedule your AI Meeting Notetaker to automatically join all your Zoom, Microsoft Teams, and Google Meet meetings.”
   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”

   proof ↗⚑ flag

   Fellow—none0/10

   Fellow is a meeting-notes/AI assistant product with a REST API, webhooks, and MCP server, but nothing in the evidence describes scheduling recurring jobs or automated workflows (e.g., cron-like triggers, scheduled report generation, or recurring automation pipelines). Webhooks are event-driven, not schedule-based, and no docs mention recurring task orchestration.

   ⚑ flag

Calendar

1. product managerI connect Google or Outlook calendar once and control per-meeting-type rules for which meetings get captured automatically

   weight 3 · round to Fellow
   Otter.ai—none0/10

   Evidence shows Otter can auto-join Zoom/Teams/Google Meet meetings via scheduling (otter-docs-17), but nothing in the pack describes connecting a Google or Outlook calendar or setting per-meeting-type rules for which meetings get captured. This specific calendar-integration and rule-based control capability is unevidenced.

   • [claimed-docs] “Schedule your AI Meeting Notetaker to automatically join all your Zoom, Microsoft Teams, and Google Meet meetings.”

   proof ↗⚑ flag

   Fellow~partialclaimed3/10

   Fellow's evidence shows organization-wide recording policies and manual per-meeting record/pause control, but there is no explicit mention of connecting a Google or Outlook calendar or of configuring rules that vary automatic capture by meeting type. Missing for 10: explicit calendar OAuth connection flow, documentation of per-meeting-type (e.g. 1:1 vs external) auto-capture rule configuration, and any UI/API evidence tying calendar events to capture policy.

   • [claimed-docs] “Set organization-wide policies for how meetings are recorded, accessed, and retained”
   • [claimed-docs] “Users choose when to record, pause, or resume capture when part of a conversation needs to stay off the record.”
   • [claimed-docs] “Standardize how meetings are captured, managed, and protected across every platform and format your teams use.”
   • [claimed-docs] “Set configurable retention policies, including zero-day retention, so data is handled according to your organization’s requirements.”

   proof ↗⚑ flag

2. founderI walk into each meeting prepped — the tool surfaces past meetings with the same people and a brief of open threads before the call

   weight 1 · round to Fellow
   Otter.ai~partialclaimed4/10

   Otter clearly supports search across past meetings, grouping by team/project/topic, and AI Chat that can surface insights and follow-ups (otter-docs-1, otter-docs-5, otter-docs-11, otter-docs-12, otter-docs-18), which could be used to find prior context with the same people. However, there is no evidence of a proactive, calendar-triggered 'pre-meeting brief' that automatically surfaces past meetings with the same attendees before a call starts — all capabilities described are pull-based search/chat rather than an automated prep experience tied to the upcoming meeting. Missing for 10: automatic calendar-based attendee matching, a dedicated 'pre-call brief' UI/feature, and any independent evidence confirming this specific prep workflow works as described.

   • [claimed-docs] “Otter AI Chat searches across your meetings and connected apps to instantly answer questions and help you create follow-ups, reports, and co…”
   • [claimed-docs] “Meetings grouped by team, project, or topic so everyone can find recordings and collaborate in one shared space.”
   • [claimed-docs] “Find key insights from past calls, documents, and more using natural-language.”
   • [claimed-docs] “Keep meetings and notes organized by client, opportunity, or topic to easily revisit key highlights and follow-ups.”
   • [claimed-docs] “Search your meeting transcripts across all time periods”
   • [claimed-docs] “Analyze patterns and themes across multiple meetings”

   proof ↗⚑ flag

   Fellow~partialclaimed5/10

   Fellow makes meetings searchable via full transcript search and MCP/API queries like 'what did we decide in last month's standup', which supports surfacing past context with specific people, but there is no documented feature that proactively assembles a pre-meeting brief keyed to attendees or auto-surfaces prior meetings with the same people before a call. missing for 10: a dedicated pre-meeting briefing/prep feature that auto-detects attendees and compiles related past meetings and open action items ahead of the call, plus independent hands-on evidence of this workflow.

   • [claimed-docs] “Every conversation becomes searchable through a full transcript, giving your team instant access to past context whenever they need it.”
   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?" or "What did we decide in last month…”
   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?"”
   • [claimed-docs] “Your favorite AI chatbot like Claude, ChatGPT, or Cursor can now tap directly into your meeting recaps, notes, and action items”
   • [claimed-docs] “pass transcripts to an LLM for tailored recaps and action plans, the API gives you everything you need to make it happen”

   proof ↗⚑ flag

Capture

1. product managerThe notetaker reliably captures Zoom, Google Meet, and Microsoft Teams meetings, with recording where I want it

   weight 2 · round to Fellow
   Otter.ai!disputedcontradicted5/10

   Otter documents solid capture breadth: scheduled bot-based joining across Zoom/Teams/Meet (otter-docs-17), plus bot-free desktop and Meet capture for users who don't want a bot present (otter-docs-2, otter-docs-15, otter-docs-38). But hands-on/community reports concretely contradict the 'recording where I want it' promise — users found the bot joining confidential calls unexpectedly, being unable to identify who invited it, and the bot rejoining despite attempts to remove it (otter-comm-8, otter-comm-6, otter-comm-7, otter-comm-5), undermining reliable, controlled capture. missing for 10: independent verification of accurate/controllable scheduling behavior, resolution of the 'can't stop the bot' complaints, and confirmation that bot-free recording is equally reliable across all three platforms.

   • [claimed-docs] “Schedule your AI Meeting Notetaker to automatically join all your Zoom, Microsoft Teams, and Google Meet meetings.”
   • [claimed-docs] “Record conversations directly from your Mac or Windows desktop, without bots joining the call.”
   • [claimed-docs] “Capture impromptu Google Meet calls without a bot present, or transcribe any media from every website.”
   • [claimed-docs] “Record bot-free and manage meetings directly through the Otter desktop app, providing added convenience and flexibility to capture conversat…”
   • [community] “I remember being on sensitive zoom calls and seeing Otter.ai join. Had to track down which person was using it, and even they were clueless …”
   • [community] “A lawyer invited OtterAI to a confidential meeting; the commenter read Otter's privacy statement and found they retain data in the cloud and…”
   • [community] “A lawyer used Otter to record and transcribe a confidential meeting about a child custody case; participants' first awareness of the recordi…”
   • [community] “An AI researcher said Otter recorded a Zoom meeting with investors, then shared a transcription including 'intimate, confidential details' a…”

   proof ↗⚑ flag

   Fellow✓fullclaimed8/10

   Fellow explicitly documents recording capture across Zoom, Google Meet, Microsoft Teams (plus Slack Huddles and in-person), with flexibility to record via visible bot or bot-less desktop audio capture, and user control over when to record/pause/resume. This directly matches the PM's need for reliable, controllable capture across major platforms. Missing for 10: independent/hands-on verification of recording reliability across all three platforms and no third-party reviews confirming real-world capture accuracy.

   • [claimed-docs] “Fellow gives teams the flexibility to record with a visible bot or without one — capturing audio directly from the desktop”
   • [claimed-docs] “Fellow gives teams the flexibility to record with a visible bot or without one — capturing audio directly from the desktop across Zoom, Goog…”
   • [claimed-docs] “Users choose when to record, pause, or resume capture when part of a conversation needs to stay off the record.”
   • [claimed-docs] “Standardize how meetings are captured, managed, and protected across every platform and format your teams use.”

   proof ↗⚑ flag

2. founderCapture and transcribe meetings without a visible bot joining the call — audio is captured from my device so external participants see nothing extra

   weight 3 · round to Fellow
   Otter.ai~partialclaimed6/10

   Otter explicitly documents desktop-based, bot-free recording/transcription ("Record conversations directly from your Mac or Windows desktop, without bots joining the call" and "Capture impromptu Google Meet calls without a bot present"), directly matching the story. However, all supporting evidence is vendor-authored; community discussion in the pack focuses entirely on the bot-based joining experience (visible bot, default sharing, privacy issues) rather than validating the bot-free desktop-capture mode, so there is no independent hands-on confirmation this mode works as claimed. Missing for 10: independent/third-party confirmation that bot-free desktop capture actually works and is undetectable to other participants, and detail on what info (if any) is disclosed to other call participants in this mode.

   • [claimed-docs] “Record conversations directly from your Mac or Windows desktop, without bots joining the call.”
   • [claimed-docs] “Capture impromptu Google Meet calls without a bot present, or transcribe any media from every website.”
   • [claimed-docs] “Record bot-free and manage meetings directly through the Otter desktop app, providing added convenience and flexibility to capture conversat…”

   proof ↗⚑ flag

   Fellow✓fullclaimed8/10

   Fellow explicitly documents botless recording that captures audio directly from the desktop across Zoom, Meet, Teams, Slack Huddles and in-person meetings, giving teams flexibility to record with or without a visible bot, plus transcript generation and search from the captured audio. Missing for 10: independent/hands-on confirmation that external participants truly see nothing extra during botless capture, and detail on how desktop audio capture technically avoids appearing in participant lists.

   • [claimed-docs] “Fellow gives teams the flexibility to record with a visible bot or without one — capturing audio directly from the desktop”
   • [claimed-docs] “Fellow gives teams the flexibility to record with a visible bot or without one — capturing audio directly from the desktop across Zoom, Goog…”
   • [claimed-docs] “Every conversation becomes searchable through a full transcript, giving your team instant access to past context whenever they need it.”
   • [claimed-docs] “Users choose when to record, pause, or resume capture when part of a conversation needs to stay off the record.”

   proof ↗⚑ flag

3. founderRecord and transcribe in-person conversations from a mobile app, and those notes land in the same searchable workspace

   weight 2 · round to Otter.ai
   Otter.ai~partialclaimed4/10

   Otter's docs confirm bot-free recording from desktop and searchable, shared workspaces (otter-docs-2, otter-docs-5, otter-docs-18, otter-docs-38), and general live transcription/speaker recognition (otter-docs-22), but none of the evidence explicitly describes a mobile app for recording in-person conversations — only desktop capture is documented. Missing for 10: explicit mobile-app in-person recording capability, confirmation that mobile-captured notes sync into the same workspace as other recordings, and independent hands-on evidence of mobile recording quality.

   • [claimed-docs] “Record conversations directly from your Mac or Windows desktop, without bots joining the call.”
   • [claimed-docs] “Meetings grouped by team, project, or topic so everyone can find recordings and collaborate in one shared space.”
   • [claimed-docs] “Search your meeting transcripts across all time periods”
   • [claimed-docs] “Live transcription in multiple languages, and speaker recognition.”
   • [claimed-docs] “Record bot-free and manage meetings directly through the Otter desktop app, providing added convenience and flexibility to capture conversat…”

   proof ↗⚑ flag

   Fellow—none0/10

   Evidence shows Fellow can capture in-person meetings via desktop audio capture (fellow-docs-20) and makes transcripts searchable (fellow-docs-21), but there is no mention anywhere in the pack of a mobile app for recording conversations — all capture references point to desktop/bot-based capture during scheduled meetings. Missing for 10: any documentation of a Fellow mobile app, mobile recording capability, or evidence that in-person capture happens via phone rather than laptop/desktop.

   • [claimed-docs] “Fellow gives teams the flexibility to record with a visible bot or without one — capturing audio directly from the desktop across Zoom, Goog…”
   • [claimed-docs] “Every conversation becomes searchable through a full transcript, giving your team instant access to past context whenever they need it.”
   • [claimed-docs] “Users choose when to record, pause, or resume capture when part of a conversation needs to stay off the record.”

   proof ↗⚑ flag

Integrations

1. sales leadMeeting notes and summaries sync automatically onto the right contact and deal records in my CRM (HubSpot, Salesforce, Attio)

   weight 3 · round to Otter.ai
   Otter.ai~partialclaimed5/10

   Vendor docs claim CRM integrations that extract deal details, notes, and next steps and sync them to Salesforce and HubSpot (otter-docs-4, otter-docs-8, otter-docs-25, otter-docs-36), which covers two of the three named CRMs, but Attio is never mentioned anywhere in the evidence pack. All support is first-party marketing copy with no independent/hands-on confirmation that notes actually land on the correct contact/deal record versus a generic sync, and the pricing page flags the integration with an asterisk suggesting limitations. Missing for 10: Attio support, independent verification of accurate record-level (contact/deal) matching, and confirmation the sync works outside enterprise/marketing claims.

   • [claimed-docs] “Key deal details, notes, and next steps automatically extracted from every meeting and synced to your CRM.”
   • [claimed-docs] “CRM (Salesforce and Hubspot) and document integrations that allow you to query your CRM directly through Otter AI Chat for more personalized…”
   • [claimed-docs] “Salesforce\*, HubSpot\*, Zapier integrations”
   • [claimed-docs] “CRM (Salesforce and Hubspot) and document integrations that allow you to query your CRM directly through Otter AI Chat for more personalized…”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”

   proof ↗⚑ flag

   Fellow—none0/10

   The evidence describes Fellow's Developer API, webhooks, and MCP server for accessing transcripts/notes/action items, but there is no mention of any native integration or automatic sync with HubSpot, Salesforce, or Attio contact/deal records. A sales-focused meeting tool could plausibly ship such CRM sync, so the axis applies, but no evidence confirms it exists.

   • [claimed-docs] “The Developer API opens that data to you: transcripts, structured notes, and more, all available through standard REST calls.”
   • [claimed-docs] “Fellow sends an HTTP POST request to the URL you specify with details about the event.”
   • [claimed-docs] “Webhooks allow you to receive real-time notifications when events occur in Fellow.”
   • [claimed-docs] “pass transcripts to an LLM for tailored recaps and action plans, the API gives you everything you need to make it happen”

   proof ↗⚑ flag

2. product managerNotes flow into the tools where work happens — Slack channels, Notion pages, and thousands of apps via Zapier

   weight 2 · round to Otter.ai
   Otter.ai✓fullprobed8/10

   Otter documents direct integrations with Slack-adjacent workflow tools (Notion is not explicitly named, but Zapier, Airtable, ClickUp, Zendesk, ServiceNow, JIRA, Asana, Glean, S3, CRM syncs), plus a public API/webhooks and a live, OAuth-gated MCP server confirmed by runtime probe, enabling notes/action items to flow into thousands of apps via Zapier and beyond. Missing for 10: explicit first-party mention of Slack and Notion integrations by name, and independent (non-vendor) confirmation of the Zapier/Airtable/ClickUp integrations actually working in practice.

   • [claimed-docs] “Help your team move faster by sending actions items from meetings into tools they already use, like JIRA, Asana, and others.”
   • [claimed-docs] “Salesforce\*, HubSpot\*, Zapier integrations”
   • [claimed-docs] “Otter automatically sends transcripts, summaries, and meeting metadata to Airtable.”
   • [claimed-docs] “Send meeting summaries and action items from Otter to ClickUp to manage everything in one place.”
   • [claimed-docs] “Search Otter transcripts, notes, and action items alongside the rest of your company knowledge in Glean.”
   • [claimed-docs] “Automatically turn meeting takeaways into support tickets or updates in tools like Zendesk and ServiceNow.”
   • [claimed-docs] “Otter API & Webhooks”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fellow—none0/10

   The evidence pack only documents a generic Developer API, webhooks, and MCP server — there is no mention of native Slack, Notion, or Zapier integrations or an app marketplace listing that would let notes flow automatically into those specific tools.

   ⚑ flag

Memory

1. product managerAsk questions in natural language across my whole meeting history ("what did we decide about pricing?") and get answers with sources

   weight 2 · round to Otter.ai
   Otter.ai✓fullprobed8/10

   Otter AI Chat and its enterprise MCP server explicitly support natural-language querying across meeting history ('what did we decide about pricing?'-style questions), searching transcripts across all time periods, analyzing patterns across meetings, and citing/linking back to source meetings via the AI Chat interface. This is corroborated by a live runtime probe confirming the MCP endpoint is real and OAuth-gated, not vaporware. Missing for 10: independent hands-on verification of answer accuracy/quality and explicit confirmation that answers include inline source citations (docs describe search/analysis but don't detail citation format in depth).

   • [claimed-docs] “Otter AI Chat searches across your meetings and connected apps to instantly answer questions and help you create follow-ups, reports, and co…”
   • [claimed-docs] “Find key insights from past calls, documents, and more using natural-language.”
   • [claimed-docs] “Search your meeting transcripts across all time periods”
   • [claimed-docs] “Analyze patterns and themes across multiple meetings”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fellow~partialprobed7/10

   Fellow's MCP server explicitly supports natural-language queries across meeting history (e.g. 'What did we decide in last month's standup?') and searchable full transcripts back the answers, with a runtime probe confirming the hosted MCP endpoint is live and functional. However, the evidence never explicitly describes source citations/links accompanying answers, only that transcripts and notes are the underlying data. Missing for 10: explicit documentation that MCP answers include citations/sources to specific meetings, and independent hands-on confirmation of answer quality/accuracy.

   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?"”
   • [claimed-docs] “Fellow's Model Context Protocol (MCP) Server allows you to ask your AI Assistant about your meetings, without needing to write any code.”
   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?" or "What did we decide in last month…”
   • [claimed-docs] “Every conversation becomes searchable through a full transcript, giving your team instant access to past context whenever they need it.”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Fellow's hosted MCP server https://fellow.app/mcp returned HTTP 401…”
   • [probe] “official MCP server documented at https://developers.fellow.ai/reference/mcp-server”

   proof ↗⚑ flag

2. product managerSearch across every past meeting — transcripts, summaries, and notes — and jump to the exact moment something was said

   weight 3 · round to Otter.ai
   Otter.ai✓fullprobed8/10

   Otter directly supports cross-meeting search and jump-to-moment via natural-language search over transcripts, summaries, and notes ('Search your meeting transcripts across all time periods', 'Find key insights from past calls, documents, and more using natural-language', grouping by project/topic), plus AI Chat and MCP server for querying meeting knowledge, corroborated by a live runtime probe confirming the MCP endpoint is real and functioning. Missing for 10: independent hands-on verification of precise timestamp jump-to-moment UX and any third-party review confirming search accuracy/recall across large historical archives.

   • [claimed-docs] “Search your meeting transcripts across all time periods”
   • [claimed-docs] “Find key insights from past calls, documents, and more using natural-language.”
   • [claimed-docs] “Meetings grouped by team, project, or topic so everyone can find recordings and collaborate in one shared space.”
   • [claimed-docs] “Otter AI Chat searches across your meetings and connected apps to instantly answer questions and help you create follow-ups, reports, and co…”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”

   proof ↗⚑ flag

   Fellow✓fullprobed7/10

   Fellow explicitly advertises full-transcript search ('Every conversation becomes searchable through a full transcript') and its MCP server exposes tools like search_meetings and get_meeting_transcript for asking natural-language questions like 'what did we decide in last month's standup', confirmed live via a runtime probe. Missing for 10: explicit UI evidence of clicking a search result to jump to the exact timestamp/moment in a recording, and independent (non-vendor) confirmation of search accuracy across large history.

   • [claimed-docs] “Every conversation becomes searchable through a full transcript, giving your team instant access to past context whenever they need it.”
   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?"”
   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?" or "What did we decide in last month…”
   • [claimed-docs] “Your favorite AI chatbot like Claude, ChatGPT, or Cursor can now tap directly into your meeting recaps, notes, and action items”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Fellow's hosted MCP server https://fellow.app/mcp returned HTTP 401…”
   • [probe] “official MCP server documented at https://developers.fellow.ai/reference/mcp-server”

   proof ↗⚑ flag

Summaries

1. product managerAction items with owners are automatically extracted from the conversation and collected somewhere I can track them

   weight 3 · round drawn
   Otter.ai✓fullprobed8/10

   Otter automatically extracts action items with assigned owners from meetings (otter-docs-3, otter-docs-21, otter-docs-30) and collects them in a trackable, searchable workspace, with the ability to sync/push them to task tools like JIRA, Asana, ClickUp, and CRMs for centralized tracking (otter-docs-10, otter-docs-31, otter-docs-4). This is corroborated by an enterprise blog post and integrations page confirming live functionality, plus a working MCP server for querying meeting action items. Missing for 10: independent hands-on verification specifically of action-item/owner extraction accuracy (community evidence focuses on privacy/security concerns rather than confirming or disputing action-item quality).

   • [claimed-docs] “Clear next steps are automatically captured and assigned from every meeting.”
   • [claimed-docs] “Otter turns every meeting into a clear summary with decisions, action items, and insights.”
   • [claimed-docs] “Stay on track by automatically turning your meeting notes into simple action items with deadlines.”
   • [claimed-docs] “Help your team move faster by sending actions items from meetings into tools they already use, like JIRA, Asana, and others.”
   • [claimed-docs] “Send meeting summaries and action items from Otter to ClickUp to manage everything in one place.”
   • [claimed-docs] “Key deal details, notes, and next steps automatically extracted from every meeting and synced to your CRM.”
   • [claimed-docs] “Otter's fully customizable, AI-powered meeting summaries automatically extract actionable insights based on meeting purpose and for differen…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fellow✓fullclaimed8/10

   Fellow automatically generates AI action items with assignees from meeting conversations (fellow-docs-23), and these are collected/trackable via the app and API's get_action_items endpoint with filters like assigned_to_me/assigned_to_others (fellow-docs-5, fellow-docs-19), plus surfaced via MCP queries like 'what were my action items' (fellow-docs-32). Missing for 10: no independent/hands-on evidence confirming extraction accuracy or owner-assignment reliability beyond vendor docs.

   • [claimed-docs] “You automatically receive a clear meeting summary, suggested AI action items, decisions, and topic-based minutes for every meeting.”
   • [claimed-docs] “List action items with optional filters and pagination.”
   • [claimed-docs] “assigned_to_me: Only action items assigned to the authenticated user\n- assigned_to_others: Only action items the user can edit, assigned to…”
   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?" or "What did we decide in last month…”
   • [claimed-docs] “pass transcripts to an LLM for tailored recaps and action plans, the API gives you everything you need to make it happen”

   proof ↗⚑ flag

2. sales leadShape the notes with custom templates or saved prompts per meeting type (discovery call, 1:1, standup) instead of one generic format

   weight 2 · round to Otter.ai
   Otter.ai~partialclaimed4/10

   Otter claims 'fully customizable, AI-powered meeting summaries' that adapt to meeting purpose and functional role (sales, recruiters, PMs), implying some template-like customization, but there's no documentation of a concrete UI for creating/saving custom templates or prompts per meeting type (discovery call vs 1:1 vs standup) that a sales lead could configure themselves. Missing for 10: explicit template/prompt library or editor, evidence of user-defined per-meeting-type presets, and any hands-on confirmation that summaries can be shaped beyond the automatic role-based defaults.

   • [claimed-docs] “Otter's fully customizable, AI-powered meeting summaries automatically extract actionable insights based on meeting purpose and for differen…”
   • [claimed-docs] “Otter turns every meeting into a clear summary with decisions, action items, and insights.”

   proof ↗⚑ flag

   Fellow—none0/10

   The evidence pack covers Fellow's API, MCP server, webhooks, recording controls, and retention policies, but contains no mention of customizable note templates or saved prompts tied to meeting type (discovery call, 1:1, standup). This is a fair axis for a meeting-notes product, but no evidence supports it.

   ⚑ flag

3. sales leadThe tool drafts my follow-up email from the meeting so I can review and send it in a couple of clicks

   weight 1 · round to Otter.ai
   Otter.ai✓fullclaimed8/10

   Otter directly claims automatic follow-up email drafting from meetings (otter-docs-41: 'Instantly auto-generate follow-up emails and next steps for client calls'), plus related CRM sync of key deal details and next steps (otter-docs-4) and role-tailored summaries for sales (otter-docs-37), matching the sales-lead persona. Missing for 10: independent hands-on confirmation of the follow-up email drafting feature specifically (evidence is vendor-sourced only) and clarity on whether it's Enterprise-tier gated like other advanced features.

   • [claimed-docs] “Instantly auto-generate follow-up emails and next steps for client calls, internal reviews, and more.”
   • [claimed-docs] “Key deal details, notes, and next steps automatically extracted from every meeting and synced to your CRM.”
   • [claimed-docs] “Otter's fully customizable, AI-powered meeting summaries automatically extract actionable insights based on meeting purpose and for differen…”
   • [claimed-docs] “Clear next steps are automatically captured and assigned from every meeting.”
   • [claimed-docs] “Help sales leaders coach and forecast more effectively by revealing blockers, objections, and competitor mentions.”

   proof ↗⚑ flag

   Fellow—none0/10

   Fellow's evidence covers meeting summaries, action items, transcripts, and an API/MCP server for querying meeting data and even passing transcripts to an LLM for 'tailored recaps and action plans,' but there is no evidence of a native feature that drafts a follow-up email for one-click review and send — that would require custom API integration, not a documented built-in capability.

   • [claimed-docs] “You automatically receive a clear meeting summary, suggested AI action items, decisions, and topic-based minutes for every meeting.”
   • [claimed-docs] “pass transcripts to an LLM for tailored recaps and action plans, the API gives you everything you need to make it happen”
   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?"”
   • [claimed-docs] “Ask anything about your meetings - Get answers to questions like "What were my action items this week?" or "What did we decide in last month…”

   proof ↗⚑ flag

4. product managerI get a structured summary right after each meeting — key points, decisions, and next steps — good enough to share without editing

   weight 3 · round to Fellow
   Otter.ai!disputedcontradicted5/10

   Otter's docs claim every meeting is turned into a structured summary with decisions, action items, and next steps (otter-docs-21, otter-docs-3, otter-docs-37, otter-docs-30), which matches the story. However a hands-on account describes Otter emailing an 'absurd, inaccurate outline' after a real meeting (otter-comm-1), directly contradicting the 'good enough to share without editing' bar, and another user notes it doesn't handle accented English well (otter-comm-9), suggesting summaries often need review. Missing for 10: independent benchmarking of summary accuracy/completeness, and confirmation that decisions/action items are reliably correct without user correction.

   • [claimed-docs] “Otter turns every meeting into a clear summary with decisions, action items, and insights.”
   • [claimed-docs] “Clear next steps are automatically captured and assigned from every meeting.”
   • [claimed-docs] “Otter's fully customizable, AI-powered meeting summaries automatically extract actionable insights based on meeting purpose and for differen…”
   • [claimed-docs] “Stay on track by automatically turning your meeting notes into simple action items with deadlines.”
   • [community] “The Otter bot joined two confidential meetings on my behalf and recorded the whole thing, then emailed every member an absurd, inaccurate "o…”
   • [community] “I use Otter pretty religiously to record all work meetings that I participate in... it doesn't do an amazing job with English in various acc…”

   proof ↗⚑ flag

   Fellow✓fullclaimed8/10

   Fellow's core product docs state you automatically receive a clear meeting summary, suggested AI action items, decisions, and topic-based minutes for every meeting, directly matching the story of a structured post-meeting summary. Missing for 10: independent/hands-on user reviews confirming the summary quality is share-ready without edits, and no detail on editing workflow before sharing.

   • [claimed-docs] “You automatically receive a clear meeting summary, suggested AI action items, decisions, and topic-based minutes for every meeting.”
   • [claimed-docs] “Every conversation becomes searchable through a full transcript, giving your team instant access to past context whenever they need it.”
   • [claimed-docs] “Fellow gives teams the flexibility to record with a visible bot or without one — capturing audio directly from the desktop”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Fellow
   Otter.ai~partialprobed4/10

   Otter documents a Public API/Webhooks (Pro+ tier) and a hosted MCP server for querying meeting transcripts, summaries and action items (otter-docs-26/40/46, otter-probe-rt-1 confirms the MCP endpoint is live and OAuth-gated), but these are limited to read/query-style meeting-data access and are gated to paid/Enterprise workspaces rather than exposing full UI parity (recording controls, collaborative editing, CRM/ticket integrations, admin/security settings) as callable API operations, and no public OpenAPI/reference spec was found (otter-probe-1 all 404). Missing for 10: evidence of API coverage for non-meeting-data UI actions (recording management, collaborative editing, integration configuration), a public API reference/spec, and availability outside Enterprise tier.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [claimed-docs] “ChatGPT, Claude, and other AI chat tools can securely access your meeting knowledge through Otter's MCP Server for deeper analysis and smart…”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”

   proof ↗⚑ flag

   Fellow~partialprobed5/10

   Fellow's Developer API exposes meaningful UI-parallel functionality (list recordings, list action items, append note agenda, webhooks, MCP conversational access) but the evidence only covers a subset of read/limited-write operations, not full parity with UI actions like recording controls, retention policy configuration, keyword tracking, or admin dashboard settings. missing for 10: API coverage for recording start/pause/resume, retention/compliance policy management via API, keyword tracking configuration, and broader write/update operations beyond appending agenda text.

   • [claimed-docs] “The Developer API opens that data to you: transcripts, structured notes, and more, all available through standard REST calls.”
   • [claimed-docs] “List recordings with optional filters and pagination.”
   • [claimed-docs] “List action items with optional filters and pagination.”
   • [claimed-docs] “Add Fellow Markdown to the end of a note's agenda, leaving the rest of the content in place.”
   • [claimed-docs] “Webhooks allow you to receive real-time notifications when events occur in Fellow.”
   • [claimed-docs] “pass transcripts to an LLM for tailored recaps and action plans, the API gives you everything you need to make it happen”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.fellow.ai/openapi.json, https://developers.fellow.ai/swagger.json, https://develo…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Fellow
   Otter.ai~partialclaimed3/10

   Otter offers some data egress via S3 export of transcripts/summaries/metadata and its public API/webhooks, which could support portability, but there is no documented comprehensive 'export all your data' or account-deletion/data-portability feature, nor any explicit open-format guarantee (e.g., standard transcript formats, full account export tool). missing for 10: dedicated full-account data export tool, explicit open/standard file formats, documented account deletion/data-takeout process, independent confirmation of successful full export.

   • [claimed-docs] “Export transcripts, summaries, and metadata directly to your Amazon S3 bucket.”
   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”

   proof ↗⚑ flag

   Fellow~partialclaimed6/10

   Fellow's Developer API exposes transcripts, notes, action items, and recordings via standard REST calls, and the Super Admin API can 'retrieve, export, and delete data across the entire workspace' for Enterprise admins, giving a path to full data export. However, there is no explicit documentation of a bulk 'export everything' feature, no stated output format guarantees (e.g., JSON/CSV schema for full account export), and no independent verification of completeness. Missing for 10: a documented one-click/bulk full-account export tool, explicit open-format (JSON/CSV) export spec, and independent confirmation that all data types are covered.

   • [claimed-docs] “The Developer API opens that data to you: transcripts, structured notes, and more, all available through standard REST calls.”
   • [claimed-docs] “List recordings with optional filters and pagination.”
   • [claimed-docs] “List action items with optional filters and pagination.”
   • [claimed-docs] “Fellow’s Super Admin API lets designated Enterprise‑plan administrators retrieve, export, and delete data across the entire workspace”
   • [claimed-docs] “pass transcripts to an LLM for tailored recaps and action plans, the API gives you everything you need to make it happen”

   proof ↗⚑ flag

Pricing

1. founderStart free and see exactly what each paid tier costs and adds — no "talk to sales" wall for basic use

   weight 2 · round to Otter.ai
   Otter.ai~partialclaimed4/10

   The evidence confirms a public /pricing page listing tier-specific features (e.g., otter-docs-23-27 detail limits like '3 lifetime file imports' and '3 concurrent meetings' presumably tied to a plan), and enterprise-tier features explicitly require contacting an account manager (otter-docs-43), implying lower tiers are self-serve. However, no evidence shows actual dollar prices, a clear free-vs-paid breakdown, or confirmation that all paid-tier costs are shown without a sales contact requirement. Missing for 10: explicit price points per tier, confirmation of a self-serve checkout flow, and independent corroboration that no sales-gate exists for basic paid tiers.

   • [claimed-docs] “3 lifetime audio/video file imports”
   • [claimed-docs] “Team vocabulary & taggable speakers”
   • [claimed-docs] “Salesforce\*, HubSpot\*, Zapier integrations”
   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Join 3 concurrent meetings”
   • [claimed-docs] “Keep your organization's data out of AI model training. Contact your account manager to get started.”

   proof ↗⚑ flag

   Fellow—none0/10

   The evidence pack only mentions two feature names ('Keyword tracking', 'Transcript redaction') from the pricing page but contains no details on free tier availability, tier pricing, or whether higher tiers require contacting sales. No evidence supports or contradicts a transparent self-serve pricing structure.

   • [claimed-docs] “Keyword tracking”
   • [claimed-docs] “Transcript redaction”

   proof ↗⚑ flag

Privacy

1. it adminThe product ships real consent features — participant notifications, in-meeting disclosure, or admin-enforced transparency — not just a policy PDF

   weight 3 · round drawn
   Otter.ai—none0/10

   No evidence pack item describes any real consent mechanism (participant notification banners, in-meeting disclosure indicators, or admin-enforced consent settings); the docs focus entirely on recording, transcription, and integrations. Community reports go further, describing the bot silently joining sensitive/confidential meetings, transcripts shared with all participants by default without prior notice, and company support dismissing responsibility when participants weren't informed — confirming the absence of a genuine consent feature rather than just a documentation gap.

   • [community] “I just deleted my account because of that, also they share conversations with everyone in the meeting by DEFAULT, it wasn't nice receiving a…”
   • [community] “I stopped using them when I saw they share with everyone by default. I wanted the notes only for myself so I could be more present in meetin…”
   • [community] “A lawyer used Otter to record and transcribe a confidential meeting about a child custody case; participants' first awareness of the recordi…”
   • [community] “I remember being on sensitive zoom calls and seeing Otter.ai join. Had to track down which person was using it, and even they were clueless …”
   • [community] “An AI researcher said Otter recorded a Zoom meeting with investors, then shared a transcription including 'intimate, confidential details' a…”

   proof ↗⚑ flag

   Fellow—none0/10

   The evidence shows admin-side policy controls (retention settings, org-wide recording/access policies) and user-side recording controls, but nothing describing participant-facing consent mechanisms such as in-meeting recording disclosure banners, automated participant notifications when a bot joins, or admin-enforced transparency toward attendees. Notably, Fellow explicitly supports recording 'without a visible bot' by capturing desktop audio directly, which underscores the absence of a documented notification/disclosure mechanism rather than confirming one.

   • [claimed-docs] “Fellow gives teams the flexibility to record with a visible bot or without one — capturing audio directly from the desktop”
   • [claimed-docs] “Fellow gives teams the flexibility to record with a visible bot or without one — capturing audio directly from the desktop across Zoom, Goog…”
   • [claimed-docs] “Users choose when to record, pause, or resume capture when part of a conversation needs to stay off the record.”
   • [claimed-docs] “Set organization-wide policies for how meetings are recorded, accessed, and retained”
   • [claimed-docs] “Set configurable retention policies, including zero-day retention, so data is handled according to your organization’s requirements.”
   • [claimed-docs] “Standardize how meetings are captured, managed, and protected across every platform and format your teams use.”

   proof ↗⚑ flag

2. it adminThe vendor documents whether meeting data trains AI models and gives my org an enforceable opt-out, alongside SOC 2 / HIPAA posture

   weight 2 · round to Otter.ai
   Otter.ai~partialcommunity4/10

   Otter documents an enterprise-tier opt-out from AI model training ('Keep your organization's data out of AI model training. Contact your account manager to get started' — otter-docs-43), and community evidence confirms that by default Otter's privacy policy allows using 'anonymized' recordings for training (otter-comm-6), consistent with an opt-in-by-default posture that requires manual admin action to disable. However, the opt-out is not a self-service, enforceable admin toggle — it requires contacting an account manager — and no evidence pack item documents SOC 2 or HIPAA compliance status. Missing for 10: explicit SOC 2/HIPAA certification documentation, a self-service admin-console opt-out control, and independent audit confirmation that opted-out orgs' data is actually excluded from training.

   • [claimed-docs] “Keep your organization's data out of AI model training. Contact your account manager to get started.”
   • [community] “A lawyer invited OtterAI to a confidential meeting; the commenter read Otter's privacy statement and found they retain data in the cloud and…”
   • [claimed-docs] “Maintain visibility into account activity with audit trails and logging, supporting your security, compliance, and regulatory reporting need…”
   • [claimed-docs] “Easily control access with secure identity tools like Okta, Azure AD, and others.”

   proof ↗⚑ flag

   Fellow—none0/10

   Evidence shows retention policies and org-wide recording/access controls, but there is no documentation addressing whether meeting data is used to train AI models, no explicit opt-out mechanism for AI training, and no mention of SOC 2 or HIPAA compliance posture anywhere in the pack.

   • [claimed-docs] “Set organization-wide policies for how meetings are recorded, accessed, and retained”
   • [claimed-docs] “Set configurable retention policies, including zero-day retention, so data is handled according to your organization’s requirements.”
   • [claimed-docs] “Standardize how meetings are captured, managed, and protected across every platform and format your teams use.”

   proof ↗⚑ flag

3. it adminSet retention policies — auto-delete transcripts and recordings on a schedule — and permanently erase data on demand

   weight 2 · round to Fellow
   Otter.ai—none0/10

   No evidence describes configurable retention schedules, auto-deletion of transcripts/recordings, or an on-demand data erasure mechanism; enterprise docs mention audit trails and excluding data from AI training but nothing about retention/deletion controls, and community reports even highlight data being retained/shared unexpectedly. This axis clearly applies to an IT-admin/enterprise product but is unaddressed in the evidence.

   • [claimed-docs] “Maintain visibility into account activity with audit trails and logging, supporting your security, compliance, and regulatory reporting need…”
   • [claimed-docs] “Keep your organization's data out of AI model training. Contact your account manager to get started.”
   • [community] “A lawyer invited OtterAI to a confidential meeting; the commenter read Otter's privacy statement and found they retain data in the cloud and…”

   proof ↗⚑ flag

   Fellow~partialclaimed6/10

   Fellow documents configurable retention policies including zero-day retention, and the Super Admin API allows retrieving, exporting, and deleting data across the workspace, which supports on-demand erasure. However, there's no explicit documentation of a scheduled auto-delete mechanism for transcripts/recordings specifically or a UI/API for setting retention schedules with confirmation of enforcement. Missing for 10: detailed retention policy configuration UI/API docs, evidence of scheduled automated deletion execution, and independent confirmation that erasure requests are honored end-to-end.

   • [claimed-docs] “Set configurable retention policies, including zero-day retention, so data is handled according to your organization’s requirements.”
   • [claimed-docs] “Fellow’s Super Admin API lets designated Enterprise‑plan administrators retrieve, export, and delete data across the entire workspace”
   • [claimed-docs] “Set organization-wide policies for how meetings are recorded, accessed, and retained”
   • [claimed-docs] “Standardize how meetings are captured, managed, and protected across every platform and format your teams use.”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Otter.ai—none0/10

   No evidence anywhere in the pack mentions data residency, regional storage options, or geographic controls over where data is stored; the closest privacy-related item (otter-docs-43) only addresses excluding data from model training, not storage location. Community evidence discusses data sharing and retention concerns but not regional choice, so this applicable privacy axis has no supporting evidence.

   ⚑ flag

   Fellow—none0/10

   No evidence pack item mentions data residency, regional data storage options, or geographic data center selection; retention policies and admin controls are covered but region choice is not addressed.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round to Otter.ai
   Otter.ai~partialcommunity5/10

   Otter explicitly advertises an enterprise-only opt-out ('Keep your organization's data out of AI model training. Contact your account manager to get started' — otter-docs-43), but this is gated behind Enterprise plans and manual account-manager setup rather than a self-serve control available to all users. Community reports (otter-comm-6) note that by default Otter's privacy policy allows use of 'anonymized' recordings as training data, meaning most users cannot avoid this without enterprise contracting. Missing for 10: self-serve toggle for all tiers, independent confirmation the enterprise opt-out is honored in practice, and clarity on what 'anonymized' training use means for non-enterprise accounts.

   • [claimed-docs] “Keep your organization's data out of AI model training. Contact your account manager to get started.”
   • [community] “A lawyer invited OtterAI to a confidential meeting; the commenter read Otter's privacy statement and found they retain data in the cloud and…”

   proof ↗⚑ flag

   Fellow—none0/10

   The evidence pack covers retention policies, redaction, recording controls, and API/MCP access, but contains no statement about whether Fellow uses customer data to train AI models or any opt-out mechanism for AI training.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Fellow
   Otter.ai—none0/10

   Otter's docs mention only a narrow enterprise-only opt-out from AI-model training (otter-docs-43) via contacting an account manager, but there is no documented self-service data retention policy, deletion controls, or export/delete workflow for individual users. Community evidence (otter-comm-2, otter-comm-4, otter-comm-6, otter-comm-7) further indicates data is retained in the cloud, used for training unless specially arranged, and that deletion/support requests go unanswered, undermining any claim of user control over retention/deletion.

   • [claimed-docs] “Keep your organization's data out of AI model training. Contact your account manager to get started.”
   • [community] “I just deleted my account because of that, also they share conversations with everyone in the meeting by DEFAULT, it wasn't nice receiving a…”
   • [community] “I have opened a support ticket with screenshots but there is no response, and according to Twitter they are essentially not reviewing ticket…”
   • [community] “A lawyer invited OtterAI to a confidential meeting; the commenter read Otter's privacy statement and found they retain data in the cloud and…”
   • [community] “A lawyer used Otter to record and transcribe a confidential meeting about a child custody case; participants' first awareness of the recordi…”

   proof ↗⚑ flag

   Fellow✓fullclaimed8/10

   Fellow documents configurable retention policies including zero-day retention, org-wide policies on how data is recorded/accessed/retained, and Super Admin API to retrieve, export, and delete data across the entire workspace, directly addressing retention/deletion control. missing for 10: independent/hands-on verification of deletion actually purging data end-to-end and clearer per-user (non-admin) self-service deletion controls.

   • [claimed-docs] “Set configurable retention policies, including zero-day retention, so data is handled according to your organization’s requirements.”
   • [claimed-docs] “Set organization-wide policies for how meetings are recorded, accessed, and retained”
   • [claimed-docs] “Fellow’s Super Admin API lets designated Enterprise‑plan administrators retrieve, export, and delete data across the entire workspace”
   • [claimed-docs] “Standardize how meetings are captured, managed, and protected across every platform and format your teams use.”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Otter.ai—none0/10

   No evidence of a telemetry/usage-tracking opt-out setting; the closest item (otter-docs-43) only covers excluding org data from AI model training for Enterprise accounts, not general telemetry/usage analytics opt-out, and community reports actually highlight data-sharing/retention concerns rather than opt-out controls.

   • [claimed-docs] “Keep your organization's data out of AI model training. Contact your account manager to get started.”
   • [community] “A lawyer invited OtterAI to a confidential meeting; the commenter read Otter's privacy statement and found they retain data in the cloud and…”
   • [community] “Otter is the only thing approaching affordable for individuals, but I don't really trust it given they're playing fast and loose with user d…”

   proof ↗⚑ flag

   Fellow—none0/10

   No evidence pack item discusses telemetry opt-out or usage tracking controls for AI-native users; retention/recording policies are mentioned but not telemetry/usage-tracking opt-out specifically.

   ⚑ flag

Sharing

1. sales leadCut a soundbite or highlight clip from a call and share that moment instead of the whole recording

   weight 1 · round drawn
   Otter.ai—none0/10

   The evidence pack shows Otter can share full transcripts, notes, and summaries, and sync them to other tools, but there is no mention of cutting a specific soundbite/highlight clip from a recording to share instead of the whole call. Missing for 10: any documented clip/highlight creation or snippet-sharing feature, timestamped audio/video excerpt export, or hands-on evidence of this specific capability.

   • [claimed-docs] “Sync transcriptions and meeting notes for easy editing, sharing, and collaboration with all your teammates.”
   • [claimed-docs] “Keep meetings and notes organized by client, opportunity, or topic to easily revisit key highlights and follow-ups.”

   proof ↗⚑ flag

   Fellow—none0/10

   Evidence covers transcripts, recordings listing, action items, webhooks, and MCP access, but nothing describes clipping/highlighting a soundbite from a call or sharing a short excerpt instead of the full recording.

   ⚑ flag

2. it adminSharing is controlled — private-by-default notes, granular link/folder/workspace permissions, and admin visibility into what's shared

   weight 2 · round to Fellow
   Otter.ai!disputedcontradicted4/10

   Otter documents enterprise access controls (SSO via Okta/Azure AD, audit trails/logging, OAuth-gated granular permissions for MCP) suggesting admin-controlled sharing exists at the enterprise tier, but multiple independent hands-on reports directly contradict the 'private-by-default' premise: users report Otter shares transcripts with every meeting participant by default without consent, and confidential/sensitive meetings were transcribed and distributed without attendees' knowledge, causing real harm (killed business deal, custody case exposure). Missing for 10: documented granular link/folder/workspace-level permission controls, clear evidence of a private-by-default note setting, and resolution of the community reports of default-sharing behavior.

   • [claimed-docs] “Easily control access with secure identity tools like Okta, Azure AD, and others.”
   • [claimed-docs] “Maintain visibility into account activity with audit trails and logging, supporting your security, compliance, and regulatory reporting need…”
   • [claimed-docs] “OAuth-authenticated with granular permissions”
   • [community] “I just deleted my account because of that, also they share conversations with everyone in the meeting by DEFAULT, it wasn't nice receiving a…”
   • [community] “I stopped using them when I saw they share with everyone by default. I wanted the notes only for myself so I could be more present in meetin…”
   • [community] “An AI researcher said Otter recorded a Zoom meeting with investors, then shared a transcription including 'intimate, confidential details' a…”
   • [community] “A lawyer used Otter to record and transcribe a confidential meeting about a child custody case; participants' first awareness of the recordi…”
   • [community] “I remember being on sensitive zoom calls and seeing Otter.ai join. Had to track down which person was using it, and even they were clueless …”

   proof ↗⚑ flag

   Fellow~partialclaimed5/10

   Fellow offers org-wide retention/recording policies, workspace admin control over MCP tool access, and Super Admin API for workspace-wide visibility, which addresses some admin oversight needs. However, there is no explicit evidence of private-by-default note settings, granular link/folder-level sharing permissions, or a dedicated sharing-audit dashboard for admins. missing for 10: private-by-default note defaults, granular link/folder/workspace permission controls, admin visibility/audit log specifically for shared content.

   • [claimed-docs] “As a workspace admin, you decide which MCP tools your members’ AI assistants can use.”
   • [claimed-docs] “Set organization-wide policies for how meetings are recorded, accessed, and retained”
   • [claimed-docs] “Fellow’s Super Admin API lets designated Enterprise‑plan administrators retrieve, export, and delete data across the entire workspace”
   • [claimed-docs] “Build admin dashboards that display data from a specific user's perspective”
   • [claimed-docs] “Set configurable retention policies, including zero-day retention, so data is handled according to your organization’s requirements.”
   • [claimed-docs] “Standardize how meetings are captured, managed, and protected across every platform and format your teams use.”

   proof ↗⚑ flag

Transcription

1. founderRun meetings in languages other than English — transcription and summaries support many languages and handle language switching

   weight 2 · round to Otter.ai
   Otter.ai~partialcommunity3/10

   Otter's marketing states 'live transcription in multiple languages' but the evidence pack has no detail on which languages are supported, whether meeting summaries (not just transcripts) are generated in non-English languages, or how mid-meeting language switching is handled. Community evidence only discusses English-accent transcription quality, giving no corroboration of multilingual performance. Missing for 10: documented language list/coverage, evidence that AI summaries (not just live transcript) work in non-English languages, evidence of handling code-switching/mixed-language meetings, and independent hands-on confirmation of non-English accuracy.

   • [claimed-docs] “Live transcription in multiple languages, and speaker recognition.”
   • [community] “I use Otter pretty religiously to record all work meetings that I participate in... it doesn't do an amazing job with English in various acc…”

   proof ↗⚑ flag

   Fellow—none0/10

   No evidence in the pack mentions multi-language support, non-English transcription, or handling language switching within meetings; all citations focus on API access, MCP integration, and English-language feature descriptions.

   ⚑ flag

2. product managerThe transcript attributes words to the right named speakers (diarization plus real name matching), not just "Speaker 1/2"

   weight 3 · round to Otter.ai
   Otter.ai~partialcommunity4/10

   Otter's docs mention 'speaker recognition' during live transcription and 'taggable speakers' in pricing tiers, suggesting some diarization plus a manual tagging mechanism to assign real names, but there's no detailed documentation of automatic real-name matching accuracy or independent verification of correctness. Community threads only discuss transcription accuracy for accents, not speaker attribution reliability. Missing for 10: documentation of automatic vs. manual name assignment, accuracy benchmarks for speaker identification, and independent hands-on verification that speakers are correctly named rather than generic labels.

   • [claimed-docs] “Live transcription in multiple languages, and speaker recognition.”
   • [claimed-docs] “Team vocabulary & taggable speakers”
   • [community] “I use Otter pretty religiously to record all work meetings that I participate in... it doesn't do an amazing job with English in various acc…”

   proof ↗⚑ flag

   Fellow—none0/10

   The evidence pack covers API access, webhooks, MCP server, and recording/retention features, but nowhere mentions speaker diarization or matching transcript segments to real named speakers versus generic labels like 'Speaker 1/2'.

   ⚑ flag

3. product managerThe vendor documents how transcription actually works and its quality (models, accuracy claims, known limits) rather than just saying "AI-powered"

   weight 3 · round drawn
   Otter.ai—none0/10

   The evidence pack shows only marketing-style feature claims (AI-powered summaries, live transcription, speaker recognition) with no vendor documentation of the transcription model(s) used, quantified accuracy benchmarks, or explicitly stated known limitations (e.g., accent/language performance, noise handling). Community evidence even flags real accuracy gaps (accents, non-English speech) that the vendor's own docs never acknowledge, reinforcing the absence of transparent quality documentation.

   • [claimed-docs] “Live transcription in multiple languages, and speaker recognition.”
   • [community] “I use Otter pretty religiously to record all work meetings that I participate in... it doesn't do an amazing job with English in various acc…”
   • [community] “I'm generally a 'hater' of the cloud, and I have to admit that Otter is very good. I used it speaking with someone using airpods on a shitty…”

   proof ↗⚑ flag

   Fellow—none0/10

   The evidence pack covers API access, MCP server, webhooks, and recording/retention features, but contains no documentation of the transcription model used, accuracy benchmarks, or known limitations (e.g., accent/language handling, error rates). This axis clearly applies to a transcription product, but no such technical/accuracy disclosure is evidenced.

   ⚑ flag