Navigation
ELOWEN · Documentation

Last updated: October 27, 2026

Browse documentation · Get a reminder or a regular summary

Get a reminder or a regular summary

Chetty can come back to you on its own: once in twenty minutes, or every working morning with the same overview. You do not need any page for it; ask in the conversation.

One reminder, or the same task again and again

What you want Ask like this What happens
One reminder "remind me in 20 minutes to call Novák" Chetty returns to the conversation once and the reminder removes itself.
One reminder at a time "remind me at 18:30 to lock the office" The same, at a set time. Seconds work too, from five up.
A repeated task "every working day at 8:00, send me what came in overnight" Chetty does it again on the same schedule until you pause or delete it.

A repeated task can also be a weekly summary or a check of one Project every morning. Say the time and the days in your own words; Chetty turns them into a schedule. The page Automation shows what was created and lets you change it: Manage tasks that run on their own.

Where the result arrives

A reminder created in a conversation comes back to that conversation. A repeated task started in the web chat or in a shared room works in its own conversation, named after the task, so the result does not interrupt your discussion.

Anything a task does, it does with your permissions, so it can read only what you can read. A task belongs to the person who created it; colleagues do not see it.

Calendar and history

The Automation page has a Calendar of the coming runs and a History of the ones that already happened, with their result. Runs are kept for seven days, daily totals for ninety.

Limits worth knowing

  • One account can keep up to 20 tasks of its own.
  • A repeated task usually cannot run more often than every 15 minutes, and a plain weekday-and-time schedule is enough for almost everything.
  • A task set up for the whole organization is the administrator's job; you can ask for one.
  • If a task is paused, or the Project it belongs to is deleted, it stops running.

When a result arrives late

  • A temporary hiccup is retried before Chetty gives up, so a single failure usually does not lose the run.
  • If a result cannot be delivered, Chetty tries again without repeating the work. Up to 50 results may wait.
  • When a run has nothing to report, no message arrives. That is not a failure.
  • A failed run alerts the owner of the task, and the reason is in the history.