Tasks

The Tasks page (/crm/tasks) is your to-do list across the workspace. Tasks can be attached to a specific lead (and surface inside that lead's detail view) or stand on their own (a general team to-do).

Quick add

The card at the top of the page is your task composer. Four parts:

• Body — multi-line text. Type whatever you need: instructions, context, links. Type # anywhere to tag a client (more on that below).
• Assign to — pick the team member responsible. Optional. "Anyone" if you leave it blank.
• About lead — the lead this task is primarily about. Optional. Use the searchable picker; this links the task to that lead's detail page and surfaces it in the lead's tasks rail.
• Due — optional date and time.

Hit Add task. The task appears in the Open list immediately.

Tagging a client inline with #

Inside the body, type # and a popover appears with a searchable list of leads. Pick one and the lead's name gets inserted as a clickable tag. The tag opens that lead's detail page in a new tab when clicked, but it does not automatically attach the task to the lead. (Use the About lead dropdown for that.)

You can tag multiple leads in one task. Useful for things like:

Reach out to #Jane Doe by Friday and let #Acme Corp know about the change.

Both names become blue clickable chips on the rendered task.

Lead vs tag distinction

• About lead = the primary lead for this task. Linked structurally. Surfaces in that lead's right-rail tasks. Activity rows in the lead's timeline reference this task.
• #tag = inline mention of a lead within the body. Just a clickable cross-reference. Doesn't affect the task's structural link.

Filters

Above the composer there's a filter row. Two filters in v1:

• Owner — restrict to a specific assignee. Pick a teammate from the dropdown, or pick Unassigned to see only the orphan tasks.
• Lead — the searchable lead picker. Restrict to tasks attached to a specific lead via the About field. (Inline #tag mentions don't count toward this filter; only the structural About link does.)

Filters compose with the Open / Completed tab and with each other. The URL reflects the active set, so a "show me Sam's overdue work on Jane Doe" view is a bookmarkable URL.

Open vs Completed

The tab switcher in the top-right toggles which list you see:

• Open — tasks that haven't been ticked yet. Sorted by due date (earliest first), then by creation time.
• Completed — tasks that have been marked done. Sorted by completion time (most recent first).

Each tab shows its count.

The URL reflects the active tab (/crm/tasks?status=done), so you can bookmark or share a particular view.

Task rows

Each row shows:

• A checkbox on the left. Click to mark complete; click again to reopen.
• The task title. Strikes through when complete.
• The linked lead's name (if any), as a clickable link to that lead's detail page.
• A due date, if set. Overdue tasks (open and past their due date) display in amber as Overdue.

What happens when a task moves

• Marking a task complete writes completed_at = now(). If the task is linked to a lead, a Task completed activity row also lands in that lead's timeline.
• Reopening a task clears completed_at. No activity row for the reopen (we figured the timeline doesn't need that noise; revisit if it does).

Real-time

The list updates live for everyone on your team. Add a task in one tab, watch it appear in another. Mark complete on a teammate's screen, watch the row strike through on yours.

What's not in v1

• @person mentions. Inline @-tagging in the body to assign tasks to people is queued for v2. The Assign to dropdown handles assignment in v1.
• Editing a task title or due date after creation. Add and complete; edit lands later.
• Deleting a task. Defer to v2.
• Recurring tasks. Not on the v1 roadmap.
• Task notifications (email or push). Not in v1.