> 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。您还可以将此功能与 [电子邮件工作流模板](https://help.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 平台。了解如何导入潜在合作伙伴，请参阅 [批量导入潜在合作伙伴到您的项目](https://help.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 平台并完成分组后，您可以将他们与一个 [工作流](https://help.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 %}

## 对您的益处

“潜在合作伙伴导入”功能可帮助您在无需额外工具、也无需等待的情况下拓展合作伙伴网络。

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

## 限制

* 导入潜在合作伙伴时，您无法创建新群组。请确保在导入潜在合作伙伴名单之前，已 [创建所需的群组](https://help.impact.com/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.
