> 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/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/introduction-welcome-to-impact.com/step-3-partner-engagement.md).

# Step 3: Partner Engagement

## Plan your outreach <a href="#plan-your-outreach-0-0" id="plan-your-outreach-0-0"></a>

Plan a series of persistent, value-driven [outreach emails](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/email-workflows/create-and-manage-email-workflows.md). Keep it concise and focus on the benefits of participating in your program, such as the higher payout rates, longer cookie window, and any performance bonuses.

Sweeten the deal with a sign-on bonus or a temporary rate increase to drive initial adoption. [Scheduled Terms](/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/set-limited-time-payouts-with-scheduled-terms.md) or [Product Boost](/brand/what-would-you-like-to-learn-about/beta-product-boost/product-boost-campaign-management/create-a-product-boost-campaign.md) can help you do this.

## Share relevant news <a href="#section-id23524846371987" id="section-id23524846371987"></a>

It’s important to keep your partners in the loop regarding promotions, product/feature launches, company updates, etc. impact.com’s [Newsletters](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/introduction-to-newsletters.md) feature is the easiest way to do this while also increasing partner engagement and productivity.

## Educate partners <a href="#section-id235248464024764" id="section-id235248464024764"></a>

Use your [*Resources*](https://app.impact.com/secure/advertiser/engage/ads/manage-resources-flow.ihtml) page to share [training materials and educational assets](/brand/what-would-you-like-to-learn-about/platform-features/ads/requests-from-partners/create-a-resource-to-share-with-partners.md) that help partners market your Amazon products effectively and generate sales. Link out to your *Resources* page in your initial welcome message and any scheduled newsletters.

Feel free to share relevant help documentation to make sure partners understand how to promote your products and what [best practices](https://help.impact.com/partner/what-would-you-like-to-learn-about/seller-partnerships/amazon-seller-partnerships/best-practices-for-seller-partners) will get them the most success.


---

# 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/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/introduction-welcome-to-impact.com/step-3-partner-engagement.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.
