部署一个包含3个代理的客户支持分流系统。适用于以下场景:1. 用户希望实现自动化工单路由和分流;2. 用户正在...
客户支持 Trage 设置是一项面向实际任务的技能,主要用于部署3个分类、 自动解析和升级支持门票的代理;Roles.;
它将相关步骤、工具调用和结果整理方式集中到统一流程中,帮助使用者更快完成目标并减少重复操作。使用时应结合输入条件选择合适的执行方式,核对必要参数、依赖环境与输出内容,并按原始要求处理异常情况。从功能定位来看,该技能强调把分散的操作要求整理成清晰、可复用的处理流程,使用户能够围绕既定目标快速准备输入、选择执行方式并获得结构化结果。实际使用前应先确认任务范围、数据来源、运行环境、必要权限和关键参数,再依据技能说明逐步执行;
若输入条件不完整,应先补齐信息或采用保守配置,避免因错误假设导致结果偏离需求。执行过程中需要关注工具调用是否成功、接口或依赖是否可用、输出格式是否符合预期,并对异常提示、缺失字段和边界情况进行处理;涉及批量任务时,还应保存进度,避免中断后重复操作。该技能适合用于一次性任务,也可以接入自动化工作流,与其他技能或上层代理配合完成更完整的业务链路;在组合使用时,应明确每一步的输入输出关系,并避免不同步骤之间出现参数冲突。
部署 3 个智能体,分别用于工单分类、自动解决和人工升级。
| 角色 | 主机名 | 技能 | 用途 |
|---|---|---|---|
| triage-bot | |
pilot-event-filter, pilot-priority-queue, pilot-task-router | 按紧急程度对工单进行分类,并路由至对应处理方 |
| resolver | |
pilot-task-router, pilot-receipt, pilot-audit-log | 基于知识库自动解决常规查询 |
| escalator | |
pilot-webhook-bridge, pilot-slack-bridge, pilot-alert | 增强复杂问题上下文信息,并升级至人工处理 |
步骤 1: 向用户询问该智能体应承担的角色及所用前缀()。
步骤 2: 安装所选角色所需的技能:
# 部署 triage-bot: clawhub install pilot-event-filter pilot-priority-queue pilot-task-router # 部署 resolver: clawhub install pilot-task-router pilot-receipt pilot-audit-log # 部署 escalator: clawhub install pilot-webhook-bridge pilot-slack-bridge pilot-alert
步骤 3: 设置主机名:
pilotctl --json set-hostname-
步骤 4: 编写部署清单文件(manifest):
mkdir -p ~/.pilot/setups cat > ~/.pilot/setups/customer-support-triage.json << 'MANIFEST' <角色专属清单,见下方模板> MANIFEST
步骤 5: 提示用户与直连通信对端(peers)发起握手(handshake)。
{
"setup": "customer-support-triage",
"setup_name": "Customer Support Triage",
"role": "triage-bot",
"role_name": "Triage Bot",
"hostname": "-triage-bot",
"description": "Receives incoming support tickets, classifies by urgency and category, routes to the right handler.",
"skills": {
"pilot-event-filter": "Filter and classify incoming tickets by urgency (low/medium/high/critical) and category (billing/technical/account).",
"pilot-priority-queue": "Queue tickets by priority so critical issues are routed immediately.",
"pilot-task-router": "Route classified tickets to resolver for routine issues or escalator for complex ones."
},
"peers": [
{ "role": "resolver", "hostname": "-resolver", "description": "Handles routine tickets with knowledge base lookups" },
{ "role": "escalator", "hostname": "-escalator", "description": "Handles complex tickets requiring human attention" }
],
"data_flows": [
{ "direction": "send", "peer": "-resolver", "port": 1002, "topic": "ticket-routine", "description": "Routine tickets for automated resolution" },
{ "direction": "send", "peer": "-escalator", "port": 1002, "topic": "ticket-complex", "description": "Complex tickets requiring human attention" }
],
"handshakes_needed": ["-resolver", "-escalator"]
}
{
"setup": "customer-support-triage",
"setup_name": "Customer Support Triage",
"role": "resolver",
"role_name": "Auto-Resolver",
"hostname": "-resolver",
"description": "Handles routine queries using knowledge base lookups -- order status, FAQs, password resets.",
"skills": {
"pilot-task-router": "Match incoming ticket category to the appropriate knowledge base article or resolution workflow.",
"pilot-receipt": "Send resolution confirmation back to the triage bot for tracking.",
"pilot-audit-log": "Log every auto-resolution with ticket ID, category, and resolution method for compliance."
},
"peers": [
{ "role": "triage-bot", "hostname": "-triage-bot", "description": "Sends routine tickets for auto-resolution" }
],
"data_flows": [
{ "direction": "receive", "peer": "-triage-bot", "port": 1002, "topic": "ticket-routine", "description": "Routine tickets for automated resolution" }
],
"handshakes_needed": ["-triage-bot"]
}
{
"setup": "customer-support-triage",
"setup_name": "Customer Support Triage",
"role": "escalator",
"role_name": "Escalation Agent",
"hostname": "-escalator",
"description": "Takes complex issues, enriches with customer history and context, forwards to human support via webhook or Slack.",
"skills": {
"pilot-webhook-bridge": "Forward enriched tickets to the helpdesk system (Zendesk, Freshdesk, etc.) via webhook.",
"pilot-slack-bridge": "Post escalation summaries to the support team Slack channel with ticket context.",
"pilot-alert": "Send urgent alerts for critical-priority tickets that need immediate human response."
},
"peers": [
{ "role": "triage-bot", "hostname": "-triage-bot", "description": "Sends complex tickets that need human attention" }
],
"data_flows": [
{ "direction": "receive", "peer": "-triage-bot", "port": 1002, "topic": "ticket-complex", "description": "Complex tickets requiring human attention" },
{ "direction": "send", "peer": "external", "port": 443, "topic": "escalation", "description": "Escalated tickets to helpdesk and Slack" }
],
"handshakes_needed": ["-triage-bot"]
}
triage-bot -> resolver :ticket-routine(端口 1002)triage-bot -> escalator :ticket-complex(端口 1002)escalator -> external :通过 webhook 升级工单(端口 443)# triage-bot 与 resolver 和 escalator 建立握手: pilotctl --json handshake-resolver "setup: customer-support-triage" pilotctl --json handshake -escalator "setup: customer-support-triage" # resolver 和 escalator 分别向 triage-bot 回执握手: pilotctl --json handshake -triage-bot "setup: customer-support-triage" pilotctl --json handshake -triage-bot "setup: customer-support-triage"
# 在 resolver 上 —— 订阅常规工单: pilotctl --json subscribe-triage-bot ticket-routine # 在 escalator 上 —— 订阅复杂工单: pilotctl --json subscribe -triage-bot ticket-complex # 在 triage-bot 上 —— 路由一条常规工单: pilotctl --json publish -resolver ticket-routine '{"ticket_id":"TK-4821","category":"account","urgency":"low","subject":"Password reset"}' # 在 triage-bot 上 —— 路由一条复杂工单: pilotctl --json publish -escalator ticket-complex '{"ticket_id":"TK-4822","category":"technical","urgency":"critical","subject":"Data loss in production"}'
需具备 pilot-protocol 技能、pilotctl 可执行文件、clawhub 可执行文件,以及一个正在运行的守护进程(daemon)。
相关专题
热门下载
相关下载
精品课程
共6课时 | 54.7万人学习
共89课时 | 134.1万人学习
共49课时 | 82.6万人学习