ConversaLabs Help Center
en
Language
pt_BR Portuguese (Brazil) en English es Spanish

Subtasks, dependencies, recurrence and reminders

Open in
View as Markdown Open in ChatGPT Open in Claude
Conversa Labs

Conversa Labs

Last updated on Jun 27, 2026

Overview

Four features help you structure larger work and forget nothing:

  • Subtasks: split a big task into smaller steps, each with its own assignee and due date.
  • Dependencies: chain tasks together — a task can block another (or be blocked by it). While a blocker is still open, the dependent task shows a blocked badge.
  • Recurrence: repeat a task automatically on a cadence (daily, weekly, monthly or yearly). The next occurrence is created when the current one is completed.
  • Reminders: scheduled alerts (in-app or email) for you or the assignees, at a chosen date/time.

Prerequisites

  • The Tasks module enabled for the account.
  • A task to which you'll add subtasks, dependencies, recurrence or reminders.
  • For email reminders, users need a valid email on the account.

Step by step

  1. Subtasks: open a task and add subtasks in the corresponding panel; each subtask can have its own assignee, due date and status.
  2. Dependencies: on the task, define which tasks it blocks and which block it. The blocked badge shows while any blocker is not yet done or cancelled.
  3. Recurrence: set the cadence (frequency, interval and, optionally, days of the week, an end date or a number of occurrences). When you complete the task, the next occurrence is generated.
  4. Reminders: add one or more reminders with a date/time and a channel (in-app or email), pointing at you, another user or the assignees.
  5. Track everything across the list/board/calendar views.

Settings & options

  • Subtasks: inherit the parent's context but have a life of their own; they survive if the parent task is deleted (they're orphaned).
  • Dependencies: the "blocked" calculation considers blockers that are not yet done or cancelled.
  • Recurrence: the new occurrence clones assignees, list, labels and attributes, with shifted dates, and starts in the to do status. Generation is idempotent — it never duplicates occurrences.
  • Reminders: fire exactly once; a system reprocessing never resends the same reminder.

Use cases

  • Break a customer onboarding into subtasks (contract, setup, training).
  • Enforce execution order with dependencies (only publish after review).
  • Automate recurring routines: weekly report, monthly close, yearly backup.
  • Schedule a reminder to resume a negotiation on an agreed date.

Tips, limits & best practices

  • Avoid very deep dependency chains — they make the critical path hard to see.
  • A task cannot be its own ancestor; subtask cycles are blocked.
  • On recurring tasks, set a due date on the template task so the next occurrence is anchored correctly.
  • Schedule reminders with enough lead time to actually act.

Troubleshooting

  • The "blocked" badge won't clear: check that the blocker is truly done or cancelled.
  • The next occurrence wasn't created: confirm recurrence is configured and the task was marked done (the occurrence is born on completion).
  • I didn't get the reminder: check the chosen channel (app/email), the date/time and whether the reminder has already fired.

See also