customer-pulse

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Customer Pulse

客户脉搏

Quick start

快速上手

Ask: "How are customers feeling this month?"
Claude pulls disputes, tickets, email threads, and Intercom conversations for the last 30 days, groups them into 3–5 themes with verbatim evidence, and delivers a "do these 3 things this week" action list.
To include Google/Yelp reviews, paste them after triggering — or say "I have some reviews to add."
提问:“本月客户感受如何?”
Claude会提取过去30天内的纠纷、工单、邮件线程和Intercom对话,将它们归类为3–5个主题并附上原始证据,同时生成一份「本周需完成的3件事」行动清单。
若需纳入Google/Yelp评论,可在触发后粘贴评论内容,或告知“我有一些评论要添加”。

Workflow

工作流程

  1. Set the date window. Default: last 30 days. If the user specifies a range, use it.
  2. Pull PayPal disputes. Fetch disputes opened in the window. If the PayPal API returns a rate-limit error, skip and add
    PayPal: rate-limited — not included
    to the Sources section. Do not retry; do not error. See reference/gotchas.md for the rate-limit pattern.
  3. Pull HubSpot tickets and feedback. Fetch open and recently closed tickets. If 0 tickets exist, record
    HubSpot tickets: 0
    and continue — do not surface a warning.
  4. Pull Gmail threads. Search for threads in the window containing:
    refund cancel unhappy issue problem disappointed frustrated broken late slow wrong missing
    . Extract subject lines and 1–2 sentence excerpts per thread.
  5. Pull Intercom conversations. Call
    search_conversations
    to fetch open and recently closed conversations. Then call
    get_conversation
    for each conversation ID returned to access the full
    conversation_parts
    . Extract parts where
    author.type === 'user'
    — these are customer messages. Exclude parts where
    author.type
    is
    admin
    or
    bot
    .
  6. Accept pasted reviews (optional). If the user pastes Google or Yelp review text, include it in the source pool tagged as
    [Review]
    . No connector required.
  7. Extract themes. Group all evidence into 3–5 recurring themes. Each theme must include:
    • A one-sentence label (e.g., "Shipping delays causing repeat complaints")
    • 2–3 verbatim quotes with source tags:
      [PayPal]
      ,
      [HubSpot]
      ,
      [Gmail]
      ,
      [Intercom]
      , or
      [Review]
    • A signal count (how many items touch this theme)
    Verbatim quotes are non-negotiable — never paraphrase. See reference/gotchas.md for the verbatim anti-pattern.
  8. Generate the "do these 3 things" list. Rank themes by signal count. Pick the top 3 and write one concrete, owner-actionable step per theme. Format as a numbered checklist.
  9. Deliver the report. Structure the output with these sections in order:
    • Header — H2 with "Customer Pulse" and the date range.
    • Sources pulled — Bullet list with signal counts per source (PayPal disputes, HubSpot tickets, Gmail threads, Intercom conversations, pasted reviews). Note any source that was rate-limited and skipped.
    • Themes — For each theme, show a bold numbered theme label with the signal count, followed by two verbatim quotes as blockquotes, each attributed to its source.
    • Do these 3 things this week — Numbered list of three concrete, owner-actionable steps, each tied to one of the top themes.
    For a complete worked example, see reference/examples/example-report.md.
  1. 设置时间范围:默认范围为过去30天。若用户指定了时间范围,则使用该范围。
  2. 提取PayPal纠纷:获取该时间范围内发起的纠纷。若PayPal API返回速率限制错误,则跳过该数据源,并在「数据源」部分添加
    PayPal: rate-limited — not included
    。请勿重试,也无需报错。速率限制相关规则请参考reference/gotchas.md
  3. 提取HubSpot工单与反馈:获取已打开和近期关闭的工单。若不存在工单,则记录
    HubSpot tickets: 0
    并继续执行——无需发出警告。
  4. 提取Gmail线程:搜索该时间范围内包含以下关键词的线程:
    refund cancel unhappy issue problem disappointed frustrated broken late slow wrong missing
    。提取每个线程的主题行和1–2句摘录。
  5. 提取Intercom对话:调用
    search_conversations
    获取已打开和近期关闭的对话。然后针对返回的每个对话ID调用
    get_conversation
    以访问完整的
    conversation_parts
    。提取
    author.type === 'user'
    的部分——这些是客户消息。排除
    author.type
    admin
    bot
    的部分。
  6. 接受粘贴的评论(可选):若用户粘贴了Google或Yelp评论文本,将其标记为
    [Review]
    纳入数据源池,无需使用连接器。
  7. 提取主题:将所有证据归类为3–5个重复出现的主题。每个主题必须包含:
    • 一句主题标签(例如:“配送延迟引发多次投诉”)
    • 2–3条带有来源标签的原始引用:
      [PayPal]
      [HubSpot]
      [Gmail]
      [Intercom]
      [Review]
    • 信号计数(涉及该主题的条目数量)
    原始引用为必填项——切勿改写。原始引用的反模式请参考reference/gotchas.md
  8. 生成「本周需完成的3件事」清单:按信号计数对主题排序。选取排名前三的主题,为每个主题撰写一个具体、可落地的行动步骤。格式化为编号清单。
  9. 交付报告:按以下顺序构建输出内容:
    • 标题 — H2格式的“客户脉搏”及时间范围。
    • 提取的数据源 — 项目符号列表,包含每个数据源的信号计数(PayPal纠纷、HubSpot工单、Gmail线程、Intercom对话、粘贴的评论)。注明任何因速率限制而被跳过的数据源。
    • 主题 — 每个主题以加粗的编号主题标签加信号计数展示,随后附上两条作为块引用的原始引用,每条引用标注其来源。
    • 本周需完成的3件事 — 编号列表,包含三个具体、可落地的行动步骤,每个步骤对应一个排名靠前的主题。
    完整示例请参考reference/examples/example-report.md

Approval gates

审批权限

This skill is read-only — it does not post, send, reply, or modify any records. No approval gate is required.
此Skill为只读——不会发布、发送、回复或修改任何记录。无需审批权限。

Reference

参考资料

  • reference/gotchas.md — PayPal rate limits, HubSpot empty state, verbatim quote requirement, Gmail keyword drift
  • reference/examples/example-report.md — full worked example output
  • reference/gotchas.md — PayPal速率限制、HubSpot空状态、原始引用要求、Gmail关键词偏差
  • reference/examples/example-report.md — 完整的报告输出示例