mcpField
C
call-prep

call-prep

github.com/w95营销与增长28537 次安装35 周前更新
代码仓库

关于 call-prep

call-prep 是面向销售人员的通话准备技能,可研究公司并结合会议信息生成定制简报、议程和问题。连接销售工具后还能自动获取相关背景。

主要功能

  1. 01公司与参会者研究
  2. 02查询近期新闻与融资
  3. 03整合 CRM、邮件、聊天和日历信息
  4. 04生成会议议程与问题

适用场景

  1. 01准备客户探索通话
  2. 02为潜在客户定制演示
  3. 03规划谈判或季度业务回顾

安装

复制下面的命令,在终端中运行。

$npx skills add https://github.com/w95/awesome-claude-corporate-skills --skill call-prep

安装后在 Claude Code 中输入/call-prep确认已加载。

详细介绍

电话会准备

几分钟内为任何销售电话做好充分准备。此技能适用于你提供的任何上下文;连接销售工具后,效果会显著提升。

工作原理

┌─────────────────────────────────────────────────────────────────┐
│                        CALL PREP                                 │
├─────────────────────────────────────────────────────────────────┤
│  ALWAYS (works standalone)                                       │
│  ✓ You tell me: company, meeting type, attendees                │
│  ✓ Web search: recent news, funding, leadership changes         │
│  ✓ Company research: what they do, size, industry               │
│  ✓ Output: prep brief with agenda and questions                 │
├─────────────────────────────────────────────────────────────────┤
│  SUPERCHARGED (when you connect your tools)                      │
│  + CRM: account history, contacts, opportunities, activities    │
│  + Email: recent threads, open questions, commitments           │
│  + Chat: internal discussions, colleague insights               │
│  + Transcripts: prior call recordings, key moments              │
│  + Calendar: auto-find meeting, pull attendees                  │
└─────────────────────────────────────────────────────────────────┘

开始使用

运行此技能后,我会询问所需信息:

必需信息:

  • 公司或联系人姓名
  • 会议类型(需求探索、演示、谈判、跟进等)

如果有,提供以下信息会有帮助:

  • 参会人员(姓名和职务)
  • 你希望我了解的任何上下文(粘贴之前的笔记、邮件等)

如果你已连接 CRM、电子邮件或其他工具,我会自动提取上下文并跳过提问。


连接器(可选)

连接工具,增强此技能的效果:

连接器提供的信息
CRM客户详情、联系人历史记录、进行中的交易、近期活动
电子邮件与该公司的近期邮件往来、未解决的问题、已分享的附件
聊天关于该客户的内部聊天讨论(例如 Slack)、同事的见解
通话记录之前的通话录音、讨论过的主题、提及的竞争对手
日历自动查找会议,提取参会人员和说明

没有连接器? 没问题。告诉我会议情况,并粘贴你掌握的任何上下文即可。其余信息我会自行调研。


输出格式

# Call Prep: [Company Name]

**Meeting:** [Type] — [Date/Time if known]
**Attendees:** [Names with titles]
**Your Goal:** [What you want to accomplish]

---

## Account Snapshot

| Field | Value |
|-------|-------|
| **Company** | [Name] |
| **Industry** | [Industry] |
| **Size** | [Employees / Revenue if known] |
| **Status** | [New prospect / Active opportunity / Customer] |
| **Last Touch** | [Date and summary] |

---

## Who You're Meeting

### [Name] — [Title]
- **Background:** [Career history, education if found]
- **LinkedIn:** [URL]
- **Role in Deal:** [Decision maker / Champion / Evaluator / etc.]
- **Last Interaction:** [Summary if known]
- **Talking Point:** [Something personal/professional to reference]

[Repeat for each attendee]

---

## Context & History

**What's happened so far:**
- [Key point from prior interactions]
- [Open commitments or action items]
- [Any concerns or objections raised]

**Recent news about [Company]:**
- [News item 1 — why it matters]
- [News item 2 — why it matters]

---

## Suggested Agenda

1. **Open** — [Reference last conversation or trigger event]
2. **[Topic 1]** — [Discovery question or value discussion]
3. **[Topic 2]** — [Address known concern or explore priority]
4. **[Topic 3]** — [Demo section / Proposal review / etc.]
5. **Next Steps** — [Propose clear follow-up with timeline]

---

## Discovery Questions

Ask these to fill gaps in your understanding:

1. [Question about their current situation]
2. [Question about pain points or priorities]
3. [Question about decision process and timeline]
4. [Question about success criteria]
5. [Question about other stakeholders]

---

## Potential Objections

| Objection | Suggested Response |
|-----------|-------------------|
| [Likely objection based on context] | [How to address it] |
| [Common objection for this stage] | [How to address it] |

---

## Internal Notes

[Any internal chat context (e.g. Slack), colleague insights, or competitive intel]

---

## After the Call

Run **call-follow-up** to:
- Extract action items
- Update your CRM
- Draft follow-up email

执行流程

第 1 步:收集上下文

如果有可用的连接器:

1. Calendar → Find upcoming meeting matching company name
   - Pull: title, time, attendees, description, attachments

2. CRM → Query account
   - Pull: account details, all contacts, open opportunities
   - Pull: last 10 activities, any account notes

3. Email → Search recent threads
   - Query: emails with company domain (last 30 days)
   - Extract: key topics, open questions, commitments

4. Chat → Search internal discussions
   - Query: company name mentions (last 30 days)
   - Extract: colleague insights, competitive intel

5. Transcripts → Find prior calls
   - Pull: call recordings with this account
   - Extract: key moments, objections raised, topics covered

如果没有连接器:

1. Ask user:
   - "What company are you meeting with?"
   - "What type of meeting is this?"
   - "Who's attending? (names and titles if you know)"
   - "Any context you want me to know? (paste notes, emails, etc.)"

2. Accept whatever they provide and work with it
第 2 步:补充调研

始终执行(网络搜索):

1. "[Company] news" — last 30 days
2. "[Company] funding" — recent announcements
3. "[Company] leadership" — executive changes
4. "[Company] + [industry] trends" — relevant context
5. Attendee LinkedIn profiles — background research
第 3 步:综合并生成
1. Combine all sources into unified context
2. Identify gaps in understanding → generate discovery questions
3. Anticipate objections based on stage and history
4. Create suggested agenda tailored to meeting type
5. Output formatted prep brief

不同会议类型的准备方式

需求探索电话会
  • 重点:了解对方的情况、痛点和优先事项
  • 议程侧重:提问 > 讲解
  • 关键产出:资格判断信号、下一步建议
演示 / 介绍会
  • 重点:对方的具体用例、量身定制的示例
  • 议程侧重:展示相关功能、收集反馈
  • 关键产出:技术需求、决策时间表
谈判 / 方案评审
  • 重点:解决顾虑、说明价值
  • 议程侧重:处理异议、弥合分歧
  • 关键产出:达成协议的路径、明确的后续步骤
跟进 / 季度业务评审
  • 重点:已交付的价值、拓展机会
  • 议程侧重:回顾成果、发现新需求
  • 关键产出:续约信心、增购机会管线

更充分准备的技巧

  1. 上下文越多,准备效果越好 — 粘贴邮件、笔记或任何你掌握的信息
  2. 提供参会人员姓名 — 即使只提供职务,也有助于我开展调研
  3. 说明你的目标 — “我希望让他们同意开展试点”
  4. 指出顾虑 — “他们提到预算紧张”

相关技能

  • account-research — 首次联系前深入了解一家公司
  • call-follow-up — 处理通话笔记并执行会后工作流
  • draft-outreach — 调研后撰写个性化的外联内容

评论

支持 Markdown