---
name: customer-feedback-loop
description: Turn support conversations into product change through structured tagging, aggregation, and a route into the roadmap. Use when support hears the same complaints and nothing changes.
---

# Customer feedback loop

Support is the highest-volume source of product truth in most companies
and the least used, because the signal arrives as thousands of
individual conversations and nobody aggregates them.

## Method

1. **Tag by underlying cause, not by symptom.** Three tickets about
   confusion, a workaround, and a feature request may all be one
   unclear interface.
2. **Keep the tag set small and enforced.** A sprawling taxonomy is
   applied inconsistently and cannot be aggregated (see
   support-ticket-triage).
3. **Count customers affected, not tickets.** One customer filing five
   tickets is not five customers, and conflating them distorts
   priority.
4. **Attach real quotes to the aggregate.** A number moves nobody; a
   number plus three verbatim customer sentences moves a roadmap
   discussion (see customer-interviews).
5. **Route it into the existing prioritisation.** Feedback that arrives
   outside the normal process is ignored regardless of quality (see
   prioritization-frameworks).
6. **Close the loop back to support and the customer.** Agents who never
   see an outcome stop tagging carefully, and customers who hear back
   about a fix become advocates.
7. **Separate loud from representative.** The people who write in are
   not a random sample, and weighting by volume alone over-serves the
   vocal (see sampling-and-bias).

## Boundaries

Support feedback describes existing users' problems; it says nothing
about people who never signed up or already left. It reveals pain rather
than solutions, and customers' proposed fixes are often worse than the
problem. Aggregation is not prioritisation, which weighs strategy too.