> 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/technical-library/zh/guan-li-yuan-zhuan-qu/account-and-endpoint-management/contacts-field-guide/contact-types-overview.md).

# 联系人类型概述

Zoom 为管理员和用户提供了几种类型的联系人，供其在平台内管理，下面的章节中进行了说明。

### <mark style="color:蓝色;">公司目录</mark>

在账户级别，由管理员管理的公司目录包含同一 Zoom 账户和组织内的所有用户。为了进一步组织目录，管理员可以通过导入现有用户组或创建自定义组来创建联系人组。

### <mark style="color:蓝色;">外部联系人</mark>

除了公司目录之外，单个用户还可以将任何外部 Zoom 用户添加为联系人。他们还可以通过内置联系人集成，将自己的 Zoom 联系人与 Google、Office 365 或 Exchange 同步，从而简化联系人管理。

### <mark style="color:蓝色;">个人联系人</mark>

对于不使用 Google、Office 365 或 Exchange 的账户，用户可以使用个人联系人功能。这使他们能够维护自己的外部联系人目录，该目录既可以通过上传 CSV 文件批量填充，也可以一次添加一个联系人。

### <mark style="color:蓝色;">适用于 Zoom Phone 的共享外部联系人</mark>

此外，Zoom Phone 用户还可受益于一个额外的联系人资源。账户所有者和管理员可以专门为 Zoom Phone 创建一个共享的外部联系人目录，从而让用户更轻松地访问和管理相关联系人。

通过提供这些多样化的联系人管理选项，Zoom 使管理员和用户都能在平台内高效地组织和访问他们所需的联系人。


---

# 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/technical-library/zh/guan-li-yuan-zhuan-qu/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.