mcpField
W
warm-transfer-execution

warm-transfer-execution

github.com/louisblytheマーケティング・グロース190404 回インストール40 週間前に更新
リポジトリ

warm-transfer-execution について

営業ボットから担当者への引き継ぎを設計する開発者向けスキルです。転送のタイミング、会話情報の共有、担当者の状況に応じた手順、品質評価を扱います。

主な機能

  1. 01転送の条件とタイミング
  2. 02見込み客への案内と引き継ぎ手順
  3. 03担当者向けコンテキストの共有
  4. 04即時・待機・非同期の転送
  5. 05転送品質の指標

活用シーン

  1. 01営業ボットの有人引き継ぎ設計
  2. 02担当者への見込み客情報の準備
  3. 03待機中や営業時間外の転送計画
  4. 04引き継ぎ結果の評価

インストール

コマンドをコピーしてターミナルで実行します。

$npx skills add https://github.com/louisblythe/sales-skills --skill warm-transfer-execution

インストール後、Claude Code で/warm-transfer-executionを入力して読み込まれたか確認します。

詳細

スムーズな引き継ぎの実行

営業ボットから人間の担当者へのシームレスな引き継ぎシステムの構築に詳しい専門家として、開発者を支援します。会話の流れを途切れさせず、スムーズに感じられる引き継ぎを実現することが目標です。

スムーズな引き継ぎとは

コールド転送(望ましくない例)
Bot: "Let me transfer you to a representative."
[Call connects]
Rep: "Hi, how can I help you?"
Prospect: "I was just talking to your chatbot about..."
Rep: "Can you start from the beginning?"
スムーズな引き継ぎ(望ましい例)
Bot: "Sarah from our enterprise team will help you
from here. She knows you're looking at the 500-user
plan for Q2. One moment while I connect you."
[Transfer happens]
Rep: "Hi [Name]! I see you're evaluating our enterprise
plan for about 500 users. I also saw you had questions
about Salesforce integration. Let's dive in!"

引き継ぎのトリガー

引き継ぎを行うタイミング
Positive triggers (opportunity):
- High-value prospect identified
- Ready to buy signals
- Request for demo/meeting
- Complex questions needing expertise
- Enterprise-level inquiry

Necessary triggers (capability):
- Bot can't answer question
- Negotiation required
- Contract/legal discussions
- Escalation requested
- Language routing needed

Rescue triggers (risk):
- Frustrated prospect
- Repeated misunderstandings
- Sensitive situation
- VIP/strategic account
- Complaint in progress
引き継ぎのタイミング
Good timing:
- Natural conversation break
- After collecting key information
- When they ask for human
- Before conversation degrades

Bad timing:
- Mid-sentence/thought
- Before understanding their need
- Without warning
- When no human available

コンテキストパッケージ

必要な情報
Transfer context must include:

PROSPECT INFO:
- Name
- Company
- Contact info
- Account history (if any)

CONVERSATION SUMMARY:
- How they found you
- What they asked about
- Key needs expressed
- Pain points mentioned
- Budget/timeline indicators

QUALIFICATION DATA:
- Company size
- Use case
- Decision timeline
- Budget range
- Decision maker status

SENTIMENT:
- Overall tone
- Frustration points
- Excitement points
- Specific concerns

RECOMMENDED APPROACH:
- What they respond to
- What to avoid
- Suggested next step
コンテキストの形式
{
  "transfer_id": "xfer_12345",
  "timestamp": "2024-01-15T14:30:00Z",
  "prospect": {
    "name": "John Smith",
    "email": "[email protected]",
    "phone": "+1-555-123-4567",
    "company": "Acme Corp",
    "title": "VP Sales",
    "account_id": null
  },
  "conversation": {
    "channel": "web_chat",
    "duration_minutes": 12,
    "messages_exchanged": 24,
    "started_at": "2024-01-15T14:18:00Z"
  },
  "summary": {
    "entry_point": "Clicked pricing page chat widget",
    "initial_question": "Enterprise pricing for 500+ users",
    "key_needs": [
      "Salesforce integration",
      "SSO/SAML support",
      "Custom reporting"
    ],
    "pain_points": [
      "Current tool doesn't scale",
      "Poor reporting capabilities"
    ],
    "objections_raised": [
      "Concerned about migration effort"
    ],
    "objections_addressed": true
  },
  "qualification": {
    "company_size": "500+ employees",
    "use_case": "Sales team productivity",
    "timeline": "Q2 implementation",
    "budget": "Mentioned 'Enterprise budget available'",
    "decision_maker": true,
    "score": 85
  },
  "sentiment": {
    "overall": "positive",
    "frustration_level": "low",
    "buying_intent": "high",
    "notes": "Impressed by Salesforce integration depth"
  },
  "transfer_reason": "Ready for demo, enterprise deal",
  "recommended_approach": "Focus on migration support and timeline",
  "conversation_transcript": "[full transcript link or embedded]"
}

引き継ぎの流れ

ステップ 1:見込み顧客に準備してもらう
"Based on what you're looking for, I think [Rep Name]
from our enterprise team would be perfect to help.
[He/She] specializes in [relevant expertise].

Before I connect you, is there anything else I should
let [them] know?"
ステップ 2:対応可能か確認する
[Internal check]
- Is rep available?
- What's estimated wait time?
- Who else can take it?

If available:
"Perfect—[Rep] is available now. Let me connect you."

If not available:
"[Rep] is with another customer right now. You'll be
connected in about [X] minutes. Would you prefer to
wait, or should I have [them] call you back?"
ステップ 3:引き継ぎを実行する
To prospect:
"Connecting you now. [Rep] has the full context of
our conversation—you won't need to repeat anything."

To rep:
[Push notification with context package]
"Incoming: John from Acme Corp. 500-user enterprise
opportunity. Ready for demo. Hot lead."
ステップ 4:引き継ぎを確認する
Rep acknowledgment:
"Got it—I see the context. Taking over."

Prospect confirmation:
Rep: "Hi John! I'm Sarah from the enterprise team.
I see you're looking at our solution for your 500-person
sales team, with Salesforce integration being key.
And you're hoping to have this in place by Q2, right?"

引き継ぎのシナリオへの対応

即時引き継ぎ(リアルタイム)
Chat/Phone - rep available:

Bot: "Connecting you with Alex now..."
[2-3 second transition]
Rep: "Hi [Name], Alex here. I saw you were asking about
[topic]. Let me help with that!"
キューに入れて引き継ぐ場合
Rep not immediately available:

Bot: "Our team is helping other customers right now.
You're [2nd] in queue—estimated wait is [3 minutes].

While you wait, is there anything else I can help with?
Or if you prefer, I can have someone call you back at
a specific time."

Options:
1. Wait in queue
2. Scheduled callback
3. Email follow-up
非同期の引き継ぎ
After hours or no availability:

Bot: "Our team isn't available right now, but I've
captured everything we discussed. [Rep Name] will
reach out first thing tomorrow.

Is email or phone better for you?"

Then send:
- Confirmation to prospect
- Full context to rep
- Calendar task for follow-up
引き継ぎ失敗時の復旧
If transfer fails:

Bot: "I apologize—we're having a technical issue
connecting you. Let me take your number and have
[Rep] call you directly within [X minutes].

What's the best number to reach you?"

Then:
- Collect callback info
- Alert rep immediately
- Log the issue
- Follow up to confirm connection made

担当者の支援

引き継ぎ前の通知
[Push notification to rep]

🔥 HOT TRANSFER INCOMING 🔥
Prospect: John Smith, VP Sales @ Acme Corp
Score: 85/100 (Enterprise)
Context: 500 users, Salesforce integration, Q2 timeline
Sentiment: Positive, ready for demo
Transfer reason: Qualified, requesting demo

[Accept] [Defer to colleague] [Schedule callback]
コンテキストの表示
Rep interface should show:
- Quick summary (scannable in 10 seconds)
- Key talking points
- Things to avoid
- Full transcript (expandable)
- Prospect profile (if in CRM)
- Suggested next steps
引き継ぎ用スクリプトの支援
Suggested opener:
"Hi John! I'm [Rep] from the enterprise team.
[Bot name] filled me in—sounds like you're looking
to upgrade your 500-person sales team before Q2.
I'd love to help make that happen."

Key points to address:
☐ Salesforce integration details
☐ Migration support (concern raised)
☐ Q2 timeline feasibility
☐ Next step: Demo scheduling

品質保証

引き継ぎの指標
Track:
- Transfer completion rate
- Time to rep pickup
- Prospect satisfaction post-transfer
- Conversation continuation rate
- Conversion rate of transfers
- Context utilization by reps
フィードバックループ
After transfer:
- Did rep find context helpful?
- Was anything missing?
- Did prospect have to repeat info?
- How could handoff improve?

Use feedback to improve context package.

コメント