> 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/shang-ye-ban-fu-wu/zoom-contact-center/zoom-customer-experience/zoom-contact-center-components.md).

# 组件

本节概述随 Zoom 呼叫中心提供的核心组件。本节所提供的信息旨在从整体视角介绍相关概念，并帮助理解各个部分如何相互配合。考虑到这一点，读者应当注意：虽然从整体上看该产品很容易理解，尤其是在聚焦较大的基础设施部分时，但这些相同的部分通常由更小的部分组成，而这些小部分必须先构建。也就是说，本节内容以前向容量的方式介绍核心概念，但要使这些部分发挥作用，实际上必须反向构建它们。关于这一点的更多信息将在 [构建您的系统部分](/technical-library/zh/shang-ye-ban-fu-wu/zoom-contact-center/zoom-customer-experience/zoom-contact-center-components/building-your-system-within-zcc-advice.md).

### 概述

以下图表概述了 Zoom 呼叫中心的组件。第一张图以最广泛的术语对其组件进行了高级概览，旨在帮助读者对产品形成基础理解。第二张图则对相同组件进行了详细视图，展示底层部分如何共同构成产品的更大结构。

#### <mark style="color:蓝色;">概览图 - 高级别</mark>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcVlagFfF2J30zbW0r8gC17zmlkoQg_-rXCv7f_bPBcozxmhhIJha3WUBdWn3kS5vqLKa4KFHFUS6on7LOy3IIK-3NYL1cvmJ9A9sgCkriXWUAKFCEtf_yLUSL4SiXjpUkF5b-TkA?key=KRgQ_4ail54dHZXUquLpIw" alt=""><figcaption></figcaption></figure>

#### <mark style="color:蓝色;">概览图 - 详细级别</mark>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeAfjQOV_XUlkfVmlr5aqiMTwLYRgz8y4T8lUBi8U4wai-0n0HG4B6D3bMSwrH8wHeWZbIQ0sEGIkiGrTGUaQr38XIkg5AUy6Lx_w7qOi-s7FX2ObFkUHAuvtJIYvGNsJMmWsp5ww?key=KRgQ_4ail54dHZXUquLpIw" alt=""><figcaption></figcaption></figure>


---

# 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/shang-ye-ban-fu-wu/zoom-contact-center/zoom-customer-experience/zoom-contact-center-components.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.