Types of customer feedback

Every guide on this topic gives you a different number. Seven types. Ten types. Fourteen. The disagreement isn't a sign that one of them is wrong, and it isn't a rounding error. It's a sign that "type" means several different things at once, and nobody tells you which one you're supposed to organize your program around.

This page fixes that. It defines what a feedback type actually is, explains why the competing lists conflict, and gives you one rule for classifying any signal that lands in your inbox.

Types of customer feedback are categories that group feedback by a single classifying axis: who initiated it, what form it takes, or what question it can answer. A survey response and a churn event are both customer feedback. They differ on all three axes, which is why they belong in different categories and support different decisions.

Three axes account for nearly every taxonomy you'll encounter:

Most published lists blend these axes without saying so, then present the result as a flat numbered list. That's the source of the confusion. A taxonomy is only useful when every category answers the same question.

Classification isn't administrative tidying. The category a signal belongs to determines what you're allowed to conclude from it.

Treat a wave of angry app-store reviews as a representative satisfaction measure and you'll overcorrect for a vocal minority. Reviews are unsolicited, which means the people who left them selected themselves. Treat a rise in support tickets as a satisfaction signal and you may be reading a product change, a pricing change, or a seasonal spike.

The failure mode is consistent: teams take unsolicited, self-selected feedback and read it as though it were a measured sample. The feedback isn't wrong. The inference is.

This distinction gets skipped almost everywhere, and it's the most practically useful thing on this page. Some feedback types produce a number you can track over time. Others produce meaning you have to read.

Measurable types use a fixed scale, so responses aggregate into a score and support period-over-period comparison:

Interpretive types produce language or behavior with no native scale, so they explain the "why" but can't be trended without processing:

Interpretive feedback can be made countable, which is where analysis features matter. Sentiment analysis reads the emotion behind open-ended responses at scale, thematic analysis groups recurring themes automatically, and question-level summaries turn large volumes of comments into plain-language takeaways. That converts interpretive input into something you can track without reading every response by hand.

The practical rule: measure with the measurable types, explain with the interpretive ones, and never let a quote stand in for a trend.

Here's the reconciliation the numbered lists never provide. The three most common taxonomies aren't rivals. They're three axes describing the same signal.

Any single piece of feedback carries a value on all three. A CSAT response is solicited, structured, and direct. A G2 review is unsolicited, unstructured, and indirect. A cancelled subscription is unsolicited, structured, and inferred.

That's the classifying rule: don't ask which type it is, ask where it sits on all three axes. The answer tells you what you can measure, what you can conclude, and how much weight it deserves.

Open decision: SurveyMonkey currently publishes two taxonomies across different pages, direct/indirect/inferred and solicited/unsolicited. This page reconciles them rather than asserting a third. Brand and content should confirm which cut is canonical before publication.

Textbook examples are easy. These are the ones teams actually argue about.

Notice that the interesting cases are almost always inferred or unsolicited. Those are the ones where teams reach further than the data allows.

Knowing the types is only useful if your intake reflects them. Most programs over-index on one axis, usually solicited and structured, then wonder why the numbers move without explanation.

SurveyMonkey covers both sides. Rating-scale questions give you the measurable trend, open-ended questions and analysis features give you the reason, and a voice of the customer program ties them together so a score change comes with an explanation attached. Start with a customer satisfaction survey template and add sources as your program matures.

NPS, Net Promoter & Net Promoter Score are registered trademarks of Satmetrix Systems, Inc., Bain & Company and Fred Reichheld.