Customer Feedback Synthesizer
Synthesize customer feedback from multiple channels into actionable themes, sentiment analysis, and product insights.
You have feedback in NPS surveys, support tickets, G2 reviews, sales call notes, and Slack messages from your CS team. Individually they're anecdotes. Together they reveal the 3 things your customers actually care about — but nobody has time to read all of it and connect the dots.
Who it's for: product managers synthesizing customer feedback into feature priorities, VoC program managers building customer insight reports, customer success leaders identifying systemic issues from feedback data, UX researchers combining qualitative feedback across channels, heads of product wanting data-driven roadmap input
Example
"Synthesize all customer feedback from Q1" → Thematic analysis revealing 5 top themes, sentiment breakdown by channel and segment, 12 specific feature requests ranked by frequency, NPS driver analysis, and a product recommendations memo with supporting quotes
New here? 3-minute setup guide → | Already set up? Copy the template below.
# Customer Feedback Synthesizer
## Your Role
You are an expert voice-of-customer analyst. Your job is to synthesize multi-channel feedback into actionable themes and product insights.
## Core Principles
- Combine quantitative scores with qualitative comments
- Track themes over time for trend analysis
- Distinguish frequency from severity
- Segment by customer type for nuanced insights
- Prioritize by business impact, not just volume
## Instructions
Produce: sentiment overview, top themes, verbatim highlights, segment patterns, product insights, and prioritized recommendations.
## Commands
- "Synthesize feedback" - Full analysis
- "Top themes this period" - Ranked recurring issues
- "Segment comparison" - By customer type/size
- "Trend analysis" - Theme tracking over time
Get new playbooks like this one
One email a week with new Claude Code workflows. Free, like everything here.
No spam. Unsubscribe anytime.
What This Does
Aggregates customer feedback from surveys, support tickets, reviews, and interviews to identify recurring themes, track sentiment trends, and surface product improvement opportunities.
Quick Start
Step 1: Download the Template
Click Download above to get the CLAUDE.md file.
Step 2: Gather Feedback Sources
Collect: NPS responses, support tickets, app store reviews, customer interviews, social mentions.
Step 3: Start Using It
claude
Say: "Synthesize this month's customer feedback from NPS surveys and support tickets. What are the top themes and what should we fix?"
Analysis Output
| Section | Content |
|---|---|
| Sentiment Overview | Overall health with trend direction |
| Top Themes | Recurring topics ranked by frequency and impact |
| Verbatim Highlights | Representative quotes (positive and negative) |
| Segment Patterns | Differences by customer type/size/plan |
| Product Insights | Feature requests and pain points |
| Recommendations | Prioritized actions for product/CS teams |
Tips
- Combine quantitative and qualitative: NPS scores + open-ended comments = full picture
- Track themes over time: Is a theme getting better or worse month-over-month?
- Distinguish volume from severity: Many small complaints ≠ one critical issue
- Close the loop: Share back with customers what you changed based on feedback
Commands
"Synthesize customer feedback from these sources"
"Top 5 product improvement themes this quarter"
"Compare enterprise vs. SMB feedback patterns"
"Track how the 'onboarding difficulty' theme is trending"
Troubleshooting
Too many themes Say: "Consolidate into top 5 themes by business impact, not just frequency"
Feedback seems contradictory Segment: "Break by customer type — enterprise and SMB often want opposite things"
No clear prioritization Ask: "Rank by: frequency × revenue impact × effort to fix"