arXivDaily arXiv每日学术速递 周一至周五更新
arXiv 2607.01426cs.AIcs.CL
收藏

服务代理何时应重新考虑?客户服务运营中的难度路由控制

When Should Service Agents Reconsider? Difficulty-Routed Control in Customer-Service Operations

The Pennsylvania State University(宾夕法尼亚州立大学)

Qian Chen, Chengyuan Liu, Xin Yu

AI总结:

提出一种难度路由的服务控制架构,通过轻量级路由器将常规会话与操作耦合会话分流,在关键后端写入前集中审查,提升零售和航空任务的可靠性。

摘要:

自主客户服务代理正从对话界面转向操作执行角色:它们检索公司记录、应用服务策略,并执行后端写入,如退款、取消、换货、订单修改和预订变更。这种转变带来了服务控制问题:公司必须保持常规服务快速且低摩擦,同时防止在客户指令、策略约束、公司记录和后端写入交互的请求上出现操作错误。我们提出了一种难度路由的服务控制架构,询问服务代理在行动前何时应重新考虑。轻量级路由器将常规会话保持在低成本基线路径上,并将操作耦合的会话路由到升级工作流。升级路径使用冲突感知通信和写入触发的重新考虑,在关键后端写入前集中进行审议和安全保障,而不是对所有服务会话统一应用额外控制。我们在来自 $\ au^{2}$-bench 的人工验证的零售和航空任务上评估了该架构。在零售中,该方法在具有操作冲突的服务请求上持续提高了可靠性。路由证据表明,更强的控制被导向冲突请求,而非广泛应用于常规请求。对话和工具使用概况表明,收益并非来自无差别的交互扩展或更广泛的工具链;相反,增加的轮次和工具调用支持证据收集、写入分离和写入前重新考虑。案例级证据表明,升级工作流保留了后备计划,将检索到的记录绑定到正确的操作,排序写入,并分解多实体请求。航空结果将相同的服务控制逻辑扩展到预订操作。

英文摘要:

Autonomous customer-service agents are shifting from conversational interfaces toward operational execution roles: they retrieve firm records, apply service policies, and execute backend writes such as refunds, cancellations, exchanges, order modifications, and reservation changes. This shift creates a service-control problem: firms must keep routine service fast and low-friction while preventing operational errors on requests where customer instructions, policy constraints, firm records, and backend writes interact. We propose a difficulty-routed service-control architecture that asks when service agents should reconsider before acting. A lightweight router keeps routine sessions on a low-cost baseline path and routes operationally coupled sessions to an escalated workflow. The escalated path uses conflict-aware communication and write-triggered reconsideration to concentrate deliberation and safeguards before consequential backend writes, rather than applying additional control uniformly across all service sessions. We evaluate the architecture on human-verified retail and airline tasks from $τ^{2}$-bench. In retail, the method improves reliability consistently on service requests with operational conflict. Routing evidence shows that stronger control is directed toward conflicted requests rather than broadly applied to routine ones. Dialogue and tool-use profiles suggest that gains do not come from indiscriminate interaction expansion or broader tool chains; instead, added turns and tool calls support evidence gathering, write separation, and pre-write reconsideration. Case-level evidence shows that the escalated workflow preserves fallback plans, binds retrieved records to the correct action, sequences writes, and decomposes multi-entity requests. Airline results extend the same service-control logic to reservation operations.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑