Move from what a customer said to what your team chooses to do. Every stage leaves room to question the interpretation.
01
Read the exact words.
Open the supporting customer excerpt and its conversation context. Check what was actually said, not just what a summary suggests.
02
Review the themes.
Inspect candidate groupings. Rename, merge, split, reclassify, or dismiss a theme when the evidence calls for it.
03
Make the call.
Organize decisions into Fix next, Build next, or Investigate. Record your reasoning; TuoIQ does not automatically commit a roadmap for you.
04
Keep a private brief.
Bring the theme, supporting evidence, and decision notes into a private, permission-checked brief for your project’s authorized reviewers.
Context changes the conversation
A complaint is not a feature request.
A failed export and a request for scheduled reports both mention reporting. They need different conversations.
Keep observed problems separate from suggested improvements.
Review the original context, not just the theme’s title.
Choose to act, investigate, or leave a theme aside.
AI analysis can be incomplete or wrong. Check the evidence and source coverage before acting.
Private brief · Synthetic example
Reporting: review notes
Two observations. Keep them distinct.
Evidence
An export times out. A separate customer asks for scheduled reports.
Team decision
Investigate the export failure; assess the scheduling request separately.
Open question
Is the failure tied to report size?
Illustrative synthetic example, not an actual saved brief.
A deliberate starting point
Know where your feedback comes from.
Gmail, structured JSON feedback imports, and an optional Tuolen web-widget mirror are the implemented paths. Other channels are planned, not connected.