About 20 minutes to set up · claude.ai only

Turn reviews and tickets into a product fix list

Today

You know the three star reviews are telling you something useful. Reading four hundred of them is a job nobody owns, so the same complaint gets rediscovered in a meeting a quarter later.

With Claude

You paste the export and get complaints grouped by cause, split into product problems, page problems, and expectation problems, with the customer's own words under each one so you can check the grouping yourself.

The prompt

Paste this into claude.ai and replace anything in brackets.

You are analyzing customer reviews and support tickets for my store to find what we should actually fix. Work only from the text I paste. This is not a summary exercise, it is a diagnosis.

The product or category: [name it, and paste the current product description so you can compare what we promise to what buyers say]
The reviews and tickets: [paste the export here, with customer names, emails, addresses, and order numbers removed]
What we already know is a problem: [list it, or write NOTHING YET]

Rules that override everything else:
1. Count only what I pasted. Never estimate what percentage of all customers feel something, never extrapolate to our whole customer base, and never compare us to an industry norm.
2. Every theme must be supported by two or three verbatim quotes from the text I pasted. If you cannot quote it, do not name it.
3. If a theme rests on only one or two mentions, label it THIN and say so plainly.

Give me:
1. The themes, ordered by how many of the pasted items mention them, with the count of pasted items for each and the verbatim quotes underneath.
2. For each theme, one cause from this list: product defect, sizing or fit, description or photo mismatch, packaging or transit damage, instructions unclear, expectation set by our marketing, or price to value.
3. A split into three buckets: fixable by editing the product page today, fixable by changing packaging or process, and needs a product or supplier change.
4. The exact sentences in our current description that are setting a wrong expectation, quoted, with a replacement line for each.
5. The five things you would fix first and the reason each one is ahead of the others.
6. Anything in this text that reads like a safety issue, a returns pattern worth investigating, or a claim we make that a buyer is disputing. Flag it, quote it, and do not soften it.

What to skip in ecommerce and retail businesses

  • Anything that depends on what your systems say right now. In a plain browser chat with no connectors, Claude cannot see your inventory, order status, tracking, carrier delays, live prices, or your storefront, so it must never state them. A description that says in stock and ships tomorrow, or a chargeback response that asserts a delivery date Claude cannot see, is worse than no draft at all. Keep those as bracketed placeholders that a person fills from the real system before anything goes out.
  • Product claims a human has not verified against supplier documentation. Claude will write a confident sentence about materials, certifications, country of origin, warranty terms, or compatibility because that is how product copy usually reads, and it has no way to know whether yours is true. Health, safety, supplement, cosmetic, and children's products are the sharp end of this: phrases like clinically proven, FDA approved, non-toxic, hypoallergenic, or BPA free carry real regulatory weight in the US. Draft with Claude, then verify every claim against the spec sheet or certificate before it is published.
  • Raw customer data. Strip names, email addresses, shipping addresses, phone numbers, and order numbers out of any export before you paste it, and never paste payment card details anywhere. You lose nothing analytically, because the useful signal is in what people wrote. Know your plan too: on Free, Pro, and Max accounts, whether your chats are used to improve Claude is a setting you control in Privacy Settings, while Team and Enterprise accounts sit under Anthropic's commercial terms instead.

Want all 4 workflows for ecommerce and retail businesses in your inbox?

Every prompt on this page plus the rest, so you still have them on Monday. One email, then four short ones on making it stick. Unsubscribe any time.

Or answer four questions and Claude writes three workflows for your specific business rather than the industry generally.

Before you try it

More for ecommerce and retail businesses

Full guide for ecommerce and retail businesses