# 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: 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:

```
GET https://library.zoom.com/admin-corner/account-and-endpoint-management/contacts-field-guide/contact-types-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.