Back to Details

crm-hygiene

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

CRM Hygiene

CRM数据健康维护

Systematically identify and resolve data quality issues in your CRM to improve forecast accuracy, reporting, and automation reliability.
系统性地识别并解决CRM中的数据质量问题，以提升预测准确性、报表质量和自动化流程可靠性。

When to Use This Skill

何时使用此Skill

  • Quarterly CRM audits
  • Before major reporting periods
  • When automation workflows fail
  • After team changes or migrations
  • Preparing for CRM integrations
  • 季度CRM审核
  • 重大报表周期前
  • 自动化工作流失败时
  • 团队变动或系统迁移后
  • CRM集成准备阶段

Methodology Foundation

方法论基础

Based on Salesforce Data Quality Best Practices and RevOps Co-op Data Governance frameworks, focusing on:
  • Completeness (required fields populated)
  • Consistency (standardized values)
  • Accuracy (correct and current data)
  • Timeliness (recent updates)
基于Salesforce Data Quality Best Practices和RevOps Co-op数据治理框架，重点关注：
  • 完整性（必填字段已填充）
  • 一致性（值标准化）
  • 准确性（数据正确且最新）
  • 及时性（最近更新）

What Claude Does vs What You Decide

Claude负责的工作 vs 由您决定的事项

Claude DoesYou Decide
Defines audit criteriaWhich fields are required
Identifies data issuesPriority of fixes
Categorizes problems by typeWho owns cleanup tasks
Suggests remediation stepsAutomation vs manual fix
Creates cleanup reportsEnforcement policies
Claude负责由您决定
定义审核标准哪些字段为必填项
识别数据问题修复优先级
按类型分类问题谁负责清理任务
建议补救步骤自动化修复还是手动修复
生成清理报告执行政策

What This Skill Does

此Skill的功能

  1. Audit design - Define required fields and validation rules
  2. Issue identification - Find missing, inconsistent, duplicate data
  3. Prioritization - Rank issues by business impact
  4. Remediation planning - Action steps to fix issues
  5. Governance recommendations - Prevent future issues
  1. 审核设计 - 定义必填字段和验证规则
  2. 问题识别 - 查找缺失、不一致、重复的数据
  3. 优先级排序 - 按业务影响程度对问题分级
  4. 修复规划 - 制定解决问题的行动步骤
  5. 治理建议 - 预防未来出现同类问题

How to Use

使用方法

For Audit Design:

审核设计场景：

Help me create a CRM hygiene audit for [CRM System].

Key objects to audit:
- [Leads, Contacts, Accounts, Opportunities]

Critical fields for each:
- Leads: [list required fields]
- Opportunities: [list required fields]

Our main issues:
- [Describe known problems]
Help me create a CRM hygiene audit for [CRM System].

Key objects to audit:
- [Leads, Contacts, Accounts, Opportunities]

Critical fields for each:
- Leads: [list required fields]
- Opportunities: [list required fields]

Our main issues:
- [Describe known problems]

For Data Audit:

数据审核场景：

Audit this opportunity data for hygiene issues:

[Paste export or describe data]

Required fields:
- [List fields that must be populated]

Validation rules:
- [List rules like "Stage must match Amount > $0"]
Audit this opportunity data for hygiene issues:

[Paste export or describe data]

Required fields:
- [List fields that must be populated]

Validation rules:
- [List rules like "Stage must match Amount > $0"]

Instructions

操作步骤

Step 1: Define Audit Scope

步骤1：定义审核范围

Object Priority (typical):
  1. Opportunities - Revenue impact
  2. Accounts - Relationship foundation
  3. Contacts - Communication accuracy
  4. Leads - Pipeline source
Field Categories:
  • Critical - Blocks processes if missing
  • Important - Affects reporting/segmentation
  • Nice-to-Have - Enriches but not required
对象优先级（典型）：
  1. 商机（Opportunities）- 影响营收
  2. 客户账户（Accounts）- 客户关系基础
  3. 联系人（Contacts）- 沟通准确性
  4. 线索（Leads）- 销售管道来源
字段分类：
  • 关键字段 - 缺失会阻塞流程
  • 重要字段 - 影响报表/细分
  • 可选字段 - 丰富数据但非必需

Step 2: Completeness Audit

步骤2：完整性审核

Check required fields by object:
Opportunities:
FieldCriticalityWhy Required
AmountCriticalForecast, pipeline value
Close DateCriticalForecast timing
StageCriticalPipeline reporting
OwnerCriticalAccountability
AccountCriticalCompany linkage
Primary ContactImportantCommunication
Next StepImportantDeal momentum
CompetitorImportantWin/loss analysis
Loss ReasonCritical (if lost)Improvement insights
Accounts:
FieldCriticalityWhy Required
IndustryImportantSegmentation
Employee CountImportantICP fit
WebsiteImportantResearch, enrichment
Billing AddressCriticalInvoicing
Account OwnerCriticalAccountability
按对象检查必填字段：
商机（Opportunities）：
字段重要性必填原因
金额（Amount）关键预测、销售管道价值
关闭日期（Close Date）关键预测时间节点
阶段（Stage）关键销售管道报表
负责人（Owner）关键责任归属
客户账户（Account）关键关联公司信息
主要联系人（Primary Contact）重要沟通对接
下一步动作（Next Step）重要推进交易节奏
竞争对手（Competitor）重要赢单/丢单分析
丢单原因（Loss Reason）关键（若已丢单）改进方向洞察
客户账户（Accounts）：
字段重要性必填原因
行业（Industry）重要客户细分
员工数量（Employee Count）重要理想客户画像匹配度
官网（Website）重要调研、数据补充
账单地址（Billing Address）关键开票需求
账户负责人（Account Owner）关键责任归属

Step 3: Consistency Audit

步骤3：一致性审核

Check for standardization issues:
Issue TypeExampleImpact
Picklist variations"US" vs "USA" vs "United States"Reporting breaks
Case inconsistency"ACME" vs "Acme" vs "acme"Duplicates
Format variations"(555) 123-4567" vs "5551234567"Automation fails
Null vs blankNULL vs "" vs "N/A"Filters don't work
检查标准化问题：
问题类型示例影响
下拉选项不一致"US" vs "USA" vs "United States"报表出错
大小写不一致"ACME" vs "Acme" vs "acme"产生重复记录
格式不一致"(555) 123-4567" vs "5551234567"自动化流程失败
空值表示不一致NULL vs "" vs "N/A"筛选功能失效

Step 4: Accuracy Audit

步骤4：准确性审核

Identify likely incorrect data:
CheckCriteriaAction
Stale close datesPast date, still openUpdate or close
Amount mismatches$0 in late stageVerify pricing
Stage regressionStage 4 → Stage 2Investigate
Impossible values200% probabilityFix validation
Bounced emailsMarked invalidRemove or update
识别可能的错误数据：
检查项判断标准操作建议
过期关闭日期日期已过但状态仍为开放更新日期或关闭交易
金额不匹配后期阶段金额为$0核实定价
阶段倒退从阶段4回到阶段2调查原因
不合理值赢单概率200%修复验证规则
邮件退回标记为无效删除或更新

Step 5: Duplicate Detection

步骤5：重复记录检测

Find potential duplicates:
Match TypeCriteriaConfidence
Exact emailSame email address99% duplicate
Domain matchSame company domain80% duplicate
Fuzzy nameSimilar company nameInvestigate
Phone matchSame phone number90% duplicate
查找潜在重复项：
匹配类型判断标准置信度
邮箱完全匹配相同邮箱地址99%为重复
域名匹配相同公司域名80%为重复
名称模糊匹配相似公司名称需要调查
电话匹配相同电话号码90%为重复

Step 6: Timeliness Audit

步骤6：时效性审核

Flag stale records:
ObjectStaleness ThresholdAction
Open OpportunityNo activity 30 daysReview with rep
LeadNo touch 14 daysReassign or nurture
AccountNo contact 90 daysRe-engagement
ContactBounced + 30 daysArchive
标记过期记录：
对象过期阈值操作建议
开放商机30天无活动与销售代表复核
线索14天无跟进重新分配或培育
客户账户90天无联系重新激活
联系人邮件退回+30天无更新归档

Examples

示例

Example 1: Opportunity Audit

示例1：商机审核

Input:
Audit these opportunities:

1. Acme Corp - Stage: Proposal, Amount: $0, Close: Jan 15 (past), Owner: Empty
2. Beta Inc - Stage: Closed Won, Amount: $50K, Close: Feb 1, Loss Reason: "Price"
3. Gamma LLC - Stage: Discovery, Amount: $100K, Close: Mar 30, No activity 45 days
4. Delta Co - Stage: Negotiation, Amount: $75K, Close: Feb 28, Next Step: Empty
5. Echo Systems - Stage: Closed Lost, Amount: $200K, Loss Reason: Empty
Output:
undefined
输入：
Audit these opportunities:

1. Acme Corp - Stage: Proposal, Amount: $0, Close: Jan 15 (past), Owner: Empty
2. Beta Inc - Stage: Closed Won, Amount: $50K, Close: Feb 1, Loss Reason: "Price"
3. Gamma LLC - Stage: Discovery, Amount: $100K, Close: Mar 30, No activity 45 days
4. Delta Co - Stage: Negotiation, Amount: $75K, Close: Feb 28, Next Step: Empty
5. Echo Systems - Stage: Closed Lost, Amount: $200K, Loss Reason: Empty
输出：
undefined

CRM Hygiene Audit: Opportunities

CRM Hygiene Audit: Opportunities

Summary

Summary

  • Total Records: 5
  • Critical Issues: 4
  • Warnings: 2
  • Clean Records: 0
  • Total Records: 5
  • Critical Issues: 4
  • Warnings: 2
  • Clean Records: 0

Critical Issues (Fix Immediately)

Critical Issues (Fix Immediately)

1. Acme Corp - 3 Critical Issues

1. Acme Corp - 3 Critical Issues

IssueFieldCurrentRequired
🔴 MissingOwnerEmptyAssigned rep
🔴 MissingAmount$0Deal value
🔴 StaleClose DateJan 15 (past)Future date
Action: Assign owner, verify if deal is active, update amount and close date.
IssueFieldCurrentRequired
🔴 MissingOwnerEmptyAssigned rep
🔴 MissingAmount$0Deal value
🔴 StaleClose DateJan 15 (past)Future date
Action: Assign owner, verify if deal is active, update amount and close date.

2. Beta Inc - Logic Error

2. Beta Inc - Logic Error

IssueFieldCurrentProblem
🔴 InconsistentLoss Reason"Price"Stage is "Closed Won"
Action: Either change stage to Closed Lost, or clear Loss Reason.
IssueFieldCurrentProblem
🔴 InconsistentLoss Reason"Price"Stage is "Closed Won"
Action: Either change stage to Closed Lost, or clear Loss Reason.

3. Echo Systems - Missing Required

3. Echo Systems - Missing Required

IssueFieldCurrentRequired
🔴 MissingLoss ReasonEmptyRequired for Closed Lost
Action: Rep must document why deal was lost.
IssueFieldCurrentRequired
🔴 MissingLoss ReasonEmptyRequired for Closed Lost
Action: Rep must document why deal was lost.

4. Delta Co - Missing Next Step

4. Delta Co - Missing Next Step

IssueFieldCurrentImpact
🟠 MissingNext StepEmptyNo clear action
Action: Rep should define next step for Negotiation stage.
IssueFieldCurrentImpact
🟠 MissingNext StepEmptyNo clear action
Action: Rep should define next step for Negotiation stage.

Warnings (Review This Week)

Warnings (Review This Week)

5. Gamma LLC - Stale Deal

5. Gamma LLC - Stale Deal

IssueIndicatorValue
🟡 StaleLast Activity45 days ago
Action: Review with rep - is this deal still active? If yes, update. If no, close lost.
IssueIndicatorValue
🟡 StaleLast Activity45 days ago
Action: Review with rep - is this deal still active? If yes, update. If no, close lost.

Hygiene Score: 20/100 (Poor)

Hygiene Score: 20/100 (Poor)

Recommended Actions by Priority

Recommended Actions by Priority

  1. Today: Fix Acme Corp (no owner = orphaned deal)
  2. Today: Fix Beta Inc logic error (affects win rate)
  3. This Week: Get Echo Systems loss reason
  4. This Week: Update Gamma LLC status
  5. This Week: Add Delta Co next step
  1. Today: Fix Acme Corp (no owner = orphaned deal)
  2. Today: Fix Beta Inc logic error (affects win rate)
  3. This Week: Get Echo Systems loss reason
  4. This Week: Update Gamma LLC status
  5. This Week: Add Delta Co next step

Process Recommendations

Process Recommendations

  • Add validation rule: Amount required when Stage > Discovery
  • Add validation rule: Owner required on all opportunities
  • Add validation rule: Loss Reason required when Closed Lost
  • Create stale deal report (no activity 30+ days)
undefined
  • Add validation rule: Amount required when Stage > Discovery
  • Add validation rule: Owner required on all opportunities
  • Add validation rule: Loss Reason required when Closed Lost
  • Create stale deal report (no activity 30+ days)
undefined

Example 2: Duplicate Detection

示例2：重复记录检测

Input:
Check these accounts for duplicates:

1. Acme Corporation, acme.com, San Francisco
2. ACME Corp, acme.com, SF
3. Acme Inc, acme-inc.com, San Francisco
4. Beta Technologies, beta.io, New York
5. Beta Tech, betatech.com, NYC
6. Beta Technologies Inc, beta.io, New York
Output:
undefined
输入：
Check these accounts for duplicates:

1. Acme Corporation, acme.com, San Francisco
2. ACME Corp, acme.com, SF
3. Acme Inc, acme-inc.com, San Francisco
4. Beta Technologies, beta.io, New York
5. Beta Tech, betatech.com, NYC
6. Beta Technologies Inc, beta.io, New York
输出：
undefined

Duplicate Detection Report

Duplicate Detection Report

High Confidence Duplicates (Merge)

High Confidence Duplicates (Merge)

Duplicate Set 1: Acme Corporation

Duplicate Set 1: Acme Corporation

RecordNameDomainLocationConfidence
#1Acme Corporationacme.comSan FranciscoMaster
#2ACME Corpacme.comSF99% - Same domain
Recommendation: Merge #2 into #1
  • Same domain (acme.com)
  • Same location (SF = San Francisco)
  • Name variation only (Corp vs Corporation)
RecordNameDomainLocationConfidence
#1Acme Corporationacme.comSan FranciscoMaster
#2ACME Corpacme.comSF99% - Same domain
Recommendation: Merge #2 into #1
  • Same domain (acme.com)
  • Same location (SF = San Francisco)
  • Name variation only (Corp vs Corporation)

Duplicate Set 2: Beta Technologies

Duplicate Set 2: Beta Technologies

RecordNameDomainLocationConfidence
#4Beta Technologiesbeta.ioNew YorkMaster
#6Beta Technologies Incbeta.ioNew York99% - Same domain
Recommendation: Merge #6 into #4
  • Same domain (beta.io)
  • Same location (New York)
  • Name variation only (Inc suffix)
RecordNameDomainLocationConfidence
#4Beta Technologiesbeta.ioNew YorkMaster
#6Beta Technologies Incbeta.ioNew York99% - Same domain
Recommendation: Merge #6 into #4
  • Same domain (beta.io)
  • Same location (New York)
  • Name variation only (Inc suffix)

Investigate (Possible Duplicates)

Investigate (Possible Duplicates)

Possible Set 1: Acme variations

Possible Set 1: Acme variations

RecordNameDomainLocationConfidence
#1Acme Corporationacme.comSan Francisco-
#3Acme Incacme-inc.comSan Francisco40%
Recommendation: Investigate manually
  • Same location, similar name
  • BUT different domains (acme.com vs acme-inc.com)
  • Could be: subsidiary, different company, or typo
RecordNameDomainLocationConfidence
#1Acme Corporationacme.comSan Francisco-
#3Acme Incacme-inc.comSan Francisco40%
Recommendation: Investigate manually
  • Same location, similar name
  • BUT different domains (acme.com vs acme-inc.com)
  • Could be: subsidiary, different company, or typo

Possible Set 2: Beta variations

Possible Set 2: Beta variations

RecordNameDomainLocationConfidence
#4Beta Technologiesbeta.ioNew York-
#5Beta Techbetatech.comNYC50%
Recommendation: Investigate manually
  • Same location (NYC = New York)
  • Similar names (Beta Tech vs Beta Technologies)
  • Different domains - likely different companies
RecordNameDomainLocationConfidence
#4Beta Technologiesbeta.ioNew York-
#5Beta Techbetatech.comNYC50%
Recommendation: Investigate manually
  • Same location (NYC = New York)
  • Similar names (Beta Tech vs Beta Technologies)
  • Different domains - likely different companies

Summary

Summary

  • Definite Duplicates: 2 sets (4 records → 2)
  • Possible Duplicates: 2 sets (need research)
  • Unique Records: Pending investigation
  • Definite Duplicates: 2 sets (4 records → 2)
  • Possible Duplicates: 2 sets (need research)
  • Unique Records: Pending investigation

Merge Checklist

Merge Checklist

Before merging, verify:
  • All opportunities moved to master record
  • All contacts linked to master
  • Activity history preserved
  • Custom fields compared
  • Integration IDs noted (for external systems)
undefined
Before merging, verify:
  • All opportunities moved to master record
  • All contacts linked to master
  • Activity history preserved
  • Custom fields compared
  • Integration IDs noted (for external systems)
undefined

Skill Boundaries

Skill边界

What This Skill Does Well

此Skill擅长的工作

  • Defining audit criteria systematically
  • Identifying common data quality issues
  • Prioritizing fixes by business impact
  • Creating actionable remediation plans
  • 系统性定义审核标准
  • 识别常见数据质量问题
  • 按业务影响优先级排序修复任务
  • 制定可执行的修复计划

What This Skill Cannot Do

此Skill无法完成的工作

  • Access your actual CRM data
  • Execute cleanup automatically
  • Know your specific business rules
  • Detect all semantic errors
  • 访问您的实际CRM数据
  • 自动执行清理操作
  • 知晓您的特定业务规则
  • 检测所有语义错误

When to Escalate to Human

何时需要人工介入

  • Merge decisions (data loss risk)
  • Business rule definitions
  • Enforcement policy decisions
  • Cross-object relationship issues
  • 合并决策（存在数据丢失风险）
  • 业务规则定义
  • 执行政策决策
  • 跨对象关系问题

Iteration Guide

迭代指南

Follow-up Prompts

后续提示示例

  • "Create a monthly hygiene report template."
  • "What validation rules would prevent these issues?"
  • "Prioritize the top 10 issues by revenue impact."
  • "Design a data entry form that enforces these rules."
  • "Create a monthly hygiene report template."
  • "What validation rules would prevent these issues?"
  • "Prioritize the top 10 issues by revenue impact."
  • "Design a data entry form that enforces these rules."

Continuous Improvement Cycle

持续改进周期

  1. Audit → Identify issues
  2. Fix → Clean data
  3. Prevent → Add validation rules
  4. Monitor → Track hygiene score weekly
  5. Iterate → Refine rules quarterly
  1. 审核 → 识别问题
  2. 修复 → 清理数据
  3. 预防 → 添加验证规则
  4. 监控 → 每周跟踪数据健康评分
  5. 迭代 → 每季度优化规则

Checklists & Templates

检查表与模板

Weekly Hygiene Report Template

每周数据健康报告模板

markdown
undefined
markdown
undefined

CRM Hygiene Report - Week of [Date]

CRM Hygiene Report - Week of [Date]

Hygiene Score: X/100

Hygiene Score: X/100

Critical Issues (Fix Today)

Critical Issues (Fix Today)

ObjectRecordIssueOwner
ObjectRecordIssueOwner

Warnings (Fix This Week)

Warnings (Fix This Week)

ObjectCountIssue Type
ObjectCountIssue Type

Trends

Trends

  • Issues closed this week: X
  • New issues this week: X
  • Net change: +/- X
  • Issues closed this week: X
  • New issues this week: X
  • Net change: +/- X

Action Items

Action Items

undefined
undefined

Data Governance Checklist

数据治理检查表

  • Required fields defined per object
  • Validation rules implemented
  • Duplicate rules active
  • Stale record reports scheduled
  • Ownership assignments current
  • Integration mappings documented
  • 已按对象定义必填字段
  • 已实施验证规则
  • 已启用重复记录规则
  • 已计划过期记录报表
  • 所有权分配为最新状态
  • 已记录集成映射关系

References

参考资料

  • Salesforce Data Quality Best Practices
  • RevOps Co-op Data Governance Framework
  • Marketo Database Health Guide
  • Gartner Data Quality Market Guide
  • Salesforce Data Quality Best Practices
  • RevOps Co-op Data Governance Framework
  • Marketo Database Health Guide
  • Gartner Data Quality Market Guide

Related Skills

相关Skill

  • pipeline-forecasting
    - Clean data improves forecasts
  • lead-scoring
    - Requires complete lead data
  • deal-risk-scoring
    - Depends on activity data
  • pipeline-forecasting
    - 清洁数据可提升预测准确性
  • lead-scoring
    - 需要完整的线索数据
  • deal-risk-scoring
    - 依赖活动数据

Skill Metadata

Skill元数据

  • Domain: RevOps
  • Complexity: Intermediate
  • Mode: centaur
  • Time to Value: 30-60 min for audit, varies for cleanup
  • Prerequisites: CRM data export, field requirements list
  • 领域（Domain）: RevOps
  • 复杂度（Complexity）: 中级
  • 模式（Mode）: 人机协作（centaur）
  • 价值实现时间（Time to Value）: 审核需30-60分钟，清理时间视情况而定
  • 前置条件（Prerequisites）: CRM数据导出文件、字段需求列表