· Feedbot team
Customer Feedback Examples and How to Respond to Each
24 customer feedback examples (positive, negative, bugs, feature requests, churn) with replies, plus 8 ways to collect customer feedback on your site.
TL;DR. Customer feedback comes in six main types: positive feedback, negative feedback and complaints, bug reports, feature requests, confused questions, and churn reasons. Below are 24 realistic customer feedback examples across those types, what each one tells you, and a reply you can adapt. Then: how to collect customer feedback without annoying people, with a table of eight methods and when each one works.
The examples are illustrative, written to match the kinds of messages small SaaS teams, online stores and service businesses actually receive. We make Feedbot, an AI chatbot that also collects feedback in chat, and we mention it at the end.
What counts as customer feedback?
Customer feedback is anything a customer tells you about their experience with your product, service or support, whether you asked for it or not. Most of it isn’t labeled “feedback”. It arrives as a support question, a one-star review, a cancellation reason or a sentence in the middle of a sales chat.
| Type | Example signal | Who should own it |
|---|---|---|
| Positive | “This saved me hours” | Marketing, product (what to protect) |
| Negative / complaint | “Third time my order is late” | Support, operations |
| Bug report | “Export does nothing in Safari” | Engineering |
| Feature request | “Can I schedule reports?” | Product |
| Confusion | “Where do I change my plan?” | Product, docs |
| Churn | “Too expensive for how much I use it” | Founder, product, pricing |
Positive customer feedback examples
Positive feedback is most useful when it’s specific. Vague praise (“great app!”) feels nice but tells you nothing.
1. Specific product praise
“The CSV import matched all 340 of my products on the first try. I was expecting to spend the weekend on this.”
What it tells you: import is a strength, and setup time is a selling point. Ask if you can quote it.
2. Praise for a team member
“Ana answered at 11pm and fixed my billing problem in one email. Please tell her boss.”
What it tells you: speed and ownership matter to this customer. Pass it to Ana and her manager.
3. Praise with a hidden request
“Love the new dashboard. Would be perfect if I could export it as PDF.”
What it tells you: the redesign works, and there’s a feature request inside. Log both.
4. Public review
“5 stars. Ordered Tuesday, arrived Thursday, packaging was plastic-free like they promised.”
What it tells you: delivery speed and the sustainability promise drive reviews. Keep both true.
How to respond to positive feedback
Thanks so much, {name}! [Specific thing they mentioned] is something we worked hard on, so this means a lot. Would you mind if we shared your comment on our site? Totally fine if not.Reply to public reviews too, briefly and personally. Never offer a reward for a positive review: in the US, the FTC’s Consumer Reviews and Testimonials Rule bans incentives that depend on a review saying something positive or negative.
Negative customer feedback examples
5. Service failure
“My order was supposed to arrive Friday. It’s Wednesday. Nobody has emailed me.”
What it tells you: the delay hurt, but the silence hurt more. Proactive delay emails would have prevented this.
6. Repeated contact
“This is the third time I’m explaining this. Do you people read the tickets?”
What it tells you: your handoffs lose context. Fix the process, not just this ticket.
7. Price complaint
“You raised the price 40% and the product is the same as last year.”
What it tells you: the value story behind the price change didn’t land, or there wasn’t one.
8. Unclear policy
“I canceled within a week and still got charged for a year. That’s a scam.”
What it tells you: the billing terms weren’t clear at checkout. Look at the page, not just the refund.
9. Rude interaction
“Your agent told me to ‘read the docs’. I did. That’s why I wrote.”
What it tells you: a tone problem and probably a docs gap. Both are fixable.
How to respond to negative feedback
- Reply fast, ideally the same day.
- Restate the problem in their words, so they know you read it.
- Own your part without excuses.
- Say what you’ve done and what happens next, with a date.
- Follow up when it’s resolved.
Hi {name},
You're right, and I'm sorry. Your order was due Friday and you heard nothing from us. That's on us.
I've [refunded shipping / sent a replacement with express delivery, arriving DATE]. I've also flagged the missing delay email to our team so it doesn't happen to anyone else.
I'll check in on [date] to make sure it arrived.
[Agent name]For a public review, reply in two or three sentences, apologize, and invite them to a private channel for the details. More reply wording for upset customers is in our canned responses examples.
Bug report examples from customers
Customers rarely write bug reports like engineers. Here’s what they look like in practice.
10. Vague bug
“The app is broken.”
What it tells you: almost nothing yet. Ask one question: “What were you trying to do when it broke?”
11. Useful bug
“When I click Export on the Contacts page in Safari, nothing happens. It works in Chrome.”
What it tells you: page, action, browser and a comparison. This one is ready for engineering.
12. Bug described as a complaint
“I’ve lost my changes twice today. I’m about to give up on this.”
What it tells you: possible data loss, high severity, and churn risk. Escalate.
13. Bug that’s really confusion
“The discount code doesn’t work.”
What it tells you: could be a bug, an expired code or a code for a different product. Check before you escalate.
How to respond to a bug report
Thanks for reporting this, {name}. Could you tell me which browser you're using and what you clicked right before it happened? With that, I can pass it straight to our engineers. I'll email you when it's fixed.Then actually email them when it’s fixed. That one message turns a frustrated user into someone who reports the next bug too. Our bug report template has a five-question version for customers and a full one for engineers.
Feature request examples
14. Direct request
“Can you add dark mode?”
15. Request with a use case
“I need to send a weekly summary to my boss. Can reports be emailed automatically?”
16. Request disguised as a question
“Is there a way to bulk-edit prices?”
17. Competitor comparison
“[Competitor] lets me connect my calendar. Are you planning that?”
What they tell you: #15 is the most useful kind, because the use case (“send a summary to my boss”) might have a simpler solution than the feature they named. Always ask “what would you use it for?” and record the answer with the request.
How to respond to a feature request
Thanks for the idea, {name}. Can I ask what you'd use it for? Knowing the job behind it helps us build the right thing. I've logged it either way, and I'll let you know if we build it.Don’t promise a date. If you won’t build it, say so politely and suggest a workaround.
Confusion and question examples
These are feedback even though nobody calls them that. Each one is a sign your product or docs aren’t clear.
18. Settings
“Where do I change my billing email?”
19. Plans
“Does the Starter plan include the API?”
20. Setup
“I set up the integration but nothing is happening.”
If the same question comes up five times a month, fix the page, the button label or the onboarding step that causes it. Answering it well each time is good. Not getting it at all is better.
Churn feedback examples
21. Price
“It’s good, but I only use it twice a month. Can’t justify the cost.”
22. Missing feature
“We need SSO and you don’t have it.”
23. Switched to a competitor
“Our new CRM has this built in.”
24. Didn’t get value
“Never really figured out how to set it up.”
What they tell you: #21 may be a pricing gap (is there a smaller plan?), #24 is an onboarding problem, and #22 and #23 are product strategy. Reply to every one with a thank-you and a single honest question. Don’t try to save every customer, but do read every answer.
How to collect customer feedback: 8 methods compared
The best method depends on what you need to learn. Most teams combine a passive channel (always available) with a few targeted asks.
| Method | Best for | Response rate | Effort |
|---|---|---|---|
| Feedback in your website chat or app | Bugs, ideas, confusion, in context | High, because users are already there | Low once set up |
| Post-support survey (CSAT) | Quality of support | Moderate | Low |
| NPS survey | Overall loyalty, trends over time | Low to moderate | Low |
| Customer effort score (CES) | How hard a task was (onboarding, checkout) | Moderate | Low |
| Cancellation / exit survey | Churn reasons | High if it’s one question | Low |
| Support conversations and tickets | Everything; your largest source | Already happening | Needs tagging |
| Public reviews (Google, G2, app stores) | Reputation, purchase drivers | Low unless you ask | Medium |
| Customer interviews | The “why” behind behavior | Small sample | High |
Tips that raise response rates
- Ask at the moment it matters. Ask about checkout right after checkout, not in a quarterly email.
- One question first. “How easy was this?” with a 1–5 scale, then an optional “Why?” box.
- Make the open question specific. “What almost stopped you from signing up?” beats “Any feedback?”
- Don’t gate support behind a survey. People who need help will skip it and get angrier.
- Close the loop. Tell people what changed because of their feedback. Users who see results give feedback again.
Don’t forget the feedback you already have
Your support inbox, chat logs and sales calls contain more feedback than any survey will. The work is grouping it: ten customers describing the same bug in ten different ways is one issue with a count of ten, not ten separate tickets. Tag conversations by type (bug, feature request, complaint, confusion) and review the totals weekly.
How Feedbot collects customer feedback
Feedbot is an AI chatbot for your website that answers questions from your docs and also collects feedback in the same conversation. When a visitor mentions a bug, a complaint or an idea, the bot asks a follow-up for the missing detail and carries on helping. No separate form.
After the chat, Feedbot groups similar reports across conversations into product issues, each with a category, how many times it was reported, user quotes and affected pages. When you mark an issue fixed, you can email the people who reported it. On Pro and Business, your coding agent can pull the issues through MCP or the CLI. See how the feedback widget works, or read how to send user feedback to Claude Code.
Plans start at $0 (50 conversations a month). The details are on the pricing page.