Find the Themes in Customer Feedback and CSAT Comments with Real Counts
Returns a theme table with exact counts, a verbatim quote from your data, likely root cause and suggested owner, plus top actions and data gaps.
You getFirst line, table with columns and top 3 actions
Prompt
You are a customer support analyst who turns raw feedback into clear action items for product, support and operations teams.
I will paste customer feedback or CSAT comments right after this prompt. Group them into themes and show what is driving them.
Rules:
1. Count only what is in the pasted data. Each count is the exact number of comments you assigned to that theme. If a comment fits two themes, count it in both and note it.
2. Quote examples word for word from the data, in quotation marks. Do not paraphrase, merge or correct quotes.
3. Label root causes as likely, and base each one on wording in the comments, not on guesses about internal systems.
4. Suggest one owner per theme: Product, Engineering, Support, Billing, Logistics, Marketing, or Other (name it).
5. Do not add percentages, trends or benchmarks unless they can be calculated directly from the pasted data.
Output format:
- First line: total comments analyzed, and how many were too vague to classify.
- Table with columns: Theme | Count | Verbatim example quote | Likely root cause | Suggested owner. Sort by count, highest first.
- Top 3 actions: numbered, one sentence each, each tied to a theme.
- Positive themes: up to 3 bullets with counts and one verbatim quote each.
End with one line on what this data cannot tell us, such as small sample size, missing scores, dates or customer segments.Example output
Tips and common edits
Why this works
- Requiring exact counts from the pasted data stops the model from inventing percentages or survey-style statistics.
- Verbatim quotes in quotation marks let you check every theme against the source text quickly.
- A named owner per theme turns the analysis into a list you can route to teams the same day.
Use after a CSAT survey, NPS export or a week of ticket comments. Paste the raw text right after the prompt in ChatGPT, Claude or Gemini. Remove names and emails first.
Common edits
- Add a column for average CSAT score per theme if your pasted data includes scores.
- Limit the table to the top 5 themes for a short slide or weekly update.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Audit a Help Center Article for Gaps, Jargon and Outdated Steps
Paste a help center article and get a pass/fail checklist scorecard plus a line-by-line fix list ranked by customer impact, without a full rewrite.
Find Help Center Gaps by Matching Support Tickets to Existing Articles
Get a ticket-to-article match table and a ranked list of new help articles to write, with ticket counts and deflection potential for each.
Turn Feature Notes into a Step-by-Step Help Center How-To Guide
Paste rough notes about a product feature and get a customer-ready how-to guide with one action per step, bold UI labels, expected results and a troubleshooting section.
Write Chatbot Intent Answers with Trigger Phrases and Human Handoff Rules
Get a set of chatbot intents for your top support questions, each with customer-style trigger phrases, a short bot answer, and an exact rule for handing off to a human.
Write Help Article Titles and Meta Descriptions in Your Customers' Words
Get help article titles that start with the customer's task verb and meta descriptions within search length limits, each with a character count and the customer phrase it matches.
Build a Yes/No Troubleshooting Decision Tree for a Recurring Product Issue
You get a step-by-step yes/no troubleshooting tree ordered from fastest, most likely checks to slowest, with ready-to-send customer messages and a clear escalation point.