← All posts
Customer Feedback & Roadmaps

Customer Feedback Examples: Real Ones and How to Use Them

September 6, 2026

Example customer feedback quote cards with star ratings

"Customer feedback" covers wildly different things, and each type calls for a different response. Treating a churn warning like a compliment — or a feature request like a complaint — wastes the signal. Here are real examples of the main types of customer feedback, what each is telling you, and how to act on it.

1. Praise / positive feedback

Example: "Love the new dashboard — it's exactly what I needed."

What it tells you: what's working, and what to protect. Don't just enjoy it — mine it. Praise reveals your strengths, which are worth doubling down on and highlighting in marketing. How to use it: note the pattern (which features get praised?), and ask happy users for reviews or referrals while they're delighted.

2. Complaints / negative feedback

Example: "The export keeps failing and it's driving me crazy."

What it tells you: something's broken or frustrating — often a basic expectation, which makes it urgent. How to use it: if it's a bug, route it to engineering fast (see feature request vs bug report); if it's a recurring frustration, it belongs on your board as a fix to prioritize. Complaints are gifts — they're free detection of your weak points.

3. Feature requests

Example: "It'd be great if I could filter the list by tag."

What it tells you: a gap between what users want and what you offer. How to use it: capture it on a feature request board so others can vote and demand becomes visible. One request is a data point; fifty votes is a roadmap item. See feature request examples for how to shape these well.

4. Churn signals

Example: "We're evaluating alternatives because X isn't working for us."

What it tells you: urgent risk — and often a fixable one. How to use it: treat these as high priority. A churn signal tied to a specific gap tells you exactly what's at stake if you don't act (this is cost of delay in the wild). Respond personally and log the underlying need.

5. Questions / confusion

Example: "How do I change my billing email? I can't find it."

What it tells you: a usability or discoverability problem — the feature exists but users can't find or understand it. How to use it: recurring questions signal UX fixes or documentation gaps, not always new features. Track their frequency; a question asked fifty times is a design problem.

6. Comparisons

Example: "Tool X does this thing that I wish you had."

What it tells you: a competitive gap and, usefully, a specific benchmark. How to use it: capture the underlying need (not just "copy competitor"), and weigh it against your strategy and demand.

The common thread: give feedback a home

Notice that every type ends the same way — capture it somewhere it can be ranked and acted on. Feedback scattered across channels is feedback wasted. A central feedback board turns all six types into a single, prioritized signal, and closing the loop turns responders into loyal users.

Create a free feedback board on FeatureRequest and give every kind of customer feedback a place to become action.

Let your users tell you what to build

A public board where customers post requests and vote on them. Free for your first board.

Start free