线索资格评估
使用“线索资格评估”模板为购买意向打分、设定优先级、用线索评分排序,并将入站线索路由给销售、SDR 或培育流程——同时拦截垃圾信息。
目标:每条入站线索(联系表单、聊天、电子邮件)都能在几百毫秒内获得购买意向评分、优先级、线索评分和目标团队,而明显的垃圾信息永远不会进入你的 CRM。该模板组合了三种模式:意图路由、置信度把关路由和复合评分。
创建决策
在应用中打开 模板 → 线索资格评估 → 创建决策。草稿包含:
| 部分 | 内容 |
|---|---|
| State | message(string,必填)、company_size(number)、source(string) |
purchase_intent | probability——未来 30 天内是否有真实的购买意向?是:询问价格、演示、报价或开始日期。否:只是随便看看、学生、供应商或垃圾信息。 |
priority | score——low、medium、high、critical |
route | choice——sales(意向高,可以与销售沟通)、sdr(有一定意向,需要资格评估)、nurture(早期阶段,发送内容)、spam(垃圾信息、供应商推销或不相关)、other |
| Composite | lead_score = 2 × purchase_intent + 1 × priority + 1 × p(route = sales),取值 0 到 1——参见复合指标 |
| Policies | 1. route = spam → block · 2. purchase_intent 的置信度低于 0.6 → escalate |
在 Playground 中测试,然后部署 v1。
调用它
curl -X POST https://api.dcision.io/v1/decisions/lead-qualification \
-H "Authorization: Bearer $DCISION_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: lead-8421" \
-d '{
"state": {
"message": "We need pricing for 500 users and want to start next month.",
"company_size": 500,
"source": "website"
}
}'{
"decision_id": "dec_3fKq9ZtW1mXcV7bN2pLa",
"execution_id": "exec_8HsT2kQw9ZyR4vMn1cXe",
"schema": "lead-qualification",
"version": 1,
"result": { "purchase_intent": 0.9412, "priority": "high", "route": "sales" },
"confidence": { "purchase_intent": 0.8824, "priority": 0.69, "route": 0.85 },
"scores": { "priority": 2.81 },
"composites": { "lead_score": 0.8414 },
"action": "continue",
"action_reason": { "type": "default" },
"metrics": { "latency_ms": 412, "engine": "jev", "model": "jev-1.13.0", "estimated_cost_usd": 0.00001575, "input_tokens": 375, "output_tokens": 36 }
}你还会看到的其他结果:
| 线索 | action | action_reason |
|---|---|---|
供应商推销:route = spam | block | { "type": "policy", "rule": 0 } |
含糊的消息:purchase_intent = 0.45(置信度 0.1) | escalate | { "type": "policy", "rule": 1 } |
都不合适——一份求职申请:route = other | escalate(fallback 行动) | { "type": "other_option", "question": "route" } |
probability 的置信度为 |2p − 1|,因此规则 2 会升级所有 purchase_intent 介于 0.2 和 0.8 之间的线索——参见置信度与概率。
据此行动
async function qualify(lead) {
const response = await fetch("https://api.dcision.io/v1/decisions/lead-qualification", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.DCISION_API_KEY}`,
"Content-Type": "application/json",
"Idempotency-Key": `lead-${lead.id}`,
},
body: JSON.stringify({ state: { message: lead.message, company_size: lead.companySize, source: lead.source } }),
});
if (!response.ok) return crm.assign(lead, "sdr"); // on errors, a person decides
const { action, result, composites, execution_id } = await response.json();
switch (action) {
case "block":
return crm.discard(lead, { reason: "spam", execution_id });
case "escalate":
return crm.assign(lead, "sdr", { note: "needs review", execution_id });
default: {
const sla = { critical: "1h", high: "4h", medium: "1d", low: "3d" }[result.priority];
return crm.assign(lead, result.route, { sla, score: composites.lead_score, execution_id });
}
}
}按 lead_score 对每个团队的队列排序,优先处理最好的线索。决策未声明的字段仍会转发给引擎,因此你可以添加 country 或 page 等上下文,而无需修改 schema。
调优
-
在决策的
context中描述你的业务:你卖什么、卖给谁、价格区间。它会随每条线索一起发送。 -
用排除条件(“不适用于现有客户”、“未提及预算或时间表”)理清
sales、sdr和nurture之间的边界。如果 Playground 提示接近平局,说明这些描述有重叠。 -
即使路由的置信度很高,也把关键线索升级给人工:
{ "field": "priority", "on": "output", "operator": "gte", "value": "critical", "action": "escalate" } -
按加权等级升级,以捕捉那些即使
high是最可能等级、却仍偏向 critical 的线索:{ "field": "priority", "on": "score", "operator": "gte", "value": 3.5, "action": "escalate" }。 -
在
route上设置"minConfidence": 0.7来要求有把握的路由:低于该值时适用 fallback 行动。 -
通过修改权重或添加项——例如
− 3 × spam概率、company_fit评分——来调整lead_score,然后据此路由:{ "field": "lead_score", "operator": "gte", "value": 0.8, "action": "continue" }。 -
重放真实线索:在执行记录中打开一次运行,然后点击在 Playground 中重新运行此输入,在部署 v2 之前确认修改确实改善了结果。