Calendar reminders and AI actions
A reminder is for work you must revisit at a particular time without needing a separate task. An AI action uses the same calendar context but also connects a prompt with a work chat or assistant. If the work needs an owner, result, and acceptance, create a task and link the reminder to it.
Create a reminder
In /calendar, choose New reminder or New AI action. For a reminder, enter a title and time, then optionally add an assignee, comment, and link to a task, CRM record, document, or project. For an AI action, also check the prompt and work conversation. Fix an empty title, invalid interval, or end time before sending. In an open company or deal context, the calendar shows only reminders linked to that exact record. An empty list means there are no reminders for the selected object, not that personal reminders are absent from the whole calendar; creating from the context keeps that link.
A draft without a time is temporary planning, not a scheduled commitment. If creation fails, check permissions, time, and required fields before retrying; do not create a duplicate by clicking blindly. Technical text shown on failure can be a server response rather than usable guidance: do not copy or publish it—record the route and time, then contact an administrator.
An untimed draft is one-time planning: set a start before making it recurring. A series may have an optional end; its interval starts at 1, and an end before the start is rejected.
Statuses and actions
Reminders use draft, active, snoozed, done, and canceled:
- Complete moves an active reminder to
done; - Snooze moves it to
snoozeduntil the selected time; - Cancel closes the commitment without marking it complete;
- editing changes the title, time, link, assignee, or schedule only when permitted.
Check Calendar after it loads. If tasks load but the reminder feed does not (or the reverse), Calendar can show a partial result with a warning; do not treat an incomplete list as proof that data is absent.
Dragging and recurring series
In the day and week schedule, a card can be dragged to another day or slot only with edit permission. Dragging changes the start and end; the separate signal can move independently. A reminder from Without time can be dragged into the schedule. Completing, snoozing, or editing a recurring reminder asks for confirmation and applies to the whole series; an occurrence is not detached. A linked card may show loading or “no access”; that does not mean the record was deleted.
Repetition and time zone
Recurring reminders support daily and weekly intervals, including selected weekdays. The time zone is saved for a recurring schedule and controls local firing time. Confirm before editing a recurring item: editing an occurrence updates the whole series, not only one date.
Before rescheduling, check whether the change affects a client commitment or linked task deadline. Record the reason in the work object, not only in Calendar.
Permissions and linked records
The owner or a user with edit permission can change a reminder. Assigning another person may require a separate permission; a hidden button is an access boundary, not a reason to create a copy. A linked card may show a title and status, or only a safe no-access state.
Open the task, CRM record, document, or project to keep files, comments, decisions, and acceptance there. Do not copy private linked data into a reminder title.
AI actions
An AI action needs a clear prompt and selected conversation/channel. The conversation is required; a configured assistant profile is optional. Set the tool-call limit from 1 to 5 (default 3). The form rejects a missing prompt or conversation. Review the prompt before running it and the result afterward: AI can prepare a signal or suggestion, but it does not confirm an agreement or replace a person. Never provide passwords, tokens, payment data, or unnecessary personal data.
Choose a conversation in the picker by its visible title and preview, for example Client Test · Project Brief (“Confirm delivery window”) or Northwind Demo · Internal. Search covers only the recent conversations page; a missing row there does not prove that the conversation was deleted—refresh or open chat and choose a visible synthetic thread. Loading, error, and no-results states are distinct and do not send the action. If a saved conversation can no longer be resolved, the portal shows a neutral Personal chat or Direct chat label, never a technical ID.
Safe demonstrations
Use synthetic titles, dates, tasks, and links. Keep real calendars, client names, and internal URLs out of demonstration data.
Related pages
Conceptual guidance, not a UI screenshot or state evidence.