Slack reminder bots: Slackbot, workflows, and when you need another bot

Most people searching for a Slack reminder bot already have one. Slackbot handles personal and channel reminders, and it does that job well. The trouble starts when you want something it was never built for: a standup that collects answers, or a nudge that only arrives if nobody replied. This guide covers what Slackbot can do, where it stops, and which kind of bot picks up from there. For the full /remind reference, see our guide to Slack reminders.

Slackbot is the reminder bot you already have

Every Slack workspace comes with Slackbot, and reminders are its most useful trick. You can set one in three ways.

The quickest is on a message. Hover over it, open the three dots menu and choose Remind me about this, then pick a time. Slackbot brings the message back when it is due.

The most flexible is the /remind command. Slack documents the format as /remind [#channel] [what] [when], with me in place of the channel for a reminder to yourself:

/remind me to send the renewal quote tomorrow at 10am/remind #team-support to check the overnight queue every weekday at 9am

You can also simply ask. Slack's help center notes that you can ask Slackbot to create reminders for you. That is handy when you would rather describe the reminder in plain words than remember the syntax.

What Slackbot reminders can't do

Slackbot reminders are deliberately simple, and four limits come up again and again.

First, they repeat by the day, not by the hour. Slack is explicit that reminders can repeat every Monday but not every hour, so anything more frequent needs another tool.

Second, they go to you or to a channel, not straight to a colleague. The documented format takes yourself or a channel. To nudge a person, post a channel reminder that mentions them. For a group, use a user group, which notifies every member at once.

Third, they are plain text. A channel reminder posts its description to the channel at the time you chose, with no formatting, buttons or form.

Fourth, and most important, they cannot see what happened. A reminder fires on schedule whether or not the thing it was about is already done. It has no idea whether anyone answered your question, whether the update was posted, or whether the customer got a reply.

Match the job to the bot

Most reminder problems fall into a handful of jobs. Some are covered by Slack itself, and some need an app.

The pattern is simple. If the reminder depends only on the clock, Slack's own tools almost always cover it. If it depends on what people did or did not do, you need something that can watch the conversation.

Scheduled workflows: a no-code reminder bot

When a channel reminder is too plain, a scheduled workflow is the next step, and it is included with paid Slack plans. Slack's own help describes scheduling recurring messages in a channel to send reminders, run daily stand-ups or keep project updates organized.

A workflow can post a formatted message, add a button, and open a short form when someone clicks it. It can also be edited later, which a channel reminder cannot. That makes it the better choice for a weekly metrics prompt or a Friday checklist that several people rely on. Our guide to Slack Workflow Builder includes a weekly prompt you can copy step by step.

Standup and check-in bots

If your recurring prompt is really a standup, a dedicated standup bot may be worth it. These apps ask each person a few questions on a schedule, collect the answers, and post a tidy summary.

Geekbot runs asynchronous standups inside Slack and Teams, and its pricing page says you pay per person each month, not per standup. Standuply automates team processes through surveys in Slack and Teams, and connects to task trackers. Both are a step up from a reminder when you want the answers in one place and a record over time.

For a small team, try a scheduled workflow first. A reminder that says "post your update in the thread" plus a habit of replying gets you most of the way, for free. Move to a standup bot when the summaries and history start to matter.

Follow-up bots for questions nobody answered

The hardest reminder to set is the one that should only fire if something did not happen. You ask a colleague a question on Tuesday and want a nudge on Thursday, but only if they have not replied. A time-based reminder cannot do that. It either fires anyway, which is annoying when they already answered, or you forget to set it.

The reminders people actually need often depend on whether someone replied, and Slackbot cannot see that. A follow-up bot watches for replies instead of the clock. Follow Up Bot works this way. When you ask a colleague something with an @mention and they have not answered in time, it privately asks whether you want to send a reminder. Every plan follows up on questions between colleagues, and the smallest plan is $118 a year, billed annually.

If your follow-ups are about tasks rather than messages, a task manager with Slack notifications may suit you better. The right tool depends on where the work you are chasing actually lives.

Reminders in channels you share with customers

Shared channels add a twist. Reminders still work there, but think about who will see them. A channel reminder posts for everyone in the channel, customers included, so a prompt like "chase Northwind about the overdue invoice" belongs in your internal channel, never the shared one.

The more common need in a customer channel is the reverse: knowing when a customer is waiting on you. A reminder cannot help, because you do not know in advance which message will need a nudge. That is a job for an alert that watches the shared channel and tells your team when a customer message has gone unanswered for too long. Our playbook on Slack for customer service covers response targets and coverage for exactly this situation.

Should you build your own?

Building a reminder bot with Slack's developer tools is possible, and some teams do it for unusual schedules or reminders driven by their own systems. It is rarely worth it for ordinary reminders. You take on hosting, permissions, and fixing it when Slack's platform changes, all for something Slackbot or an existing app already does.

Build your own only when the reminder depends on facts that live in your own systems, such as an invoice that is overdue in your billing tool. Even then, a no-code automation tool that posts to Slack is often enough.

Here is the kind of case where custom code earns its keep. A finance team wants a reminder in #finance when an invoice is ten days overdue, naming the customer and the amount. Slack cannot know any of that, but a small script that checks the billing system each morning and posts a message can. If your reminder needs facts from another system, build or automate. If it only needs a time, use what Slack already has.

When you are choosing, start from the job, not the tool. A reminder about a time belongs to Slackbot. A recurring prompt that collects answers belongs to a workflow or a standup bot. A nudge that depends on a reply belongs to a follow-up bot. Get that match right and you will need far fewer reminders, because the ones you keep will actually get acted on.

For more ready-made wording, see our Slack reminder examples, and for reminders that repeat on a schedule, our guide to recurring reminders in Slack. Everything else about Slackbot's reminders is in the main Slack reminders guide.

Questions people ask