Objective
For customers already being followed up, combine CRM follow-up records to determine the product matching path and output an executable deal-closing plan.
Knowledge Base References
Load the following documents (relative to this skill directory):
- Product System Overview:
knowledge/claude.md - Pre-sales Digital Employee Product Description:
knowledge/数字员工/售前数字员工产品说明书.md - Langtum Platform Introduction:
knowledge/langtum/什么是langtum.md - Langtum Platform Architecture:
knowledge/langtum/Langtum平台架构.md - Langtum Use Cases:
knowledge/langtum/Langtum使用场景.md
Dependencies
lcrm-searchskill: Obtain customer business records (follow-up history)
Workflow
Step 1: Obtain Customer Information
Proactively ask the user:
- What is the customer name?
- What requirements or scenarios are already known?
- Are there any follow-up records to reference?
If follow-up records need to be referenced, call the lcrm-search skill to obtain the customer's business records:
- Script:
node scripts/search.mjs customer-business-records --customer-id "<customerId>" - If the customerId is unknown, first use:
node scripts/search.mjs customers --company-name "<客户名>" --limit 5
Step 2: Determine the Product Matching Path
| Customer Characteristics | Recommended Path |
|---|---|
| Complex SKUs/Frequent bidding/B2B/Direct sales team | Pre-sales Digital Employee deal-closing strategy |
| Does not match the above profile, but has AI needs or business process optimization needs | Langtum platform deal-closing strategy |
Step 3: Output the Deal-Closing Strategy
Pre-sales Digital Employee Path
Based on the 5 core capabilities + customer scenarios, output:
| Output Item | Content |
|---|---|
| Match Rating | High/Medium/Low + analysis of match points (product features/sales model/industry) |
| Core Entry Points | At most 3, sorted by priority, each including talking points |
| Objection Handling | Address the 3 main objections the customer may raise |
| Next Steps | Clear 1-2 advancement actions |
Reference for the 5 core capabilities:
- ① Deep knowledge ingestion and precise Q&A → Applicable: many SKUs, sales cannot remember parameters
- ② Consultative needs guidance → Applicable: vague needs, reliance on veteran experience
- ③ Deterministic logical reasoning and calculation → Applicable: compatibility verification, high cost of misconfiguration
- ④ Strong compliance and bid document generation → Applicable: frequent bidding, time-consuming bid writing
- ⑤ Solution and quotation closed loop → Applicable: complex configuration lists, cross-department verification
Langtum Platform Path
Based on the customer's business pain points, output:
| Output Item | Content |
|---|---|
| Core Pain Points | Inefficient links in the customer's business processes |
| Platform Capability Match | Chatbot/Multi-Agent/Workflow/Knowledge Base/Plugin System |
| Custom Scenario Suggestions | Specifically which module is used to solve which problem |
| Entry Talking Points | Opening + value proposition |
| Next Steps | Clear 1-2 advancement actions |
Output Style Requirements
- Structured: use tables and lists, no long blocks of text
- State the conclusion directly: put the core point first
- Speak plainly: avoid AI jargon, use the customer's business language
- Quantify value: every value point must have a number
- Actionable: give a clear next step