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

# Zoom Contact Center 報表與即時分析

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

如需更多資訊，請參閱 [分析與報表](https://library.zoom.com/technical-library/zh-tw/shang-wu-fu-wu/zoom-contact-center/zoom-customer-experience/analytics-and-reporting.md) 一節。
{% endhint %}

### 看板特別說明

看板是一種數位顯示畫面，可即時更新聯絡中心的關鍵績效指標，例如通話量、等候時間和客服人員的可用狀態。看板讓主管和客服人員都能清楚掌握中心的狀態與整體績效，通常會公開顯示，方便整個團隊監控。

鑑於看板對掌握營運狀況的重要性，本節特別介紹「報表與即時分析」中的重要功能： [即時看板](https://library.zoom.com/technical-library/zh-tw/shang-wu-fu-wu/zoom-contact-center/zoom-customer-experience/analytics-and-reporting/real-time-reports.md#wallboards) 。

如需 [自訂看板](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-tw/shang-wu-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.
