I need you to analyze customer feedback and prepare an action brief for my team. Context Product or service: [PRODUCT OR SERVICE] Decision this feedback should inform: [DECISION TO INFORM] Customer feedback: [CUSTOMER FEEDBACK] Relevant customer segments or account context: [CUSTOMER SEGMENTS] Current constraints or commitments: [CONSTRAINTS]
Work from the supplied feedback only. Do not treat a single comment as representative, infer customer demographics, or invent metrics. Preserve the difference between a customer’s stated request, the underlying problem it may indicate, and a proposed solution. Produce a 700-1,000 word feedback action brief with these sections: 1. Executive readout: three to five sentences on the strongest signals, including the volume and source limits of the evidence. 2. Theme table: group feedback into 4-7 mutually distinct themes. For each, list the underlying customer need, supporting comment IDs or short excerpts, affected segment, frequency where countable, severity, and confidence level (high, medium, or low). 3. What not to conclude: identify weak, conflicting, or unrepresentative signals that should not drive a decision yet. 4. Prioritized actions: recommend no more than five actions using impact, evidence strength, effort, risk, and reversibility. Separate immediate operational fixes from items requiring discovery or product work. Give each action an owner role, first step, and target date relative to today. 5. Follow-up plan: write 5-8 precise questions or research actions to close the most important evidence gaps. Before answering, check that every recommendation traces to cited feedback and that no theme combines unrelated complaints merely because they sound negative. Flag claims that cannot be supported by the supplied material. Ask up to three clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PRODUCT OR SERVICE] | Name the offering and briefly state what customers use it for. | InvoiceFlow, web invoicing software for independent design studios. |
| [DECISION TO INFORM] | State the specific decision, such as renewal priorities, onboarding changes, or a quarterly roadmap. | Choose the two onboarding improvements for the next six-week product cycle. |
| [CUSTOMER FEEDBACK] | Paste survey responses, interview notes, tickets, reviews, or a labeled summary with dates and sources. | Survey, 18 responses: 7 mention confusion about tax settings; 5 want recurring invoices; 3 say reminders feel too frequent. Support tickets from August: 11 tax-setting questions, 2 recurring-invoice requests. |
| [CUSTOMER SEGMENTS] | Describe relevant groups such as plan type, company size, tenure, or use case. | Most respondents are US studios with 2-10 employees; three are UK freelancers. |
| [CONSTRAINTS] | List budget, staffing, technical, policy, or timing limits that affect possible actions. | One product engineer and one designer are available; no accounting-rule changes before January. |
How to use
- Paste feedback with a source label, date, and customer segment wherever available.
- State the decision the team must make; this prevents a general recap from replacing a useful recommendation.
- Check that each priority cites real feedback and that frequency is not confused with business impact.
- Follow up with: “Turn the top two discovery items into interview questions and a one-week research plan.”
Variations
Feedback request email
Use this to ask customers for feedback after a defined interaction.
Write a customer-feedback email for [CUSTOMER TYPE] who recently [TRIGGER EVENT]. The goal is to learn about [DECISION AREA], not to solicit praise. Produce a subject line, a 90-130 word email, and 4 questions: one rating question, two open questions about friction and alternatives, and one permission question for follow-up. Keep the questions neutral and avoid promising changes. Include [INCENTIVE OR NONE] only if supplied. Ask up to three questions if required information is missing.
Executive feedback summary
Use this when leadership needs a short decision memo rather than a full analysis.
Using [FEEDBACK NOTES], write a one-page executive feedback memo for [AUDIENCE] about [DECISION]. Include the three strongest evidence-backed themes, an explicit sample-size and selection-bias note, two recommended actions, and one decision that should wait for more evidence. Cite the source label after every material claim. Do not invent customer quotes, percentages, or revenue impact. Before answering, verify that recommendations match the evidence and separate facts from interpretation. Ask up to three questions only if inputs are missing.
Support ticket review
Use this to find repeatable service fixes in a support queue.
Analyze [SUPPORT TICKETS] from [TIME PERIOD] for [PRODUCT]. Create a ticket-quality and customer-friction report with issue categories, ticket counts, repeat-contact signals, probable root causes, and fixes grouped into documentation, process, and product changes. For each fix, give an owner role and a measurable leading indicator. Do not assume a root cause where ticket evidence is incomplete; label it as a hypothesis. Check that categories do not double-count tickets and that every count can be audited. Ask up to three questions only if required inputs are missing.
Tips
- Keep raw wording and source labels in the input; a cleaned summary can hide a recurring but important distinction.
- Count feedback separately from customer impact: one blocked enterprise account can matter more than ten cosmetic requests.
- Tag feedback by lifecycle stage when possible, because acquisition, setup, habitual use, and renewal complaints require different owners.
- Do not turn a requested feature directly into a roadmap item until the underlying job and affected segment are clear.
FAQ
Can AI tell me what customers want from a few responses?
It can organize patterns and identify hypotheses, but a small or self-selected sample cannot establish prevalence. Keep the sample limits in the final brief.
Should I include negative feedback only?
No. Positive feedback shows what customers rely on and helps distinguish a broken core experience from a missing enhancement.
How many themes should a feedback report have?
Usually four to seven. More themes often becomes a list of comments instead of a set of decisions.