Slack reminders for teams: what /remind cannot do and how to run recurring checks

If you set a Slack reminder for a channel every Thursday and assume the chase is handled, you have automated the nudge and none of the follow-through. The message posts, it scrolls away under the day's other traffic, and you are still the person who notices who did not reply. Below are the exact /remind formats, the limits that matter for a small firm, and a way to run a recurring check that has an owner, a reply count and a record of what happened.

It is written for the founder, owner or operations generalist who chases timesheets, invoices and client updates by hand and is starting to wonder whether this is a job for a new hire.

The short answer

1. Use /remind for what it is good at: a personal nudge, or a plain channel message on a fixed day.
2. Do not use it as the owner of a check. It has no owner, no completion state and no history.
3. When the check needs an answer, put the question, the person who answers for it and the follow-up in one scheduled job, and read the replies after every run.

How to set a Slack reminder for yourself or a channel

The format in Slack's help page on setting a reminder is /remind [#channel] [what] [when]. Slack's own example is /remind #marketing-team to submit expenses every Thursday. Type /remind, send the message, and Slack schedules it.

The details that decide whether your reminder behaves:

• Repeats are by day, not by interval. Slack says you can repeat a reminder "by the day (ex., every Monday)" but not "in time increments (ex., every hour)". There is no hourly nudge.
• The time defaults to 9 a.m. A reminder set for a specific day, such as "tomorrow" or "every Tuesday", arrives at 9 a.m. in your time zone unless you change your default reminder time under Preferences. If you want 3 pm, say the time in the command.
• Date formats matter. Slack recommends American English date and time wording, so write "every Thursday at 3pm" rather than a local shorthand.
• Guests cannot create channel reminders. A contractor or client who is a guest in your workspace cannot set one and has to ask a full member.
• A channel reminder cannot be edited. To change it, type /remind list in the channel where it posts, delete it, and create it again.

Thena's recurring reminders guide repeats the same limits: recurring reminders for yourself or a channel, no hourly repeats. It is a vendor page, so treat it as a second reading of Slack's documentation, not independent proof.

What /remind cannot do

/remind was built for one person's memory, so a recurring chase asks more of it than it was designed to give.

It has no owner. A channel reminder posts a message into the channel. Nobody is assigned to answer it. Siit's analysis of Slack reminders puts it this way: reminders "carry no owner, no queue, and no history", and a reminder "only ever notifies one person", so if that person is out, nobody picks it up. Siit sells a service-desk product, so weigh the conclusion accordingly, but the three missing things are exactly what Slack's help page also leaves out.

It records no completion. Slack's help page describes how to create, list and delete a channel reminder. It describes no way to mark a channel reminder as answered, or to see who responded. Chaser's guide draws the same line for assigned work: for team work, record who has accepted the request and whether it is complete. Chaser is also a vendor.

It cannot be set for other people through Slack's API. Slack's reminders.add reference says the user argument is "No longer supported - reminders cannot be set for other users", and lists cannot_add_others_recurring: "Recurring reminders can't be set for other team members." That is the official statement for the API. Slack's help page is silent on whether typing /remind @person still works in the message box, so do not assume either answer. Test it once in your own workspace before you build a process on it.

It does not tell you when it has stopped. If someone deletes the channel reminder, or recreates it with different wording, nothing marks the change. You find out when the Thursday message does not appear, and only if you notice the absence.

Practitioners describe the human cost. On Hacker News, one commenter describes a "probably janky habit" of creating reminders and rolling them over by hand by three hours, the next day or next Monday. Another reports that several "remind me tomorrow" reminders fire together at 9 am, each with its own pop-up and sound. Both are single-user reports, not measurements, but they match what the documentation implies: a reminder is a prompt for you, and you stay the engine.

Where Slack itself says /remind stops

The same Slack help page says it before it gives the format: channel reminders "work best for simple team reminders", and for "more complex messages", Slack recommends creating a workflow with the scheduled message template or creating a Slackbot task.

Slack's own help page presents channel reminders as the tool for simple team nudges and points anything more complex to a scheduled workflow or a Slackbot task, so a recurring chase that needs an answer has already outgrown /remind by Slack's own description. If your Thursday message asks people to do something and you then check who did, it is no longer a simple reminder.

Choosing the tool for a recurring check

Slack says workflows "built to start on a schedule will start automatically", so a Thursday post or form is a real step up. It collects structure. It does not, by itself, tell you on Friday morning who has not answered. That is the reading job, and it is the job a coordinator is hired for.

Pick the row by one question: after the message goes out, who finds out that someone did not answer? If the answer is "me, eventually", you are using a reminder where you need a check.

Anatomy of a recurring check someone answers for

A reminder says "do this". A check asks a question, expects an answer from a named person by a stated time, and does something when the answer does not come. Define five parts before you schedule anything:

1. The question. One question that can be answered in one line: "Is your timesheet for this week submitted? Reply yes, or give the blocker."
2. The owner. One person who answers for the check running, usually you, plus one named backup.
3. The audience. Who is asked, written down as a list of people, not "the team".
4. The deadline. When replies are due, in the channel's time zone, such as Friday 10 am.
5. The follow-up. What happens at the deadline: a summary of who replied and who did not, and who contacts the people who did not.

Because a channel reminder can only be deleted and recreated, never edited, whoever rewrites the wording can also end the check without anyone noticing, so the owner and the schedule of every recurring check should be written down somewhere other than the reminder itself. This is a recommendation, not a Slack rule: keep a short list, in a pinned message or a shared page, with one line per check giving its owner, schedule, audience and deadline. When Slack forces you to delete and recreate, update that line the same minute. Review the list monthly.

A worked example

This is a made-up illustration, not a customer story. A 12-person design agency wants timesheets in by Friday at noon. The operations lead, call her Dana, currently sets /remind #design to submit timesheets every Thursday and then scrolls the channel on Friday to see who replied.

The failure is visible in the setup. The reminder posts at 9 a.m. by default, not at the hour Dana intended. It names the channel, not a person. Two freelancers are guests, and guests cannot create channel reminders, so they could never take over the chase. Dana cannot see replies without reading the thread, and on the Friday she is at a client site, nobody does.

Rewritten as a check:

• Question: "Reply in this thread: timesheet submitted, or the blocker."
• Owner and backup: Dana, with the studio manager as backup.
• Audience: the ten full members, listed by name; the two guests are asked by Dana directly once a week, since guests cannot create channel reminders and the process should not depend on what they can see.
• Deadline: Friday 10 am.
• Follow-up: at 10 am Friday, a summary of who replied, who did not, and any blockers named.

That specification can run as a scheduled workflow plus a person reading the replies, or as a single scheduled job with an agent. The next section covers the second option.

Running the check with the Kipwise agent

If you already use Slack for the team's conversation, a scheduled request to the Kipwise agent can carry the whole specification. Per the product description, you mention the agent in a thread or channel and ask in plain language for a request to run later or on a schedule. It uses your Slack timezone when available and posts the result in the channel, with the same tools and permissions as a live request from you.

A request might read: "Every Thursday at 3 pm, post in this channel asking each person on this list to reply with their timesheet status by Friday 10 am. On Friday at 10:15, summarise who replied and who did not." Ask for the reply summary in the request itself, and read the first few Friday summaries against the thread by eye before you trust them.

How it behaves, as the product works today:

• Approval once. Creating a scheduled task needs your approval once, together with the list of changes the task may make on its own. Later runs do not ask again for those. Any other change, such as a write to a connected tool, still shows a fresh Approve or Deny card, and the card expires after 30 minutes.
• Visible lifecycle. You can list or cancel your jobs and ask what happened on previous runs, including failures. That answers the "did the check silently stop" problem that a deleted channel reminder leaves open.
• Your permissions. The job runs with the same tools and permissions as a request from you, so a check that reads a connected tool reads only what you can read.

What stays with a person: judgment calls, escalations and customer conversations. A scheduled message can ask who owes a timesheet. It cannot decide whether a late timesheet is a payroll problem. The decision to hire a coordinator for relationship-heavy chasing is still a human decision; the before-you-hire page for virtual assistants lays out how to weigh it.

On price: the agent costs $10 per user per month with a 3-user minimum. Installing starts a trial of $2 for 7 days on the fast model; a saved card or a paid Slack plan gives a $10, 14-day trial with all models. Check the live pricing page before you plan around those figures.

Handle failure and edge cases

A recurring check fails in a handful of predictable ways. Decide the response for each before it happens.

• Nobody replies. Zero replies is a warning sign. The summary should say "no replies", and your backup should check whether the post reached the channel.
• The channel is archived or renamed. After any channel archive or rename, confirm the next run posted where you expect it, and ask the agent about its previous runs.
• Someone is on leave. Add a line to the specification: people on leave are excluded by name for that week, and the exclusion is dated.
• The job was cancelled by accident. List your jobs monthly against the written list described above. The listing is the audit.

For deeper treatment of scheduled-job failure modes, see scheduling recurring AI agent jobs in Slack without silent failures. For tracking open items that outlive one run, see keeping follow-ups from falling through the cracks in Slack, and for turning replies into a status roll-up, see getting team status updates in Slack without an ops coordinator.

Verify it works

Run the check for four weeks as a pilot and track one number: a recurring check is finished when someone answers it, so the number to track is replies received per run, not reminders sent. Write down, per run, the number asked, the number who replied by the deadline, and the number you had to chase by hand.

A simple pass mark, offered as a recommendation and not a benchmark: by week four, the share you chase by hand should be falling, and the Friday summary should save you the thread scroll. If the number you chase by hand is not falling, the question or the audience needs rework. If you cannot find the summary, the delivery is failing, so ask the agent about the previous runs.

Keep a short checklist:

1. The written list has an owner, schedule, audience and deadline for this check.
2. The first three runs posted at the intended time in the intended zone.
3. The summary matched the thread when you compared them.
4. You know how to list and cancel the job.
5. A person, not the scheduler, handles every escalation.

What to do next

Pick the one recurring chase you currently do by hand, write its five parts (question, owner, audience, deadline, follow-up) in a pinned message, and run it for two weeks. If you already use the Kipwise agent, mention it in that channel and ask for the first scheduled run with the summary built in, as in the example above. If you do not use it yet, the same five-part specification works for a Workflow Builder post with you reading the replies, which tells you honestly how much of the chase is the nudge and how much is the reading.

The other /remind neighbours are in Kipwise's list of Slack slash commands.

References

• Slack help: Set a reminder: the /remind formats, daily-based repeats, 9 a.m. default, guests, no edit, /remind list, and the pointer to scheduled workflows and Slackbot tasks for complex messages.
• Slack API: reminders.add: reminders cannot be set for other users via the API; recurring reminders cannot be set for other team members.
• Slack help: Guide to Workflow Builder: Workflow Builder is available on paid plans; scheduled workflows start automatically.
• Siit: Slack reminders, how to set, manage, fix and outgrow them: reminders carry no owner, queue or history (vendor with an interest).
• Chaser: How to set Slack reminders and follow up on team tasks: record acceptance and completion for assigned work (vendor).
• Thena: Slack recurring reminders: reminders for yourself or a channel, no hourly repeat (vendor).
• Hacker News comment 39834011: author report of rolling reminders over by hand.
• Hacker News comment 46824386: author report of stacked reminder notifications at 9 am.
• Kipwise: 25+ Slack slash commands: the full slash command list.
• Kipwise: Keep follow-ups from falling through the cracks in Slack: open-loop registry and ownership.
• Kipwise: Schedule Slack AI agent jobs without silent failures: scheduled-job failure modes.
• Kipwise: Get team status updates in Slack without an ops coordinator: status digests.
• Kipwise: Build a thread-native AI agent for Slack: thread-native agent design.
• Kipwise: Before you hire a virtual assistant: hire-versus-Slack decision.