Awesome Claude Prompts Unofficial

Analyze customer feedback

Group raw customer comments into themes, priorities or feature requests, with counts and quotes that show where each finding comes from.

Task: Analyze customer feedback · Other tasks

Fill in the details

One comment per line works best. Remove names, emails and other personal details before pasting.

Optional. A short description helps Claude interpret product-specific terms.

Copy your prompt

This site doesn't run Claude or show model output. Results depend on your input and the model you use.

1 required field is empty.

What you type is kept in this tab's session storage so a reload doesn't lose it. Use "Clear this task" to remove it. Browsers can restore session data when they reopen tabs, so closing a tab isn't a guaranteed way to erase it.

When to use this template

  • You have a pile of open-ended comments from a survey, reviews or support tickets and need to see the patterns quickly.
  • You want findings you can trace back to real comments, with counts and quotes, before sharing them with a team.
  • You need a first pass at priorities or a feature-request list to discuss, not a final report.

When not to use it

  • You need statistically sound results from thousands of responses. Use a proper survey tool or analysis; a prompt can miscount at that scale.
  • The comments contain personal data you are not allowed to share. Remove it before pasting, or do not paste at all.
  • The feedback is already structured, such as numeric survey answers. A spreadsheet will summarize those more reliably.

Why this structure

  • All comments go first inside <feedback> tags, so the full set comes before the instructions, and the tags help Claude keep customer words apart from yours.
  • The prompt asks for groups by underlying issue rather than wording, so comments that say the same thing differently are counted together. That is the main value of the exercise.
  • The request for counts and verbatim quotes for every group gives you a way to trace each finding back to the comments.
  • The ordering rule changes with your goal, which keeps one template useful for themes, priorities and feature requests.
  • The last paragraph asks for unplaced comments and a warning about thin samples, so weak evidence is not presented as a trend.

Example input (fictional)

Customer feedback
Delivery was late again this week.
Love the recipes but the portions are small.
The app logged me out twice during checkout.
Please add a vegetarian plan.
Driver left the box in the rain.
Would like more vegetarian options.
What you want to learn
Which problems to fix first
Product or service
Fernbox (fictional), a weekly meal-kit delivery service

Follow-ups to send Claude

  • Show every comment you placed in the top group, so I can check the grouping.
  • Draft a short reply we could send to customers about the most common issue.
  • Which groups overlap? Would merging any of them change the order?

Common mistakes

  • Pasting more comments than Claude can count carefully. For large sets, analyze in batches and combine the group counts yourself.
  • Leaving personal details in the comments. Strip names, emails and order numbers first.
  • Treating the counts as exact. Spot-check one or two groups against the raw comments before quoting numbers to others.
  • Extract data to JSON: Pull specific fields out of messy text into JSON that matches your field list, with clear rules for missing or ambiguous values.
  • Summarize a document: Turn a long document into a faithful summary: main point first, key points by importance, then decisions and open questions.
  • Compare options and recommend one: Weigh two or more options against your criteria and hard limits, see the trade-offs side by side, and get a recommendation when the facts support one.

See all templates

Sources