Reference table
What support tickets can and cannot tell you

Seven questions support and CX teams get asked, with whether ticket data can answer each one and what can. Tickets are good at what breaks and what costs agent time. They rarely say what the customer was trying to do, and never why self-service failed or whether the customer will churn. Use the table to decide where ticket analysis stops and follow-up interviews should start.
Where this appears
What's in this reference table
| Question | Tickets answer it? | What actually answers it |
|---|---|---|
| What is breaking most often? | Yes | Ticket analysis |
| Which issues cost the most agent time? | Yes | Ticket analysis |
| What was the customer trying to accomplish? | Rarely | Follow-up interview |
| What did they try before contacting you? | No | Follow-up interview |
| Why did self-service fail them? | No | Interview with deflected users |
| Are they going to churn over this? | No | Post-resolution research |
| What would have prevented the contact entirely? | No | Interview with the customer |
Use this image
Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:
html
<a href="https://www.koji.so/visuals/what-support-tickets-can-and-cannot-tell-you"><img src="https://www.koji.so/visuals/what-support-tickets-can-and-cannot-tell-you/what-support-tickets-can-and-cannot-tell-you.png" alt="Table of seven questions support teams ask, showing that tickets answer only the first two and which kind of interview answers the rest." width="1200" height="881" /></a>
<p>Source: <a href="https://www.koji.so/visuals/what-support-tickets-can-and-cannot-tell-you">What support tickets can and cannot tell you</a>, Koji</p>




