> 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/expert-insights/configuring-agent-occupied-rules/implementation-best-practices.md).

# 實作最佳實務

### <mark style="color:藍色;">定義您的業務需求</mark>

在設定規則之前，先確定全通路對您的營運而言代表什麼：

**關鍵問題**:

* 哪些通路應計入判定客服人員忙碌或已被占用？
* 某些通路（例如語音／視訊）是否應始終優先於其他通路（例如訊息、電子郵件）？
* 通路占用狀態應按各通路獨立評估，還是跨多個通路合併評估？
* 您的客服人員是否能在進行語音通話時同時處理訊息互動，還是這種多工會影響他們提供的客戶服務品質？

您的規則應反映實際服務標準，而不只是技術能力。請在考量客服人員效率的同時，也納入對客戶體驗的影響。

### <mark style="color:藍色;">使用範本以確保一致性</mark>

為不同客服角色建立使用者範本，內容包括：

* 各通路適當的互動容量設定
* 占用規則設定
* 在相似角色間一致套用

#### 新進人員範本範例

<div align="left"><figure><img src="https://2668295848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FctBXUMeBy4rtLMmMkKRG%2Fuploads%2Fgit-blob-f9c62b7d291a5336d7d080afb8a2ffd5a23bbcb3%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure></div>

#### 通路設定範例

每個使用者範本都可指定完整的通路設定互動容量設定。

<div align="left"><figure><img src="https://2668295848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FctBXUMeBy4rtLMmMkKRG%2Fuploads%2Fgit-blob-b5cf098820c046bb092d2037321c2c74d562bee3%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure></div>

使用範本的好處包括：

* 跨客服群組的一致設定
* 簡化新進客服人員的到職訓練
* 當業務需求變更時，更容易進行批次更新


---

# 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/expert-insights/configuring-agent-occupied-rules/implementation-best-practices.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.