> 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/platform-features/reach-out-to-partners/email-workflows/reactivate-partners-with-email-workflows.md).
# 使用电子邮件工作流重新激活合作伙伴
**升级**：此功能仅适用于某些 impact.com 版本或附加组件。如果您在账户中看不到它， [联系我们](https://app.impact.com/support/portal.ihtml?createTicket=true&) 以了解升级选项并获得访问权限。
使用自动化电子邮件工作流，简化并扩展合作伙伴重新激活流程。选择合作伙伴重新激活工作流模板，快速做几处修改，其余交给 impact.com 处理。
1. 从左侧导航菜单中，选择  **\[Engage] → 合作伙伴 → 自动化 → 工作流**.
2. 在右上角，选择 **创建工作流**，然后选择 **合作伙伴重新激活** 模板。
3. 查看模板中的每个电子邮件工作流。选择 **编辑** 开始使用。
4. 查看并批准合作伙伴细分条件。满意后，选择 **保存**.
* 在……中 *合作伙伴细分*，选择  **\[编辑]** 以查看默认细分条件。
* 该细分的 **预先配置的** 条件适用于大多数使用场景。您也可以选择 [进一步个性化它们](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/email-workflows/partner-segments-for-email-workflows-explained.md) 进一步设置触发重新互动尝试的条件——例如，如果合作伙伴的点击量、行动量、收入或佣金较低。
5. 设置一个 **发件人** 以及一个 **回复地址** 电子邮件地址。
* 在 *动作类型*，在 *编辑电子邮件* 字段中，选择  **\[编辑]** 中指定电子邮件地址。然后，选择 **完成**.
6. 选择 **保存** 以返回电子邮件工作流设置界面。完成所有电子邮件工作流的自定义后，选择 **激活工作流** 以启动它们！
就这样！我们会联系您选择的合作伙伴，重新与他们建立互动。
{% hint style="info" %}
**想了解自动化工作流还能做什么？** 查看我们关于以下内容的文档： [创建和管理电子邮件工作流](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/email-workflows/create-and-manage-email-workflows.md) 和 [自动化决策](/brand/zh/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/create-workflows-to-automatically-process-partner-applications.md) 关于合作伙伴申请！
{% endhint %}
---
# 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/platform-features/reach-out-to-partners/email-workflows/reactivate-partners-with-email-workflows.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.
