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
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.
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.
AI software factories: agents that turn tickets into pull requests, and why no vendor will publish a first-attempt merge rate
The article explores the rise of AI software factories—systems where coding agents autonomously convert tickets into pull requests—and highlights the gap between widespread vendor hype and the absence of public benchmarks to validate their claims.
@notablecap: A developer prompting their way through a Jira ticket gets about 20 to 30% faster, says @rbren_dev. So that's why he sa…
A tweet shares that developers using AI prompting for Jira tickets can be 20-30% faster, and highlights a podcast episode featuring the CEO of OpenHandsDev discussing AI coding agents.
What are the best AI customer support agent tools that actually reduce ticket volume?
A user seeks recommendations for AI customer support agents that can reduce ticket volume by handling repetitive queries using documentation and knowledge bases, expressing frustration with basic chatbots that fail on specific issues.