> 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/getting-started/key-concepts/records/contacts.md). # Contacts A contact is a person. They belong to at most one company, can be involved in any number of deals, and are what emails, meetings, sequences and LinkedIn messages attach to. Contacts are identified by their **Email**, and a contact can hold several addresses in **All Emails** — activity on any of them lands on the same record. You will not create most of them by hand: with **Auto-contact creation** on for a connected mailbox or calendar, Zero creates contacts from the people you email and meet, skipping your own domains. See [Mailbox Settings](/settings/mailbox-settings.md). ## What Zero fills in for you {% hint style="success" %} **A name or an email address is usually all you need.** Zero looks the person up and fills in the rest — including a missing **Email** or **Phone number**. {% endhint %} Enrichment only fills fields that are empty, so it never overwrites something you or a teammate typed. It can fill **Name**, **Email**, **Phone number**, **Title**, **LinkedIn**, **X**, **Location** and the contact's photo, plus the contact profile: **Positions** (their position history), **Current position since**, **Current company since**, **Education** and **Languages**. An address Zero already has gets verified, and the **Email** property then shows when. It runs automatically when a contact is created and again when you set or change their **Email** or **LinkedIn**, or assign a company to a contact with no email address; on import, unless you ask Chat to skip enrichment when it shows the import for approval; and on demand, by selecting contacts in a list and clicking **Run enrichment** in the floating toolbar, or the same button in the record header. An empty **Phone number** property also has its own **Find phone number** button. Enrichment uses credits, and the confirmation tells you the cost first. ## Adding contacts * **Manually** — **Add contact** at the top of any contact list (and of **Contacts**), from the command menu (**Cmd + K**, then **P**), or from the **⋯** menu of a company record's header (**Add contact to deal** on a deal). * **Mailbox and calendar sync** — automatic, as above. In the Inbox, **Add contacts from email** opens **Add contacts from inbox**, where you pick people from your mailbox by hand. * **From Lead Search** — select contacts in the results and use **Add to list or sequence**. See [Lead Search](/features/lead-search.md). * **Import** — CSV or a migration from another CRM. See [Data Import](/getting-started/data-import.md). * **Agents** — an agent action can create or update contacts. See [Agents](/features/agents.md). * **Chat, MCP and the API** — `add_contact` for Chat and MCP clients, `POST /api/contacts` for REST. See [MCP](/developers/mcp.md). ## Standard properties * **Name** (also **First name** and **Last name**), **Email**, **All Emails**, **Phone number**, **Title**, **LinkedIn**, **X**, **Location** * **Company** — the company the contact belongs to * **Owners**, **Deals**, **Lists**, **Sequences** * **Unsubscribed from all messaging** — the contact opted out of emails and sequences * **LinkedIn connections** — which of your team members are connected to them, with status and connection date * Enrichment properties from the contact profile, such as **Current position since**, **Current company since**, **Positions**, **Education** and **Languages** * The same activity roll-ups as companies: **First activity**, **Last activity**, **Last email**, **Last meeting**, **Next meeting**, **Next steps** * **Created at**, **Created by**, **Updated at**, **Updated by**, **External ID**, **Archived** Anything beyond this is a [custom property](/settings/custom-properties.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 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/getting-started/key-concepts/records/contacts.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.