> 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/ja/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/messaging/set-your-priority-messages-as-a-brand.md).
# ブランドとして優先メッセージを設定する
受信トレイの「優先」ビューに表示する連絡先を選択でき、あなたにとってより重要な会話を強調表示できます。詳しくはこちら [パートナーにメッセージを送る](/brand/ja/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/ja/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.
