> 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/home-view/recommendations.md). # Recommendations Nobody opens a CRM wanting to hunt for what needs doing. Recommendations are Zero's answer: a carousel on Home of work it has already found — a follow-up that is due, a meeting to prepare for, a record that has gone stale — each card naming the work and the contact or company behind it. Buttons above the carousel jump to a category and count what is in it: **Follow-ups**, **Meetings**, **Customer issues**, **Churn risk**, **Reactivation**, **New opportunities**, **CRM upkeep** and **Other**. Step through the cards with the chevrons on either side, or the **←** and **→** keys. ## Focus mode Clicking a card or **Start Focus mode** (**⌘ + Enter**) opens the middle card in a chat dedicated to it. The chat already has the recommendation as context, proposes what it would do, and shows how far through the queue you are — so the whole queue is one keyboard-driven pass rather than a series of page loads. * **↑** and **↓** move to the previous or next recommendation. * **⌘ + Enter** approves anything still pending and marks the recommendation done. The button above the chat spells out what it will do — for example **Send email & mark done**, or just **Mark done** when there is nothing to approve. * **⌘ + Del** declines the recommendation. **Snooze** puts it off until tomorrow or a date you pick, and **Assign** hands it to a teammate. * The category picker at the top switches which category you are working through. The full queue lives on the **Recommendations** tab of the [Tasks](/features/tasks.md) page. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.zero.inc/features/home-view/recommendations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.