Back to Details

crm-cleanup

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Run a HubSpot hygiene pass using the 
crm-maintenance
skill cleanup workflow. Act immediately — the user typed /crm-cleanup, so skip the intent-detection step.
Parse arguments:
  • --scope
    (default: 
    all
    ) — 
    deals
    for deal audit only, 
    contacts
    for contact dedup only, 
    all
    for both
使用
crm-maintenance
技能清理工作流运行HubSpot数据合规检查。立即执行——用户输入了/crm-cleanup，因此跳过意图检测步骤。
解析参数：
  • --scope
    （默认值：
    all
    ）——
    deals
    仅审核交易，
    contacts
    仅去重联系人，
    all
    同时处理两者

Step 1 — Scan for stale deals

步骤1 — 扫描过期交易

If scope includes deals:
  1. Pull all open deals from HubSpot.
  2. Flag deals with no activity (email, call, meeting, note) in the last 14 days.
  3. For each stale deal: show deal name, stage, last activity date, associated contacts, and amount.
  4. Propose actions per deal: update next-step, change stage, add a note, or close-lost.
Present the full stale-deals list before making any changes.
如果范围包含交易：
  1. 从HubSpot拉取所有未结交易。
  2. 标记过去14天内无活动（邮件、电话、会议、备注）的交易。
  3. 针对每笔过期交易：显示交易名称、阶段、最后活动日期、关联联系人及金额。
  4. 为每笔交易建议操作：更新下一步计划、更改阶段、添加备注或标记为关闭-流失。
在进行任何更改前，先展示完整的过期交易列表。

Step 2 — Scan for duplicate contacts

步骤2 — 扫描重复联系人

If scope includes contacts:
  1. Search HubSpot contacts for likely duplicates (same email, similar names, same company + similar name).
  2. For each duplicate set: show both records side-by-side — name, email, company, deals, last activity.
  3. Propose which record to keep and which fields to merge.
Present all duplicate sets before merging anything.
如果范围包含联系人：
  1. 在HubSpot联系人中搜索疑似重复项（相同邮箱、相似姓名、相同公司+相似姓名）。
  2. 针对每组重复项：并排显示两条记录——姓名、邮箱、公司、关联交易、最后活动。
  3. 建议保留哪条记录以及合并哪些字段。
在合并任何内容前，先展示所有重复组。

Step 3 — Scan for missing required fields

步骤3 — 扫描缺失必填字段

  1. Check all open deals for missing fields: close date, amount, deal stage, associated contact, next-step/notes.
  2. Check contacts associated with open deals for missing fields: email, company, phone.
  3. Present a table of records with missing fields and what's missing.
  1. 检查所有未结交易是否存在缺失字段：截止日期、金额、交易阶段、关联联系人、下一步计划/备注。
  2. 检查与未结交易关联的联系人是否存在缺失字段：邮箱、公司、电话。
  3. 展示包含缺失字段的记录表以及具体缺失内容。

Step 4 — Apply approved fixes

步骤4 — 应用经批准的修复

  1. Walk through each finding from Steps 1-3.
  2. Apply only the changes the owner explicitly approves.
  3. Report each change as it's made with a HubSpot link.
  1. 逐一处理步骤1-3中的每项发现。
  2. 仅应用所有者明确批准的更改。
  3. 每次更改完成后，附带HubSpot链接进行报告。

Connector failures

连接器故障

If HubSpot is unreachable, stop — this command requires HubSpot as the data source. Tell the owner: "HubSpot isn't connected. Connect it in Cowork settings, then rerun /crm-cleanup."
如果无法连接HubSpot，则停止操作——此命令需要HubSpot作为数据源。告知所有者：“HubSpot未连接。请在Cowork设置中连接它，然后重新运行/crm-cleanup。”

Approval gates

审批限制

  • Never delete records. Not contacts, not deals, not activities. If the user asks, say the skill cannot and direct them to HubSpot.
  • Never change deal stage or close a deal without explicit approval. Even if evidence is strong. Flag and defer.
  • Never auto-merge duplicate contacts. Show side-by-side and wait for approval per pair.
  • Side-by-side diffs for all changes. Show current value and proposed value; wait for approval per item.
  • 切勿删除记录。包括联系人、交易、活动。如果用户要求删除，说明本技能无法执行，并引导他们前往HubSpot操作。
  • 未经明确批准，切勿更改交易阶段或关闭交易。即使证据充分，也要标记并等待审批。
  • 切勿自动合并重复联系人。并排展示记录，等待针对每组重复项的审批。
  • 所有更改均需并排对比。显示当前值和建议值，等待针对每项更改的审批。

Output

输出

End with a summary: X deals updated, Y contacts merged, Z fields filled. Include links to the affected records.
最后生成总结：更新了X笔交易，合并了Y个联系人，补充了Z个字段。包含受影响记录的链接。