Collecting feedback is easy — knowing what to do with it is the hard part. These prompts help you design surveys that get honest answers, analyze patterns in feedback data, build feedback-to-product pipelines, and turn complaints into shipped features. Tested across GPT-4.1, Gemini 2.5 Pro, Claude Sonnet 4, and Grok 3 so you know which model helps you listen better.
PROMPTS
Create surveys that get honest, actionable answers
I need a customer feedback survey for [product/service/experience]. Goal of the survey: [what you want to learn] Audience: [who will fill it out] Survey length target: [number of questions] Distribution method: [email, in-app, post-purchase, etc.] Last survey sent: [when, or never] Design the survey: 1. 8-12 questions in optimal order (easy to hard, closed to open) 2. A mix of rating scales, multiple choice, and open-ended questions 3. The one question that reveals the most actionable insight 4. NPS question placement and follow-up question for detractors 5. An incentive strategy that increases completion without biasing results 6. A pre-survey message that explains why their feedback matters (under 50 words)
PRO TIPS
Put your most important question in position 3, not position 1. The first two questions warm people up and build commitment. By question 3, they're invested enough to give thoughtful answers instead of rushing through.
Tested Mar 15, 2026
Find patterns in unstructured customer feedback
Analyze this customer feedback and tell me what to prioritize: [Paste 20-50 pieces of customer feedback: reviews, survey responses, support tickets, social comments] Product/service: [what they're giving feedback on] Recent changes: [anything you've changed recently] Known issues: [problems you're already aware of] Provide: 1. Theme analysis: group feedback into 5-7 categories with frequency counts 2. Sentiment breakdown: positive, negative, neutral percentages 3. The #1 issue to fix immediately (biggest impact, most mentioned) 4. Hidden insights: feedback patterns that aren't obvious on first read 5. Exact customer quotes that best represent each theme 6. A prioritized action plan: what to fix this week, this month, this quarter
PRO TIPS
Include the raw feedback verbatim, including typos and emotions. AI extracts more insight from unfiltered customer language than from your cleaned-up summaries. The anger and excitement in raw feedback reveals what actually matters most to customers.
Tested Mar 15, 2026
Respond to online reviews professionally at scale
Help me respond to these customer reviews: [Paste 5-10 reviews with star ratings] Business type: [what you do] Brand voice: [professional/friendly/empathetic/casual] Common misconceptions: [things reviewers often get wrong] Changes you've made: [improvements based on past feedback] For each review, write: 1. A personalized response (not generic 'thank you for your feedback') 2. Acknowledgment of their specific experience 3. For negative reviews: what you're doing to address the issue 4. For positive reviews: a genuine reaction that encourages loyalty 5. A subtle invitation to return or try something new 6. Flag any reviews that need private follow-up (and a DM template)
PRO TIPS
Respond to negative reviews within 4 hours and positive reviews within 24 hours. Speed on negative reviews shows you care. Delayed responses on positive reviews feel fine because happy customers aren't waiting anxiously for acknowledgment.
Tested Mar 15, 2026
Turn NPS scores into measurable improvements
Help me act on our NPS results. Current NPS score: [number] Previous NPS score: [number and when] Promoters feedback themes: [what happy customers say] Detractors feedback themes: [what unhappy customers say] Passives feedback themes: [what neutral customers say] Response rate: [percentage who responded] Build an NPS action plan: 1. Score interpretation: what our NPS really means in context 2. Top 3 actions to convert passives to promoters 3. Top 3 actions to reduce detractor volume 4. A promoter program: how to activate happy customers as advocates 5. Detractor rescue workflow: steps to save at-risk customers 6. Quarterly NPS improvement targets with specific initiatives for each
PRO TIPS
Call your detractors personally. A phone call from a real person to someone who gave a low score converts 30-40% of them back to satisfied customers. AI can write the script, but the human call does the actual work of rebuilding trust.
Tested Mar 15, 2026
Prioritize customer feature requests with business logic
Help me prioritize these feature requests from customers: [List 10-15 feature requests with: who requested it, how many times it's been asked, customer tier/value] Product roadmap capacity: [how many features you can build this quarter] Strategic priorities: [company goals this year] Competitor features: [what competitors have that you don't] Technical constraints: [anything limiting what you can build] Prioritize and provide: 1. A scoring matrix: impact (revenue, retention, acquisition) x effort 2. The top 5 features to build, in order, with business justification 3. Features to explicitly NOT build (and how to communicate that) 4. A 'quick wins' list: low-effort features that delight customers 5. A customer communication plan for each decision (yes, not yet, no) 6. A feedback loop: how to validate the priority order with customers before building
PRO TIPS
Ask customers 'what would you stop using if we built this?' instead of 'do you want this feature?' The first question reveals actual value trade-offs. The second always gets a 'yes' that means nothing for prioritization.
Tested Mar 15, 2026
Build a system that turns customer feedback into product decisions
Help me build a system that connects customer feedback directly to product decisions. Current state: [how feedback reaches the product team today — or doesn't] Feedback sources: [support tickets, surveys, reviews, social, sales calls, churned customer interviews] Product team structure: [PMs, designers, engineers — how they work] Sprint/release cadence: [how often you ship] Biggest gap: [the disconnect between what customers say and what gets built] Design a feedback-to-product pipeline: 1. Collection layer: how to tag and categorize feedback at the source (support, sales, reviews) with consistent taxonomy 2. Aggregation layer: how to centralize feedback from all sources into one view with theme detection 3. Signal detection: how to distinguish noise (one loud customer) from signal (pattern across many) 4. Product integration: how to inject customer evidence into sprint planning, roadmap reviews, and design critiques 5. Closed loop: how to notify customers when their feedback becomes a shipped feature 6. Measurement: how to track whether the pipeline is actually influencing product decisions (not just existing on paper)
PRO TIPS
The feedback-to-product pipeline fails when product teams only see summarized reports. Raw customer quotes in Slack channels, Jira tickets, and sprint planning create more empathy and urgency than any dashboard. Pipe the actual voice of the customer into every decision point.
Tested Mar 15, 2026
Build a continuous customer feedback ecosystem
Help me build a continuous customer feedback system. Business type: [product/service/SaaS/e-commerce] Customer base size: [number of active customers] Current feedback sources: [surveys, support tickets, reviews, social — or none] Team responsible: [who handles feedback] Biggest feedback gap: [what you don't know about your customers] Design a feedback ecosystem: 1. Feedback collection touchpoints: when and where to ask (map to customer journey) 2. Passive feedback sources: signals you can read without asking 3. A feedback aggregation system: how to centralize data from all sources 4. A weekly feedback review ritual: agenda, attendees, and action format 5. Closed-loop process: how to tell customers their feedback led to changes 6. Quarterly 'voice of customer' report template for leadership
PRO TIPS
The closed loop is everything. When you make a change based on feedback, email every customer who requested it. 'You asked, we built it' is the most powerful retention message you can send — and it costs nothing.
Tested Mar 15, 2026
Based on actual testing — not assumptions. See our methodology
Gemini 2.5 Pro
Categorizes unstructured feedback data efficiently and builds clear scoring matrices for feature prioritization. Strongest at detecting patterns across large volumes of feedback.
Best for AnalysisGPT-4.1
Writes the most natural, personalized review responses and customer-facing communications. Strongest at feedback system design and customer journey mapping.
Best for ResponsesClaude Sonnet 4
Creates the most unbiased surveys and provides the most honest NPS interpretation. Strongest at feedback-to-product pipeline design and closed-loop process architecture.
Best for SurveysGrok 3
Cuts through complaint noise to identify the real issues customers are communicating. Delivers actionable analysis without sugarcoating negative feedback patterns.
Best for Blunt AnalysisAsk 'why' after every rating. A 3-star rating tells you nothing. The follow-up 'what would make this a 5?' tells you everything. Always pair quantitative scores with one open-ended question that reveals the story behind the number.
Negative feedback is a gift — silence is the threat. Customers who complain are giving you a chance to fix things. The ones who leave without saying anything are the real problem. Build systems that make it easy to complain before they walk away.
Share raw feedback with the whole team. Don't filter customer quotes into sanitized summaries. Let engineers, designers, and leadership read actual words customers use. Raw emotion drives action faster than any quarterly report.