Customer Support · 10 min read · May 2026
Customer Support AI That Actually Deflects in 2026: Post-Klarna Lessons
By Thinklytics, AI Workflow Automation Practice
Klarna walked back its agent-only customer service deployment after admitting cost was a too-predominant evaluation factor and quality dropped. Reddit's Salesforce Agentforce 360 deployment deflected 46 percent of support cases and cut resolution time by 84 percent. Bank of America's Erica passed 3 billion interactions with 98 percent of users finding what they need. Decagon reports 80%+ deflection at named clients. Here is what works in customer support AI in 2026, what fails, and how to build the deflection rate that actually holds up.
Topics covered
- customer-support
- ai-agents
- deflection
- cx
- agent-fleet
Frequently asked questions
What's a realistic deflection target for the first category?
40-60 percent for the first category if scoped to a predictable / repeatable type (password reset, order status, basic billing inquiry). 60-80 percent for the second and third categories once the operational layer is in place.
Should we use Klarna as a cautionary tale internally?
Yes, with the CEO quote. The cost-as-dominant-factor failure mode is the most common internal political failure mode and the Klarna case gives the CFO and the COO a shared reference point.
What about the AI agent disclosure laws?
California, Utah, and Texas all have AI disclosure laws on the books or in committee for 2026. The 14 percent of consumers who lose trust if AI is hidden is the demand-side rationale. Disclose AI by default; it is the new standard.
What's the right relationship between AI deflection and live-rep capacity?
Plan for a 60-80 percent agent-handled / 20-40 percent human-handled ratio at maturity, with human-handled biased toward higher-revenue or higher-stakes interactions. Klarna's failure was eliminating the human escalation path; the success cases all preserve it.
How does this fit with the broader agent fleet?
The customer-support AI is one fleet within the larger enterprise agent fleet. Apply the Operating an Agent Fleet in 2026 operating model: shared identity, shared observability, shared eval harness, shared incident-response playbook. --- If you want the longer version of this analysis, including the vendor selection matrix, the deflection-quality measurement playbook, and the AI-disclosure compliance template, our AI Workflow Automation Consulting, AI Readiness, and Analytics & BI practices ship the operating model. The broader agent fleet operating context is in our Operating an Agent Fleet…
What about regulatory disclosure laws for AI in support?
California (SB 243), Colorado (the AI Act), and the EU AI Act all require disclosure that the user is interacting with AI. The disclosure has to be clear and upfront; buried in a terms-of-service link is not enough. Most modern support AI vendors handle this with a banner; verify in your pilot.
Should we use Klarna as a cautionary tale internally?
Klarna's reversal from AI-first to bringing humans back is misread as 'AI failed.' Reading the Klarna writeup, the issue was scope creep, not AI inadequacy. They turned AI on for use cases beyond deflection (refunds, account changes) without the data plumbing those need. Stick to documented questions and AI deflection works.
How does Thinklytics measure deflection in a pilot?
Closed without escalation AND without customer reopen within 30 days. Most vendor-claimed deflection rates are inflated because they count first-touch resolution but ignore reopens. Our pilots measure both. Read more at [customer support AI automation](/services/customer-support-ai-automation).