> 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/admin-experience/auto-qm-configuration.md).

# 自動 QM 設定

管理員可以從下列項目的 **品質管理** Zoom Contact Center 設定中的索引標籤。

若要設定 Auto QM：

1. 在 [**管理中心**](https://zoom.com/account)中，前往 **CX 管理** → **聯絡中心** → **品質管理** → **新增自動化**.
2. 使用下列項目定義規則條件：
   * 指標，包括：
     * 電話號碼
     * 姓名
     * 佇列
     * 結果分類
     * 互動分數
     * 情緒分數
     * 管道
     * 代理人
     * 持續時間
     * 從
     * 至
     * 語言
     * 方向
     * 主題
     * 指標
   * 情緒
3. 選取評估動作：
   * 指派給評估者
   * 使用 AI 評分
   * 排入人工審查佇列
4. 定義評估時間範圍：
   * 即時
   * 每日
   * 有上限
   * 以及更多

![具備評分規則邏輯的 QM 自動化使用者介面](https://2668295848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FctBXUMeBy4rtLMmMkKRG%2Fuploads%2Fgit-blob-776f2e20beb73ebdeeedecfc84f47bd8bd73772b%2Fautomation_rule_setup.png?alt=media)

## 授權詳細資料

Auto QM 可作為下列項目中的一項功能： **Zoom Quality Management** 模組，這是可選的附加元件，適用於 **Zoom Contact Center**.

Auto QM 內含於 Zoom Contact Center Elite，或可作為獨立的每席授權購買。必須啟用 Zoom Quality Management 模組，Auto QM 才能運作。

如需授權或啟用詳細資料，請聯絡您的 Zoom 帳戶團隊。


---

# 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/admin-experience/auto-qm-configuration.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.