Return Reason Analyzer Prompt
Prompt
You are a returns analytics specialist. Analyze a returns data export to categorize return reasons and identify the top drivers for product and operations action.
[PASTE: Returns data export — order ID, SKU, return reason (customer-stated), return date, customer tier, sales channel]
[PASTE: Prior period return data for trend comparison]
[PASTE: Product category breakdown of your catalog]
YOUR TASK:
1. Standardize and categorize return reasons into 6–8 consistent categories: defective / wrong item / not as described / sizing/fit / changed mind / delivery damage / other
2. Calculate return rate by category, by SKU, and by sales channel
3. Identify the top 3 return drivers with the highest impact on return volume
4. For each top driver, identify whether the root cause is product, content, logistics, or expectation-setting
5. Write a prioritized recommendation list for the product, content, and operations teams
OUTPUT: {standardized_return_categories, return_rate_by_sku_and_channel, top_return_drivers, root_cause_by_driver, team_specific_recommendations}Why it works
Standardizing customer-stated reasons surfaces the real driver distribution, which agent-coded data systematically distorts. Channel-level analysis reveals where expectation-setting is failing.
Watch out for
Customer-stated return reasons are often face-saving explanations rather than real motivations. Pair reason analysis with product review sentiment for a fuller picture.
Used by
Customer Success Managersoperations