Elbuz reminds organizer record participants by itself: at a set minute, on a schedule or at the deadline, by email, Telegram, browser and in-app notification. No chasing colleagues.
When you need this:
- A deadline must not slip — one reminder arrives at the deadline, even without a rule.
- A job repeats daily or weekly — a rule reminds on schedule until a set date.
- A reminder came at a bad time — “+15 min”, “+1 hour” or “Tomorrow 9:00” moves it for everyone.
- An employee has no email or Telegram — an in-app notification still arrives.
Where to start: open the record → the “Reminders” section → the “Remind” field.
What reminders can do
- Repeat rule — once, daily, weekly, monthly or annually.
- Reminder at the deadline — no rule, just the “Deadline date, until” date.
- Dates and limits — when to start and when to stop.
- Four channels at once — email, Telegram, browser and in-app notification.
- Snooze — move a reminder by 15 minutes, an hour or until morning.
- Pause for a closed record — a completed record doesn't remind, the rule stays.
How to set a reminder
The “Remind” field sets how often. Your choice decides which fields appear next to it:
- “Once” — a reminder at the moment set in “Reminder date, start”. After sending it switches off if “Deadline date, until” is empty or already past. If the deadline is still ahead, a second reminder arrives at the deadline.
- “Daily” — the “every” field labeled “days” and “Reminder time”.
- “Weekly” — adds “Day of the week”.
- “Monthly” — the “Month” and “Day” fields.
- “Annually” — also month and day.
The number in “every” is the step. 2 with “Daily” means every other day.
Reminder settings are saved when the form is saved — by autosave or by closing the window. “Next reminder date” is recalculated only if the rule fields or dates changed: “Start Date”, “Deadline date, until”, “Don't remind after date”, “Reminder date, start”. A random autosave doesn't reset a snoozed reminder.
1
Remind2
Reminder time3
Don't remind after date4
Start Date5
Next reminder date and Total reminders- Remind — the choice here decides which fields appear next to it.
- Reminder time — the reminder arrives at exactly this minute.
- Don't remind after date — after this date the reminders stop.
- Start Date — a future date mutes the reminder, and sending only begins after it.
- Next reminder date and Total reminders — filled in by the program; use them to check that everything works.
Further down the section are the limits: “Max reminders” (0 means no limit) and “Don't remind after date”. Below them are the record's two dates: “Start Date” and “Deadline date, until”. What each does is covered in the section on dates.
Two fields are filled in by Elbuz: “Next reminder date” and “Total reminders”. Use them to check that everything works. Zero in “Total reminders” means nothing has been sent yet. An empty next date with a rule set happens when:
- “Max reminders” is used up;
- “Start Date” is still in the future — this is waiting, the field fills in by itself when the date comes;
- “Once” has an empty or past “Reminder date, start” and no future deadline (including after “Once” has fired);
- after “Don't remind after date” has passed, someone changed the repeat rule or one of the dates.
Simply saving again doesn't clear the field: if the rule and dates weren't changed, it keeps a date that lies past the stop date — that reminder just isn't sent.
- Start
- State
- End
When the first reminder arrives
Elbuz checks records once a minute, so a reminder arrives in the minute it is scheduled for. Which moment that is depends on what's filled in the record:
- There is a “Remind” rule — the first arrives at the nearest moment by the rule.
- No rule, or the rule gave no date (only possible with “Once” whose “Reminder date, start” is empty or past), and “Deadline date, until” is in the future — one reminder arrives exactly at the deadline.
- Neither a rule nor a future deadline — there will be no reminder.
- “Start Date” is still in the future — silence until then. When it comes, Elbuz calculates the first reminder by the rule itself; no need to save the record again.
- Action or result
- Decision: the path depends on the answer
After each send, “Total reminders” goes up by one and “Next reminder date” is recalculated by the rule.
What each date really does
Field names don't tell the whole story, so we tested them on live records: set the options, waited for the send and looked at the result.
| Settings | What happens |
|---|---|
| “Daily” + “Deadline date, until” already past | The reminder was sent and keeps coming daily. A deadline doesn't stop a repeating reminder. |
| “Once” + “Don't remind after date” in 10 days | Sent once, then the reminder switched off, as “Once” should. |
| “Daily” + “Don't remind after date” in 10 days | Sent, the next one is tomorrow. Sending goes on until that date. |
| “Daily” + “Start Date” tomorrow | Nothing sent, “Total reminders” is 0, “Next reminder date” is empty. No reminders before “Start Date”. When it comes, Elbuz calculates the next reminder by the rule itself. |
Hence three rules:
- “Start Date” — when to start reminding. Silence before it; after it, reminders follow the rule by themselves. An empty field or a past date means remind right away.
- “Don't remind after date” does what it says: until this date reminders follow the rule, after it they stop. It's a date with time: leave 00:00 and there will be no reminders on that day itself.
- “Deadline date, until” doesn't switch off a repeating reminder. It works in two cases: when there's no rule or the rule gave no date (“Once” with an empty or past “Reminder date, start”, or after “Once” has fired), one reminder arrives at the deadline; and in the record list an overdue record is marked “Overdue” with the deadline in red.
The calendar places records by “Start Date”: without it a record doesn't appear in the calendar grid. A filled “Start Date” in the past both shows the record in the calendar and doesn't block reminders.
Who gets it and where
Reminders go to all participants and assignees of the record who are active employees. A manager who isn't among the participants doesn't get them.
If there are no active participants, Elbuz sends to the participants of the record's calendar event, and if there are none either, to whoever first saved a reminder in the record (not necessarily the author).
There are four channels and you can't choose between them: Elbuz sends to all the ones set up for the person at once.
- Email. The address is taken from “Email for notifications” in the employee card, or from the main email if that's empty. A copy goes to “Email #2”, a blind copy to “Email #3” (these fields are in the card's contacts). Email is sent only if a mailbox for sending is set up in Elbuz (): without it nobody gets email, whatever addresses are in the cards. The subject is “Notification <type> #<number> - <name>”.
- Telegram — if the company Telegram bot is connected in Elbuz and “Telegram chat ID” is filled in the employee card. A chat ID alone, without a connected bot, isn't enough. The message has the same line as the email subject in bold, with the text below.
- Browser notification — if the employee clicked “Subscribe to notifications” in their card.
- In-app notification — always, no setup needed.
The “Notifications” section of the employee card holds three items: “Email for notifications”, “Telegram chat ID” and the “Subscribe to notifications” button; see how it looks in the article on tasks and projects.
In-app notifications
If the person is in Elbuz now, a pop-up “Reminder: <record name>” appears, and the “Notifications” tab of the “Notifications and operations” panel gets a row with that title and the start of the description. If they're offline, the row waits there until they sign in. Title and buttons are in the recipient's language.
Notifications are kept for 90 days, but after a page load the panel shows only the 30 latest entries, operations and notifications together. An older notification may not appear in the panel.
A notification has four buttons: “Open” opens the record, while “+15 min”, “+1 hour” and “Tomorrow 9:00” snooze the reminder.
1
Reminder title2
Open3
Snooze buttons- The title starts with “Reminder:” followed by the name of the task.
- Open — opens the task itself.
- +15 min, +1 hour and Tomorrow 9:00 — snooze the task's reminder; the new time applies to all participants.
If the employee card has neither email nor Telegram (or Elbuz has no sending mailbox or bot set up), the email and Telegram message aren't sent, and Elbuz won't warn you. But the in-app notification still arrives.
The Snooze buttons: what happens
You click “+15 min”, “+1 hour” or “Tomorrow 9:00”, and Elbuz does this:
- Checks that you're a participant of the record. If not, you see “Update failed” and nothing changes.
- Checks the record's limits. Limit used up — “Not snoozed: the reminder limit is used up. Increase the maximum number of reminders in the item.” New time later than “Don't remind after date” — “Not snoozed: the new time is after the “Do not remind after” date. Change it in the item.” Either way nothing changes.
- Sets “Next reminder date” to now + 15 minutes, now + 1 hour or tomorrow 09:00 and switches the record's reminder back on, even if “Once” has already fired.
- Shows “Will remind at <date time>” with the moment the reminder will really arrive. If “Start Date” is still in the future, it will be that date. The snooze buttons in this notification disappear until the page reloads; “Open” stays.
- Action or result
- Decision: the path depends on the answer
The buttons disappear only in the current browser tab. After a page reload, the “Notifications and operations” panel shows them again in the same notification if it's among the panel's 30 latest entries, and you can snooze again, with the same effect for all participants. Every snoozed reminder counts toward “Total reminders” and the “Max reminders” limit.
Only organizer record reminders can be snoozed. Notifications about support tickets don't have these buttons.
A deadline without a rule, and quick add
The rule is optional. If the record only has “Deadline date, until”, one reminder arrives exactly at that moment — to all participants, through all channels.
A deadline typed in quick add, such as “… tomorrow 10:00”, works the same way: it becomes the record's deadline, and a reminder arrives at 10:00 tomorrow. How quick add works is covered in the article on the record list.
If the deadline is already past when you save, there will be no reminder.
Moved the deadline in the form? The reminder arrives at the new moment: a date change recalculates “Next reminder date”. Moving an event in the Calendar works the same, by dragging or in the event form: the reminder is recalculated and the change goes into the record's change history.
How to stop reminders
A passed deadline doesn't stop a repeating reminder.
A closed record doesn't remind: a completed or canceled status, the archive or the Trash pause reminders. The rule stays. Put the record back to work and reminders resume; if their time has already passed, one arrives at the next check.
To stop reminders in an active record, there are three ways:
- “Don't remind after date” — no reminders after this date and time.
- “Max reminders” — sending stops after the set number of sends. Snoozed reminders count too.
- “Remind” = “---” — the rule is removed. If a future “Deadline date, until” is filled in, one reminder at the deadline still arrives. To avoid that too, clear the deadline.
You can't turn off organizer reminders just for yourself with a checkbox in the employee card: a reminder goes to all participants of the record.
Scenarios
Remind once at the deadline
Fill in only “Deadline date, until”, or type “… tomorrow 10:00” in quick add. One reminder arrives at the deadline; nothing else to set up. If the deadline is already past when you save, there will be no reminder.
Remind daily until the due date
“Remind” — “Daily”, “Reminder time” — 09:00, “Don't remind after date” — the due date with a time at the end of the day, such as 23:59. Every morning up to and including the due date participants get a reminder, then sending stops. Leave 00:00 and there's no morning reminder on the due date itself.
Start reminding on Monday
Set a rule and put “Start Date” on Monday. No reminders until Monday; from Monday they follow the rule, and Elbuz calculates them itself.
A reminder came at a bad time
Click “+1 hour” in the notification. In an hour the reminder comes again — to you and to all other participants of the record. It won't move if “Max reminders” is used up or the new time is after “Don't remind after date”: you'll see “Not snoozed: …”, and nothing changes in the record.
An employee has no email or Telegram
Add them as a participant of the record. They'll see the reminder as an in-app notification: it pops up if they're online, or waits on the “Notifications” tab of the “Notifications and operations” panel until they sign in.
What to do when a reminder doesn't arrive
| What you see | Why | What to do |
|---|---|---|
| A rule is set, but “Total reminders” is 0 | “Start Date” is still in the future, or the record is closed: completed, canceled, archived or in the Trash | Wait for “Start Date” — then reminders follow by themselves; put a closed record back to work (when the first arrives) |
| Empty “Next reminder date” with a rule set | “Max reminders” is used up, “Once” has fired with no future deadline, or “Start Date” is still in the future — then the field fills in by itself when it comes | Raise the limit or set a new date and save the record (how to set) |
| An employee got no reminder at all | They aren't a participant of the record, or they're an inactive employee | Add them as a participant and check the status in their card (who gets it) |
| The reminder is in Elbuz, but no email | The employee card has no email, or Elbuz has no mailbox set up for sending (SMTP) | Fill in “Email for notifications” in the card and make sure the sending mailbox is set up (channels) |
| “Telegram chat ID” is filled in, but nothing comes in Telegram | The company Telegram bot isn't connected in Elbuz | Connect the bot in integrations (channels) |
| Reminders keep coming after the deadline | “Deadline date, until” doesn't stop a repeating reminder | Put the same date in “Don't remind after date” (how to stop) |
| Snoozed for an hour, and colleagues got the reminder | You snooze the record's reminder, not a personal copy | That's by design: the new time applies to all participants (the Snooze buttons) |
| Put a task back to work, and a reminder came right away | Closing only paused reminders; the time missed during the pause is made up with one reminder | Nothing — then reminders follow the rule. Don't need them? Set “Remind” = “---” (how to stop) |
| “Not snoozed: the reminder limit is used up…” or “Not snoozed: the new time is after the “Do not remind after” date…” | The snoozed reminder wouldn't pass the record's limits, so Elbuz doesn't move it | Raise “Max reminders” or push “Don't remind after date” later in the record and snooze again (the Snooze buttons) |
| “Update failed” after clicking “+15 min”, “+1 hour” or “Tomorrow 9:00” | You aren't a participant of the record, or the request failed | Ask the author to add you as a participant of the record (the Snooze buttons) |
| The notification has no “+15 min”, “+1 hour”, “Tomorrow 9:00” buttons | It was just snoozed in this browser tab, or it isn't an organizer record — for example, a support ticket | Reload the page — the buttons come back in a record's notification (the Snooze buttons) |
FAQ
Why does a reminder come daily even though the task deadline has passed?
Because “Deadline date, until” doesn't switch off a repeating reminder. To end sending, set a date in “Don't remind after date” or cap the count in “Max reminders”.
If I snooze a reminder, will other participants get it?
Yes. You snooze the record's own reminder, so at the new time it goes to all participants, through all channels. There's no personal snooze.
Will an employee without email or Telegram get the reminder?
Yes, as an in-app notification. If they're online, it pops up right away; if not, it's on the “Notifications” tab of the “Notifications and operations” panel after they sign in. Email and Telegram aren't sent in that case.
Can I snooze the same notification twice?
Yes. The buttons disappear only in the current browser tab, and after a page reload the “Notifications and operations” panel shows them again if the notification is among the panel's 30 latest entries. Each snooze moves the record's reminder for all participants and counts toward the “Max reminders” limit.
What does “Start Date” do?
It sets when to start reminding. No reminders before it, and when it comes, Elbuz calculates the first reminder by the rule itself. An empty field means remind right away.
Will the assignee's manager get the reminder?
Only if they're added as a participant of the record. Elbuz doesn't send a separate copy to the manager.
Will reminders stop if I mark the task completed?
Yes, they pause. A completed or canceled record, as well as one in the archive or the Trash, doesn't remind. The rule stays: put the record back to work and reminders resume. To remove them for good, set “Remind” to “---”.
Can I choose where reminders are sent?
No. An organizer reminder goes to all channels set up in the employee card at once, plus the in-app notification.
Where to find it and who has access
The “Reminders” section is the same in the forms of every organizer record type. You open the form from the list of records or straight from a notification.
- Menu
- Organizer → Tasks / Notes / Projects / Documents / Tables / Presentations / Forms
- From the list
- “Edit” on a card or in a table row → the “Reminders” section
- From a notification
- the “Open” button in the reminder opens the record itself
- Access right
- the window of that record type; you only see records where you are an assignee or participant
- Prepare
- a mailbox for sending email, the company Telegram bot, an email address or chat in employee cards
Related topics
- To create a record and assign the people who will get reminders — tasks and projects.
- To type a deadline in one line when creating a record — quick add in the organizer list.
- To call a colleague to a record now, not at the deadline — comments and @mentions.
- To hear about orders or price lists rather than organizer records — event notifications.
