AI support vendor quoted 40% deflection, called 8% normal after 8 months
Summary
A founder shares experience with an AI support bot that only achieved 8% ticket deflection after 8 months, compared to a peer's 47%, highlighting the difference between AI-native tools and legacy ticketing systems with LLM wrappers.
Similar Articles
Support agents that actually close tickets vs ones that just deflect, what's the difference?
The article compares AI customer support agents that effectively resolve tickets with those that deflect, highlighting key features like tool integration, helpdesk compatibility, and clear escalation rules.
We put AI into a client's support inbox last year. Here's what changed and what didn't.
An AI agency shares their experience implementing AI in a client's support system, detailing benefits like improved self-service and agent efficiency, but noting that AI cannot fix underlying policy issues and requires ongoing maintenance.
A client paid me to rip the AI out of the tool I built them.
A developer built an LLM-powered ticket routing tool, but the support team distrusted the black-box decisions. The client paid to replace the LLM with a simple rules engine, resulting in higher accuracy, lower costs, and greater user trust.
Our AI agent ROI looked a lot better before we counted repeat tickets.
作者重新计算 AI 客服 agent 的 ROI:原以为 78% 自动关单、11% 重开率很好,但按客户+订单号+意图标签匹配 7 天内的新工单后,发现约 13% 的"已解决"其实是同一问题重开,实际近四分之一仍需人工,单次成功任务成本从 $0.54 升到 $0.71。文中用 Pointfive 做调用追踪、Zendesk 存工单,并询问重复工单的最佳匹配键。
We deployed AI agents across our company, including autonomous support in Jira. AMA.
A company deployed AI agents across their organization for autonomous support in Jira, internal knowledge assistance, and documentation writing, achieving 70%+ auto-resolve on repetitive tickets and faster response times.