> 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/manage-your-inbox-as-a-brand.md).

# 作为品牌管理收件箱

本文将通过介绍如何优先处理消息、按合作伙伴关系状态筛选等内容，来说明如何管理您的收件箱。

1. 在顶部导航栏中，选择 ![](/files/40d2791b1cde23ae9a3ed926f61f1a355d557ba7) **\[收件箱]**.
2. 选择 ![](/files/10d6aeb3c4f4273c23b60f22f6a36ab55be47c61) **\[筛选]** 通过筛选和标记不同状态的消息来优化您的收件箱。

<details>

<summary>设置消息线程状态</summary>

您可以设置消息状态，例如 *优先级*, *未读*，或 *垃圾信息* 在与特定合作伙伴沟通时。

| 消息状态                                                             | 说明                                                                                                                                                      |
| ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **标记为优先** ![](/files/cc981745ca9de525572e049c1e6cda34655c3a32)   | <p>您可以标记哪些联系人会显示在您的收件箱 <em>优先级</em> 视图中，从而突出显示对您更重要的对话。</p><p>• 了解更多关于如何 <a href="/pages/5e3b689ea2209ba701f09f484786bc2db8d48457">将您的优先消息设为品牌</a>.</p> |
| **标记为未读** ![](/files/c46af45ed38054207bea364019555922218ea1dd)   | 您可以将消息线程标记为 *未读*。在您的账户用户下次打开它之前，该线程会持续生成通知。                                                                                                             |
| **标记为垃圾信息** ![](/files/96ec758682b1f11347799fd3872671737ba24ec3) | 您可以将消息线程移至 *垃圾信息*。您将不再收到来自此消息线程的通知。                                                                                                                     |

</details>

<details>

<summary>搜索或筛选您的消息线程</summary>

* 您可以使用 **搜索栏** 在小组件顶部或您的 *收件箱*.
* 您只能从您的 *收件箱*。通过选择 ![](/files/e479ac02c3c47339b993d9cfadb1ce4541025fa1) **\[筛选]** 搜索栏旁边的，选择您要使用的筛选条件，然后选择 **应用**.

| 筛选器    | 说明                                                                                                                                                                             |
| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| 状态     | 为所有被标记为垃圾信息的消息进行筛选。这些是您已标记为垃圾信息的消息。                                                                                                                                            |
| 关系     | 选择您想查看消息线程的合作伙伴关系（例如， *已加入*）。                                                                                                                                                  |
| 合作伙伴规模 | 选择你要查看的 [合作伙伴规模](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/partner-management/partner-size-rating-criteria.md) 您想查看消息线程的。（例如， *大型*) |

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/messaging/manage-your-inbox-as-a-brand.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
