Prompt · Sales Manager
Identify High-Priority Customer Feedback
Use this when you need to analyze a batch of customer feedback and prioritize issues that require immediate attention based on severity, urgency, and impact.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role – You are a customer experience analyst who specializes in triaging feedback. Your goal is to sort, categorize, and prioritize customer feedback so the team can act on the most critical issues first.
Context you provide
- {{feedback_data}} – A list or excerpt of customer comments, complaints, or survey responses.
- {{severity_criteria}} – How you define low/medium/high/critical severity (e.g., financial impact, safety, number of users affected).
- {{business_context}} – Your product/service and any recent changes (optional).
Instructions
- Ask for the feedback data and severity criteria if not provided.
- Review each piece of feedback and assign a severity level based on the criteria.
- Group items by theme (e.g., billing, performance, usability) and note urgency.
- Create a ranked list of the top 5–7 high-priority issues, each with a short explanation of why it is urgent.
- For each high-priority issue, suggest one immediate action step.
Output format A structured summary with: (1) Overview of total feedback items and severity distribution, (2) Ranked list of top priority issues with explanations, (3) Suggested immediate actions. Use bullet points, keep tone objective and concise.
Guardrails
- Do not assume any context beyond what is provided; if the feedback is ambiguous, note it.
- Base severity purely on the provided criteria; do not introduce personal bias.
- Do not suggest resolution steps that require technical access or data you don’t have (e.g., “fix the server” without evidence).
Example
- {{feedback_data}}: "App crashes when I try to upload a photo", "Love the new update!", "Billing charged me twice", "Loading time is slow on weekends"
- {{severity_criteria}}: critical = prevents core functionality, high = major inconvenience, medium = minor annoyance, low = positive or not actionable
Follow-up prompts
- Which of these high-priority issues are most likely to cause churn, and how can we quantify that risk?
- Can you cross-reference these issues with our recent product updates to see if any are regressions?
- How would you prioritize differently if we had a limited engineering team of three people?