> 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/pt-br/what-would-you-like-to-learn-about/advocate-program/introduction-welcome-to-advocate/step-3-manage-your-advocate-participant-experiences.md).

# Etapa 3: gerenciar as experiências dos participantes do seu Advocate

O próximo passo seria personalizar o seu defensor [experiência do participante](/brand/pt-br/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/introduction-to-participant-experiences.md). Você pode enviar e-mails transacionais para os seus defensores da marca e para qualquer pessoa que eles indiquem. Seu programa é configurado inicialmente com versões padrão dos e-mails do programa, mas recomendamos [personalizar os e-mails do seu programa](/brand/pt-br/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/email-experiences/create-and-customize-advocate-program-emails.md) para garantir que as informações sejam relevantes para o seu programa e produto e criar uma sensação mais personalizada.

Em seguida, vem a personalização dos seus [widgets do programa](/brand/pt-br/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences.md) ou [microssites](/brand/pt-br/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences.md). Um widget do programa ou microssite é a principal forma de os seus participantes acessarem e usarem o seu programa de indicação. Widgets e microssites reforçam a identidade da marca na comunicação do seu programa de indicação e dão aos seus defensores da marca um ponto de partida para fazer indicações.


---

# 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/pt-br/what-would-you-like-to-learn-about/advocate-program/introduction-welcome-to-advocate/step-3-manage-your-advocate-participant-experiences.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.