Productivity - Setup Guide

How to set up Read.ai

Otto's honest, no-fluff walkthrough. Every step here is what we'd actually do if we were sitting at your keyboard. Real gotchas first, real steps second, and a link to the personalized version at the bottom.

Read these before you start

• The bot's persistent, calendar-linked auto-join behavior is THE defining issue with this product, once enabled by one person, it can join their future meetings automatically without notifying or requesting consent from other participants, this has caused real documented incidents of the bot appearing uninvited in sensitive or unrelated meetings, treat this as a hard blocker for any client with confidentiality concerns, not a minor UX quirk (Source: multiple user reports and university IT guidance, via WebSearch summary 2026)
• Review sentiment is unusually and consistently negative specifically because of this behavior, 84% 1-star on Trustpilot with reviewers using words like "virus," this is a strong, convergent signal, not a fringe complaint
• Multiple university IT departments have published explicit deactivation/blocking guidance specifically in response to unwanted Read.ai meeting joins, this level of institutional pushback is a meaningful red flag Otto should weigh heavily
• If recommending this tool at all, it must come with EXPLICIT guidance to the client: enable calendar-linking deliberately per-meeting rather than persistently, and proactively inform all meeting participants before use

The 7-step setup

1. 1

   Create your Read.ai account

   Sign up at the link below. Free tier available - no card required. Use your business email so you can invite teammates later.

   Open Read.ai signup
2. 2

   Complete the initial onboarding

   Skip the marketing questionnaires when you can. Fill only the fields that actually configure the product - name, timezone, your first workspace or project. If Read.ai pushes you into a setup wizard, take it - it usually accelerates the first productive session.

3. 3

   Connect your existing tools

   Wire Read.ai into the rest of your stack. The integrations that most people set up first: Zoom, Google Meet, Teams, Slack, Salesforce.. Do these before importing data - clean integration first, data second.

4. 4

   Import your existing data (only what you'll actually use)

   Do NOT bulk-import everything. Import the last 30 days of the ONE workflow you're moving over first. Prove it works. Then import more. Big-bang migrations are how Read.ai deployments die in month 3.

5. 5

   Set up your first real workflow

   Pick the single most-frequent task you'll do in Read.ai - the daily-driver workflow. Configure it end-to-end. Use it live for a week. Do not touch any other feature yet. Adoption failure comes from teams trying to use everything on day one instead of the one thing that actually pays.

6. 6

   Add your team (if applicable) and set access

   Once your solo workflow works, invite one teammate at a time. Watch them use it. The friction points you missed are the ones they hit. Fix those before scaling to more users. Never invite 20 people at once - you'll get 20 confused people and 0 useful feedback.

7. 7

   Compound with the right pairings

   Recommend Read.ai only with heavy caveats, and lean toward NOT recommending it for most clients given the severity and consistency of the uninvited-bot complaint pattern. If a client specifically wants meeting-engagement coaching analytics, tl;dv or Grain are safer default recommendations without this documented consent problem. If Read.ai is used, Otto must explicitly instruct the client to disable persistent calendar auto-join and notify all meeting participants before every use, this is one o...