2026-07-14 our lane
Otter meeting knowledge now searchable in Glean — its meeting memory feeds another enterprise AI
Why it matters to us: Otter keeps making its meeting record the memory that OTHER AIs read. Its transcripts, notes, decisions and action items are now searchable inside Glean, the enterprise work assistant. So a rep or PM asks Glean, and Otter's meeting history answers — no Otter app needed. Same land-grab as Otter→OpenAI Codex and Read AI→Claude: be the context layer other agents build on. We defend on the goal kept across meetings, with decision provenance and a human approval gate — not just searchable recall.
Otter (own blog, 14 Jul 2026) became a native connector in Glean, part of Glean's 14 Jul sales-connector expansion (Glean press / BusinessWire). Once connected, Glean indexes Otter transcripts, AI notes, action items and key decisions, so users can ask Glean what a customer committed to during onboarding, or find open action items from past planning calls, without opening Otter.
Otter.ai blog ↗Our move
Say: Otter makes your meetings searchable inside Glean; Collabix keeps the goal moving across meetings — its decisions, risks and the approved next step — not just recall you can query.
Ship: Show one goal advancing across four meetings with a decision trail and a human approval gate, next to a Glean search that returns past meeting notes.
Sell: 'We'll just search our meetings in Glean' → search finds what was said; we carry the goal to done and only act once a human approves.
2026-07-08 our lane
Otter joins OpenAI Codex role-specific plugins — meeting context now completes whole workflows
Why it matters to us: Otter keeps growing as the context layer other AIs build on. Its meeting data now feeds OpenAI's Codex 'role-specific plugins', so an agent uses your conversations to finish a whole task — a meeting-prep pack of summaries, follow-ups, reports and plans — not just answer one question. It is still recall plus auto-actions. We defend on the goal kept across meetings, with decision provenance and a human approval gate.
Otter (own X/LinkedIn post, 8 Jul 2026) said it is part of OpenAI's new role-specific plugins in Codex: 'instead of using your meeting data to answer a single question, Codex uses trusted conversation context to complete an entire workflow.' Example: ask 'How should I get ready for my meeting tomorrow?' and get a prep package with summaries, follow-ups, reports, plans and analysis. Extends Otter's MCP / Conversational Knowledge Engine into OpenAI's agent surface.
Otter.ai (X) ↗Our move
Say: Otter feeds your meeting talk into agents that draft the next task; Collabix keeps the goal moving across meetings — its decisions, risks and the approved next step — not a one-shot workflow built from one call's context.
Ship: Demo one goal advancing across four meetings with a decision trail and a human approval gate, next to an agent that spins a prep pack from recall.
Sell: 'We'll just pull meetings into Codex or ChatGPT' → that is context for a one-off task; we drive the goal to done and only act once a human approves.
2026-04-28 our lane
Otter launches the ‘Conversational Knowledge Engine’ — auto-updates Salesforce/Gmail/Jira after a call + runs as an MCP server
Why it matters to us: This is cross-stack EXECUTION + a memory/context layer — our exact territory. Otter now does meeting→auto-update-Salesforce/Gmail/Jira AND exposes meetings to Claude/ChatGPT via MCP. We defend on the GOAL kept across meetings with decision provenance and a human approval gate (Otter auto-acts).
Otter.ai (28 Apr 2026, +CEO manifesto pushed on LinkedIn ~Jul) reframes itself from notetaker to a ‘system of record for meetings’: the moment a call ends it can update Salesforce, draft the Gmail follow-up and drop action items into Jira with no babysitting; runs as an MCP server so Claude/ChatGPT use meeting history as live context. Claims a new $100B+ category; 35M users, a billion meetings.
TechCrunch ↗Our move
Say: Otter turns meetings into a searchable knowledge base and fires off tasks; Collabix keeps the goal moving across meetings — its decisions, risks and the approved next step — not a pile of auto-actions.
Ship: Show one goal advancing across four meetings with provenance + a human approval gate, vs an auto-updated CRM record.
Sell: For ‘system of record for meetings’ buyers: recall + auto-actions isn’t a goal that knows its own history and only acts once a human approves.