Customer research workshop / 5 MIN READ
Turn a support conversation into a better research question
Use service records to identify uncertainty before commissioning a study.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
Support conversations can reveal moments that deserve investigation. Their immediate purpose and coverage shape what they contain, so the useful research move is to define a question that further work can answer.
What you will leave with: A service-signal note linking a permitted record to an open research question.
Use this when
- A team wants to learn from existing support material.
- A vivid customer complaint is being treated as the whole audience’s view.
This is not operational ticket triage, a root-cause analysis of service defects or a prevalence estimate.
Read records within their original purpose
GOV.UK discovery guidance includes examining existing evidence such as support logs. Use only records you are authorized to inspect for the relevant purpose.
Identify what the record was created to do: solve an immediate problem, document a complaint or route a request. Note how that purpose may shape the wording. A support agent’s summary may omit the customer’s reasoning, and a resolved ticket may leave important questions unanswered. Remove personal details from the working research note unless they are genuinely needed and appropriately protected.
Extract the uncertainty, not just the frustration
Write the specific moment that raises a question. A buyer asking whether two documents are the same might suggest uncertainty about terminology, versioning or approval status. Preserve these competing possibilities instead of deciding immediately that the customer needs more education.
Ask what the record establishes and what it does not. It may show that someone asked a question, but not what they saw before asking or whether other people had the same difficulty. Keep the original evidence reference so the team can inspect context through the proper access route. Do not turn a paraphrase into an exact customer quote.
Choose a question that new research can address
Translate the uncertainty into a bounded question about a task or decision. For example: how do buyers decide which certificate applies to their order? Then identify which people and situations would help answer it. Include people who did not contact support if their experience is relevant.
Select an appropriate next research activity, such as reviewing a recent episode or observing document selection. Avoid asking participants simply whether they agree with the ticket’s complaint. The new study should allow a different explanation to emerge. A support record is a starting point for inquiry, not a script for getting the same answer again.
Carry the limits into the research brief
Explain why the signal was selected and what coverage it lacks. Support users are a particular subset of customers, and internal tagging may reflect operational categories rather than research concepts. Do not estimate market-wide frequency from a handful of selected cases.
Record the decision the research could inform and leave any immediate service repair with its appropriate owner. Research should not delay correction of a clear factual error or known defect. Close the signal note when the question is addressed, superseded or deliberately deferred, preserving the reason so the same anecdote does not repeatedly restart the discussion.
Make the reasoning concrete.
A fictional professional service receives a ticket asking which compliance document to send to a customer. A marketer concludes that buyers do not understand the product category.
Use the complaint as a broad conclusion
Opening: Build an educational campaign around presumed category confusion.
Hypothesis: The team can act quickly on a concrete story.
Risk: The uncertainty may instead concern document naming or order-specific scope.
Frame a research question
Opening: Investigate how buyers identify the document that applies to a particular order.
Hypothesis: The study can distinguish different explanations.
Risk: The original ticket alone cannot determine how common the issue is.
The team prepares a bounded document-selection study and keeps the customer’s immediate support issue on its existing service route. The research brief labels the ticket as a signal, not a representative finding.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Record purpose
Why was this material originally collected?
Moment
What specific question or behavior needs explanation?
Alternatives
Which different causes remain plausible?
Research question
What could a new study actually establish?
Coverage
Who is missing from this evidence route?
Watch for the wrong conclusion.
- Generalizing from only the people who contacted support.
- Treating an agent’s summary as a verbatim quote.
- Delaying a known service fix until a research project is complete.
Your next action
Choose one support signal and write the question it raises without assuming the explanation or estimating its frequency.
Sources & scope
The workflow, worksheets and hypothetical examples are original editorial analysis. Sources support only the identified principles. No measured business results or named human reviewer are claimed.
- GOV.UK Service Manual: User research in discovery →Primary government research guidance · Supports: Discovery can examine existing evidence including support logs; the research-question workflow is original editorial analysis.