> 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/it/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/messaging/set-your-priority-messages-as-a-brand.md).
# Imposta i tuoi messaggi prioritari come brand
Puoi selezionare quali contatti verranno mostrati nella vista Priorità della tua casella di posta, consentendoti di evidenziare le conversazioni più importanti per te. Scopri di più su [l'invio di messaggi ai tuoi partner](/brand/it/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/messaging/send-a-message-to-a-partner.md).
#### Imposta i tuoi messaggi prioritari
1. Nella barra di navigazione superiore, seleziona  **\[Posta in arrivo]**.
2. Passa dalla visualizzazione dei contatti che hanno **Priorità**, e **Tutti** messaggi.
3. Seleziona  **Contrassegna come prioritario** pulsante per dare priorità a un contatto, oppure selezionalo di nuovo per rimuovere la priorità.
4. Per configurare la tua casella di posta prioritaria, nella pagina della posta in arrivo, seleziona  **\[Impostazioni]**, quindi configura la casella di posta prioritaria.
5. Seleziona **Salva**.
---
# 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/it/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.
