Everyone's obsessed with "seamless" Slack integration. Let's be real: both will dump a transcript into a channel. That's not integration.
The real question is what happens next. Otter's baked-in workflows assume you want their summary. Read seems to push you toward its own platform for analysis. So which one actually lets you *use* the meeting data *in* Slack without clicking away? I've seen both fail at actionable follow-ups.
Also, check the bot permissions. One of them required near-admin scopes just to post a message. That's a hard no for any sane workspace.
Your vendor is not your friend.
I'm ChrisM, a platform engineer at a ~250 person SaaS shop where we live in Slack and run a mix of Zoom and Google Meet calls. We've had both Read and Otter in production for different teams over the last year.
* **Actionable Data in Slack:** Otter wins here. Its Slack bot can answer questions directly in-thread about the meeting transcript (e.g., "What were the action items?"). Read posts a transcript and a link; to ask questions, you leave Slack for Read's interface. For your "use the data in Slack" test, Otter works.
* **Bot Permission Footprint:** You're right to check. Otter asks for standard `chat:write` and `files:write`. Read required `channels:history`, `groups:history`, and `im:history` scopes at my last shop, which let it read all channel messages, not just its own. That was a non-starter for security and we had to push back.
* **Post-Meeting Workflow:** Otter assumes you stay in its ecosystem for summaries and highlights, but those are delivered back into Slack. Read pushes harder toward its own platform for deeper analysis, like sentiment tracking. If your goal is centralized meeting analytics, Read's path is clearer.
* **Pricing & Tier Fit:** Otter's business plan (~$20/user/month) gets you the Slack Q&A features. Read's equivalent "Read for Teams" tier is roughly $15-20/user/month but often feels aimed at enterprise insights teams. For pure engineering standup/retro integration, Otter's model is simpler.
My pick is Otter if your primary need is asking quick, ad-hoc questions about a meeting directly in a Slack thread without switching context. Go with Read if you have a dedicated person or team synthesizing insights from many meetings into reports, and Slack posting is just the notification layer. To decide cleanly, tell us: who's the main user (individuals vs. a central team), and is this for tactical follow-ups or strategic analysis?
K8s enthusiast