> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/email-notification/best-practice.md).

# 最佳实践

## 以下是有效使用电子邮件通知的一些最佳实践：

* \*\*设计清晰、信息明确：\*\*确保通知消息清晰且信息明确。使用简洁的语言传达通知的核心内容，并在必要时提供明确的说明或行动号召。
* \*\*避免通知过载：\*\*谨慎选择通知的触发条件，避免向用户发送过多不必要的通知。确保通知只在相关事件发生时触发，并为接收者提供实际价值。
* \*\*设置优先级：\*\*如果通知有不同的优先级，请确保在设置中体现出来。例如，可以区分紧急通知和不太重要的通知，并采取相应措施。
* \*\*定期更新电子邮件地址：\*\*定期检查并更新用户的电子邮件地址，确保通知发送给正确的接收者。员工变动或职责变更时，这一点尤为重要。
* \*\*个性化：\*\*如果可能，在通知中加入接收者的姓名和其他相关信息，使通知更具吸引力，并帮助用户认真对待通知。
* \*\*收集反馈：\*\*定期征求用户反馈，确保通知符合他们的需求且有效。调整通知设置时，请考虑这些反馈。
* \*\*测试和监控：\*\*定期测试通知系统，确保其正常运行，并监控其表现，以便及早发现和解决问题。

遵循这些最佳实践，可以确保电子邮件通知有效运行，并帮助贵组织顺畅地沟通与协作。


---

# 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://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/email-notification/best-practice.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.