> 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/call-monitoring.md).

# 通話監控

以下各節說明 Zoom Contact Center 主管可使用的通話監控功能。通話監控已包含在 Zoom Contact Center 中，不需要額外的授權或附加元件。

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

每次互動一次只能由一位主管監控。兩位主管可以分別監控不同的對話，但無法同時監控同一段對話。
{% endhint %}

如需更多資訊，請參閱 Zoom 支援中心，了解如何 [監控互動](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0062852).

### 選取要監控的對話

在 Zoom Workplace 應用程式中有進行中工作階段的主管，可以前往 **開啟的互動** 索引標籤，查看所有未結束的互動。該索引標籤位於 **互動** 選單中。

接著，可在各個通道索引標籤中查看所有進行中的互動，包括 **語音**, **視訊**, **訊息**和 **電子郵件**.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXclHKeP3XzXRAzufaDbqxuZ6YS24l7UYtVa5Ae_fUr6Z8yLwW010g34MMgNG4I1GFU7_-ZoYXASMhl55zxjfdVMXFOMBAc042sDqPsZVfcjw4fvPthx8NC0nhMyhAPBrytrlk8-Cw?key=KRgQ_4ail54dHZXUquLpIw" alt=""><figcaption></figcaption></figure>

主管可以透過閱讀即時文字稿、聆聽、低聲提示或加入對話，來監控該對話。

### 聆聽

**聆聽** 對話時，主管可單向接收對話音訊，並依互動所使用的通道，閱讀或聽取客服專員與消費者之間的互動內容。

聆聽互動時，客服專員會在應用程式內收到通話正在被聆聽的通知 [（若已啟用通知）](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0058779)；否則，客服專員不會收到通知。

<div align="center" data-full-width="false"><figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdloxInukUvHJuyr3ttuAET9kkASpqGHDCqZbrUS1VDIW9Jc0YZnRcLBLD8I1uUVW0SRGuL00imEkIWETQaLuh4geYhMxtEhs8FGXe1yYFgUJPlHcYVEV6OjTiF6qCL0OZL9iLR?key=KRgQ_4ail54dHZXUquLpIw" alt="" width="375"><figcaption></figcaption></figure></div>

### 低聲提示

**低聲提示** 對話時，主管可以向互動中的客服專員提供單向音訊，而消費者不會聽見。這有助於在互動期間向客服專員提供指引或回饋，同時不影響消費者的體驗。

在對話中低聲提示時，客服專員會在應用程式內收到主管正在低聲提示的通知 [（若已啟用通知）](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0058779)；否則，客服專員不會收到通知。

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeZCxnCYCX1xgMVSsma5j5mbzBJbcOZE6HXfvtbAcMmLv1T7U_zAYhfr1OnRdrw7c-UCVw9jYf768WUbmGJiXkB8mKJqjxG9W3oc_a9jJ1NiIbtn091JnQQGMmK3_dJbtt0ILeZug?key=KRgQ_4ail54dHZXUquLpIw" alt="" width="375"><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/call-monitoring.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.
