Slack Reminders: How to Set, Manage, Fix, and Outgrow Them

At 9:15 someone needs Figma access, which means checking with their manager, confirming the spend with Finance, provisioning the license, and updating HR's spreadsheet. At 10:30 a new hire starting on Monday needs a laptop that has to clear procurement first. By 2:45 the Figma follow-up is gone, because when you run a service desk in Slack, none of it arrives as a ticket.

Coordination work shows up looking like IT work, and the piece that goes missing is the check-back nobody scheduled. Slack reminders are the cheapest tool you have for that gap.

This covers the five reminder types, the /remind syntax that works, which reminders to set first, how to repair a broken one, and the point where a reminder stops being the right answer.

TL;DR:

• /remind [me or #channel] [what] [when] is the whole command. The first part accepts two values only: yourself, or a channel.
• Slack documents five reminder types, and four of them are private to you. Anything a teammate needs to see has to be a channel reminder.
• Personal and channel reminders differ on one thing that matters. You can push a personal reminder to a new date. A channel reminder can only be deleted and set again.
• Reminders were built for one person's memory, so they carry no owner, no queue, and no history. Once a request needs those three things, an AI Service Desk like Siit holds it in the same Slack channel.

What Are Slack Reminders?

Slack reminders are a built-in feature that schedules a Slackbot notification for you or for a channel at a date and time you set. They can fire once or repeat on a schedule, and they are available on every Slack plan, including Free. For an internal support queue, that means the password reset follow-up, the VPN escalation, or the app-access approval comes back at the right moment instead of settling into scrollback.

Personal reminders collect in the Later tab in your sidebar, where you complete, reschedule, or delete them. There is no setup, no admin step, and no third-party app involved.

Slack documents five reminder types, each starting from a different place in the product. Which one you reach for depends on where the work is already sitting.

Reminder types and examples as documented in Slack's Help Center.

How Do You Set Up Slack Reminders?

Type /remind in any message field. That is the fastest path and the one you will use for almost everything. Slack also offers a form, reached by clicking Later in your sidebar and then the plus sign at the top-right.

The other four methods start the reminder from somewhere you are already looking: a channel, a message, a list, or a canvas date. Pick whichever one is closest to where the request landed, because every extra click is another chance for an access request to slip.

Write the /remind Command

The command follows the same shape every time, /remind [who] [what] [when]. Type /remind and Slack surfaces it in the shortcuts menu, or type the whole thing in one go and send it. Slackbot confirms immediately, so if no confirmation appears, the command did not go through.

• /remind me to follow up on the benefits enrollment email tomorrow at 10 am
• /remind me to review the Q2 expense reports on Friday at 2 pm
• /remind me to check onboarding status in 3 hours

The quotation marks matter more than they look. Without them, Slack can read a number or date inside your message as the delivery time. Slack handles everyday phrasing for dates and times, and recommends the American English date and time format for best results.

One repeat limit is worth committing to memory. Reminders can repeat by day, like every Monday. Slack does not support repeats measured in hours or minutes, so there is no every-hour option and no way to build one from the command.

Set a Channel Reminder

A channel reminder posts a Slackbot message to the whole channel at the scheduled time. Use it for shared deadlines and team rituals where everyone needs the same nudge. Because it posts publicly, check the wording and the channel before you send it.

• /remind #finance-ops to submit expense reports every Friday at 11 am
• /remind #hr-team to review open onboarding tickets every Monday at 9 am
• /remind #it-support to check SLA status every day at 4 pm

Slack's own guidance is to keep channel reminders simple. The message posts once, exactly as typed, with no way to collect a response. Anything more involved is a job for a workflow, covered further down.

Set a Reminder on a Specific Message

Hover over any message, click the three dots icon, and select Remind me about this, then pick a preset time or a custom one. The same menu works on files shared in a conversation. On mobile, tap and hold the message, tap Remind Me, and choose a time.

Message reminders earn their place when someone posts a request you cannot address yet but do not want to lose. The reminder links back to the original message, so the context arrives with the nudge. That is the difference between a follow-up you handle in thirty seconds and one that starts with reading twelve messages of scrollback.

Set a Reminder from a List or a Canvas

From a list, hover over the item, click Open, click the three dots icon, and choose Remind me about this. In a canvas, start typing a date, select it so it becomes a date object, then hover over the date and click Add reminder.

Slack limits both methods to desktop, which makes them a poor fit for anything you need to catch on a phone. They suit rollout plans and maintenance windows you review from your desk. The advantage is that the reminder stays attached to the project it belongs to, so you do not have to rebuild that context inside a standalone /remind message.

Control When a Reminder Lands

Reminders you set for a specific day, like tomorrow or every Tuesday, arrive at 9 a.m. in your time zone by default. That is exactly when your morning queue is already full.

Changing it takes one pass through settings. Click your profile picture, open Preferences, and choose an option under Set a default time for reminder notifications. Moving it to 11 a.m. is often enough to stop reminders stacking on top of the day's first urgent requests.

Every reminder resolves against the time zone in your Slack profile, and that includes channel reminders. A 4 p.m. channel nudge is your 4 p.m., not each reader's, so a distributed team gets it whenever your afternoon happens to be.

When the time arrives, Slackbot sends the notification and badges your Later and Activity tabs. From the notification itself you can mark the reminder complete, snooze it, or delete it. That path is the same whether the reminder was set by command or by form.

Which Slack Reminders Should Ops Teams Set First?

Six patterns cover almost everything an internal support team schedules. The first three react to work already sitting in your queue. The last three run on a fixed calendar. Each one below ends with the point where it stops helping.

IT Queue and SLA Reminders

Set a daily review nudge and an end-of-day handoff prompt. Requests age quietly, and nobody escalates a ticket that has just been sitting there for four days.

• /remind me to review the on-call handoff notes every weekday at 9 am
• /remind #it-support to review unanswered requests every weekday at 5 pm
• /remind me "Follow up on the VPN escalation" tomorrow at 9 am

The nudge fires whether your queue is clean or forty deep. You still open Slack and read to find out which requests are aging.

Onboarding and Offboarding Checklists

Give every handoff its own reminder instead of one reminder for the whole new hire setup. Day-one provisioning, the day-five manager check-in, equipment return, and the full access revoke all move at different speeds. These matter most when HR owns the people process and Finance owns payroll, and you are still accountable for the laptop and the app access.

• /remind me to confirm laptop provisioning for [new hire] on Monday at 9 am
• /remind #hr-team to send the benefits enrollment reminder on the 1st of every month
• /remind me to revoke [departing employee] system access on Friday at 5 pm

Each of those is a checklist item with no checklist behind it. Nothing in Slack records that step four happened, so on the Friday somebody leaves, you are checking from memory.

Approval Follow-Ups

Set a personal reminder for the window you expect the approver to need. A manager approval that stalls costs more than the approval itself, because whoever is waiting starts asking you for status.

• /remind me to follow up on the new hire offer approval in 24 hours
• /remind me to check vendor contract status on Wednesday at 2 pm
• /remind me to chase the security review sign-off on Thursday at 10 am

Match the window to how the approver actually works. A 24-hour check on someone who clears their queue every Friday just adds five nudges you have to dismiss.

Expense and Reporting Deadlines

Put the deadline nudge in a channel reminder so one person stops retyping it every month. For IT, the same pattern helps when software renewals and budget approvals keep bouncing back into your queue.

• /remind #all-teams to submit expense reports by EOD Friday every Thursday at 10 am
• /remind #finance-ops to close monthly books on the 28th of every month
• /remind #finance-ops to send the payroll cutoff reminder on the 25th of every month

The prompt posts to everyone at once, which is its whole advantage and its whole ceiling. Finding out whether anyone acted on it takes a second round of asking.

Recurring Team Rituals

A channel reminder can replace a standing status meeting. Set it to prompt written updates at a fixed time, and it works across time zones where a live standup never suits everyone.

• /remind #people-ops Hey team, what's your focus today? every weekday at 9:30 am
• /remind #it-support to review open purchase requests every Monday at 10 am
• /remind me "Submit timesheet" every Friday at 5 pm

Nobody owns the response. Some weeks three people skip it and nobody notices, which is fine for a ritual. It becomes a problem the moment you use one of these to track a live request.

Policy and Compliance Reviews

Use yearly and monthly repeats for access reviews and security training. Both get pushed aside by whatever is urgent, and a repeat at least gets the prompt onto the calendar on time.

• /remind me to review access permissions every January 1, then separate reminders for April 1, July 1, and October 1
• /remind #finance-ops to reconcile vendor invoices on the 15th of every month
• /remind me to schedule the annual security awareness training every March 30

Slack does not recognize quarterly as a repeat option, which is why that first line takes four separate reminders instead of one. Expect the same workaround on anything that runs twice a year or every six weeks.

How Do You Manage and View Your Slack Reminders?

Open the Later tab. Every active personal reminder sits there under the In progress view, which catches the follow-ups that never became formal tickets. Channel reminders are managed somewhere else entirely, and that split is the most common source of confusion here.

Manage Personal Reminders in the Later Tab

The Later tab on desktop gives you three controls. Together they cover everything except changing the wording.

• Mark a reminder complete by clicking the checkmark icon
• Change its timing by clicking the clock icon and picking a new due date, which is also how you snooze one that fired too early
• Delete it by clicking the three dots icon and choosing Delete reminder

Slack's only documented edit is picking a new due date. If the wording is wrong, delete the reminder and set a new one. A recurring reminder runs until somebody deletes it, which means deleting is also how you switch one off.

On mobile, tap Later at the top of the app, then open the In progress tab. Tap Complete when a task is done, or tap the reschedule icon to change the time. To clear something out, tap and hold it, then tap Remove from Later.

Heavy users hit one limitation. The In progress tab mixes saved messages and reminders together, so it gets long and stays long. Clearing it every morning is the only real defense, especially when password resets and access requests are landing in the same workspace all day.

Manage Channel Reminders With /remind list

Run /remind list in the channel where the reminder posts. Slack replies with a message only you can see, listing the channel reminders you can delete, and you click Delete on the one you want gone.

Channel reminders never show up in anyone's Later tab, because that tab only covers reminders you set for yourself. They also cannot be edited after creation, so a wording change means removing the reminder and building it again with the new details. Those two facts together are why stale channel reminders sit in channels for months.

What Are Common Slack Reminder Issues and How Do You Fix Them?

Reminder problems come in two kinds, and telling them apart first saves twenty minutes of fixing the wrong thing. Either the reminder was never scheduled the way you thought, or it was scheduled correctly and the notification never reached you.

Scheduling and Syntax Failures

A reminder never fired. Check the Later tab for a personal reminder, or run /remind list in the channel for a channel reminder. If it is missing, the original command did not go through, so retype it as /remind [me or #channel] [what] [when] and wait for Slackbot to confirm before moving on.

Slack cannot read your time format. When Slack asks you to rephrase, the time format is almost always the cause. Stick to formats that work, like in 5 minutes, at 3:30 pm, on Tuesday, or next week. Put quotation marks around the message text so a number inside it does not get read as the delivery time.

Reminders fire at the wrong time. The schedule uses the time zone in your Slack profile, not your device's local time. Open Preferences, then Language & Region, and confirm the profile time zone is right before you go looking for anything more complicated.

A channel reminder keeps posting and nobody wants it. Recurring reminders run until somebody deletes them. A channel reminder never appears in anyone's Later tab, so nothing prompts that cleanup. Run /remind list in the affected channel to see everything scheduled there, delete what has gone stale, and recreate it only if the nudge is still useful.

Notification Failures

Do Not Disturb is blocking notifications. While DND is active, Slack pauses notifications, so a reminder can fire on time without ever alerting you. Check your Do Not Disturb schedule in Preferences and confirm it is not sitting over your reminder times.

Nothing appears on mobile. Confirm Slack has notification permissions in your device settings. On iOS that is Settings, then Notifications, then Slack; on Android it is Settings, then Apps, then Slack, then Notifications. If the permission is on and reminders still do not surface, the reminder has done its job and the delivery is where it broke. Chase that in Slack's notification settings.

When Does a Slack Reminder Need to Become a Workflow?

As soon as the message has to change or somebody has to respond to it. Slack's own recommendation for anything past a simple channel reminder is Workflow Builder and its scheduled message template.

You set a start date, a frequency, a message, and a channel. The message stays editable afterward, which a channel reminder never allows. Workflow Builder sits on Slack's paid plans, Pro and above, so check your plan before you build a routine on it.

Third-party reminder apps in the Slack Marketplace cover narrower gaps, mostly response tracking and repeat schedules the /remind command does not accept. Test any of them in your own workspace before you rely on it. None of them gives a request an owner.

When Do Slack Reminders Stop Being Enough?

When a request needs an owner, an approver, and a record. Reminders were built for personal task management and simple team nudges, and past a certain request volume people push them into work they were never built for. Four gaps show up in the same order on every lean team.

A reminder only ever notifies one person. It fires for you, and if you are out sick or pulled into an incident, nobody picks it up. The task falls through because it lives in your personal queue rather than anywhere the team can see.

An approval needs somewhere to go. A reminder gets you to send the follow-up message. When an onboarding checklist needs sign-off from IT, Finance, and the hiring manager, you are still chasing sign-off at every step, one desk at a time.

Reminders do not add up to a view of anything. There is no screen showing how many onboarding tasks are open, which expense approvals are overdue, or where requests are stuck. When leadership asks for status, you are reading Slack history instead of tracking open work.

A dismissed reminder leaves no record it existed. Once it is cleared, there is nothing to say what was handled, how long it took, or which requests keep coming back. The quarterly access review is the first place that bites.

Recognizing all four does not mean you have outgrown Slack. It means you have outgrown unstructured Slack. Structure is what closes those four gaps: a request that arrives with an owner attached, a route to whoever has to approve it, and a clock somebody can audit.

Monzo's Tech Ops team hit this exact point. IT ran on Slack messages and threads, with no tracking of status or SLAs, and common requests like VPN and 2FA needed a call. Monzo now automates and solves 60% of its inbound support requests with Siit, keeps ticket acknowledgement under one hour, and was live in under two weeks. On a desk taking 150 requests a week, 60% is 90 that never reach a human.

Deciding What Belongs in a Slack Reminder

Reminders work right up to the point where a request needs an owner. Keep them for your own follow-ups and for fixed-cadence channel nudges, and move anything with an approver in it somewhere else. That is the line where a notification runs out, and it is not a reason to stop using reminders.

Siit will not remind you to drink water at 3 p.m., and it should not, because personal nudges belong in the Later tab. It handles the parts a reminder cannot: shared queues, routed approvals, SLA tracking, and reporting, all inside the channels your team already uses. Centralizing Slack requests is the change, and the tool your team opens every morning stays the same.