> 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/prospect-import-for-brands/prospect-import-explained.md).

# 潜客导入说明

潜在合作伙伴导入功能让您能够在平台内轻松处理大量潜在合作伙伴名单。您可以使用潜在合作伙伴导入，将新潜在合作伙伴添加到招募中，或将其他平台上的现有合作伙伴迁移到 impact.com。您还可以结合使用 [电子邮件工作流模板](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/email-workflows/create-and-manage-email-workflows.md) ，自动接受新合作伙伴和创作者加入您的项目。

## 运作方式

1. 只需创建一个包含您的潜在合作伙伴的 CSV 文件，并将其上传到 impact.com 平台。要了解如何导入潜在合作伙伴，请参阅 [将潜在合作伙伴批量导入到您的项目中](/brand/zh/what-would-you-like-to-learn-about/platform-features/prospect-import-for-brands/bulk-import-prospects-to-your-program.md).
2. 潜在合作伙伴导入完成后，您将收到一封包含导入摘要的电子邮件确认。您可以在这里查看是否有任何可能需要修复的错误。
3. 当您的潜在合作伙伴已进入 impact.com 平台并分组后，您可以将它们与一个 [工作流](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/email-workflows/create-and-manage-email-workflows.md) 配对，该工作流会在潜在合作伙伴注册后自动将其接受加入您的项目。

{% hint style="success" %}
**注意：** 虽然此功能主要用于导入潜在合作伙伴，但您也可以将其他平台上的现有合作伙伴迁移到 impact.com。为此，在导入时将现有合作伙伴分配到某个组中，然后将该组与自动接受工作流配对，以便立即将他们引入您的项目。
{% endhint %}

## 它如何为您带来帮助

潜在合作伙伴导入可帮助您在无需额外工具或延迟的情况下扩大合作伙伴网络。

* **更快地引入合作伙伴**：在几分钟内上传完整的潜在合作伙伴名单，并立即开始与高价值合作伙伴和创作者互动。无需外部协助、手动流程或变通方法。
* **无需第三方招募工具**：将这些支出用于其他增长驱动因素，例如合作伙伴激励和营销活动。
* **事先测试您的文件**：使用试运行按钮测试是否存在错误、匹配账户，并查看哪些记录成功或失败。

## 限制

* 导入潜在合作伙伴时，您无法创建新组。请确保您已提前 [创建所需的任何组](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/partner-groups/create-and-manage-partner-groups.md) ，然后再导入您的潜在合作伙伴列表。如果您在文件中包含一个不存在的组，该记录将不会被导入，并且您会在摘要报告中看到错误。
* 如果已导入潜在合作伙伴的邀请被分享给他人，而新申请者使用该共享邀请进行申请，则生成的申请不会与您最初导入的潜在合作伙伴关联。


---

# 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/prospect-import-for-brands/prospect-import-explained.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.