> 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/supervisor-experience/zoom-contact-center-reporting-and-real-time-analytics.md).

# Zoom 呼叫中心报表和实时分析

{% hint style="info" %}
**注**

请参阅 [分析和报告](/technical-library/zh/shang-ye-ban-fu-wu/zoom-contact-center/zoom-customer-experience/analytics-and-reporting.md) 用于提供更多信息的章节。
{% endhint %}

### 关于看板的特别说明

看板是数字显示屏，可提供关键呼叫中心绩效指标的实时更新，例如呼叫量、等待时间和坐席可用性。看板可以让主管和坐席清楚了解中心的状态和整体绩效，并且通常会公开展示，以便整个团队轻松监控。

鉴于看板在支持运营感知方面发挥着重要角色，本节专门用于强调 [实时看板](/technical-library/zh/shang-ye-ban-fu-wu/zoom-contact-center/zoom-customer-experience/analytics-and-reporting/real-time-reports.md#wallboards) 作为“报告和实时分析”部分中的一项重要功能/特性。

有关以下内容的更多信息，请参阅 Zoom 的支持中心： [自定义看板](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0059227).

{% hint style="info" %}
**注**\
看板需要身份验证才能访问并使用动态链接，从而导致 URL 定期更改。
{% endhint %}

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXd4_iiO65H63JU9W0wpkdQM58peUOEpjAkZbQLAKHS7N71r6IhK-eYT50KEx5w-kwkseFcJooSOP4dfHuYGnRyAkbj6uuFVVS3FzYWQpSpagpJ4aEvC7hPF2X7PQ7nIyUp2INSo?key=KRgQ_4ail54dHZXUquLpIw" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdDD3l2a8B92k5XSfwY76aMUOnUQOHrhzyu2iMe5zBCCxWtoelrpWZ4pC2PzVkLFqEojTjN796_2OnEbdIy4_GtF1ymovDVjR25N1Kd3XJdxfK2buGEWFV-AZwEr1K8d74wXHw2yA?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/supervisor-experience/zoom-contact-center-reporting-and-real-time-analytics.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.