> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/messaging/set-your-priority-messages-as-a-brand.md).
# 作为品牌设置优先消息
您可以选择哪些联系人会显示在收件箱的优先视图中，从而突出显示对您更重要的对话。了解更多关于 [给您的合作伙伴发送消息](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/messaging/send-a-message-to-a-partner.md).
#### 设置您的优先消息
1. 在顶部导航栏中，选择  **\[收件箱]**.
2. 在查看以下联系人的视图之间切换： **优先级**，以及 **全部** 消息。
3. 选择  **标记为优先** 按钮可将联系人设为优先，或再次选择以取消优先。
4. 要设置优先收件箱，请在收件箱页面选择  **\[设置]**，然后设置优先收件箱。
5. 选择 **保存**.
---
# 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://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/messaging/set-your-priority-messages-as-a-brand.md?ask=&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.
