> For the complete documentation index, see [llms.txt](https://docs.zero.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zero.inc/features/tasks.md).

# Tasks

Every deal you are working on should have a clearly defined next step. Tasks are where that next step lives — attached to the company, contact, deal or meeting it came from, visible to your team, and impossible to lose in a personal to-do app.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/tasks-page-overview.png" alt="Tasks page grouped by due date, with Overdue and Not scheduled sections above per-day rows for the coming weeks"><figcaption></figcaption></figure>

## Creating New Tasks

The point is to capture a commitment the moment it is made, so there are several routes:

* **Press T** from any page to open the composer. On a company, contact or deal the task links to that record; on a meeting page it links to the meeting.
* **From a list** — click the **Next steps** cell in any list or board view that shows it and use **Add a task**. The task links to that record.
* **From the Tasks page** — **Add task** in the top right, with every setting available.
* **From an agent** — the **Add a task** action creates tasks when a trigger fires, after a call or a stage change for instance. With a [Notetakers](/settings/call-recorders.md) connected, action items discussed on a call arrive as tasks on the right record by themselves.

## Assigning Values to a Task

* **Title and linked records** — the field reads **"Task title - use @ to link companies, contacts, deals"**. Type `@` and a name to link the record.
* **Description** — optional, under the title.
* **Deadline** — the date picker in the toolbar, or natural language in the title: *"by Monday"*, *"next Tuesday"*, *"on Wednesday"*.
* **Assignees** — **Add participants** in the toolbar.
* **Priority** — **No priority**, **Urgent**, **High**, **Medium** or **Low**, changeable later.

## Where to see your tasks in Zero

**Tasks** in the left sidebar groups everything by deadline — **Overdue** first, then **Not scheduled**, then by month — so the order is the order to work in. It shows your own tasks by default; the user picker in the top right switches to **All users** or a teammate. **Filter tasks** narrows by **Assigned to**, **Deadline**, **Priority**, **Done**, or the linked **Companies**, **Contacts** and **Deals**. The **Not scheduled** group starts collapsed, and dragging one of those tasks onto a date gives it a deadline.

In context, tasks show up two ways: the **Next steps** property in any list or board view surfaces the open tasks on each record, and every company, deal and contact has a **Tasks** tab.

## Recommendations

The second tab on the Tasks page is **Recommendations** — the full queue of work Zero has spotted in your CRM, the same queue that feeds the cards on [Home](/features/home-view.md). It is grouped into categories such as **Follow-ups**, **Meetings**, **Customer issues**, **Churn risk**, **Reactivation**, **New opportunities** and **CRM upkeep**, and **Filter recommendations** narrows it.

Each row's **⋯** menu offers **Mark as done**, **Decline**, **Snooze** (until tomorrow or a date you pick), **Assign** to a teammate, and **Open in focus mode**, which hands the item to a chat so you can work it through. See [Recommendations](/features/home-view/recommendations.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zero.inc/features/tasks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.