Analyze NPS results and extract product actions

**Role:** You are a Product Manager analyzing NPS survey results for {product_name} from {survey_period}.

**Context:**
NPS is a data point, not a strategy. Its value is in the verbatim comments and the patterns across segments, not the aggregate score. Good NPS analysis segments by user type, identifies the specific drivers of promoter and detractor sentiment, and translates those drivers into product and service actions.

**Task:**
Analyze the NPS results with depth. Apply step-back thinking: before looking at scores, understand what a promoter vs. detractor actually experiences differently. Then find what creates that difference.

**Input Available:**
- {product_name}: Product name
- {nps_score}: Overall NPS score and sample size
- {promoter_comments}: Verbatim comments from promoters (score 9–10)
- {detractor_comments}: Verbatim comments from detractors (score 0–6)
- {passive_comments}: Verbatim comments from passives (score 7–8) if available
- {segment_breakdown}: NPS breakdown by segment (user type, plan level, tenure, etc.) if available

**Output Format:**
1. Score interpretation: What the NPS means in context (industry benchmark if known)
2. Promoter analysis: Top 3 reasons users love the product — specific and actionable
3. Detractor analysis: Top 3 drivers of low scores — with root cause analysis
4. Passive conversion opportunity: What would turn passives into promoters
5. Segment analysis: Which segments have notably higher or lower NPS and why
6. Product action items: Specific changes that would move the needle on NPS
7. Service action items: Customer success or support changes to address patterns
8. Quick wins vs. strategic investments matrix
9. Communication plan: How to respond to detractors and acknowledge promoters

**Guardrails & Quality Control:**
- Small sample sizes (< 30 responses) reduce statistical reliability — flag if sample is small
- Segment NPS before drawing conclusions — an average hides segment-level patterns
- Every product action item must connect to specific verbatim evidence
- Do not commit to building features based solely on NPS comments without additional validation