8 User Feedback Prompts That Uncover Your Next Big Feature
User feedback scattered across support tickets, reviews, and sales calls while your roadmap stays guesswork? Feature requests pile up but you can't spot the real patterns. Manual analysis takes forever and you miss the insights that matter.
Here's how you use AI to help automate your job as a product manager. These 8 AI prompts transform messy user feedback into ranked feature opportunities that actually drive retention and revenue. From support tickets to churn surveys, these prompts extract actionable insights your team would otherwise miss.
Perfect for product teams at B2B SaaS companies drowning in user data but starving for clarity. Each prompt works with ChatGPT, Claude, or any AI assistant. Total time saved per week: 15+ hours of manual feedback analysis.
The Prompts
Pro tip: Click the heart icon on any prompt to save it to your account for quick access later.
1. Transform Support Tickets Into Product Roadmap Insights
Transform Support Tickets Into Product Roadmap Insights
Stop letting valuable user feedback get buried in support queues. Use this when you have a collection of support tickets and need to identify feature opportunities. It analyzes ticket patterns to reveal what users actually want built next. Saves 2-3 hours of manual analysis while uncovering insights your team might miss.
You are an expert product analyst specializing in user feedback analysis and feature prioritization.
Analyze these support tickets to identify feature opportunities and roadmap insights:
- Support tickets: [PASTE SUPPORT TICKETS OR DESCRIPTIONS]
- Current product focus: [YOUR PRODUCT AREA]
- Team capacity: [SMALL/MEDIUM/LARGE TEAM]
Provide:
1. Pattern Analysis
- Top 5 recurring issues or requests
- Frequency count for each pattern
- User impact level (high/medium/low)
- Current workarounds users mention
2. Feature Opportunities
- 3 specific features to consider building
- Expected effort level for each (small/medium/large)
- Potential user satisfaction impact
- Dependencies or technical considerations
3. Roadmap Recommendations
- Quick wins (features under 2 weeks)
- High-impact opportunities (2-8 weeks)
- Strategic bets (8+ weeks)
- Features to deprioritize and why
4. Action Plan
- Next steps for validation
- Key stakeholders to involve
- Success metrics to track
Format with clear headers. Focus on actionable insights, not generic observations.Customization Tips
- • Add specific product categories for targeted analysis
- • Include customer tier data for impact weighting
- • Specify timeline constraints for realistic prioritization
Expected Output
- • Ranked list of feature opportunities with effort estimates
- • Quick wins vs strategic bets breakdown
- • Actionable next steps with stakeholder assignments
Get Free AI Tips & Prompts Weekly
Join thousands getting exclusive AI automation tips, ready-to-use prompts, and custom agents delivered to your inbox.
3. Design Survey Questions That Reveal True Feature Demand
Design Survey Questions That Reveal True Feature Demand
Stop getting useless 'everything sounds great' survey responses that waste your development time. Use this when planning user research to validate feature ideas. It creates questions that reveal what users actually want versus what they say they want. Saves 45+ minutes of survey design while getting actionable data.
You are an expert user researcher specializing in survey design and behavioral psychology.
Create a survey that reveals true user preferences and feature demand:
- Feature ideas to test: [LIST 3-5 FEATURE IDEAS]
- Target user segment: [DESCRIBE YOUR USERS]
- Survey goal: [PRIORITIZATION/VALIDATION/DISCOVERY]
Provide:
1. Survey Structure
- Opening questions to establish context
- Screening questions to qualify respondents
- Total estimated completion time
- Recommended sample size
2. Feature Demand Questions
- Behavioral questions revealing current pain points
- Prioritization exercises (MaxDiff, ranking, or trade-offs)
- Willingness-to-pay indicators for each feature
- Usage frequency predictions
3. Bias-Reducing Techniques
- Questions that reveal actual vs stated preferences
- Scenarios testing real-world usage
- Competitive alternatives to gauge switching intent
- Follow-up questions to validate initial responses
4. Analysis Framework
- How to score and rank responses
- Red flags indicating false positives
- Sample size needed for statistical significance
- Key metrics to calculate from responses
5. Implementation Guide
- Survey platform recommendations
- Distribution strategy for your user base
- Timeline for data collection and analysis
Focus on questions that predict actual user behavior, not just opinions.Customization Tips
- • Add specific user persona details for targeted questions
- • Include current product usage data for context
- • Specify budget constraints for realistic feature scoping
Expected Output
- • Complete survey with 15-25 strategic questions
- • Scoring methodology and analysis framework
- • Implementation timeline with platform recommendations
4. Extract Feature Ideas from Sales Call Transcripts
Extract Feature Ideas from Sales Call Transcripts
Stop guessing what features customers actually want based on vague feedback. Use this when analyzing sales call recordings to uncover specific feature requests and pain points. It systematically extracts actionable product insights from conversational data, saving 2-3 hours of manual transcript analysis while identifying features that directly impact revenue.
You are an expert product analyst specializing in customer feedback analysis and feature prioritization.
Analyze this sales call transcript to extract actionable feature ideas:
- Transcript: [SALES CALL TRANSCRIPT]
- Product context: [YOUR PRODUCT/SERVICE]
- Current roadmap focus: [ROADMAP PRIORITIES]
Provide:
1. Feature Requests Mentioned
- Direct requests (exact quotes)
- Implied needs (what they wished existed)
- Workarounds they currently use
- Integration requests
2. Pain Points Analysis
- Current process frustrations
- Time-consuming manual tasks
- Compliance or security concerns
- Scalability limitations
3. Competitive Intelligence
- Tools they currently use
- Features they love elsewhere
- Switching barriers mentioned
- Budget considerations discussed
4. Feature Prioritization Matrix
- High impact, low effort features
- Revenue-critical requests
- Competitive differentiators
- Technical feasibility assessment
5. Next Steps
- Follow-up questions to ask
- Validation experiments to run
- Stakeholders to involve
Rank each feature idea by potential revenue impact (1-10). Include direct quotes to support recommendations.Customization Tips
- • Add specific industry terminology for better context
- • Include competitor names for comparative analysis
- • Specify customer segment for targeted insights
Expected Output
- • Ranked list of feature ideas with revenue impact scores
- • Direct customer quotes supporting each recommendation
- • Prioritization matrix with effort vs impact assessment
5. Identify Power User Needs from Usage Data Patterns
Identify Power User Needs from Usage Data Patterns
Finally understand what your most valuable users actually need instead of building features nobody uses. Use this when analyzing usage analytics to identify patterns among power users. It reveals hidden workflows and feature gaps that drive retention, saving 4-5 hours of manual data analysis while focusing development on high-impact improvements.
You are an expert product data analyst specializing in user behavior analysis and feature discovery.
Analyze these usage patterns to identify power user needs and feature opportunities:
- Usage data summary: [USAGE ANALYTICS DATA]
- Power user definition: [CRITERIA FOR POWER USERS]
- Product areas: [MAIN PRODUCT MODULES/FEATURES]
Provide:
1. Power User Behavior Patterns
- Most frequently used feature combinations
- Unique workflow sequences
- Time spent in different product areas
- Advanced features they've adopted
2. Usage Gaps Analysis
- Features they avoid (and likely reasons)
- Workarounds they've created
- Manual processes outside your product
- Integration points they rely on
3. Engagement Correlation Insights
- Features that predict long-term retention
- Usage patterns of churned power users
- Onboarding paths of successful users
- Feature combinations that drive expansion
4. Hidden Feature Opportunities
- Workflow automation possibilities
- Data connections they're making manually
- Reporting needs based on export patterns
- Mobile/accessibility requirements
5. Development Recommendations
- High-impact features for power user retention
- Quick wins to reduce friction
- Advanced capabilities to build
- Sunset candidates (unused features)
Prioritize recommendations by power user adoption potential and retention impact. Include specific usage metrics to support each suggestion.Customization Tips
- • Define power user criteria based on your metrics
- • Include churn data for stronger insights
- • Add revenue data to weight recommendations
Expected Output
- • Power user workflow analysis with friction points identified
- • Ranked feature opportunities with adoption predictions
- • Retention-focused development roadmap recommendations
6. Transform Churn Feedback Into Retention Features
Transform Churn Feedback Into Retention Features
Stop losing customers to preventable issues by turning exit feedback into actionable retention features. Use this when analyzing churn surveys and cancellation reasons to identify systematic product gaps. It converts negative feedback into specific development priorities, saving 3-4 hours of manual analysis while building features that directly reduce churn.
You are an expert customer success analyst specializing in churn analysis and retention feature development.
Analyze this churn feedback to identify retention-focused feature opportunities:
- Churn feedback data: [CUSTOMER EXIT SURVEYS/FEEDBACK]
- Product offering: [YOUR PRODUCT DESCRIPTION]
- Typical customer journey: [ONBOARDING TO CHURN TIMELINE]
- Main competitors: [COMPETITOR ALTERNATIVES]
Provide:
1. Churn Root Cause Analysis
- Most common cancellation reasons
- Timeline of when issues typically surface
- Feature gaps that drive switching
- Onboarding failures leading to churn
2. Competitive Loss Analysis
- Features competitors offer that you don't
- Pricing or packaging issues mentioned
- Integration capabilities you're missing
- User experience advantages cited
3. Retention Feature Opportunities
- Quick wins to address common pain points
- Onboarding improvements to increase stickiness
- Advanced features to prevent competitive switching
- Pricing/packaging adjustments needed
4. Implementation Roadmap
- High-impact, low-effort retention features
- Medium-term competitive parity features
- Long-term differentiation opportunities
- Process improvements (non-product solutions)
5. Success Metrics Framework
- KPIs to track for each feature
- A/B testing approaches
- Customer segment targeting
- Timeline for measuring impact
Rank each recommendation by churn reduction potential (1-10). Include specific customer quotes and quantify the percentage of churn each feature could prevent.Customization Tips
- • Include competitor feature comparisons for context
- • Add customer segment data for targeted solutions
- • Specify churn timeline patterns for better prioritization
Expected Output
- • Churn root cause analysis with prevention strategies
- • Ranked retention features with impact predictions
- • Implementation roadmap with success metrics defined
8. Convert User Stories Into Prioritized Development
Convert User Stories Into Prioritized Development
End the chaos of scattered user feedback turning into random features. Use this when you have raw user stories but need structured development priorities. It transforms messy feedback into clear roadmap decisions, saving 3-4 hours of analysis while ensuring you build what users actually want.
You are an expert product manager specializing in user story analysis and development prioritization frameworks.
Convert these user stories into a prioritized development roadmap:
- User stories: [PASTE USER STORIES/FEEDBACK]
- Product goals: [YOUR CURRENT PRODUCT OBJECTIVES]
- Development capacity: [TEAM SIZE AND SPRINT CAPACITY]
Provide:
1. Story Classification
- Feature requests vs bug reports vs enhancements
- User type breakdown (power users, casual users, prospects)
- Impact area (core functionality, UX, performance, integrations)
- Complexity assessment (simple, moderate, complex)
2. Prioritization Matrix
- User impact score (1-10 scale)
- Business value assessment (revenue, retention, acquisition)
- Development effort estimate (story points or hours)
- Risk factors and dependencies
3. Development Roadmap
- Sprint 1 priorities (immediate wins)
- Sprint 2-3 medium-term features
- Future backlog items (3+ sprints)
- Features to decline with rationale
4. Implementation Strategy
- MVP scope for each priority feature
- Success metrics and KPIs to track
- User validation approach needed
- Resource allocation recommendations
5. Stakeholder Communication
- Executive summary for leadership
- User communication plan for declined requests
- Timeline expectations and milestones
Format with clear priority rankings and specific user quotes supporting decisions.Customization Tips
- • Include your specific prioritization framework (RICE, MoSCoW, etc.)
- • Add business metrics that matter most to your company
- • Specify technical constraints or platform limitations
Expected Output
- • Prioritized feature list with impact and effort scores
- • Three-sprint roadmap with clear MVP definitions
- • Stakeholder communication plan with timeline and rationale
How to Use These Prompts
1. Choose Your Platform: These prompts work with ChatGPT, Claude, Gemini, Grok, Copilot and other AI assistants. Click the dropdown button to select your preferred AI tool.
2. Click Run: Click the run button to open your preferred AI tool with the prompt pre-filled.
3. Fill in the Placeholders: Replace all text in [BRACKETS] with your specific information. The "What You'll Need" section tells you exactly what to prepare.
4. Press Enter: Hit enter. The AI will generate your result based on the instructions.
5. Refine if Needed: If the output isn't perfect, use the customization tips to adjust the prompt or ask follow-up questions.
Prompt Engineering Tips for user feedback prompts
Tip 1: Include Sample Data in Your Prompts
Always provide 3-5 examples of the feedback type you're analyzing. If you're mining support tickets, paste actual ticket snippets. For user reviews, include real review text. This helps the AI understand your specific context and terminology, producing more accurate feature recommendations instead of generic suggestions.
Tip 2: Specify Your Product Development Context
Define your team size, sprint capacity, and current roadmap priorities in every prompt. Tell the AI whether you're a 3-person startup or 50-person product team. This context shapes the output - you'll get features sized appropriately for your resources rather than enterprise-scale recommendations that don't fit.
Tip 3: Request Effort Estimates with Every Feature
Ask for development complexity ratings (small/medium/large) alongside feature ideas. This prevents your team from falling in love with massive features that derail your roadmap. The AI can estimate effort based on your product description and team context, helping you balance quick wins with strategic bets.
Tip 4: Ask for Direct User Quotes
Request that the AI extract specific customer language from your feedback data. These quotes become powerful stakeholder communication tools and help validate feature demand. Instead of saying "users want better search," you can say "15 customers said search is 'frustratingly slow' and 'hard to find relevant results.'"
Tip 5: Define Success Metrics Upfront
Tell the AI what metrics matter most - retention, revenue, activation, or engagement. This focuses the analysis on features that move your key numbers. Without this context, you'll get a random mix of nice-to-have features instead of business-critical improvements.
Tip 6: Combine Multiple Feedback Sources
Use prompts that analyze support tickets, reviews, and sales calls together. Cross-referencing feedback sources reveals patterns and validates demand. A feature mentioned in support tickets AND sales calls has stronger evidence than isolated feedback from one channel.
Frequently Asked Questions
Ready to Launch Your Startup?
Get 75+ AI agents that are personalized to your business and custom-built for founders. Everything you need to validate, build, and operate your business.
Claim Your Founder Pack