sales-apollo

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Apollo.io Platform Help

Apollo.io平台帮助

Help the user with Apollo.io platform questions — from configuration and CRM sync through analytics, dialer, API, and credit management.

为用户提供Apollo.io平台相关问题的帮助——从配置、CRM同步到分析、拨号器、API及信用管理等所有方面。

Step 1 — Gather context

步骤1 — 收集上下文

Ask the user:

What area of Apollo do you need help with?
- A) Prospecting & Search — finding and filtering leads (route to
```
/sales-prospect-list
```
  )
- B) Enrichment — getting emails, phones, firmographic data (route to
```
/sales-enrich
```
  )
- C) Sequences — outbound email/call sequences (route to
```
/sales-apollo-sequences
```
  for Apollo mechanics,
```
/sales-cadence
```
  for strategy)
- D) Intent & Signals — buying intent, job changes, lead scoring (route to
```
/sales-intent
```
  )
- E) Dialer — click-to-call, parallel dialing, call recording
- F) Analytics — reports, dashboards, sequence performance
- G) CRM Sync — Salesforce/HubSpot integration, field mapping, sync issues
- H) Chrome Extension — LinkedIn prospecting, website visitor identification
- I) Credits & Billing — credit management, usage, plan limits
- J) API & Integrations — REST API, Zapier, webhooks
- K) Admin — user management, teams, permissions, SSO
- L) Something else — describe it
What's your role?
- A) Sales rep / AE / BDR
- B) Sales manager / team lead
- C) RevOps / Sales Ops
- D) Admin / IT
- E) Founder / solo seller
- F) Other
What are you trying to accomplish? (describe your specific goal or question)

If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.

Note: If the user needs one of the specialized skills, route them there with a brief explanation of why that skill is a better fit.

向用户询问：

你需要Apollo哪个领域的帮助？
- A) 潜在客户开发与搜索——查找和筛选线索（转至
```
/sales-prospect-list
```
  ）
- B) 信息补充——获取邮箱、电话、企业属性数据（转至
```
/sales-enrich
```
  ）
- C) 外呼序列——邮件/电话外呼序列（Apollo操作机制转至
```
/sales-apollo-sequences
```
  ，策略设计转至
```
/sales-cadence
```
  ）
- D) 意向与信号——购买意向、职位变动、线索评分（转至
```
/sales-intent
```
  ）
- E) 拨号器——点击拨号、并行拨号、通话录音
- F) 分析——报表、仪表盘、序列绩效
- G) CRM同步——Salesforce/HubSpot集成、字段映射、同步问题
- H) Chrome扩展程序——领英潜在客户开发、网站访客识别
- I) 信用与账单——信用额度管理、使用情况、计划限制
- J) API与集成——REST API、Zapier、Webhooks
- K) 管理员——用户管理、团队、权限、SSO
- L) 其他——请描述具体需求
你的角色是什么？
- A) 销售代表/AE/BDR
- B) 销售经理/团队主管
- C) 营收运营/销售运营
- D) 管理员/IT人员
- E) 创始人/独立销售
- F) 其他
你想要达成什么目标？（描述你的具体目标或问题）

**如果用户的请求已经提供了大部分上下文，可直接跳至相关步骤。**先基于合理假设给出最佳答案（需明确说明假设），然后仅询问最关键的1-2个澄清问题——不要要求用户提供完整上下文才给出回应。

注意：如果用户需要的是某类专项技能的帮助，请引导至对应技能并简要说明为何该技能更合适。

Step 2 — Route or answer directly

步骤2 — 转至对应技能或直接解答

If the request maps to a specialized skill, route:

List building / prospecting →
```
/sales-prospect-list
```
Contact enrichment / data hygiene →
```
/sales-enrich
```
Intent signals / lead scoring →
```
/sales-intent
```
Sequence strategy / cadence design →
```
/sales-cadence
```
Apollo sequence mechanics →
```
/sales-apollo-sequences
```

Otherwise, answer directly from platform knowledge using the reference below.

如果用户的请求对应某类专项技能，进行跳转：

列表构建/潜在客户开发 →
```
/sales-prospect-list
```
联系人信息补充/数据清理 →
```
/sales-enrich
```
意向信号/线索评分 →
```
/sales-intent
```
序列策略/外呼节奏设计 →
```
/sales-cadence
```
Apollo序列操作机制 →
```
/sales-apollo-sequences
```

否则，直接基于以下平台知识库内容进行解答。

Step 3 — Apollo platform reference

步骤3 — Apollo平台参考指南

Provide module-by-module guidance based on the user's area:

根据用户的需求领域，提供分模块指导：

Dialer

拨号器

What it is: Built-in click-to-call and parallel dialer with call recording and disposition tracking
Key concepts: Click-to-call, parallel dialer (call multiple numbers simultaneously), call recording, voicemail drop, call dispositions, local presence
Plan requirements: Dialer available on Professional+; international dialing on Organization plan
Common configs: Caller ID setup, recording consent settings, voicemail drop recordings, disposition lists, parallel dialer settings
Best practices: Use local presence for higher connect rates, always set call dispositions for analytics, enable recording for coaching

功能介绍：内置点击拨号和并行拨号功能，支持通话录音和通话状态追踪
核心概念：点击拨号、并行拨号（同时拨打多个号码）、通话录音、语音信箱留言、通话状态、本地号码显示
计划要求：拨号器功能需Professional+及以上套餐；国际拨号需Organization套餐
常见配置：来电显示设置、录音同意设置、语音信箱留言录制、通话状态列表、并行拨号设置
最佳实践：使用本地号码显示提高接通率，始终设置通话状态以便分析，启用录音用于销售培训

Analytics & Reporting

分析与报表

What it is: Built-in dashboards for team and individual performance across sequences, calls, and pipeline
Key concepts: Pre-built dashboards, custom dashboards, sequence analytics, email analytics, call analytics, team goal tracking
Common reports: Sequence performance (open/reply rates), team activity (emails sent, calls made, meetings booked), pipeline creation, deliverability monitoring
Best practices: Monitor deliverability weekly, track leading indicators (activities) not just lagging (revenue), use sequence analytics to identify top-performing messaging

功能介绍：内置仪表盘，支持查看团队及个人在序列、通话、销售漏斗等方面的绩效
核心概念：预构建仪表盘、自定义仪表盘、序列绩效分析、邮件分析、通话分析、团队目标追踪
常见报表：序列绩效（打开/回复率）、团队活动（发送邮件数、拨打通话数、预约会议数）、销售漏斗创建、送达率监控
最佳实践：每周监控送达率，追踪领先指标（活动量）而非仅滞后指标（营收），利用序列绩效分析识别最优话术

CRM Sync

CRM同步

Native CRM integrations: Salesforce (bi-directional), HubSpot (bi-directional), Pipedrive, Zoho, Dynamics 365
Key concepts: Field mapping, sync direction (Apollo→CRM, CRM→Apollo, bi-directional), sync frequency, conflict resolution
Common issues: Duplicate records, field mapping mismatches, sync lag, permission errors
Troubleshooting: Check Settings > Integrations > CRM for sync status and error logs. Verify field mappings match data types. Review conflict resolution rules.

原生CRM集成：Salesforce（双向同步）、HubSpot（双向同步）、Pipedrive、Zoho、Dynamics 365
核心概念：字段映射、同步方向（Apollo→CRM、CRM→Apollo、双向）、同步频率、冲突解决
常见问题：重复记录、字段映射不匹配、同步延迟、权限错误
排查方法：查看「设置 > 集成 > CRM」中的同步状态和错误日志。验证字段映射的数据类型是否匹配。检查冲突解决规则。

Chrome Extension

Chrome扩展程序

What it is: Browser extension for prospecting directly from LinkedIn and company websites
Key features: LinkedIn profile enrichment, company page prospecting, website visitor identification, one-click add to lists/sequences
Common issues: Extension not loading, LinkedIn rate limiting, data not matching
Best practices: Don't bulk-prospect too quickly on LinkedIn (risk of account restrictions), verify enriched data before adding to sequences

功能介绍：浏览器扩展程序，可直接在领英和公司网站上进行潜在客户开发
核心功能：领英个人资料信息补充、公司页面潜在客户开发、网站访客识别、一键添加至列表/序列
常见问题：扩展程序无法加载、领英限流、数据不匹配
最佳实践：不要在领英上过快批量开发潜在客户（有账号受限风险），添加至序列前先验证补充的数据

Credits & Billing

信用与账单

Credit types: Mobile credits (phone numbers), export credits (CSV downloads), data credits (enrichment), email credits (sending)
Key rules: Credits do NOT roll over month-to-month. Phone reveals cost ~8x email reveals in credit terms.
Common confusion: Search doesn't consume credits — only enrichment (revealing emails/phones) and export consume credits
Optimization: Enrich only qualified prospects, use bulk enrichment for efficiency, monitor usage in Settings > Usage

信用类型：移动信用（电话号码）、导出信用（CSV下载）、数据信用（信息补充）、邮件信用（发送邮件）
核心规则：信用额度不会结转至下一个月。获取电话号码消耗的信用额度约为获取邮箱的8倍。
常见误区：搜索不会消耗信用额度——只有信息补充（获取邮箱/电话）和导出操作会消耗信用额度
优化建议：仅为合格的潜在客户补充信息，使用批量信息补充提高效率，在「设置 > 使用情况」中监控信用消耗

Apollo data model

Apollo数据模型

Core entities in Apollo — understand these to navigate the UI, build reports, and work with the API:

Entity	What it represents	Key relationships
Person	An individual in Apollo's database (265M+)	Can be saved as a Contact
Contact	A person saved to your Apollo CRM	Belongs to an Account, can be added to Sequences
Account	A company/organization	Has many Contacts
Sequence	A multi-step outbound campaign	Has Steps (emails, calls, tasks), has enrolled Contacts
Deal	A sales opportunity	Linked to Contacts and Account
Task	An action item (call, email, LinkedIn, custom)	Linked to Contact
List	A saved collection of Contacts	Static or dynamic (saved search)

Apollo中的核心实体——理解这些实体有助于导航UI、构建报表及使用API：

实体	代表内容	关键关联
Person	Apollo数据库中的个人（超2.65亿条）	可保存为Contact
Contact	保存至你的Apollo CRM的个人	隶属于某个Account，可添加至Sequences
Account	公司/组织	包含多个Contact
Sequence	多步骤外呼营销活动	包含Steps（邮件、电话、任务），关联已加入的Contacts
Deal	销售机会	关联Contacts和Account
Task	行动项（电话、邮件、领英、自定义）	关联Contact
List	已保存的Contacts集合	静态或动态（已保存的搜索）

API & Integrations

API与集成

Full API reference: See
references/apollo-api-reference.md
for complete endpoint documentation, authentication details, and request/response examples.

For detailed API documentation including all endpoints, authentication, rate limits, credit consumption, and bulk operations, consult

references/apollo-api-reference.md

Quick reference: Base URL

https://api.apollo.io/api/v1/

, API key auth (

x-api-key

header), rate limits vary by plan. Key capabilities: people search, enrichment, contact/account CRUD, sequence management, deal management.

Always reference
references/apollo-api-reference.md
when answering API questions — point the user to it for the full endpoint catalog, request/response schemas, and rate limit details beyond what's covered inline here.

完整API参考：请查看
references/apollo-api-reference.md
获取完整的端点文档、认证详情及请求/响应示例。

如需包含所有端点、认证、速率限制、信用消耗及批量操作的详细API文档，请查阅

references/apollo-api-reference.md

。

快速参考：基础URL

https://api.apollo.io/api/v1/

，API密钥认证（

x-api-key

请求头），速率限制因套餐而异。核心功能：人员搜索、信息补充、联系人/账户增删改查、序列管理、销售机会管理。

回答API问题时请始终参考
references/apollo-api-reference.md
——引导用户查看该文档获取完整的端点目录、请求/响应 schema 及超出本文档范围的速率限制详情。

Using MCP tools for direct Apollo access

使用MCP工具直接访问Apollo

If you want Claude to interact with Apollo.io directly (search contacts, enrich records, manage sequences, update pipeline stages), you can install an MCP-based tool that gives Claude live API access.

Option 1: Composio — MCP server with natural language → Apollo API translation

bash

npx skills add composiohq/apollo-automation

Best for: Ad-hoc lookups, natural language queries ("find all VPs at Acme"), quick enrichment tasks. Composio handles auth and translates plain English into API calls.

Option 2: Membrane — Pre-built Apollo actions with direct API proxy

bash

npx skills add membranedev/apolloio

Best for: Structured workflows, bulk operations, pipeline management. Membrane provides typed actions for contacts, accounts, deals, sequences, tasks, and calls with authentication and rate limiting built in.

Both tools handle auth, pagination, and rate limits automatically — prefer them over raw API calls when possible. Use this skill (

/sales-apollo

) for platform knowledge and guidance; use the MCP tools when you need Claude to actually read or write Apollo data.

如果希望Claude直接与Apollo.io交互（搜索联系人、补充记录、管理序列、更新销售漏斗阶段），你可以安装一款基于MCP的工具，为Claude提供实时API访问权限。

选项1：Composio —— 支持自然语言转Apollo API请求的MCP服务器

bash

npx skills add composiohq/apollo-automation

最佳适用场景：临时查询、自然语言请求（如“查找Acme公司的所有副总裁”）、快速信息补充任务。Composio处理认证并将普通英语转换为API请求。

选项2：Membrane —— 预构建Apollo操作的直接API代理

bash

npx skills add membranedev/apolloio

最佳适用场景：结构化工作流、批量操作、销售漏斗管理。Membrane为联系人、账户、销售机会、序列、任务和通话提供类型化操作，内置认证和速率限制功能。

两款工具均自动处理认证、分页和速率限制——尽可能优先使用它们而非直接调用原始API。使用本技能（

/sales-apollo

）获取平台知识和指导；当需要Claude实际读取或写入Apollo数据时，使用MCP工具。

Admin & Settings

管理员与设置

User management: Roles, permissions, teams, seat allocation
SSO: Available on Organization plan (SAML)
Data management: Import/export, duplicate management, do-not-contact lists
Deliverability: SPF/DKIM/DMARC setup, sending domain management, Inbox Ramp Up

用户管理：角色、权限、团队、席位分配
SSO：仅Organization套餐支持（SAML）
数据管理：导入/导出、重复数据管理、禁止联系列表
送达率：SPF/DKIM/DMARC设置、发送域名管理、收件箱预热

Step 4 — Actionable guidance

步骤4 — 可执行指导

Based on the user's specific question:

Step-by-step instructions — numbered steps to accomplish their goal in Apollo
Configuration recommendations — specific settings to change, with where to find them (Settings > [section] > [page])
Common pitfalls — what can go wrong and how to avoid it
Verification — how to confirm the change worked
For API questions — always include a pointer: "For the full endpoint catalog, request/response schemas, and rate limits, see
```
references/apollo-api-reference.md
```
."

根据用户的具体问题：

分步说明——完成目标的编号步骤（在Apollo中操作）
配置建议——需修改的具体设置及位置（如「设置 > 板块 > 页面」）
常见陷阱——可能出现的问题及避免方法
验证方式——如何确认修改已生效
API问题相关——始终包含指引：“如需完整的端点目录、请求/响应schema及速率限制，请查看
```
references/apollo-api-reference.md
```
。”

Gotchas

注意事项

Don't confuse Apollo's database search with enrichment. Searching for people is free and doesn't consume credits. Enrichment (revealing emails/phones) consumes credits. Claude often generates workflows that search + enrich in one step without warning about credit costs.
Don't assume all Apollo features are available on all plans. Dialer requires Professional+, parallel dialing requires Organization, SSO requires Organization, custom reporting requires Organization. Always ask about the user's plan before recommending gated features.
Don't recommend the Chrome extension for bulk LinkedIn prospecting. LinkedIn aggressively rate-limits scraping. Prospecting too quickly via the extension can get the user's LinkedIn account restricted. Recommend Apollo's built-in search instead for bulk list building.
Don't treat Apollo's CRM as a replacement for Salesforce/HubSpot. Apollo has its own contact/account/deal objects, but most teams use it alongside a CRM, not instead of one. Sync configuration is critical — misconfigurations cause duplicates and data conflicts.
Don't generate raw API code when a UI walkthrough would suffice. Most Apollo users are salespeople, not developers. Default to UI instructions unless the user specifically asks for API/automation help.
Always cite the API reference file for API questions. When the user asks anything about the Apollo API — endpoints, authentication, rate limits, payloads, or integration code — you MUST include a pointer to
```
references/apollo-api-reference.md
```
in your response. Example: "For the complete API reference with all endpoints, authentication details, and request/response examples, see
```
references/apollo-api-reference.md
```
." Never answer an API question without this citation.

不要混淆Apollo数据库搜索与信息补充：搜索人员信息是免费的，不会消耗信用额度。信息补充（获取邮箱/电话）会消耗信用额度。Claude常生成将搜索与信息补充合并的工作流，但未提示信用成本，需注意。
不要假设所有Apollo功能对所有套餐开放：拨号器需Professional+套餐，并行拨号需Organization套餐，SSO需Organization套餐，自定义报表需Organization套餐。在推荐受限功能前，务必询问用户的套餐类型。
不要推荐使用Chrome扩展程序进行批量领英潜在客户开发：领英会严格限制抓取行为。通过扩展程序过快开发潜在客户可能导致用户的领英账号受限。建议使用Apollo内置的搜索功能进行批量列表构建。
不要将Apollo CRM视为Salesforce/HubSpot的替代方案：Apollo有自己的联系人/账户/销售机会对象，但大多数团队将其作为CRM的补充而非替代。同步配置至关重要——配置错误会导致重复数据和数据冲突。
当UI操作说明足够时，不要生成原始API代码：大多数Apollo用户是销售人员，而非开发人员。除非用户明确要求API/自动化帮助，否则默认提供UI操作说明。
回答API问题时务必引用API参考文档：当用户询问任何关于Apollo API的问题——端点、认证、速率限制、请求体或集成代码——必须在回复中包含指向
```
references/apollo-api-reference.md
```
的指引。示例：“如需包含所有端点、认证详情及请求/响应示例的完整API参考，请查看
```
references/apollo-api-reference.md
```
。”切勿在未引用该文档的情况下回答API问题。

Step 5 — Related skills

步骤5 — 相关技能

```
/sales-prospect-list
```
— Build targeted prospect lists using Apollo's search filters
```
/sales-enrich
```
— Enrich contacts with emails, phones, and firmographic data
```
/sales-intent
```
— Interpret buying signals and prioritize accounts
```
/sales-apollo-sequences
```
— Create and manage sequences in Apollo
```
/sales-cadence
```
— Design outbound cadence strategy (platform-agnostic)
```
/sales-salesloft
```
— Salesloft platform help (if using Salesloft instead of Apollo)
```
/sales-do
```
— Not sure which skill to use? The router matches any sales objective to the right skill. Install:
```
npx skills add sales-skills/sales --skills sales-do
```

```
/sales-prospect-list
```
—— 使用Apollo的搜索筛选器构建目标潜在客户列表
```
/sales-enrich
```
—— 为联系人补充邮箱、电话及企业属性数据
```
/sales-intent
```
—— 解读购买信号并优先处理高价值账户
```
/sales-apollo-sequences
```
—— 在Apollo中创建和管理序列
```
/sales-cadence
```
—— 设计外呼节奏策略（跨平台通用）
```
/sales-salesloft
```
—— Salesloft平台帮助（若使用Salesloft而非Apollo）
```
/sales-do
```
—— 不确定使用哪个技能？该路由可将任何销售目标匹配到合适的技能。安装方式：
```
npx skills add sales-skills/sales --skills sales-do
```

Examples

示例

Example 1: CRM sync troubleshooting

示例1：CRM同步排查

User says: "My Apollo-Salesforce sync keeps creating duplicate contacts" Skill does:

Identifies this as a CRM sync issue
Walks through sync settings, field mapping, and dedup rules
Recommends sync direction and conflict resolution settings Result: User has diagnosed and resolved the duplicate creation issue

用户提问：“我的Apollo-Salesforce同步一直在创建重复联系人” 技能处理：

识别为CRM同步问题
引导用户查看同步设置、字段映射及去重规则
推荐同步方向和冲突解决设置结果：用户已诊断并解决重复联系人问题

Example 2: Credit management

示例2：信用管理

User says: "I'm burning through my Apollo credits too fast" Skill does:

Reviews the user's plan and credit allocation
Identifies where credits are being consumed (enrichment vs export vs phone reveals)
Recommends credit optimization strategies (enrich only qualified prospects, use bulk enrichment, avoid unnecessary phone reveals) Result: User has a plan to optimize credit usage within their plan limits

用户提问：“我的Apollo信用额度消耗得太快了” 技能处理：

查看用户的套餐和信用分配
识别信用消耗的场景（信息补充 vs 导出 vs 获取电话号码）
推荐信用优化策略（仅为合格潜在客户补充信息、使用批量信息补充、避免不必要的电话号码获取）结果：用户获得了在套餐限制内优化信用使用的方案

Troubleshooting

常见问题排查

CRM sync conflicts

CRM同步冲突

Symptom: Duplicate records or data overwritten between Apollo and CRM Cause: Bi-directional sync with conflicting field mappings or missing dedup rules Solution: Review Settings > Integrations > CRM. Set sync direction per field. Enable duplicate detection. Use Apollo's dedup tool to merge existing duplicates.

症状：Apollo与CRM之间出现重复记录或数据被覆盖原因：双向同步的字段映射冲突或缺少去重规则 解决方案：查看「设置 > 集成 > CRM」。按字段设置同步方向。启用重复检测。使用Apollo的去重工具合并现有重复数据。

Chrome extension not working

Chrome扩展程序无法工作

Symptom: Extension doesn't load on LinkedIn or shows errors Cause: LinkedIn DOM changes, extension update needed, or browser conflicts Solution: Update the extension, clear browser cache, disable conflicting extensions. If on LinkedIn, check if you've hit LinkedIn's daily viewing limits.

症状：扩展程序在领英上无法加载或显示错误原因：领英页面结构变更、扩展程序需更新或浏览器冲突 解决方案：更新扩展程序、清除浏览器缓存、禁用冲突的扩展程序。若在领英上，检查是否达到领英的每日查看限制。

Deliverability issues

送达率问题

Symptom: Emails landing in spam or low open rates Cause: Missing SPF/DKIM/DMARC, sending volume too high too fast, or poor sender reputation Solution: Verify domain authentication in Settings > Email. Use Inbox Ramp Up for new mailboxes. Keep daily sending volume under 50/day per mailbox initially. Monitor the Deliverability Command Center.

症状：邮件进入垃圾邮箱或打开率低原因：缺少SPF/DKIM/DMARC配置、发送量过高过快或发件人声誉不佳 解决方案：在「设置 > 邮件」中验证域名认证。对新邮箱使用收件箱预热功能。初始阶段每个邮箱每日发送量控制在50封以内。监控送达率指挥中心。