Back to Details

lead-triage

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Lead Triage

线索筛选与优先级排序

Quick start

快速开始

Pull inbound leads from HubSpot, score them, and surface a ranked call list with talking points. Drafts follow-ups and proposes calendar slots — never sends or books without owner approval.
User: "prioritize my leads"
→ Pull contacts: lifecycle stage Lead or MQL, status ≠ Unqualified
→ Score each across engagement, company fit, urgency, recency
→ Return ranked list (size adapts to volume) with talking points
→ Offer to draft follow-ups and propose calendar slots
从HubSpot提取入站线索，进行评分，并展示带有沟通要点的排序后的联系列表。撰写跟进邮件草稿并建议日历时段——未经负责人批准，绝不会发送邮件或预订日程。
User: "prioritize my leads"
→ Pull contacts: lifecycle stage Lead or MQL, status ≠ Unqualified
→ Score each across engagement, company fit, urgency, recency
→ Return ranked list (size adapts to volume) with talking points
→ Offer to draft follow-ups and propose calendar slots

Workflow

工作流程

  1. Pull leads from HubSpot. Fetch contacts with 
    lifecyclestage
    = 
    Lead
    or 
    MQL
    and 
    hs_lead_status
    ≠ 
    Unqualified
    . Use the field list in reference/hubspot-scoring.md. If HubSpot is unavailable, stop: "HubSpot is disconnected — connect it and try again."
  2. Clarify if trigger is ambiguous. If the user said only "pipeline" without a qualifier, ask: "Quick pipeline overview (deal stages + total value) or prioritized call list?" — then route accordingly. Do not score leads on a bare "pipeline."
  3. Score each lead. Apply the four-dimension model in reference/hubspot-scoring.md:
    • Engagement — email replies, opens, site visits in HubSpot (last 30 days only)
    • Company fit — industry and employee count vs. owner's ICP (default: any industry, 1–50 employees)
    • Urgency — lead age, stage duration, notes containing "urgent / ASAP / deadline / budget approved"
    • Recency penalty — subtract points if last activity was <24 hours ago (already touched today)
  4. Build the ranked list. Sort descending by composite score. Adapt list size to volume:
    • ≤10 leads → show all
    • 11–30 leads → show top 5
    • 30 leads → show top 8
    For each lead: name, company, score, one-paragraph talking point, last activity summary. If engagement signals are all >30 days old, flag: "Engagement signals are stale — approach as cold outreach."
  5. Offer follow-up drafts. Ask: "Draft follow-ups for any of these?" If yes, write one email per selected lead, matching the tone of their last outbound thread in Mail. Show draft; do not send.
  6. Offer calendar slots. Ask: "Propose call slots for any of these?" If yes, check Calendar for open 30-minute windows in the next two business days (avoid slots with existing events ±15 min). Propose two options per lead. Do not create events — the owner books.
  1. 从HubSpot提取线索。获取
    lifecyclestage
    = 
    Lead
    或
    MQL
    且
    hs_lead_status
    ≠ 
    Unqualified
    的联系人。使用reference/hubspot-scoring.md中的字段列表。如果HubSpot不可用，则停止操作："HubSpot已断开连接——请重新连接后重试。"
  2. 若触发指令模糊则澄清。如果用户仅提及“pipeline”但未说明具体需求，询问："是快速概览销售渠道（交易阶段+总价值）还是优先联系列表？" — 然后根据选择进行处理。仅收到“pipeline”指令时，不得对线索进行评分。
  3. 为每个线索评分。应用reference/hubspot-scoring.md中的四维模型：
    • 互动度 — HubSpot中的邮件回复、打开记录、网站访问（仅过去30天的数据）
    • 公司匹配度 — 行业和员工数量与负责人的理想客户画像（ICP，默认：任意行业，1–50名员工）
    • 紧急程度 — 线索时长、阶段持续时间、包含“urgent / ASAP / deadline / budget approved”的备注
    • 近期操作惩罚 — 如果最后一次活动在24小时内（今日已跟进过），则扣除分数
  4. 生成排序后的列表。按综合分数降序排列。列表长度根据线索数量调整：
    • ≤10条线索 → 展示全部
    • 11–30条线索 → 展示前5条
    • 30条线索 → 展示前8条
    每条线索包含：姓名、公司、分数、一段沟通要点、最后活动摘要。如果所有互动信号均超过30天，标记提示："互动信号已失效——请按陌生客户开发方式处理。"
  5. 提供跟进邮件草稿。询问："是否为这些线索撰写跟进邮件草稿？" 如果是，为每个选中的线索撰写一封邮件，匹配Mail中上次外发邮件的语气。展示草稿；不得发送。
  6. 提供日历时段建议。询问："是否为这些线索建议通话时段？" 如果是，查看日历中未来两个工作日的30分钟空闲时段（避开已有事件前后15分钟的时段）。为每个线索提供两个选项。不得创建日程——由负责人预订。

Approval gates

审批规则

  • Never send an email. Draft only; owner sends from their inbox.
  • Never create calendar events. Propose times; owner books.
  • Never change lifecycle stage or mark a lead Unqualified unless the owner explicitly asks.
  • Never include 
    Customer
    or 
    Evangelist
    lifecycle contacts     in the lead list.
  • If zero leads match the filter, explain why and offer to check what lifecycle stages are in use — do not fabricate a list.
  • 绝不发送邮件。仅撰写草稿；由负责人从其收件箱发送。
  • 绝不创建日历事件。仅建议时段；由负责人预订。
  • 绝不更改生命周期阶段或标记线索为Unqualified，除非负责人明确要求。
  • 线索列表中绝不包含
    Customer
    或
    Evangelist
    生命周期阶段的联系人    。
  • 如果没有符合筛选条件的线索，说明原因并主动提出查看当前使用的生命周期阶段——不得编造列表。

Reference

参考资料

  • reference/hubspot-scoring.md — HubSpot field names, scoring weights, ICP defaults
  • reference/gotchas.md — edge cases: stale data, zero leads, pipeline disambiguation, customer contamination
  • reference/examples/happy-path-triage.md — worked output for a 7-lead list with draft and slot proposal
  • reference/hubspot-scoring.md — HubSpot字段名称、评分权重、ICP默认值
  • reference/gotchas.md — 边缘情况：失效数据、无匹配线索、pipeline指令模糊、客户混入
  • reference/examples/happy-path-triage.md — 包含草稿和时段建议的7条线索列表的完整输出示例