27 Customer Feedback Examples (and How to Act on Each One)

TL;DR#

Customer feedback examples fall into seven recurring categories — feature requests, bug reports, churn signals, praise, pricing objections, onboarding friction, and support complaints — and each one implies a specific action, not just a tag in a dashboard. The most common mistake is logging feedback and stopping there: companies that act on feedback see roughly 14.4% lower churn than those that only measure it. This guide breaks down 27 concrete customer feedback examples, the action each one should trigger, and the follow-up question that surfaces the "why" most feedback hides. The recurring problem across all 27 is missing context: a one-line review or a 1–5 rating tells you what a customer feels but rarely why, which is why static surveys and feedback widgets leave the highest-value insight on the table. Tools like Perspective AI close that gap by replacing the form field with an AI interview that follows up in the moment. Treat each example as a trigger: read the signal, take the action, then capture the reasoning before it disappears.

This guide is for product managers, customer success managers, CX leaders, and founders who collect feedback but want a faster path from raw comment to decision.

What counts as a customer feedback example?#

A customer feedback example is any specific instance of a customer expressing an opinion, need, frustration, or intent about your product, service, or experience — captured through a review, survey response, support ticket, interview, sales call, or in-app message. Useful customer feedback examples are concrete enough that you can map them to a clear action: a bug report points to engineering, a pricing objection points to packaging, a churn comment points to a retention play.

Feedback breaks into a few standard dimensions worth knowing before the list. By source, it is either direct (the customer tells you), indirect (a public review or social post), or inferred (behavior you observe). By solicitation, it is active (you asked, via a survey or interview) or passive (they volunteered it, via a feedback button or support chat). And by structure, it is quantitative (an NPS or CSAT score) or qualitative (open-text comments and conversations). The categorization frameworks published by enterprise CX vendors and the academic literature converge on these same axes; the Nielsen Norman Group's work on the difference between attitudinal and behavioral data maps cleanly onto the direct-versus-inferred split. The 27 examples below are organized by what the feedback is about — because that is what determines the action.

Why acting on feedback matters more than collecting it#

Acting on customer feedback matters more than collecting it because collection without action erodes trust and quietly drives churn. When a customer tells you something and nothing visibly changes, you have taught them that feedback is theater. The data is blunt: roughly 75% of businesses fail to respond to negative reviews — precisely the feedback that needs the fastest response — and failing to respond can lift churn by as much as 15%, according to review-response benchmark data compiled by Opensend. Companies that implement what they hear achieve materially lower churn than companies that only measure.

Speed compounds the effect. At-risk B2B accounts show a roughly 14-day window between when a customer first voices dissatisfaction and when they decide to cancel; teams that respond inside it save a meaningful share. The action is the point, and the clock starts the moment feedback lands. For the operating model behind this, our guides to closing the customer feedback loop and the argument that no one owns the "act" step go deeper.

27 customer feedback examples (and the action each one implies)#

Below are 27 customer feedback examples grouped into seven categories. For each, you get the example, the action it should trigger, and — where it matters — the follow-up question that turns a flat comment into a decision. The pattern to notice: almost every example begs a "why" the original channel never captured.

Feature requests and product suggestions#

Feature-request feedback tells you what customers think is missing, but the raw request is rarely the real need — your job is to act on the underlying job, not the literal ask.

1. "I wish I could export my dashboard to PDF." — Action: log it against the reporting cluster and check how many accounts share the request before building. Follow-up: What are you doing with the export once you have it? (Often the real need is a scheduled email, not a PDF.)
2. "Can you add a Slack integration?" — Action: route to product; weight by account tier and use frequency. Follow-up: Which moment do you want the notification to interrupt?
3. "It would be great if this worked on mobile." — Action: pull session data to confirm mobile intent is real, not aspirational. Follow-up: What were you trying to do when you reached for your phone?
4. "I built a workaround in a spreadsheet to do X." — Action: treat as a high-signal request; a workaround proves willingness to pay in effort. Prioritize above hypothetical asks.

The trap is taking requests literally. The disciplined move is to capture the underlying job-to-be-done, which is what a structured discovery conversation does — see our 60 customer discovery questions and the opportunity solution tree for the frameworks that keep you from building the wrong thing.

Bug reports and friction#

Bug-report feedback is the most actionable category because it maps directly to engineering, but the description quality determines how fast you can fix it.

5. "The page froze when I clicked Save." — Action: triage severity by reach and frequency; reproduce before escalating. Follow-up: What did you see right before it froze, and what browser were you on?
6. "I got logged out three times today." — Action: check session/auth logs for a pattern across accounts; this is a churn accelerant if widespread.
7. "The numbers in the report don't match my own count." — Action: treat data-integrity complaints as P1 — trust damage outlives the bug.
8. "I couldn't find where to cancel, so I just called my bank." — Action: fix the flow and flag the account for recovery; this is a bug report and a churn signal at once.

Churn signals and cancellation feedback#

Churn-signal feedback is the highest-stakes category, because the customer is telling you they are leaving — and the reason they give is often a polite proxy for a deeper one.

9. "We're going in a different direction." — Action: trigger a save play and book an exit conversation; this answer is almost never the real reason. Follow-up: What changed about your priorities?
10. "It's too expensive for what we use." — Action: distinguish a value problem from a price problem before discounting. Follow-up: Which part would have made it worth the price?
11. "We never really got it set up." — Action: route to onboarding/CS; this is a fixable activation failure, not a product rejection.
12. "My champion left and no one else knew how to use it." — Action: build a multi-threading and re-onboarding motion for orphaned accounts.

Cancellation comments are where surfacing the "why" pays off most. A dropdown reason ("too expensive") and a five-minute conversation lead to completely different retention plays. Our guides to customer churn survey questions and the difference between voluntary and involuntary churn cover how to read these signals correctly.

Praise and positive feedback#

Positive feedback is not just a morale boost — it is an underused asset for marketing, retention, and product strategy if you act on it.

13. "Your support team is the best I've worked with." — Action: thank them, then ask for a review or referral while sentiment is high. Public praise left unacknowledged is a missed loyalty moment.
14. "This saved my team about ten hours a week." — Action: capture as a quantified proof point and request a case study. Specific outcomes are gold for sales.
15. "I recommended you to two other founders." — Action: route to the referral program and flag as an advocate for your customer advisory work.
16. "The new dashboard is exactly what I needed." — Action: tag the feature as validated and tell the team that shipped it; closing the loop internally matters too.

Mirror the customer's tone when you respond, and reference specifics rather than sending a generic "thanks." For more methods of generating this kind of feedback in the first place, see our roundup of how to collect customer feedback.

Pricing and packaging objections#

Pricing feedback signals a mismatch between perceived value and cost — and the action is almost never a blanket discount.

17. "Why am I paying for seats I don't use?" — Action: review packaging fit; consider usage-based or right-sizing options before they churn.
18. "Your competitor is half the price." — Action: reinforce differentiated value; if you keep losing on this, it is a positioning problem, not a price one.
19. "The jump from the starter to pro plan is too steep." — Action: test an intermediate tier; pricing-cliff feedback recurs across accounts.
20. "I didn't know that feature cost extra." — Action: fix pricing transparency in onboarding; surprise costs damage trust fast.

Onboarding and activation friction#

Onboarding feedback predicts retention better than almost any other category, because customers who never activate rarely renew.

21. "I signed up but didn't know what to do next." — Action: audit the first-run experience and add a guided path to first value.
22. "Setup took way longer than I expected." — Action: instrument time-to-value and cut the longest step. Friction here compounds into churn.
23. "I needed a feature explained but couldn't find docs." — Action: close the content gap and consider in-context guidance instead of a separate help center.

Static onboarding forms are a common culprit here — they front-load effort before the customer feels any value. Our pieces on in-app feedback widgets and how to ask for customer feedback cover the timing and channel choices that lift both response and depth.

Support and service complaints#

Support-complaint feedback is the most emotionally charged category, so the first action is acknowledgment, and the second is root-cause analysis.

24. "I waited four days for a reply." — Action: address the SLA breach with the customer, then check whether it is systemic or a one-off.
25. "The agent didn't actually solve my problem." — Action: separate the resolution failure from the wait-time failure; they need different fixes.
26. "I had to explain my issue three times to three people." — Action: fix the handoff/context-passing process; repeat-explanation is a top driver of frustration.
27. "Great product, but your onboarding email confused me." — Action: treat mixed feedback as two items — log the praise, fix the email. Take responsibility rather than offering excuses, and invite further dialogue, a principle echoed across customer-service research.

How to act on customer feedback systematically#

Acting on customer feedback systematically means running every example through the same four-step loop: capture, categorize, act, and close. The 27 examples above are inputs; this loop is the operating system that keeps them from dying in a spreadsheet.

• Step 1 — Capture with context. Don't just log the comment; capture the reasoning behind it. A bug report without a repro step or a churn comment without a "why" forces a second round of chasing. This is where conversational capture beats a form field.
• Step 2 — Categorize by intent and sentiment. Tag each item as a feature request, bug, churn signal, praise, pricing, onboarding, or support issue, then route to the owning team. Categorizing by intent is the step most teams skip, and it is what makes feedback routable.
• Step 3 — Act and assign an owner. Every category has a default action and a default owner. Unowned feedback is the single biggest reason loops break.
• Step 4 — Close the loop. Tell the customer what changed. This is what converts a one-time respondent into a repeat one and turns feedback into a trust-building habit.

The hardest part of this loop is Step 1, because most feedback channels capture the what and discard the why. A 1–5 rating, a thumbs-down, or a one-line review gives you sentiment without reasoning. That missing reasoning is why two customers who both "rate you a 6" can need opposite fixes.

Where AI interviews surface the "why" behind each example#

AI interviews surface the "why" by replacing the static field with a conversation that follows up in real time — probing a vague answer, asking for the moment behind the rating, and capturing context the customer would never type into a form. Where a survey records "too expensive," an AI interviewer asks which part would have been worth the price and captures that the customer never reached the feature that justifies the cost — a packaging fix, not a discount.

This is the core of how Perspective AI works: it runs hundreds of these follow-up conversations simultaneously — interview-grade depth at survey scale — then analyzes the transcripts into themes automatically. Instead of a backlog of flat comments, you get the reasoning attached to each one. For teams running this as a discipline, our customer feedback analysis workflow and closed-loop feedback program guides show how to operationalize it. The role-specific setup is documented for CX teams and product teams, and CSMs can start from a ready-made customer interview template or a churn interview.

Common mistakes when acting on customer feedback#

The most common mistake is treating feedback as data to store rather than signals to act on. A few others recur across teams:

• Taking feature requests literally. The request is a clue to a job, not a spec. Build the job, not the ask.
• Discounting on every pricing objection. Price feedback is often a value-communication problem in disguise.
• Reading scores without reasons. An NPS or CSAT number without the "why" is a vanity metric — see our take on voice-of-customer metrics worth measuring.
• Letting feedback go unowned. Every category needs a default owner or the loop breaks.
• Never closing the loop. Silent action teaches customers their feedback doesn't matter, even when you fixed the thing they reported.

Frequently Asked Questions#

What are good examples of customer feedback?#

Good examples of customer feedback are specific, actionable comments tied to a real experience — such as "I built a spreadsheet workaround to export my data" or "we never got it set up." These beat vague ratings because they point directly to an action and an owning team. The most useful examples include enough context to act without a second round of questions, which is why open-ended conversation produces better examples than fixed-scale survey items.

What are the main types of customer feedback?#

The main types of customer feedback are direct, indirect, and inferred by source; active and passive by solicitation; and quantitative versus qualitative by format. In practice, teams find it most useful to organize feedback by subject — feature requests, bug reports, churn signals, praise, pricing objections, onboarding friction, and support complaints — because the subject determines the action. Each type benefits from a follow-up that captures the reasoning behind it.

How should you respond to negative customer feedback?#

Respond to negative customer feedback quickly, personally, and with ownership rather than excuses. Acknowledge the specific issue, thank the customer for raising it, and offer a clear path forward — speed matters most here, since acknowledging public feedback within hours rather than days measurably lifts the odds of a recovered relationship. After responding, run the root-cause analysis to determine whether the complaint is a one-off or systemic, then fix the underlying process.

How do you act on customer feedback instead of just collecting it?#

You act on customer feedback by running every item through a four-step loop: capture it with context, categorize it by intent and sentiment, assign an owner and take the action, then close the loop by telling the customer what changed. The step most teams skip is closing the loop, which is what turns one-time respondents into repeat ones. Companies that act on feedback rather than only measuring it see materially lower churn.

Why do customer feedback scores miss the real insight?#

Customer feedback scores miss the real insight because a number captures sentiment without reasoning — two customers who both rate you a 6 can need opposite fixes. A 1–5 rating, a thumbs-up/down, or a one-line review tells you what a customer feels but not why, and the "why" is what determines the action. Conversational follow-up that probes the score is what recovers the missing context, which is why AI interviews increasingly sit alongside or replace static surveys.

Conclusion#

The 27 customer feedback examples above share one lesson: feedback is only as valuable as the action it triggers, and the action is only as good as the context behind the feedback. A feature request is a job in disguise, a churn comment is usually a polite proxy for a deeper reason, and a pricing objection is often a value-communication gap — but you only learn that by capturing the "why," not just the "what." Run every example through the capture-categorize-act-close loop, assign an owner to each category, and never let a signal die in a spreadsheet.

The hardest part is capturing the reasoning before it disappears, and that is exactly where static forms fall short and conversations win. If you want to turn flat customer feedback into the reasoning behind it — at the scale of hundreds of customers at once — start a research project with Perspective AI and let an AI interviewer ask the follow-up your survey never could.