Tasks live at Operations → Tasks. Two views of the same list: kanban (drag across statuses) and table (filter, sort, bulk-act). Tasks come from three places: created by hand, auto-created by an automation rule, or auto-created by another module. This article is the daily working playbook. The clinician-inbox angle and the full engine internals each have their own walkthroughs.

Where it lives#

Operations → Tasks: kanban by default, switch to table via the top-right toggle.
+ New task: top-right button.
Tasks also surface where they belong: a follow-up task on a lead shows on the lead card, a callback task on a patient shows on the patient profile.

Task lifecycle#

Each task carries a status. The system-locked codes are:

Todo: created, not yet started.
In progress: owner started working on it.
In review: completed by owner, awaiting review or follow-up.
Done: completed and closed.

Tenants can add custom statuses (e.g. "Waiting on patient", "Cancelled") under Settings → Workspace → Statuses, the same locked-vs-custom pattern as session and invoice statuses.

Anatomy of a task#

Title: short, action-oriented ("Call Sara about Tuesday reschedule").
Assignee: one person accountable for completion.
Reporter: who created the task.
Followers: people who should see updates but are not accountable.
Tags: free labels for filter and reporting (follow-up, lab, callback, vendor, etc.). Task tags share the patient tag taxonomy, so names like follow-up, vendor, lab appear on both surfaces. Manage them under Settings → Tags.
Priority: low / medium / high.
Start date: when work should begin.
Due date: completion deadline. Drives overdue indicator.
Linked record: patient, lead, session, invoice, vendor (generic FK). Task shows up on that record too. The link is enforced server-side via a content-type allow-list. Arbitrary models cannot be attached.
Comments: append-only log of what was done. Each comment is timestamped and author-stamped.

Tasks auto-created by other modules#

The automation engine is the bridge. Other modules emit events, automation rules listen and call the create-task action.

Live rules#

Automation rule fires → task created via the automation handler.
Rules visible under Settings → Automations.
The bridge ships out of the box. Each example below requires a tenant-authored automation rule to be active:
- Lead sitting in Open for > 24 hours → "First contact overdue" task on assigned rep.
- Lost lead reaching 90 days → "Reactivation campaign target" task.
- Outstanding invoice > 14 days → "Collection call" task on the accountant.
- Manual creation from any module's kebab menu.