What is a Slack bot that tracks commitments and follow-ups from threads?

What the job actually is

A Slack bot that tracks commitments and follow-ups from threads turns a spoken line in a thread into a named owner and a follow-up that still fires. The phrase I'll send that over tomorrow is not a reminder, a task, or a ticket 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 hear the line and each assume someone else will do 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: detect the commitment, keep a list of it, and follow up until it is done. The agency-owner version of the same leak is on the chief of staff 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 list, a flagged task, and an unanswered wait are neighboring jobs.

Detection, a list, and a follow-up are three jobs

Detection is spotting I'll handle it in the thread. Recal does that when someone runs /recal, or uses a message shortcut, and only on the messages in that request. Its Slack page says it never reads private DMs or stores full message history, and the recap is shown only to the person who ran the command. An always-on scan of every channel is a different product, and a different privacy bargain.

A list is the extracted owners and deadlines. Recal can export those action items to Linear or Notion. That list still has to be read. It is not a reminder that still fires on Friday.

Follow-up is the later nudge. Chaser sends a reminder in the Slack thread when a task is due, and nudges the assignee privately if they have not acknowledged it. Slack's own reminder only fires if someone set it. To-dos started rolling out in October 2026 as a personal list; they replace Later, and a to-do created from a message does not get a reminder unless you add one. Conversation summaries on Pro catch you up on a thread. They do not turn a spoken promise into a follow-up.

When the follow-up leaves the thread

Copying the line into a project tool is the neighboring job. Asana creates a task from a Slack message, with an assignee and a due date, in Asana. That is the right move when the project already lives there. It is also the extra step teams skip when the conversation is the only record.

readywhen is the personal version of capture: it reads the owner's connected Slack, Gmail, and calls, then drafts the chase for an OK. The leak this prompt names is often a teammate's line in a shared channel the owner was not in. The chief-of-staff shape of that job is on the chief of staff page.

Once inbound volume needs an owner and an SLA clock, that is the helpdesk row, not the promise row. Overnight coverage is a different split, on how agencies keep client Slack answered after hours. Drafting the client-facing reply is a third job, on the approval-before-send page.

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 promise was made in a thread, three people heard it, and it never became a task.

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.

A third caveat is auto-detection. I'll handle it is not always a task. Letting a model decide which client threads still need a follow-up is a poor fit: the model often lacks the account context, and a wrong guess in client work costs more than no guess. Recal extracts when you ask. Chaser tracks after a person flags the message. readywhen waits for your OK. 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. It is in design-partner preview; the longer thesis is on the vision 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 forgotten Friday.

• Name the leak. Inbound asks, unanswered waits, and outbound promises are different. Tickets cover what the client asked. A waiting-time bot covers silence. The thread job covers what the team said they would do.
• Capture in the thread, not later. If the promise was made in Slack, it has to become an owned follow-up before the thread ages out. Manual copy into the project tool is the step that fails. A personal Later list is a graveyard.
• Keep client-facing 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 promises. The backup is named in the same pinned note.
• 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 promise.