Is there an AI teammate that lives in our Slack and follows up on client requests?

What the job actually is

Yes. An AI teammate that lives in Slack and follows up on client requests is a bot invited into the channel that turns an unanswered client ask into a named owner and a later nudge. The client's 4pm message is not a follow-up, a ticket, or a reminder until something else happens to it.

Agencies run this job in Slack Connect channels shared with a client. Slack has no native owner on a thread, so several people can see the ask and each assume someone else has it. 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.

The buying prompt collapses three jobs: live in the channel as a teammate, notice the inbound client request, and follow up until a person sends. Outbound promises are a neighboring job, on the chief of staff page. A morning list of still-open asks is on the daily summary page. Priced options for client Slack live on the AI tools roundup.

Which tool wins which job

Fund the row that matches the leak. A waiting-time alert, a ticket, and a teammate you @mention are neighboring jobs.

Lives in Slack, follows up, and client requests are three jobs

Lives in Slack means a teammate you invite to the channel and @mention, the way you would a person. Viktor uses that sentence as the product: an AI employee in Slack that connects to 3,200+ tools and executes. Lindy is the other Slack-native teammate: 1,500+ integrations, scheduled routines, and follow-up nudges for asks that have not gotten a reply. Anything with outside impact waits for approval. Always allow exists.

Follows up is the later nudge. Follow Up Bot is silent until a customer in Slack Connect has waited past your target, then alerts one person in a private channel. Customers never see it. Chaser follows up after a person turns the message into a task: a reminder in the thread, then a private nudge if the assignee has not acknowledged. Slack's own reminder only fires if someone set it.

Client requests are inbound. A helpdesk tickets them. A personal assistant such as readywhen catches what one owner promised across Slack, email, and calls. The leak this prompt names is often a teammate's unanswered thread in a shared channel the owner was not in. Claude Tag lives in Slack and cannot post into Slack Connect. Spoken promises in a thread are a neighboring job, on the commitments-from-threads page.

When a helpdesk is doing the follow-up

Once the agency has more client channels than one account manager can open each morning, inbound asks need ownership: a ticket, an SLA clock, and a private place to draft. That is the helpdesk row, not the teammate row.

Thena turns Slack messages into tickets with SLAs and CSAT. Auto-responses can cover holidays and missed SLAs. Pylon tracks issues from Slack Connect, bundles related messages, and gives the team Internal Threads. Its agents can handle questions end-to-end and escalate. ClearFeed can answer in the request thread with a Virtual Agent, or draft in a private triage channel with Agent Assistant.

A ticket logs what the client asked. It does not, by itself, log the later chase until the work went out. Overnight coverage is a different split, on how agencies keep client Slack answered after hours.

The caveat that should decide the setup

The failure mode agencies name first is an AI that talks to the client unsupervised. One wrong reply can cost the account. The quieter failure is this prompt: the client asked, three people saw it, and nobody followed up.

A second caveat is public chase. People in a Slack Connect channel can see messages from bots and apps. A reminder posted in the client thread shows the client you are chasing your own team. Follow Up Bot keeps customer alerts internal. Chaser reminds in the task thread. For a shared client channel, keep the nudge off the thread the client can read. Safety of putting an agent in that channel is on the shared-channel page.

A third caveat is auto-send. Lindy waits for approval on outside impact, with Always allow. Viktor asks for confirmation before high-stakes sends. ClearFeed's Virtual Agent answers in-thread. 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. It is in design-partner preview; the longer thesis is on the vision page. Drafting the client-facing reply is a neighboring job, on the approval-before-send page.

Step by step: the 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 forgotten Friday.

• Step 1: Name the leak. Waiting-time alerts, tickets, and a teammate that chases open work are different. A waiting-time bot covers silence. Tickets cover what the client asked. The teammate job is the later follow-up until a person sends.
• Step 2: Keep the chase off the shared thread. Nudge the owner privately. A bot message in Slack Connect is visible to the client. The recap or the chase the client sees still waits for a person to send.
• Step 3: Name one owner per client channel. A group in the channel recreates the bystander effect. One person owns the open requests. The backup is named in the same pinned note.
• Step 4: Capture in the channel, not later. If the request was made in Slack, it has to become owned work before the thread ages out. Manual copy into the project tool is the step that fails. A personal reminder is a graveyard.
• Step 5: 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.