> 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/meeting-prep.md). # Meeting Prep The half hour before a call is usually spent digging through old threads. Zero does that digging in advance: for every upcoming external meeting it writes a **meeting prep** covering the companies, the deal status and the people in the room. ## When a prep is generated You don't ask for it. A meeting qualifies if it has **external participants** and real company context — either it is linked to a company in your CRM, or at least one attendee uses a company email domain. Personal domains like gmail.com and your own workspace's domains don't count, and without that context the prep is skipped. Once a prep exists, new CRM activity involving its companies or attendees refreshes it, so it does not go stale between now and the call. A qualifying meeting with no prep yet can be generated on demand. ## Where you see the prep **Home sidebar** — in the **Calendar** tab, a meeting with a ready prep shows a short summary under it. Click the meeting for its detail view, with a **Meeting prep** section and an **Open event** link to the full calendar event. **Calendar event page** — the full prep lives in the **Meeting prep** tab of the calendar event, which only appears for external meetings and opens by default when there is something to show. Three sub-tabs: * **Overview** — an **Introduction**, the deal status and relationship summary per company, linked **Deals** (with values), the **Participants** grouped by company (with titles and LinkedIn links), and **Sources** — the CRM records the prep was built from. * **Company & deal status** — firmographics (**Industry**, **Employees**, **Last funding**), a company description, **Technologies**, **Goals & pains**, **Risks & objections**, **Open items**, **Focus for this meeting**, a **Notes recap**, and a **Company background** deep dive with **Recent signals**, **Useful context**, and linked **Online sources**. * **Participants** — a profile card for each external participant, plus any **Other attendees**. ## Generating a prep manually Open the meeting's **Meeting prep** tab and click **Generate prep**. It runs in the background and can take a few minutes — the tab shows **"Starting your brief…"**, then **"Preparing your brief…"** — while Zero researches the companies and participants. Internal meetings are rejected outright, and a meeting with no external company context keeps showing **"No meeting prep for this meeting"**. ## What goes into a prep Zero builds it from your history with the meeting's companies and attendees — past meetings, email threads, LinkedIn conversations, notes, tasks, issues, invoices and deals — plus public web research on the external companies and people. The **Sources** section on the Overview tab lists the CRM records behind it, linked back to the deals, meetings, emails and LinkedIn threads. Web findings sit under **Company background** with their **Online sources**. Participants saved as contacts in Zero show richer detail: title, avatar, LinkedIn profile and position history. You can also ask the chat on [Home](/features/home-view.md) to prepare your whole day — "Help me prepare today's meetings" — and it pulls the ready preps into one scannable brief. ## FAQ **Why don't I see a Meeting prep tab on a meeting?**\ The meeting has no external participants — preps are only available for external meetings. **Why does it say "No meeting prep for this meeting"?**\ Either the prep hasn't been generated yet (use **Generate prep** to request one on demand), or Zero found no real external company context — the attendees are on personal mail domains or your own company's domains and the meeting isn't linked to a CRM company. **Why is a participant missing details?**\ That participant likely isn't saved as a contact in Zero. Add them as a contact to pull in their title, LinkedIn profile, and history next time the prep refreshes. --- # 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/meeting-prep.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.