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

# 第 3 步：合作伙伴沟通

## 规划你的外联 <a href="#plan-your-outreach-0-0" id="plan-your-outreach-0-0"></a>

规划一系列持续的、以价值为导向的 [外联邮件](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/email-workflows/create-and-manage-email-workflows.md)。保持简洁，重点突出参与你的计划所能带来的好处，例如更高的佣金率、更长的 Cookie 有效期以及任何绩效奖金。

通过提供签约奖金或临时提高费率来吸引他们，推动初始采用。 [定时条款](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/set-limited-time-payouts-with-scheduled-terms.md) 或 [产品加速](/brand/zh/what-would-you-like-to-learn-about/beta-product-boost/product-boost-campaign-management/create-a-product-boost-campaign.md) 可以帮助你做到这一点。

## 分享相关资讯 <a href="#section-id23524846371987" id="section-id23524846371987"></a>

让你的合作伙伴及时了解促销活动、产品/功能发布、公司动态等信息非常重要。impact.com 的 [新闻简报](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/introduction-to-newsletters.md) 功能是实现这一点的最简单方式，同时还能提升合作伙伴的参与度和工作效率。

## 教育合作伙伴 <a href="#section-id235248464024764" id="section-id235248464024764"></a>

使用你的 [*资源*](https://app.impact.com/secure/advertiser/engage/ads/manage-resources-flow.ihtml) 页面来分享 [培训材料和教育素材](/brand/zh/what-would-you-like-to-learn-about/platform-features/ads/requests-from-partners/create-a-resource-to-share-with-partners.md) ，帮助合作伙伴有效推广你的 Amazon 产品并带来销售。链接到你的 *资源* 页面，在你的初始欢迎信息和任何定期新闻简报中。

欢迎分享相关帮助文档，以确保合作伙伴了解如何推广你的产品以及哪些 [最佳实践](https://help.impact.com/partner/what-would-you-like-to-learn-about/seller-partnerships/amazon-seller-partnerships/best-practices-for-seller-partners) 做法能让他们最有可能成功。


---

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