> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/admin-corner/account-and-endpoint-management/contacts-field-guide/contact-types-overview.md).

# Contact Types Overview

Zoom provides several types of contacts for admins and users to manage within the platform, described in the sections below.

### <mark style="color:blue;">Company Directory</mark>

At the account level, the Company Directory, managed by admins, includes all users within the same Zoom account and organization. To further organize the directory, admins can create contact groups by either importing existing user groups or creating custom groups.

### <mark style="color:blue;">External Contacts</mark>

In addition to the Company Directory, individual users have the ability to add any external Zoom user as a contact. They can also streamline contact management by syncing their Zoom contacts with Google, Office 365, or Exchange through built-in contact integrations.

### <mark style="color:blue;">Personal Contacts</mark>

For accounts that do not use Google, Office 365, or Exchange, users can utilize the Personal Contacts feature. This allows them to maintain their own directory of external contacts, which can be populated either in bulk by uploading a CSV file or by adding contacts one at a time.

### <mark style="color:blue;">Shared External Contacts for Zoom Phone</mark>

Furthermore, Zoom Phone users benefit from an additional contact resource. Account owners and admins can create a shared External Contacts directory specifically for Zoom Phone, making it easier for users to access and manage relevant contacts.

By providing these diverse contact management options, Zoom enables both admins and users to effectively organize and access the contacts they need within the platform.


---

# 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://library.zoom.com/admin-corner/account-and-endpoint-management/contacts-field-guide/contact-types-overview.md?ask=<question>&goal=<user_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.