> 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/analytics-and-reporting/real-time-reports.md).

# 舊版 Zoom Contact Center 即時報表

以下即時報表可提供 Zoom Contact Center 代理人、主管和帳戶管理員的即時詳細資訊；不過，若使用自訂角色，報表的可用性可能會受到使用者角色權限影響。

{% hint style="danger" %}
此內容僅適用於 **尚未** 從舊版 Zoom Contact Center 報表遷移至 [CX Analytics](https://library.zoom.com/technical-library/zh-tw/shang-wu-fu-wu/zoom-contact-center/zoom-customer-experience/analytics-and-reporting/cx-analytics.md) 架構的帳戶。
{% endhint %}

### 代理人報表

即時代理人報表可讓管理員即時監控代理人資訊，例如代理人的可用狀態和加入／退出設定。主管也可以存取這些資料，但僅限其所屬佇列中的代理人。具備適當權限的使用者可透過 Zoom Web 入口網站或 Zoom Workplace 桌面應用程式檢視這些資訊，兩個平台提供的詳細內容相同。

如需詳細資訊，請參閱 Zoom 支援中心的 [即時代理人報表](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0061938).

### 佇列分析報表

即時佇列分析報表可讓帳戶管理員和主管透過動態即時儀表板追蹤互動情形、佇列和代理人活動。此報表可全面檢視所有已設定的聯絡管道，並深入呈現特定管道和佇列的資訊，包括代理人的可用狀態和加入／退出狀態。經授權的使用者可透過 Zoom Web 入口網站或 Zoom Workplace 桌面應用程式存取這些資料，兩個平台提供的資訊相同。

如需詳細資訊（包括各項目的明細），請參閱 Zoom 支援中心的 [即時佇列分析](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0058012) 報表。

### 資訊看板

Zoom Contact Center 提供可自訂的資訊看板，讓主管、管理員和獲授權的代理人監控並呈現聯絡中心的重要績效指標和營運資料。資訊看板介面靈活，可依需求選擇並排列小工具，讓您立即存取通話量、等候時間、平均處理時間和代理人績效等重要資訊。資訊看板會顯示過去 24 小時的即時資料，也可透過 Zoom Rooms 數位看板展示，進一步提升資訊的可見度和易用性。

如需詳細資訊，請參閱 Zoom 支援中心的 [自訂 Zoom Contact Center 資訊看板](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0059227) 以及 [Zoom Contact Center 指標詞彙表](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0061948).


---

# 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/analytics-and-reporting/real-time-reports.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.
