Customer Support Experience Interview: Discussion Guide
Use this guide with customers who closed a support case in the last 14 days. It follows one case from the first problem to the outcome. It shows where effort and trust were lost or won.
- Length
- 20 min
- Questions
- 13
- People
- 10 to 12
- Sections
- 5
What this guide finds out
- What customers try before they contact support, and why self-help failed.
- The steps in the case where the customer had to repeat information or wait.
- If the customer thinks the problem is solved, compared with the case status.
- How the case changed the trust of the customer in the product.
When to use it
- Your support satisfaction scores drop and the ticket data does not show why.
- You plan to change channels, for example add a chatbot or remove phone support.
- You want to reduce repeat contacts about the same problem.
Who to talk to
Customers with a support case closed in the last 14 days, with a mix of good and bad ratings. Talk to 10 to 12 people. Each interview takes about 20 minutes.
The discussion guide
Each question has a probe note. The note tells the moderator, a person or an AI, what to do with the answer.
Warm-up
2 minLearn how the customer uses the product.
Tell me a little about how you use the product.
ProbeDo not ask a follow-up. Record the answer as context.
Before this case, how often had you contacted our support?
ProbeIf this was not the first time, ask how this case compared with the last one.
The problem
5 minLearn what happened before the customer contacted support.
Think about the problem that made you contact us. What were you trying to do when it happened?
ProbeAsk how urgent it was and what it stopped them from doing.
What did you try before you contacted support?
ProbeAsk if they searched the help center, asked a colleague or searched the web. Ask why each step did not solve it.
How did you choose the way to contact us?
ProbeAsk which channel they used and if they looked for a different one first.
The case
7 minFollow the case step by step and find the points of effort.
Walk me through what happened after you contacted us, step by step.
ProbeLet them tell the full story. Then ask how long the full case took, in their view.
Was there a point where you had to explain the problem again?
ProbeAsk how many times and to whom. Ask how that felt.
Was there a point where you waited and did not know what was happening?
ProbeAsk what they did while they waited. Ask if they contacted us again during the wait.
How did the person or the bot that helped you speak to you?
ProbeAsk for one thing that helped and one thing that did not. Do not ask for the name of the agent.
The outcome
4 minLearn if the problem is solved and how the case changed trust.
Is the problem solved now?
ProbeIf not, ask what is still wrong. If they used a workaround, ask what it is.
How did this case change how you feel about the product, if at all?
ProbeAsk what would have made the case better. Ask for one change.
Close
2 minEnd the interview.
If this problem happened again tomorrow, what would you do first?
ProbeRecord if they would contact support, search alone or give up. Do not ask a follow-up.
Is there anything else about our support that you want to tell us?
ProbeThank them and end the interview.
Example finding
Several customers with closed cases still used a workaround. They did not contact us again because they expected the same wait.
“They closed it and said it was fixed. It was not, but I just export it by hand now. I did not want another week of emails.”
Mistakes to avoid
- Do not use the interview to solve the problem again. If the problem is still open, tell the support team after the call.
- Do not ask the customer to rate a named agent. Customers then hold back, and the study becomes a review of a person.
- Do not talk only to customers with bad ratings. Good cases show what to keep when you change the process.
- Do not trust the case status as the outcome. A closed case can still be an unsolved problem for the customer.
Analyze the answers
Analysis templateSupport Ticket Analysis: Contact Reason CodebookUse this codebook to code support tickets, chats and support emails by contact reason. Then tag each ticket as preventable or not, so the product team sees which tickets it can remove.Questions
Ask about one recent case, step by step. Ask what the customer tried first, where they repeated themselves, where they waited and if the problem is solved.
Interview within 14 days of the case closing. After that, customers remember how they felt but not the steps.
Yes. Code the tickets first to find common problems. Then use interviews to learn the effort and the feelings that the tickets do not show.
Let the AI moderator ask these questions
The AI moderator interviews screened people by voice or text. Each claim in the study report links to its clip. The first 3 interviews are free.