What is an AI employee for a marketing agency that works in Slack?

What the job actually is

An AI employee for a marketing agency that works in Slack is a hire invited into the channels where client work already happens. It turns a client ask or a spoken promise into owned work, follows up until someone sends, and drafts replies a person still has to approve.

Agencies run that 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.

The buying prompt collapses several jobs into one slogan. Catch-up, ticketing, work across ads tools, and a send-gate hire in the client channel 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 tool wins which job

Fund the row that matches the leak. An ads audit, a ticket, and a draft a person still sends are neighboring jobs.

Employee, assistant, and helpdesk are three jobs

Employee, in this buying prompt, means a hire 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.

Assistant is catch-up. Conversation summaries ship with Pro. Slackbot, Slack's personal AI agent, ships with Business+ and Enterprise+; Business+ caps Slackbot at 15 messages per member per week. Claude Tag is Claude in the channel you tagged it in. It does not work in Slack Connect, and no admin setting turns it on. If a working channel becomes Slack Connect, Claude stops answering, including in threads it was already in.

Helpdesk is ownership of the inbound ask. Thena turns Slack messages into tickets with SLAs and CSAT. Pylon tracks issues from Slack Connect, bundles related messages, and gives the team Internal Threads. 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. Shops already comparing Lindy to that hire have the split on Lindy vs an AI employee in Slack. Shops already on Viktor have a priced set of swaps on Viktor alternatives for an agency.

What a marketing agency actually hires it to do

A 3-to-30 person shop usually still has the owner as the account manager for most clients. The expensive leak is the client channel, not another dashboard. Name the workflow before you install a bot in Slack Connect.

• Keep the shared client channel from going silent. A 9pm ask that three people saw and nobody owned is how clients open the next call with 'we messaged you three days ago.' The hire's job is a named owner and a later nudge, still off the thread the client can read. Missing messages in Slack Connect is on how agencies stop missing client messages.
• Run ads and reporting from the channel the team already uses. Viktor's own Slack page uses this as the demo: audit Meta Ads and Google Ads from one message, then pause what is wasting spend. That is the execution row. It is a different job from drafting the client-facing recap of those numbers.
• Catch 'I'll send that over tomorrow'. The line is said in a Slack Connect thread, or on a call that never becomes a task. Slack has no native owner on that thread. The neighboring job is on the chief of staff page.
• Draft the client-facing reply, then wait. Overnight coverage is a receipt plus a named owner plus a real reply a person still sends. Most shops of this size auto-acknowledge and catch up in the morning. That split is on how agencies keep client Slack answered after hours.

The caveat that should decide the hire

The failure mode agencies name first is an AI that talks to the client unsupervised. One wrong reply can cost the account. Put that gate in writing before you install anything in a Slack Connect channel. How to run an agent in a shared client channel is on using an AI agent in a Slack channel shared with a client.

A second caveat is the slogan. Employee is a hire with a named job and a send gate. An assistant you tag, a ticket queue, and a teammate that executes across ads tools are real products. They are neighboring jobs. A bot that auto-sends in the client channel is a different product from all of them.

Claude Tag is off the shortlist for that channel: Anthropic's docs say it does not work in Slack Connect. Lindy waits for approval on outside impact, with Always allow on each connected account. Viktor is review-first on sensitive sends such as external email, and that gate can be loosened per task. 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. Verdicts become written rules. It starts from a ready-made role such as Growth or Customer Success, then adapts. It is in design-partner preview; the longer thesis is on the vision page. Learning from those verdicts is a neighboring job, on the corrections page.

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. Ads execution, tickets, catch-up, and a send-gate hire are different. A teammate that audits Meta Ads does not own the 9pm client thread. A helpdesk logs the ask. The employee job in the client channel is the later follow-up until a person sends.
• Keep client-facing send on a tap. Lookups, summaries, and internal notes can run. Anything the client will see waits. If the vendor offers Auto or Always allow, leave it off on the send action in Slack Connect.
• 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.
• Name one owner per client channel. A group in the channel recreates the bystander effect. One person owns the open requests and the send button. The backup is named in the same pinned note.
• Pair a helpdesk when volume needs tickets. Tickets give an SLA and a private draft. The teammate in the channel still marks the ask seen and holds the reply. Those are two jobs. The follow-up job is on the AI teammate that follows up on client requests.
• 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.