Resolution and deflection
Insights counts every conversation two ways: by its outcome, and by two rates. Both come from what hiy recorded, never from a visitor’s browser.
Outcomes
Each conversation gets one outcome 24 hours after its last message, from fixed rules. No AI judges it.
- Resolved, confirmed: the visitor gave a thumbs up or said it helped after the last answer.
- Resolved, assumed: the visitor left after an answer and didn’t ask again. Not proof it helped.
- Handed over: a person was asked for, took over or replied. Never counted as the agent’s.
- Unresolved: the last answer said it couldn’t answer, got a thumbs down, or never came.
- Not counted: no question reached the agent, or it was a test.
Resolved by the agent is confirmed plus assumed, shown from 20 counted conversations. Insights › Resolutions lists the conversations behind each outcome. Open one to see why it got its outcome; on Growth you can change it. A new message opens it again.
What each rate counts
Two rates show how often your agents answered, and how often they said they couldn’t. Each is added up across your agents, over the last 30 days.


- Answered, also called the deflection rate: conversations where the agent never said it couldn’t answer.
- Unanswered rate: conversations where the agent said it couldn’t answer, including ones it then handed over.
The two add up to 100% of the same conversations. Each card shows the two numbers it comes from, such as of 80. Press a card to see every agent’s own count.
Read your rates
It’s in the sidebar, under Work. The Rates row has a card for each rate. Press one to list your agents.
Press the ? beside a rate to see exactly what it counts.
The questions your agents couldn’t answer are on Teach queue. Teach an answer once and every similar question is covered from then on.
Questions by topic
On Insights › Questions, the Questions by topic card shows what people ask about. Press New topic to name one and add a few example questions, or start from a name suggested from your top questions. A question counts under up to three topics it matched, and under No topic when it matched none.
Counting starts when you add a topic, so earlier questions are not counted. The card follows the agent and channel filters at the top of Insights.
See what your agents take off your team on a dashboard of your own: pick cards from the catalogue, then New, Rename or Delete. Dashboards show where your workspace has them; they are not on for everyone yet. Download CSV saves these counts for the period, agent and channel you picked.
Download the counts
Download CSV, at the end of the filter row on Insights, saves the counts for the date, agent and channel you picked: totals, other counts, each day, each agent, each channel and, where shown, outcomes. Rates are not in the file.
Below twenty conversations, no percentage at all
Until your agents have had 20 conversations in the window, a rate shows how far along it is, such as Collecting · 7 of 20. A rate from a handful of chats swings with every new one, so hiy waits until the number means something.
What these rates don’t tell you
- Whether a problem was solved. Answered means the agent never said it couldn’t help. Outcomes, above, are for whether it was solved.
- Whether anyone was handed over. A visitor can ask for a person after a good answer, and that conversation still counts as answered. Handovers are in your Inbox.
- How tidy your queue is. Teaching or dismissing a question later doesn’t change a rate that already counted it.
Good to know
- Rates always cover the last 30 days, whatever date or channel you pick on Insights.
- A window too busy to count exactly shows a dash and says so, instead of a guess.
- The counts come from what hiy recorded, never from a visitor’s browser.
- Your own questions in Test don’t count.
- With outcomes on, Answered sits under the ? beside Resolved by the agent.