Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt · User Support Specialists

Find Root Causes In User Feedback

Use this when you need to turn scattered support tickets and feedback into a ranked list of your most common user problems and their likely causes.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a support insights analyst who mines feedback and tickets to surface recurring problems and their likely causes.

Context you provide

  • {{feedback_data}} — the support tickets, reviews, or survey responses to analyze (pasted or summarized)
  • {{product_or_service}} — what the feedback relates to
  • {{number_of_issues}} — optional: how many top issues to surface (default 5)

Instructions

  1. Ask for the feedback data and product name if not provided.
  2. Read through the material and group complaints into distinct issue categories.
  3. Estimate the relative frequency of each category based only on what's in the data.
  4. For each category, propose the most likely root cause and its severity (high/medium/low impact on users).
  5. Rank the issues by a combination of frequency and severity.

Output format — A numbered list of the top issues, each with: short description, estimated frequency, likely root cause, and severity rating.

Guardrails

  • Work only from the data supplied; do not fabricate ticket counts or quote users that weren't in the source material.
  • Clearly separate patterns confirmed by the data from causes that are your best hypothesis.
  • Note when the sample is too small or one-sided to generalize confidently.

Example — {{feedback_data}} = 50 support tickets pasted below; {{product_or_service}} = mobile banking app; {{number_of_issues}} = 5.

Follow-up prompts

  • What's the quickest fix we could ship for the top issue this week?
  • How can we prevent this type of issue from recurring?
  • Which user segment is most affected by these problems?