🤔 Imagine you're chasing a refund. You message your bank to ask what might be causing a delay. The AI agent handling the chat tells you it's being processed, then closes the conversation. Three weeks later the money still hasn't landed, so you get back in touch, and your follow-up opens as a brand new ticket.
On the bank's dashboard, both of these conversations count as wins: two tickets left the support queue without a human getting involved. This is called deflection, and a lot of teams grade their AI agent’s effectiveness by measuring deflection rate. At Gradient Labs, we know it isn't a true indicator of success.
💡 Deflection tells you a chat ended, but it doesn't tell you the customer got what they needed. Worse, every time an unsolved problem comes back as a fresh ticket, the deflection rate looks better, but the customer gets more frustrated.
So how do you know if your AI agent is actually solving your customers' problems? You look at the resolution rate. 👈
Resolution is a much harder number, but it’s an honest one. Push to automate resolution rather than deflection, and you'll move past the 60–65% ceiling that stalls teams focused on deflection alone.
Want to understand the difference properly? We wrote a full breakdown at the link in the thread. ⬇️