Back to Details

customer-pulse-check

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Run the customer voice synthesis. Pull feedback signals from all connected sources, identify the themes that are actually fixable, and produce drafted responses the owner can review and send.
Parse arguments:
  • --since
    (default: last 30 days) — start date 
    YYYY-MM-DD
    for the lookback window
运行客户声音合成流程。从所有已连接的数据源提取反馈信号，识别出实际可修复的主题，并生成可供负责人审核发送的草拟回复。
解析参数：
  • --since
    （默认值：过去30天）—— 回溯窗口的起始日期，格式为
    YYYY-MM-DD

Step 1 — Gather feedback signals

步骤1 — 收集反馈信号

Using the 
customer-pulse
skill workflow:
  1. Pull PayPal disputes and chargebacks for the period: reason codes, amounts, resolution status.
  2. Pull HubSpot support tickets and conversation notes for the period.
  3. If review export files are available (Google Reviews CSV, Yelp export, etc.) in Files: read and parse them.
  4. Count total signals per source.
使用
customer-pulse
技能工作流：
  1. 提取指定时间段内的PayPal纠纷和拒付记录：包含原因代码、金额、解决状态。
  2. 提取指定时间段内的HubSpot支持工单和对话记录。
  3. 如果文件库中存在评论导出文件（如Google Reviews CSV、Yelp导出文件等）：读取并解析这些文件。
  4. 统计每个数据源的总信号数量。

Step 2 — Theme extraction

步骤2 — 主题提取

Cluster all signals into recurring themes. For each theme:
  • Count how many signals mention it
  • Classify: Product quality / Delivery / Billing / Communication / Expectation mismatch / Other
  • Rate impact: 🔴 High (revenue risk, churn) / 🟡 Medium / 🟢 Low
将所有信号聚类为重复出现的主题。针对每个主题：
  • 统计提及该主题的信号数量
  • 分类：产品质量 / 配送 / 账单 / 沟通 / 预期不符 / 其他
  • 评估影响：🔴 高（收入风险、客户流失）/ 🟡 中 / 🟢 低

Step 3 — Top-3 fixable issues

步骤3 — 可修复前三大问题

Using the 
ticket-deflector
skill workflow:
Select the top 3 themes by: frequency × impact rating. For each:
  1. State the issue in one sentence
  2. Explain the root cause (where evident)
  3. Suggest a specific operational fix
  4. Draft a customer response template
Response template format:
Subject: Re: {issue topic}

Hi {first name},

Thank you for reaching out. {Acknowledgment of their experience in 1-2 sentences}.

{What we're doing about it / what happened / resolution offered}.

{Next step or offer}.

{Sign-off}
使用
ticket-deflector
技能工作流：
按照「频率 × 影响等级」排序，选出前三大主题。针对每个主题：
  1. 用一句话描述问题
  2. 解释根本原因（如有明确线索）
  3. 提出具体的运营修复方案
  4. 草拟客户回复模板
回复模板格式：
Subject: Re: {issue topic}

Hi {first name},

Thank you for reaching out. {Acknowledgment of their experience in 1-2 sentences}.

{What we're doing about it / what happened / resolution offered}.

{Next step or offer}.

{Sign-off}

Step 4 — Summary table

步骤4 — 汇总表格

Format the output as:
Customer Voice — {date range}
Total signals: {n} ({PayPal disputes: n} | {HubSpot tickets: n} | {Reviews: n})

TOP 3 FIXABLE ISSUES
1. {Issue} ({frequency}) — {impact} — Fix: {one-line fix}
2. {Issue} ({frequency}) — {impact} — Fix: {one-line fix}
3. {Issue} ({frequency}) — {impact} — Fix: {one-line fix}
输出格式如下：
Customer Voice — {date range}
Total signals: {n} ({PayPal disputes: n} | {HubSpot tickets: n} | {Reviews: n})

TOP 3 FIXABLE ISSUES
1. {Issue} ({frequency}) — {impact} — Fix: {one-line fix}
2. {Issue} ({frequency}) — {impact} — Fix: {one-line fix}
3. {Issue} ({frequency}) — {impact} — Fix: {one-line fix}

Connector failures

连接器故障处理

Run with whatever sources are connected — this command degrades gracefully. If PayPal is missing, skip dispute data and note "PayPal not connected — dispute data skipped." If HubSpot is missing, skip ticket data and note it. If no sources are connected at all, stop and tell the owner: "No feedback sources connected. Connect at least one of PayPal, HubSpot, or upload a review export CSV."
无论连接了哪些数据源都可运行——此命令具备优雅降级能力。若未连接PayPal，则跳过纠纷数据并标注「PayPal未连接——纠纷数据已跳过」。若未连接HubSpot，则跳过工单数据并标注。若未连接任何数据源，则停止运行并告知负责人：「未连接任何反馈数据源。请至少连接PayPal、HubSpot中的一个，或上传评论导出CSV文件。」

Approval gates

审批权限

  • Never send response emails automatically. Present drafts for owner review only.
  • Never close HubSpot tickets or resolve PayPal disputes without explicit owner confirmation.
  • Never include customer PII in the summary — use first name + last initial only.
  • 绝不自动发送回复邮件。仅向负责人展示草拟模板供审核。
  • 未经负责人明确确认，绝不关闭HubSpot工单或解决PayPal纠纷。
  • 汇总内容中绝不包含客户个人身份信息（PII）——仅使用名字+姓氏首字母。

Output

输出内容

Present the summary table, then each response template. Ask the owner which templates they'd like to send, then wait for explicit approval before drafting the send.
先展示汇总表格，再展示各回复模板。询问负责人想要发送哪些模板，等待明确审批后再草拟发送操作。