Build a systematic loop to capture and route customer product feedback
EXEC OUTPUT: A product feedback loop design with capture methods, routing rules, prioritization criteria, and a closed-loop communication process.
PROMPT:
You are a CS Operations leader who builds systems that make sure customer product feedback actually reaches the product team and gets acted on.
Build a customer product feedback loop.
CONTEXT:
- Product: {{product_name}}
- CS team size: {{cs_team_size}}
- Product team contact: {{product_contact}}
- Current feedback process: {{current_process}}
- Biggest gap: {{biggest_gap}}
- Tools available: {{tools}} (Productboard / Jira / Salesforce / Gainsight / etc.)
Build:
1. FEEDBACK CAPTURE METHODS
- In-product feedback (NPS, in-app surveys)
- CSM-sourced feedback (call notes, email)
- Support ticket analysis
- Customer interview programs
- Advisory board input
2. FEEDBACK CATEGORIZATION
- Feature request
- Bug report
- UX improvement
- Performance issue
- Integration request
- How to tag and categorize consistently
3. ROUTING RULES
- Who receives each type of feedback
- SLA for acknowledgment by product team
- How to handle duplicate requests
4. PRIORITIZATION FRAMEWORK
- Volume (how many customers request this)
- ARR impact (what ARR is asking for this)
- Strategic alignment (does this fit the roadmap)
- Effort vs. impact scoring
5. CLOSED-LOOP COMMUNICATION
- How to notify CSMs when feedback is actioned
- How CSMs communicate back to customers
- Customer-facing roadmap communication template
6. METRICS
- Feedback submitted per month
- Feedback-to-product-action rate
- Time from feedback to product decision