# Synthesize customer feedback

Use for feedback from interviews, support, sales, surveys, or research notes.
Establish the question, period, audience, and source population before drawing
conclusions. Retrieve the relevant feedback, following pagination when necessary;
state coverage limits when the set is incomplete or selectively sampled.

## Count evidence at the right level

Keep source links and stable feedback or customer identifiers where available.
Deduplicate copied notes and cross-posted tickets by their origin. Repeated
mentions from one customer can show persistence, but are not independent customer
votes. Similar wording from distinct customers is not automatically a duplicate.
When customer identity is unknown, do not invent a match or a unique-customer count.

Distinguish feedback records, mentions, and distinct customers in any quantitative
claim. Define the denominator, period, and eligibility rules. A customer may appear
in multiple themes, so theme counts need not sum to the customer population. Do not
infer market prevalence from a selected set of interviews or support tickets.

## Preserve differences that affect the conclusion

Cluster by the underlying need or problem, retaining representative evidence and
important counterexamples. Separate requested solutions from the problems they
address. Preserve segment, plan, role, or use-case differences when sourced and
material; do not infer them from names. Avoid combining opposing needs into a
single universal recommendation.

Keep direct quotes faithful and attributable. Distinguish observations, your
interpretation, and proposed next steps. A rare but consequential failure may
deserve attention without being called widespread. Do not turn theme frequency
alone into a priority score or claim roadmap commitments.

## Deliver a traceable synthesis

Use the requested depth: themes with evidence, relevant segment differences,
exceptions, implications, and open questions. Include counts only when defensible;
qualitative synthesis is useful without percentages. Link back to supporting
feedback, respecting the intended audience's access and handling of customer data.
Save or update only when requested, following the main skill's destination and
verification workflow. Creating a synthesis does not authorize CRM edits, task
creation, or customer messages.
