> 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/shang-ye-ban-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://2325962437-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://2325962437-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/shang-ye-ban-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.