Slack and AI agents

Slack is where decisions get made and where they get lost. An agent sits in the channels you choose, pulls out the part of a thread that became a commitment, and holds the answers to the questions people ask every week.

What an agent does in Slack

  • Reads the channels you assign it to, and none of the others.
  • Turns an agreement in a thread into a task with an owner and a date.
  • Answers repeat questions from the source, not from memory.
  • Brings in what happened elsewhere: a payment, a new lead, a process that failed.
  • Assembles the week and posts it where you'll actually see it.

Processes that run themselves

A playbook isn't a button — it's a process with a condition that starts it. These three get set up most often.

An agreement becomes a task

Someone in a channel says «let's do it» and names an owner

  1. Work out that this is a decision, not a discussion
  2. Assemble the task: what, who, by when
  3. Ask in the thread if no date was given
  4. Hand it to you for confirmation before it's created

A question that keeps coming back

Someone asks a question that has been answered before

  1. Find the previous answer and check it hasn't gone stale
  2. Reply in thread, citing where it came from
  3. Flag it as a recurring question once it surfaces a third time

The week, summarised

Friday, end of the working week

  1. Collect the decisions and tasks from the week
  2. Mark what has stalled with no movement
  3. Post the summary to the channel as a single message

Where the agent stops

  • It posts in the channels you opened and never in direct messages.
  • It doesn't decide for the team: a contested agreement comes to you rather than being interpreted.
  • It won't answer from memory — if it can't find the source, it says so.
  • A task is created after you confirm it, because the cost of getting this wrong is someone else's day.
Connect SlackSetup is a conversation, 15–30 minutes

FAQ

Will the agent read all of our company's messages?

Only the channels you open to it. We don't request direct messages: the app holds no permission for them, and you can see that in the list of scopes when you install it. You can change the channel list at any point.

Will it post in channels by itself?

Yes, in the ones where you've allowed it. Creating tasks and anything that claims someone else's time goes to you first; the message only goes out after that.

What if it misreads an agreement?

That's exactly why the task isn't created silently. You see what it assembled before the assignee does, and anything ambiguous is flagged rather than decided for you.

Do we need a Slack admin to set this up?

For workspace channels, yes — an admin installs the app. After that the setup is a conversation, with no tokens or scopes to wire up by hand.

Where this shows up

Walkthroughs where Slack carries part of the process.