Lindy AI Review: A Shared Slack Teammate Billed Per Seat

Lindy (often searched as Lindy AI) is one AI teammate that a whole team shares in Slack, plus a private assistant for each person in their DMs, texts, email, a phone line and Gmail. It does the busy work around the inbox, meetings and calendars well, and by default it asks before doing anything that leaves a mark outside. The bill is per person. Its pricing page starts at $29.99 per user a month for 3,000 credits; on some visits the same page instead opens at $49.99 per user a month for 5,000 credits.^[1] Our verdict is simple. Slack teams that want a careful assistant should try it; teams outside Slack should look elsewhere.

One teammate in the channel, one private assistant per person

Lindy works as two assistants that spend from one shared credit pool. The shared Lindy lives in Slack: an admin installs it, each teammate links with one tap, and anyone can then @mention it in a channel. It answers in the thread, using approved team sources and public channel context, with web search, image generation, public Slack search and Notion as its tools there. The private Lindy sits in each person's DMs and carries the full toolset: calendar, email, SMS, reminders and meeting reads. What you ask in a DM stays private.

The private side reaches people where they already are. Lindy works over iMessage on an iPhone and SMS on any phone, so no app is needed on the phone. It has its own email address, a web app, and a Chrome extension that works inside Gmail only, with Outlook listed as coming soon. Since October 2026, on a paid plan, it can hold a phone line with a US or Canadian area code, though availability may vary by account. It joins Google Meet, Zoom and Microsoft Teams calls as a visible, named notetaker, builds internal Apps and hosted pages, and connects to 3,000+ integrations plus MCP.

The team half depends on Slack. New Slack installations need a paid Slack plan, and Slack is the supported team channel. Teams that do not use Slack get the personal assistant, not the shared teammate. Lindy's docs list Microsoft Teams as coming soon, with no date. A company that runs its chat in Microsoft Teams would therefore pay per seat for a set of private assistants and miss the shared routines, team memory and channel answers that make Lindy distinct. That gap decides many purchases.

Teaching happens in plain English, and approval comes first

Nobody draws a flowchart here. Lindy keeps memory as plain files you can open, edit or delete, with every save kept as a version you can restore. Files are Personal, Team (everyone reads, only owners and admins change) or System. More than 40 built-in skills come ready, and Lindy picks the right one when a request needs it. Routines run on a schedule or an event, such as an email arriving or a meeting ending, and a dry run fires a routine on real data to show what it would have done without sending anything.

Watch and Learn, added in October 2026, takes a screen recording of up to an hour, or written steps, and turns it into a personal skill plus a proposed routine. Recording works in Chrome, Edge or Safari on a computer, and the analysis itself uses credits. The result is a teammate you train the way you would brief a new hire. You show the task once, then ask for it by name or put it on a schedule.

By default, anything with outside impact waits for approval: sending an email, updating a ticket, posting to another channel, publishing a doc. Read-only lookups from approved sources do not wait.^[2] Approvals arrive as Approve and Deny buttons in Slack. Guardrails are set per integration (always allow, require approval, or do not offer), but they apply in shared Slack threads, not in DMs, web chat, iMessage or SMS. Email drafts wait for your approval by default; recurring follow-ups can be switched to send on their own once you trust them. Lindy's own docs also warn that it can make mistakes, so review matters.

The bill: seats times credits, drawn from one pool

Lindy's pricing page groups the three paid plans under one card called Team; the plans themselves are Plus, Pro and Max, with Enterprise above them. Every person who uses Lindy takes a seat, whether they sign up directly, join the workspace, or @mention Lindy in Slack for the first time. Direct signups are billed right away. Teammates who join through Slack get a one-time 7-day trial, and that seat converts to paid unless an admin removes it. New accounts start with $50 in free credits that last 7 days, no card needed; there is no ongoing free plan.

Every seat adds its credits to one workspace balance. Monthly credits reset each cycle and do not roll over, while top-ups at $10 per 1,000 credits never expire. When the pool runs dry, Lindy pauses credit-using work until the reset or a top-up; there is no surprise bill. Admins can cap each teammate's monthly draw. Lindy's docs say every message in a thread re-reads everything above it, so long threads cost more credits with each turn. A task that runs far over its usual draw pauses and asks whether to continue.

How far do credits go? Lindy's pricing page gives ranges: everyday asks such as summaries, lookups and reply drafts run 2 to 250 credits, deep work such as a competitor research report runs 250 to 1,000, and big builds such as a complex dashboard run 1,000 to 2,500. By our arithmetic, Pro and Max credits cost between $5.71 and $7.50 per 1,000, against $10 per 1,000 on the entry options and top-ups. Five people on the entry option come to $149.95 a month with 15,000 pooled credits when the page opens at $29.99 per user a month, or $249.95 a month with 25,000 when it opens at $49.99 per user a month.

Phone calls draw from the same pool, from 25 credits a minute, and the phone-line number carries its own monthly fee. Lindy's pricing page prints only monthly prices; it shows no annual plan. Lindy's Terms state that all purchases are non-refundable, and canceling takes effect at the end of the paid term. A removed seat stays billed through the cycle, with no proration. Our Lindy pricing guide works through every option and the team totals in detail.

Security holds up; HIPAA is an Enterprise decision

Lindy's security page lists SOC 2 Type II, audited by Johanson Group, plus GDPR and PIPEDA, and data is encrypted in transit and at rest. Lindy states it does not sell customer data and that neither it nor its providers train AI models on it. The service is hosted in the United States, so data from other regions is processed there. SOC 2 reports can be requested for a vendor review. These are sound basics for a tool that reads inboxes and calendars.

The plan line matters more for regulated teams. HIPAA-covered work needs Enterprise with a signed BAA; without one, Lindy's Terms say the service is not tailored to HIPAA. SSO, SCIM and audit logs, which record every action Lindy takes for review, are also Enterprise only, so a Pro or Max team signs in without single sign-on. Privacy inside the team is sensible: DMs stay private, and the shared Lindy uses only public sources in channels. Our Lindy buyer's checklist covers the data questions a procurement review will ask.

How we score Lindy, and what users report

Our score weighs what decides a purchase in this category: what the assistant can do across channels, how safely it acts, how predictable the bill is, and how well it fits a team's tools. Lindy scores high on reach and on its approval model, and loses ground on cost predictability and on its dependence on Slack for team use.

That composite lands at 4.0/5, our own read rather than an average of review sites. User sentiment is one input among several, not the verdict. The approval default and the channel reach pull the score up, because they shape daily use more than any single feature. The credit model pulls it down, because a team cannot know its monthly draw before a full month of real work.

Public reviews split along a clear line. Trustpilot complaints describe credit use that felt unpredictable and billing that seemed ambiguous, credits spent while iterating on a design, poor credit value on higher tiers with a wish for an unlimited plan, and updates that caused problems even though support helped. The praise centers on email, calendar and thread tracking, on responsive support, on Lindy Phone, and on meeting summaries and status searches across Slack and Gmail. Read it as a map, not a trend. Credits are the friction; the assistant work earns the praise.

Who should give Lindy a seat, and who should pass

Lindy fits a team that already runs on Slack and drowns in email, meetings and scheduling: founders, executives and their assistants, sales and account teams, and small service businesses that want a phone line answered. Ankor's CEO says he built ten agents in his first week and runs 20 to 30 active ones; that is the customer's figure, not a typical result. The phone line suits inbound calls and errands, but it is not for cold calling. Outbound calls have a daily limit.

Skip it in three cases. If your chat runs on Microsoft Teams, you get private assistants without the shared teammate. If you want many occasional users on one cheap account, every person who touches Lindy is a billed seat, including a first @mention. And if heavy research is the main job, the deep-work band drains a 3,000-credit seat quickly. Computer use starts at Pro. For those cases, our Lindy alternatives compare tools priced and built differently.

Should your Slack team give Lindy a seat?

Yes, if your team lives in Slack and wants an assistant that triages mail, takes meeting notes, books time and answers a phone, while asking before it acts. Start with the $50 in free credits, turn on spend caps per person, and watch how fast the pool drains in the first full month. Move a seat to Pro only when it regularly uses far more than its Plus credits: Pro credits cost less per 1,000, but the seat price is paid whether or not the credits are used. Our score reflects a capable, careful product whose bill takes attention. Teams outside Slack, or those needing HIPAA below Enterprise, should pass.