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

# Schritt 3: Die Erfahrungen Ihrer Advocate-Teilnehmer verwalten

Als Nächstes sollten Sie die  [Teilnehmererfahrung Ihrer Kundenfürsprecher anpassen](https://help.impact.com/brand/de/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/introduction-to-participant-experiences.md). Sie können Transaktions-E-Mails an Ihre Kundenfürsprecher und an alle Personen senden, die sie empfehlen. Ihr Programm ist zunächst mit Standardversionen der Programm-E-Mails eingerichtet. Wir empfehlen Ihnen jedoch,  [Ihre Programm-E-Mails anzupassen](https://help.impact.com/brand/de/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/email-experiences/create-and-customize-advocate-program-emails.md) , damit die Informationen für Ihr Programm und Ihr Produkt relevant sind und persönlicher wirken.

Als Nächstes passen Sie Ihre  [Programm-Widgets](https://help.impact.com/brand/de/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences.md)  oder  [Microsites](https://help.impact.com/brand/de/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences.md) an. Ein Programm-Widget oder eine Microsite ist für Ihre Teilnehmer der wichtigste Zugang zu Ihrem Empfehlungsprogramm. Widgets und Microsites greifen die Botschaften Ihres Empfehlungsprogramms im Design Ihrer Marke auf und bieten Ihren Kundenfürsprechern einen Ausgangspunkt, um Empfehlungen auszusprechen.


---

# 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/de/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.
