Lindy vs an AI employee in Slack for agencies

What the split actually is

Lindy is a Slack-native AI teammate billed per seat that connects to thousands of tools and waits for approval on outside impact, with Always allow. An AI employee in Slack for an agency is a hire in the existing client channel that drafts replies a person still sends, keeps follow-ups after downtime, and writes a correction as a rule.

Agencies run the second job in Slack Connect channels shared with a client. Slack has no native owner on a thread, so a 9pm ask can sit while three people each assume someone else replied. People in that channel can see messages from bots and apps. Shared channels sit on paid Slack plans on both sides. The Free plan only allows one-to-one external DMs. Pro is $7.25 per user per month billed annually, or $8.75 billed monthly, as of 9 October 2026.

Lindy occupies the teammate that executes across apps. The buying prompt collapses that with a send-gate hire in the client channel. Those are neighboring jobs. Priced options for client Slack live on the AI tools roundup. The send gate itself is on the approval-before-send page.

Which job each one wins

Each row names the job, the product that wins it, and why. Lindy still wins the rows it actually wins.

What Lindy is, from its own pages

Lindy is an AI teammate that lives in Slack. An admin adds it to the workspace. Each person then links their account. In channels, the team shares one Lindy summoned with an @mention. In DMs, each person gets a private assistant for inbox, meetings, and scheduling. Setup docs say it works with any Slack plan, including Free.

The pricing page lists Plus at $29.99 per user per month for 3,000 credits, Pro at $99.99 for 15,000, and Max at $199.99 for 35,000. A new workspace starts with $50 in free credits for 7 days, no card. Anyone who uses Lindy takes a seat, including an @mention in Slack after a 7-day trial. Direct signups are billed right away. Credits pool across the workspace and do not roll over. Admins can top up at $10 per 1,000 credits, or turn on overages at 2x. If the pool runs out, Lindy pauses credit-using actions.

Anything with outside impact waits for approval: sending an email, updating a ticket, posting to another channel, publishing a doc. Read-only lookups do not. Each integration then has one guardrail: Always allow, Require approval, or Don't offer. Guardrails apply in shared Slack threads only. The web app, Slack DMs, iMessage, and SMS are not guarded. When Lindy needs approval in a thread it posts Approve and Deny. Always allow changes the rule going forward.

Lindy's docs do not mention Slack Connect by name. They describe shared Slack threads versus DMs. In shared channels it keeps answers public-safe: it summarizes rather than pasting private data. Full tools, including email, calendar, SMS, and reminders, stay in DMs. Follow-up nudges cover asks that have not gotten a reply. Routines run on a schedule or a trigger, including email follow-up bumps that land in drafts for review.

What the AI employee job is for an agency

The agency job is not breadth of apps. It is a hire in the channel the client can already see. The owner is still the account manager for most clients. Hiring another account manager often costs more than one client brings in. The failure they name first is an AI that talks to the client unsupervised: one wrong reply can cost the account.

That hire has to mark the 9pm ask as seen, draft a reply a person still sends, keep the promise made on the call, and not repeat a correction. Slack has no native owner on a thread. Channel history hides thread replies unless you open them. A catch-up that reads only top-level messages drops the actual ask. Safety of putting an agent in that channel is on the shared-channel page. Overnight coverage is a different split, on how agencies keep client Slack answered after hours.

Concrete is an AI employee that works in existing Slack channels. Every incoming message gets a receipt mark. Drafts land as Send / Edit / Skip cards, and there is no auto-send mode. Follow-ups survive reboots. Each morning it nudges the owner of every open task or ask. Verdicts become written rules. It starts from a ready-made role, then adapts. It is in design-partner preview. Learning from a rejected draft is a neighboring job, on the corrections page. The later chase of an unanswered client ask is on the follow-up teammate page.

The caveat that should decide the shortlist

The failure mode agencies name first is an AI that talks to the client unsupervised. Operators on Reddit say the same for Slack and email: keep send out of the automation, because a fluent wrong reply in someone's voice borrows their authority. Approve the exact text that will post. A prompt that says ask first is not the same gate.

Lindy's pricing FAQ says anything with outside impact waits for approval. Its integration docs then say guardrails apply in shared Slack threads only, and Always allow turns the gate off for later writes. Approve allows that one action. Always allow changes the rule. Reads are never guarded. DMs, iMessage, and SMS keep their existing confirmation behavior. Lindy's Slack actions include Send Channel Message and Send Direct Message. Put the gate in writing before you install anything in a channel a client can read.

A second caveat is public chase. A reminder or a draft posted in a Slack Connect thread is visible to the client. Keep the nudge off that thread. A third caveat is billing shape. Lindy bills every active user. An @mention in Slack takes a seat after a week. Viktor bills the workspace. Concrete has no public price. Pair a helpdesk when inbound volume needs tickets and SLAs. A ticket logs what the client asked. The employee job is the reply the client is waiting on, and the promise the agency still owes.

What each one costs (October 2026)

Every figure below is from the vendor's own pricing page or docs, read 9 October 2026. Quote-only stays quote-only. Concrete has no public price.

A practical setup for a 3-to-30 person shop

This is the boring version that holds when the owner is still the account manager for most clients. Pin it in the internal channel, not after the first unsupervised reply.

• Name the job. Work across apps is Lindy. Tickets and SLAs are a helpdesk. A send-gate hire in the client channel is a different product. Fund the leak you actually have.
• Name the gate. Send is a tap on the exact text. Edit rewrites it. Skip drops it. Always allow, Auto, or a prompt that says ask first is a different setup.
• Keep client-facing send on the gate. Lookups, summaries, and internal notes can run. Anything the client will see waits. If the vendor offers Always allow, leave it off on the send action in Slack Connect.
• Keep drafts off the shared thread. People in a Slack Connect channel can see bot messages. A public chase shows the client you are chasing your own team.
• Watch the seat math. Lindy bills every person who @mentions it after a 7-day Slack trial. A shared client channel with six people in it is six seats if they all talk to the bot.
• Sweep threads in the morning. Channel history hides thread replies unless you open them. A catch-up that reads only top-level messages drops the actual ask.