销售 · 进阶
销售线索筛选
把潜在销售机会与合作、客服、Spam 和目的不明的消息区分开。
ChoiceNoulScore
适合什么时候使用
- 销售线索
- CRM 分流
- 销售提醒
示例 state
{
"message": "We have 35 support agents and need SSO. Can we get a security review and pricing call this week?",
"source": "contact_form"
}决策问题
Choiceinbound_type
判断这条收到的消息应该进入哪一类。
sales— 正在评估购买的潜在客户partnership— 提出业务合作support— 现有客户寻求帮助spam— 群发广告或无关推广unclear— 目的不明确
Noulqualified
消息中是否有具体证据表明这是值得人工跟进的销售机会?
Scorepriority
将跟进优先级评为 0 到 3。
- 0 — 不需要销售跟进
- 1 — 兴趣较弱或仍处于早期
- 2 — 有明确需求或正在评估
- 3 — 有明确需求,并且正在推进近期采购
预期输出
一个消息分类结果、值得销售跟进的概率,以及跟进优先级。
TypeScript 示例
import { choice, noul, score, TypeSafeClient } from "@typesafe-ai/sdk";
const client = new TypeSafeClient();
const result = await client.systemOne({
state: {
message:
"We have 35 support agents and need SSO. Can we get a security review and pricing call this week?",
source: "contact_form",
},
questions: {
inbound_type: choice("Choose the route for this inbound message.", {
sales: "A potential customer evaluating a purchase",
partnership: "A proposed business collaboration",
support: "An existing customer seeking help",
spam: "Unsolicited generic promotion",
unclear: "Purpose is unclear",
}),
qualified: noul(
"Does the message contain concrete evidence of a sales opportunity worth human follow-up?"
),
priority: score("Score follow-up priority.", [
"No sales follow-up",
"Weak or early interest",
"Concrete need or evaluation",
"Concrete need plus near-term procurement action",
]),
},
});为什么这样设计
- 先把销售机会和联系表单里的其他消息分开。
- 是否值得销售跟进,要看消息里的实际信息,而不是只看对方像不像一家公司。
- 把“值不值得跟进”和“优先级多高”分开,团队可以分别设置阈值。
注意事项
- 除非 state 里有明确信息,否则不要推断预算、决策权或公司规模。
- 高分也不应绕过正常的用户同意和联系规则,自动触达某个人。
来源与参考
这个模板和来源链接最近核验:2026-09-21。
继续浏览
先在Playground中运行这个模式,浏览全部模板,了解官方 SDK 用法,或使用成本计算器估算实际使用成本。