call-list

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Run the lead prioritization. Scan the pipeline, rank by urgency and opportunity, pull relevant email context, and get the owner ready to make calls.
Parse arguments:
  • --n
    (default:
    5
    ) — number of leads to surface (1–10)
  • --date
    (default: today) — date to build the call list for (
    YYYY-MM-DD
    )
执行销售线索优先级排序。扫描销售管道,按紧急程度和机会价值排序,提取相关邮件上下文,让负责人做好致电准备。
解析参数:
  • --n
    (默认值:
    5
    )—— 展示的线索数量(1–10)
  • --date
    (默认值:今日)—— 生成呼叫列表的日期(格式为
    YYYY-MM-DD

Step 1 — Pipeline scan

步骤1 — 销售管道扫描

Using the
lead-triage
skill workflow:
  1. Pull open HubSpot deals and contacts with activity in the last 30 days.
  2. Pull email threads from Mail for each lead (last 3 emails per contact).
  3. Score each lead on:
    • Recency: days since last owner touchpoint (lower = better)
    • Stage: how close to close (later stage = higher priority)
    • Signal: any recent inbound activity (email open, reply, calendar hold, web visit)
    • Value: deal size from HubSpot
使用
lead-triage
技能工作流:
  1. 提取HubSpot中过去30天有活动记录的未结交易和联系人。
  2. 为每位线索提取Mail中的邮件线程(每位联系人最近3封邮件)。
  3. 从以下维度为每位线索评分:
    • 时效性:距离负责人上次接触的天数(天数越少评分越高)
    • 阶段:交易完成的接近程度(阶段越靠后优先级越高)
    • 信号:近期是否有潜在客户主动活动(邮件打开、回复、日历预约、网站访问)
    • 价值:HubSpot中的交易规模

Step 2 — Rank and select top N

步骤2 — 排序并选择前N位线索

Rank all scored leads and select the top
--n
. For ties, prefer leads with unanswered inbound signals.
For each selected lead, produce a call card:
{Rank}. {Contact Name} — {Company}
Deal: ${amount} | Stage: {stage} | Last contact: {X days ago}
Signal: {most recent activity}

TALKING POINTS
• {point from email/deal context}
• {point from email/deal context}
• {open question to ask}

GOAL FOR THIS CALL: {one sentence — advance to next stage / re-engage / close}
对所有已评分的线索进行排序,选出前
--n
位。若出现评分相同的情况,优先选择有未回复主动信号的线索。
为每位选中的线索生成呼叫卡片:
{Rank}. {Contact Name} — {Company}
Deal: ${amount} | Stage: {stage} | Last contact: {X days ago}
Signal: {most recent activity}

TALKING POINTS
• {point from email/deal context}
• {point from email/deal context}
• {open question to ask}

GOAL FOR THIS CALL: {one sentence — advance to next stage / re-engage / close}

Step 3 — Calendar block

步骤3 — 日历预留

For each lead on the list, offer to block 20 minutes on the owner's calendar for the target date.
Show the proposed calendar entries:
{time slot} — Call: {Contact Name} ({Company})
Wait for owner to confirm which calls to block before creating calendar events.
为列表中的每位线索,在负责人的日历上为目标日期预留20分钟时间。
展示拟议的日历条目:
{time slot} — Call: {Contact Name} ({Company})
在创建日历事件前,等待负责人确认需要预留哪些呼叫的时间。

Step 4 — Draft follow-ups

步骤4 — 草拟跟进邮件

For any lead that has an unanswered email older than 3 days, draft a brief follow-up:
Subject: Re: {thread subject}

Hi {first name},

{One sentence referencing prior conversation}. {One sentence with a clear next step or question}.

{Sign-off}
对于任何有超过3天未回复邮件的线索,草拟简短的跟进邮件:
Subject: Re: {thread subject}

Hi {first name},

{One sentence referencing prior conversation}. {One sentence with a clear next step or question}.

{Sign-off}

Connector failures

连接器故障处理

If HubSpot is unreachable, stop and tell the owner — lead scoring requires CRM data. If Mail is unreachable, skip Steps 3-4 (email context and follow-ups) and note "Mail not connected — email context and follow-up drafts skipped" in output. If Google Calendar is unreachable, skip calendar blocking and note it.
若无法连接HubSpot,立即停止操作并告知负责人——线索评分需要CRM数据。若无法连接Mail,跳过步骤3-4(邮件上下文和跟进邮件),并在输出中注明“Mail未连接 — 跳过邮件上下文和跟进邮件草拟”。若无法连接Google Calendar,跳过日历预留步骤并注明该情况。

Approval gates

审批规则

  • Never send emails automatically. Present drafts for owner approval only.
  • Never create calendar blocks without owner confirmation — show the proposed list first.
  • Never update HubSpot deal stages automatically.
  • 禁止自动发送邮件。仅向负责人展示草拟内容以获取审批。
  • 禁止未经负责人确认创建日历预留 — 先展示拟议列表。
  • 禁止自动更新HubSpot交易阶段

Output

输出内容

Present the ranked call list with talk tracks. Then show proposed calendar blocks and ask for confirmation. Then show follow-up drafts and ask which to send.
先展示排序后的呼叫列表及通话脚本。然后展示拟议的日历预留并请求确认。最后展示跟进邮件草拟内容并询问发送哪些邮件。