Schedule recurring or one-off reminders that nudge employees about unsubmitted expenses, pending approvals, advance reconciliations, or any other custom message — delivered via email, in-app notifications, Slack DM, or Slack channel.
What reminders do
Reminders solve the "I forgot to submit my expenses" and "this report has been sitting in my queue" problems. Instead of relying on people remembering on their own, an admin sets up a reminder once and the system delivers it on schedule with the right context to the right people.
A reminder is made up of:
- A schedule — when and how often it fires
- A message — subject + body, supports variables like
{employee_name}and{manager_email} - One or more recipients
- One or more delivery channels — email, in-app, Slack DM, or Slack channel
- A timezone — schedules fire at the recipient's (or admin's) local time
Create a reminder
- Go to Admin Settings > Reminders.
- Click New Reminder.
- Fill in the reminder name, frequency, schedule, recipients, message, and channels.
- Click Save.
The reminder appears in the list as Active. To pause it without deleting, toggle the status to Paused.
Frequency options
| Frequency | When it fires |
|---|---|
| Once | A single delivery at the scheduled date and time |
| Weekly | Every week on a chosen day |
| Monthly | Every month on a chosen day |
| Yearly | Every year on a chosen date |
All scheduled reminders are timezone-aware. The schedule respects the timezone you set on the reminder, so a "9 AM Monday" reminder fires at 9 AM Monday in that timezone — not in UTC.
Delivery channels
Each reminder can deliver through any combination of:
- Email — sent to each recipient's registered email address. Includes the message body and, for scheduled reminders, an unsubscribe and snooze footer link.
- In-app notification — appears in the recipient's notification center inside Eloope.
- Slack — visible only if your organization has the Slack integration connected. Two delivery modes:
- DM mode — direct messages to each recipient individually
- Channel mode — a single message posted to a Slack channel you select
If all recipients have opted out of a channel, that channel is skipped — the rest of the delivery proceeds normally.
Recipients
Recipients are selected from your organization's active users. Two reminder types control who can be targeted:
- Personal reminders — only target the creating user. Useful for self-nudges ("remind me to reconcile my advance every Friday"). Created from
/reminders(the personal reminders page). - Admin reminders — can target any user(s) in the organization. Created from Admin Settings > Reminders, requires admin role.
The system enforces this distinction across the UI, API, and database, so a personal reminder cannot accidentally fan out to coworkers.
Send Now and run history
Each saved reminder has two operations beyond its scheduled cadence:
- Send Now — fire the reminder immediately, bypassing the scheduled cadence. Useful for testing a new reminder before it goes live, or for ad-hoc nudges (e.g., right before a month-end deadline).
- Run History — open the run history sheet to see every past delivery: timestamp, channel breakdown (how many emails/in-app/Slack went out), how many recipients were skipped because they unsubscribed or snoozed, and any per-channel failures (e.g., an email bounce or a Slack channel the bot can't post to).
The run history makes failure modes visible. If you notice "3 of 12 recipients suppressed" on every run, that's a signal a chunk of the team has opted out and the reminder may need rethinking.
Templates
On the Business plan and above, admins can save and re-use reminder templates — pre-written subject lines and message bodies. Templates live in the templates table on the server, so they're available to every admin in the organization (not stored per-browser). Use templates for recurring patterns like end-of-month submission reminders, quarterly compliance nudges, or onboarding sequences.
Recipient self-service: snooze and unsubscribe
Every recipient has full control over the reminders they receive. There are two ways to manage preferences:
From email
Every scheduled reminder email contains a footer with Unsubscribe and Snooze links. The links are signed with a short-lived HMAC token, so only the intended recipient can use them.
- Snooze options: 1 day, 3 days, 1 week, 1 month. After the snooze window, the reminder resumes automatically.
- Unsubscribe stops the reminder for that user only. Other recipients of the same reminder are unaffected.
From the app
- Click your profile avatar > Profile.
- Open the Notifications tab.
- Click Manage Reminder Preferences.
You see every reminder you're subscribed to. From here you can:
- Snooze an individual reminder for 1 day, 3 days, 1 week, or 1 month
- Stop (unsubscribe from) a reminder
- Resubscribe to a reminder you previously stopped
Stopping or snoozing a reminder only affects the user who triggers it — other recipients keep receiving it on schedule.
What admins see
When a recipient opts out, admins still see the reminder run as scheduled — but the run history shows the suppressed count, so it's never silent. Bulk admin reminders sent from the user list (one-shot, not scheduled) also continue to work for ad-hoc nudges.
Delivery failure visibility
If a delivery fails — an email bounce, a Slack channel the bot was removed from, an out-of-quota plan — the failure surfaces in the run history sheet for that run, with the error message. The next scheduled run still tries; failures don't disable the reminder.
Plan availability
| Capability | Plan |
|---|---|
| One-shot bulk reminders from the user list | Starter and above |
| Scheduled (recurring) reminders | Starter and above |
| Slack delivery | Starter and above (requires Slack integration) |
| Reminder templates | Business and above |
The scheduled-cron itself is plan-gated, so on lower tiers you can still send a one-time email blast from the user list but can't schedule a daily/weekly/monthly cadence.