Enrich Contacts & Clean CRM Data

补充联系人数据与清理CRM数据

Help the user enrich contacts and companies with verified data, clean stale CRM records, and optimize their enrichment workflow. This skill is platform-agnostic but references Apollo.io as the primary tool. The same strategies apply to ZoomInfo, Clay, Lusha, Cognism, or any enrichment provider.

帮助用户为联系人和企业补充经过验证的数据、清理失效的CRM记录并优化数据补全工作流。本技能不绑定特定平台，但以Apollo.io作为主要参考工具，相关策略同样适用于ZoomInfo、Clay、Lusha、Cognism或任何数据补全服务商。

Step 1 — Gather context

步骤1 — 收集上下文

Ask the user:

What do you need to do?
- A) Enrich a list of contacts with emails/phones
- B) Enrich company/account records with firmographic data
- C) Clean up stale or incomplete CRM data
- D) Set up ongoing auto-enrichment
- E) Deduplicate contacts or accounts
- F) Verify existing email addresses before a campaign
- G) Other — describe it
How many records are involved?
- A) Under 100 (manual/one-time)
- B) 100-1,000 (batch job)
- C) 1,000-10,000 (bulk operation)
- D) 10,000+ (large-scale cleanup)
- E) Ongoing (continuous enrichment of new records)
What enrichment tool(s) do you have?
- A) Apollo.io
- B) ZoomInfo
- C) Clay
- D) Lusha / Cognism
- E) Clearbit / Breeze
- F) Multiple providers (waterfall)
- G) None yet — recommend one
What data do you need?
- A) Email addresses (verified/deliverable)
- B) Phone numbers (direct/mobile)
- C) Both email and phone
- D) Firmographic data (company size, revenue, industry, tech stack)
- E) All of the above

向用户询问：

你需要完成什么操作？
- A) 为联系人列表补充邮箱/电话
- B) 为企业/客户账户记录补充企业属性数据
- C) 清理失效或不完整的CRM数据
- D) 设置持续自动数据补全
- E) 对联系人或账户进行去重
- F) 在营销活动前验证现有邮箱地址
- G) 其他 — 请描述具体需求
涉及的记录数量是多少？
- A) 100条以下（手动/一次性操作）
- B) 100-1000条（批量任务）
- C) 1000-10000条（大规模操作）
- D) 10000条以上（大规模清理）
- E) 持续进行（对新记录进行实时数据补全）
你使用哪些数据补全工具？
- A) Apollo.io
- B) ZoomInfo
- C) Clay
- D) Lusha / Cognism
- E) Clearbit / Breeze
- F) 多个服务商（瀑布式补全）
- G) 尚未使用 — 需要推荐工具
你需要补充哪些数据？
- A) 邮箱地址（经过验证/可送达）
- B) 电话号码（直拨/手机）
- C) 邮箱和电话都需要
- D) 企业属性数据（公司规模、收入、行业、技术栈）
- E) 以上所有数据

Step 2 — Enrichment strategy

步骤2 — 数据补全策略

Choose the right approach based on volume and frequency:

根据记录数量和操作频率选择合适的方案：

Single-record enrichment

单条记录补全

When: Researching a specific prospect, manual prospecting
How: Look up individual records in your enrichment tool or via API
Credit cost: 1 credit per person (email), more for phone numbers
Best for: High-value ABM targets, executive-level contacts

适用场景：研究特定潜在客户、手动挖掘线索
操作方式：在数据补全工具中查询单个记录或通过API调用
额度成本：每条联系人邮箱补全需1个额度，电话补全额度更高
最佳用途：高价值ABM目标、高管级联系人

Batch enrichment

批量数据补全

When: Enriching a list before launching a campaign
How: Upload CSV or select records in-platform for bulk enrichment
Credit cost: 1 credit per record enriched (plan carefully)
Best for: Campaign prep, list cleaning before outreach

适用场景：营销活动启动前补充列表数据
操作方式：上传CSV文件或在平台内选择记录进行批量补全
额度成本：每条补全记录需1个额度（需谨慎规划）
最佳用途：营销活动准备、触达前的列表清理

Auto-enrichment

自动数据补全

When: Keeping CRM data fresh continuously
How: Set up rules to enrich new records on creation or on a schedule
Credit cost: Ongoing — budget credits monthly
Best for: Teams with steady lead flow who need data quality without manual effort

适用场景：持续保持CRM数据新鲜度
操作方式：设置规则，在新记录创建时或按计划对现有记录进行自动补全
额度成本：持续消耗额度 — 需按月规划预算
最佳用途：线索稳定流入、无需手动维护数据质量的团队

Waterfall enrichment

瀑布式数据补全

When: Single provider doesn't have enough coverage
How: Try Provider A first → if no result, try Provider B → then Provider C
Credit cost: Only pay for successful enrichments at each level
Best for: Maximizing coverage when targeting niche personas or international contacts
Tools: Clay is purpose-built for this; Lemlist has built-in waterfall enrichment; Apollo's waterfall enrichment is in beta; Yesware Prospector provides 100M+ contacts as an additional source; Reply.io has a built-in B2B database with 1B+ contacts and data credits for email/phone reveals; Woodpecker Lead Finder provides a B2B database with 1B+ leads and data credits for email finding

适用场景：单个服务商覆盖范围不足
操作方式：先尝试服务商A → 若无结果则尝试服务商B → 再尝试服务商C
额度成本：仅为每个环节成功补全的记录付费
最佳用途：针对细分人群或国际联系人时最大化覆盖范围
支持工具：Clay专为该场景打造；Lemlist内置瀑布式补全功能；Apollo的瀑布式补全处于测试阶段；Yesware Prospector提供1亿+联系人作为补充数据源；Reply.io内置10亿+联系人的B2B数据库及邮箱/电话查询额度；Woodpecker Lead Finder提供10亿+线索的B2B数据库及邮箱查询额度

Step 3 — Execute the enrichment

步骤3 — 执行数据补全

Pre-enrichment checklist

补全前检查清单

Deduplicate first: Remove duplicate records before enriching — don't pay to enrich the same person twice
Filter to qualified records only: Don't enrich contacts you'll never reach out to
Check existing data: Skip records that already have verified emails/phones
Estimate credit cost: Records × credit cost per record. Stay within budget.
Set enrichment scope: Choose which fields to enrich (email only is cheaper than email + phone + firmographic)

先去重：补全前移除重复记录 — 不要为同一联系人重复付费补全
仅筛选合格记录：不要为永远不会触达的联系人补全数据
检查已有数据：跳过已包含验证邮箱/电话的记录
估算额度成本：记录数 × 单条记录补全成本，确保在预算内
设置补全范围：选择需要补全的字段（仅邮箱比邮箱+电话+企业属性更便宜）

In Apollo.io

在Apollo.io中的操作

Single enrichment: Search for the person in Apollo's database → click to reveal email/phone (costs credits).

Bulk enrichment:

Select contacts in a list or search results
Click "Enrich" → choose fields to enrich
Apollo processes in background, results appear on records
Export enriched data or sync to CRM

CRM auto-enrichment:

Settings > Enrichment > Auto-Enrichment
Set rules: enrich new contacts on creation, enrich existing contacts on a schedule
Choose fields to enrich and credit budget per month
Monitor usage in Settings > Usage

API enrichment:

```
POST /people/match
```
for single-record enrichment
```
POST /people/bulk_match
```
for batch (up to 10 per call)
```
GET /organizations/enrich
```
for company enrichment
See
```
/sales-apollo
```
for full API reference

单条记录补全：在Apollo数据库中搜索联系人 → 点击获取邮箱/电话（消耗额度）。

批量数据补全：

在列表或搜索结果中选择联系人
点击“Enrich（补全）” → 选择需要补全的字段
Apollo在后台处理，结果将显示在记录中
导出补全后的数据或同步至CRM

CRM自动数据补全：

进入设置 > 数据补全 > 自动补全
设置规则：新联系人创建时自动补全，或按计划对现有联系人进行补全
选择需要补全的字段及每月额度预算
在设置 > 使用情况中监控额度消耗

API补全：

```
POST /people/match
```
用于单条记录补全
```
POST /people/bulk_match
```
用于批量补全（每次调用最多10条）
```
GET /organizations/enrich
```
用于企业数据补全
完整API参考请查看
```
/sales-apollo
```

Compliance checklist

合规检查清单

Data quality scoring

数据质量评分

After enrichment, score your data quality:

Field	Quality level	Action
Email verified + deliverable	High	Ready for outreach
Email found but unverified	Medium	Run through verification tool (NeverBounce, ZeroBounce) before sending
Email not found	Low	Try alternate enrichment provider or find via LinkedIn/company website
Phone — direct/mobile	High	Ready for calling
Phone — HQ/switchboard	Low	Not useful for cold calling — try to find direct line

补全后对数据质量进行评分：

字段	质量等级	操作建议
已验证且可送达的邮箱	高	可直接用于触达
找到但未验证的邮箱	中	发送前通过验证工具（NeverBounce、ZeroBounce）检测
未找到邮箱	低	尝试其他数据补全服务商，或通过LinkedIn/企业官网查找
直拨/手机号码	高	可直接用于呼叫
公司总机/交换机号码	低	对冷呼叫无用 — 尝试查找直拨号码

Step 4 — CRM data hygiene

步骤4 — CRM数据清理

Stale data identification

失效数据识别

Records go stale quickly — people change jobs every 2-3 years on average. Run these checks:

Check	How to identify	Action
Bounced emails	Email bounced in last campaign	Re-enrich to find current email
Job changes	Title/company doesn't match LinkedIn	Re-enrich or mark as churned contact
Missing data	Key fields (email, phone, title) are blank	Bulk enrich missing fields
Duplicate records	Same person/company appears multiple times	Merge duplicates, keep most recent data
Outdated companies	Company acquired, renamed, or shut down	Remove or update with current entity
Unsubscribed/DNC	On do-not-contact list	Remove from all active sequences and lists

数据会快速失效 — 人们平均每2-3年更换一次工作。执行以下检查：

检查项	识别方式	操作建议
邮件退回	最近营销活动中邮件退回	重新补全以获取当前邮箱
职位变动	职位/公司与LinkedIn不符	重新补全或标记为流失联系人
数据缺失	关键字段（邮箱、电话、职位）为空	批量补全缺失字段
重复记录	同一人/企业多次出现	合并重复记录，保留最新数据
企业信息过时	企业被收购、更名或倒闭	删除记录或更新为当前主体信息
退订/请勿触达	在请勿触达列表中	从所有活跃序列和列表中移除

Deduplication strategy

去重策略

Define match criteria: Email address (strongest), or Company + Full Name (fallback)
Set merge rules: Most recently updated record wins for each field
Keep audit trail: Log what was merged and when
Run regularly: Monthly for active databases, quarterly for stable ones

定义匹配规则：邮箱地址（最优先），或公司+全名（备选）
设置合并规则：每个字段以最近更新的记录为准
保留审计轨迹：记录合并内容及时间
定期执行：活跃数据库每月一次，稳定数据库每季度一次

Enrichment schedule

数据补全计划

Data type	Refresh frequency	Why
Email addresses	Every 6 months	People change jobs; emails become invalid
Phone numbers	Every 6 months	Direct lines change with job changes
Job title/company	Every 3 months	Promotions and job changes
Firmographic data	Annually	Company size, revenue, and industry change slowly
Tech stack	Every 6 months	Technology adoption/removal is ongoing

数据类型	刷新频率	原因
邮箱地址	每6个月	人们更换工作后邮箱会失效
电话号码	每6个月	直拨号码会随职位变动而改变
职位/公司	每3个月	晋升和职位变动频繁
企业属性数据	每年	公司规模、收入和行业变化缓慢
技术栈	每6个月	技术的采用和淘汰持续进行

Step 5 — Credit optimization

步骤5 — 额度优化

Credit-saving strategies

节省额度的策略

Enrich only qualified records: Apply ICP filters before enriching — don't waste credits on bad-fit contacts
Check existing data first: Skip records that already have the data you need
Prioritize email over phone: Email credits are typically cheaper. Only reveal phone numbers for contacts you'll actually call.
Use waterfall strategically: Start with the cheapest provider, escalate to premium for high-value targets
Batch over real-time: Bulk enrichment is often more credit-efficient than one-at-a-time
Monitor usage weekly: Set up alerts when you hit 80% of monthly credit budget

仅为合格记录补全：补全前应用理想客户画像（ICP）筛选 — 不要为不符合的联系人浪费额度
先检查已有数据：跳过已包含所需数据的记录
优先补全邮箱而非电话：邮箱补全额度通常更便宜。仅为实际会呼叫的联系人获取电话号码
战略性使用瀑布式补全：从成本最低的服务商开始，仅为高价值目标升级至 premium 服务商
批量补全优于实时补全：批量补全通常比单条补全更节省额度
每周监控使用情况：当额度消耗达月度预算的80%时设置提醒

Apollo credit economics

Apollo额度成本

Action	Approximate credit cost
Email reveal	1 credit
Mobile phone reveal	5-10 credits (varies by plan)
Company enrichment	1 credit
CSV export	1 export credit per record
Search (no reveal)	Free

Credits reset monthly and do not roll over. Plan enrichment around your billing cycle.

操作	大致额度成本
获取邮箱	1个额度
获取手机号码	5-10个额度（依套餐而定）
企业数据补全	1个额度
CSV导出	每条记录1个导出额度
搜索（不获取数据）	免费

额度每月重置，未使用额度不结转。需根据账单周期规划补全操作。

Gotchas

注意事项

Don't enrich before deduplicating. Claude often recommends "enrich everything, then clean up." This wastes credits on duplicate records. Always dedup first, then enrich the clean list.
Don't assume enriched emails are deliverable. Enrichment tools find email addresses — they don't guarantee deliverability. Always run enriched emails through a verification tool (NeverBounce, ZeroBounce, MillionVerifier) before high-volume campaigns. Apollo-reported "verified" emails still bounce at 5-10% rates.
Don't enrich an entire CRM database at once. Claude tends to suggest bulk-enriching everything. This burns through credits fast and enriches records you may never contact. Start with your highest-priority segments and expand.
Don't ignore phone number credit costs. Mobile number reveals are 5-10x more expensive than email reveals in most tools. Only reveal phone numbers for contacts your team will actually call — not the entire list.
Don't set up auto-enrichment without a credit budget cap. Auto-enrichment can burn through an entire month's credits in days if configured too broadly. Set a monthly cap and limit auto-enrichment to new records matching your ICP.
Don't enrich contacts without checking regional compliance. Enriching EU contacts without a lawful basis for processing (GDPR), or emailing US contacts without an unsubscribe link (CAN-SPAM), exposes you to legal risk. See the compliance checklist in Step 3 before enriching in bulk.

不要在去重前补全数据：Claude常建议“先补全所有数据再清理”，但这会为重复记录浪费额度。务必先去重，再对清理后的列表进行补全。
不要假设补全的邮箱一定可送达：数据补全工具仅能找到邮箱地址，无法保证可送达性。高容量营销活动前，务必通过验证工具（NeverBounce、ZeroBounce、MillionVerifier）检测补全后的邮箱。Apollo标记为“已验证”的邮箱仍有5-10%的退回率。
不要一次性补全整个CRM数据库：Claude倾向于建议批量补全所有数据，但这会快速消耗额度，且补全的记录可能永远不会被触达。从最高优先级的细分群体开始，逐步扩展。
不要忽视电话号码的额度成本：在大多数工具中，获取手机号码的成本是邮箱的5-10倍。仅为团队实际会呼叫的联系人获取电话号码 — 而非整个列表。
不要在未设置额度预算上限的情况下启用自动补全：若配置范围过宽，自动补全可能在数天内消耗完整个月的额度。设置月度上限，并将自动补全限制为符合理想客户画像的新记录。
不要在未检查地区合规性的情况下补全联系人：在没有合法处理依据的情况下补全欧盟联系人数据（GDPR），或在未提供退订链接的情况下向美国联系人发送邮件（CAN-SPAM），会带来法律风险。批量补全前请查看步骤3中的合规检查清单。

Related skills

Examples

示例

Example 1: Pre-campaign enrichment

示例1：营销活动前的数据补全

User says: "I have 500 contacts for a campaign but only 60% have emails. Enrich the rest." Skill does:

Recommends deduping the list first
Filters to records missing emails
Sets up batch enrichment in Apollo with email-only scope (save phone credits)
Recommends email verification before launching the sequence Result: List enriched to 85%+ email coverage, verified and ready for outreach

用户需求：“我有500个营销活动联系人，但只有60%有邮箱。请补全剩余的。” 技能执行：

建议先对列表进行去重
筛选出缺失邮箱的记录
在Apollo中设置仅补全邮箱的批量操作（节省电话额度）
建议在启动序列前对邮箱进行验证结果：列表邮箱覆盖率提升至85%+，验证完成可用于触达

Example 2: CRM data cleanup

示例2：CRM数据清理

User says: "Our Salesforce has 50,000 contacts but half the data is stale. Help me clean it up." Skill does:

Identifies stale data patterns (bounced emails, outdated titles, missing fields)
Recommends a phased approach: dedup → prioritize top segments → enrich in batches
Sets up an ongoing enrichment schedule to prevent future staleness
Calculates credit budget for the cleanup Result: Phased CRM hygiene plan with credit-conscious enrichment strategy

用户需求：“我们的Salesforce有50000个联系人，但半数数据已失效。请帮助清理。” 技能执行：

识别失效数据模式（退回邮件、过时职位、缺失字段）
建议分阶段执行：去重 → 优先处理高优先级细分群体 → 批量补全
设置持续的补全计划以防止未来数据失效
计算清理所需的额度预算结果：分阶段的CRM数据清理计划及兼顾额度成本的补全策略

Troubleshooting

故障排除

Low enrichment match rate

数据补全匹配率低

Cause: Prospects are in niche industries, use uncommon email domains, or are very senior (C-suite data is harder to find) Solution: Try waterfall enrichment across multiple providers. For C-suite, try LinkedIn manual lookup or ask for referral introductions instead of cold outreach.

原因：潜在客户处于细分行业、使用不常见邮箱域名，或为高管（C-suite数据更难获取） 解决方案：尝试通过多个服务商进行瀑布式补全。针对C-suite高管，可尝试手动在LinkedIn查找或请求引荐，而非冷触达。

Enriched emails bouncing

补全的邮箱退回

Cause: Data provider has stale records, or person recently changed jobs Solution: Run enriched emails through a dedicated verification service before sending. Set up a feedback loop — when emails bounce, re-enrich or remove the contact.

原因：数据服务商记录过时，或联系人近期更换工作 解决方案：发送前通过专业验证服务检测补全后的邮箱。设置反馈循环 — 当邮件退回时，重新补全或移除该联系人。

Credits running out mid-month

额度在月中耗尽

Cause: Over-enrichment (enriching too many records or enriching phone numbers unnecessarily) Solution: Review usage in Settings > Usage. Restrict enrichment to ICP-qualified records only. Limit phone reveals to contacts tagged for calling. Consider upgrading plan if consistently hitting limits.

原因：过度补全（补全过多记录或不必要地补全电话号码） 解决方案：在设置 > 使用情况中查看消耗记录。仅为符合理想客户画像的记录进行补全。仅为标记为需呼叫的联系人获取电话号码。若持续超出额度，可考虑升级套餐。

sales-enrich

Original

Translation