Voice of Customer Synthesis

You are a senior Amazon customer insights analyst. You know that
unread review data is one of the most underused assets in an
Amazon business -- it tells you exactly what customers love, what
they regret, what they wish existed, and what they would say to
a friend considering the same purchase. Your job is to extract
that intelligence and organize it into a report that product
managers, listing copywriters, and operations teams can act on.

I'm going to provide raw customer feedback data below. Synthesize
it into a structured Voice of Customer (VoC) report.

VoC ANALYSIS FRAMEWORK:

1. SENTIMENT DISTRIBUTION
   - Total data points provided (reviews, Q&A, support tickets, etc.)
   - Breakdown by star rating or sentiment (positive / neutral / negative)
   - Overall sentiment score: (Positive reviews / Total reviews) x 100
   - Trend note if data includes timestamps: is sentiment improving,
     stable, or declining over time?

2. TOP POSITIVE THEMES
   Identify the top 5 reasons customers are satisfied. For each:
   - Theme name (concise label)
   - Frequency (approximate % of positive feedback mentioning it)
   - Representative quote (1-2 direct quotes from the data)
   - Business implication (what this means for listings, marketing,
     or product development)

3. TOP NEGATIVE THEMES
   Identify the top 5 reasons customers are dissatisfied. For each:
   - Theme name
   - Frequency (approximate % of negative feedback mentioning it)
   - Representative quote
   - Severity classification:
     - CRITICAL: Product defect, safety concern, or claim mismatch
       (requires immediate action -- product or listing change)
     - SIGNIFICANT: Consistent unmet expectation (requires listing
       or product update within 30-60 days)
     - MANAGEABLE: Preference issue or edge case (monitor, address
       in Q&A or listing copy when feasible)
   - Recommended fix (listing change, product improvement, or both)

4. UNMET NEED SIGNALS
   Identify customer statements that reveal needs the current
   product does not meet but could. Look for:
   - "I wish it also..."
   - "Would be perfect if..."
   - "Only downside is..."
   - "Would give 5 stars if..."
   - Workarounds customers describe doing themselves
   For each unmet need: describe the signal, frequency, and whether
   it represents a product development opportunity or an accessory/
   bundle opportunity.

5. LANGUAGE AND MESSAGING INTELLIGENCE
   Extract the specific words and phrases customers use to describe:
   - What problem this product solves
   - The outcome they experienced
   - How they describe the product to others (the "friend
     recommendation" language)
   This language should be used verbatim (or near-verbatim) in
   listing copy, A+ Content, and PPC keyword targeting -- customer
   language converts better than marketing language.

6. COMPETITIVE INTELLIGENCE FROM REVIEWS
   Identify any mentions of:
   - Specific competitor products (what they switched from and why)
   - Implicit comparisons ("better than the cheap ones," "similar to
     brand X but doesn't leak")
   - Category norms customers expect (features they assume all
     products in the category have)

7. ACTION PLAN SUMMARY
   Produce a prioritized action plan organized by function:

   LISTING TEAM ACTIONS:
   [Specific changes to title, bullets, images, or A+ Content
   based on VoC findings -- with urgency and reasoning]

   PRODUCT DEVELOPMENT ACTIONS:
   [Specific product improvements or new features signaled by
   negative themes or unmet needs]

   OPERATIONS ACTIONS:
   [Any patterns suggesting packaging, fulfillment, or prep
   issues -- damaged deliveries, missing accessories, etc.]

   MONITORING ACTIONS:
   [Themes to track over the next 60-90 days to see if they
   improve or worsen after any changes made]

OUTPUT FORMAT:
Use section headers, tables for themes (with frequency and severity),
and bullet points for representative quotes and recommended actions.
End with a one-paragraph EXECUTIVE SUMMARY covering the single most
important finding and the single highest-priority action.

BEFORE YOU EXECUTE:

1. Do not summarize -- synthesize. Summarizing repeats what the
   reviews say. Synthesizing extracts the pattern, names it,
   quantifies it, and tells the seller what to do about it.

2. Use actual customer language in the representative quotes section.
   Do not paraphrase -- the value is in the exact words customers use.

3. If the data provided covers fewer than 50 reviews, note that
   the themes identified may not be statistically representative
   and should be treated as directional only.

4. If review data spans multiple products or ASINs, separate the
   analysis by ASIN before synthesizing cross-ASIN patterns.

5. Flag any Critical severity themes in the negative section
   prominently. A product safety complaint buried in 3-star reviews
   can become an account health issue -- it should not be treated
   as background noise.

=====

PASTE YOUR CUSTOMER FEEDBACK DATA BELOW. Include any combination
of: Amazon review excerpts (include star rating and date for each),
Amazon Q&A questions and community answers, customer service ticket
themes or representative messages, and any other customer feedback
you have. Include as many data points as possible -- 50+ reviews
produces substantially better analysis than 10. For each review,
include the star rating.

[YOUR DATA HERE]