Collect in context
A widget on the page beats an emailed survey, because the response arrives with the page, account, and session attached.
User Feedback Examples: Questions, Templates, and What to Do Next
Most user feedback advice stops at "ask your users". This page gives you the actual questions, grouped by what you are trying to find out, a template for reporting results to your team, and a way to decide which responses are worth acting on.
Free forever: 3 sites, 150 reports/month, no credit card.
Pro free for your first month. No credit card required.
For founders, product managers, and designers
Teams that already have users and want to learn something specific from them, rather than collecting a general satisfaction score that nobody knows how to act on.
Vague questions produce unusable answers
"Any feedback?" reliably returns either silence or praise, and neither changes what you build next. Broad satisfaction scores have the same problem at scale: a number moves, nobody can say why, and the next sprint is planned on intuition anyway. The question you ask determines whether the answer is actionable.
Ask about a specific moment
Feedback is most useful when it is tied to something the person just did. Ask about the onboarding step they just finished, the page they are on, or the error they just hit. Narrow questions asked at the right moment get answered more often and produce responses you can trace back to a real interaction.
What Makes Feedback Actionable
Four properties that separate a useful response from a comment you file and forget.
-
Tied to a moment
Collected during or right after the experience, not in a survey email sent three weeks later.
-
Attached to context
You can see which page, which account, which plan, and what the app was doing when they wrote it.
-
Specific enough to disagree with
If nobody on the team could argue against acting on it, it is probably too vague to be a finding.
-
Repeated by more than one person
A single strong opinion is a data point. The same complaint three times is a priority.
From Response to Shipped Change
Feedback that never reaches a backlog was not worth collecting.
Group before you judge
Cluster responses by theme first. Individual comments are persuasive in a way that is often misleading.
Report and decide
Summarise themes with counts and verbatim quotes, then pick what changes. Close the loop with the people who raised it.
User Feedback Questions by Goal
Pick the group that matches what you are trying to learn. Asking questions from three groups at once is how surveys get abandoned halfway.
Understanding onboarding drop-off
- What were you hoping to do when you signed up?
- What nearly stopped you from finishing setup?
- Was there anything here you expected to find and did not?
- How are you solving this problem today, if not with us?
Evaluating a specific feature
- What were you trying to do on this screen?
- Did this do what you expected? If not, what did you expect?
- What would you have to stop doing manually if this worked perfectly?
- How often do you expect to use this in a normal week?
Diagnosing churn risk
- What is the main thing keeping you from using this more?
- If we removed this tomorrow, what would you switch to?
- What is the last thing that frustrated you here?
- Who else on your team would need this to work for you to keep it?
Page-level and post-error prompts
- Was this page useful? Optional comment.
- Did you find what you were looking for?
- Something went wrong. Can you tell us what you were doing?
- How is this page working for you?
Questions worth retiring
- "Any feedback?" returns silence or praise and almost never a finding
- "How satisfied are you overall?" produces a number nobody can act on in isolation
- "What features would you like?" outsources product strategy to whoever happens to reply
- "Would you recommend us?" asked on a page where the user just hit an error
User Feedback Report Template
A structure for writing up what you found, so the team reads themes and evidence rather than a scroll of raw comments.
User feedback report
# User feedback report
Period:
Source: in-app widget | interviews | support tickets
Responses reviewed:
## Headline
The single most important thing we learned, in one sentence.
## Themes
### Theme 1: [name]
- Mentions:
- Who: plan, role, or segment
- Representative quote:
- What we think is happening:
- Proposed action:
### Theme 2: [name]
- Mentions:
- Who:
- Representative quote:
- What we think is happening:
- Proposed action:
## Decisions
- Doing now:
- Doing later:
- Not doing, and why:
## Loop closed
- Who we replied to:
- What we told them:Keep the "not doing, and why" section. It is the part that stops the same theme being relitigated every quarter.
Install in Minutes
One async script tag before the closing body tag. See the full install guide or the free widget page for Webflow, WordPress, Shopify, and Next.js steps.
Embed snippet
<link rel="preconnect" href="https://feedblox.net" crossorigin />
<script src="https://feedblox.net/widget.js" async
data-site-id="YOUR_SITE_ID"
data-token="YOUR_EMBED_TOKEN"
data-position="middle-right"
data-offset-bottom="16"
data-offset-side="16"></script>User Feedback Examples FAQ
Quick answers for teams evaluating FeedBlox for this use case. Read the full FAQ for plans, privacy, and integrations.
What are some good user feedback questions?
The best questions name a specific moment. "What were you trying to do on this screen?" and "What nearly stopped you from finishing setup?" produce usable answers. "Any feedback?" and broad satisfaction ratings usually do not, because the response cannot be traced back to anything you can change.
What is an example of user feedback?
A useful example looks like this: "I tried to export my invoices to CSV, the button spun for a while and then nothing downloaded, so I took screenshots of each one instead." It names the goal, the failure, and the workaround, which together point at both a bug and a missing capability.
How much user feedback do you need before acting?
There is no fixed threshold, but the same theme from three independent users is a reasonable trigger to investigate. One strongly argued comment is a data point rather than a mandate, and treating it as a mandate is the most common way small teams end up building for a single loud account.
When is the best time to ask for feedback?
During or immediately after the experience you are asking about. A prompt on the page someone just used will outperform a survey email sent later, both in response rate and in how specific the answers are.
What should a user feedback report contain?
A one-sentence headline, themes with a mention count and a representative quote each, an explicit list of what you are doing now, doing later, and not doing, and a note on who you replied to. The "not doing" section matters as much as the rest.
How do you collect user feedback on a website?
A feedback widget on the site itself is the lowest-friction option, because the response arrives with the page URL, the account metadata, and the session context already attached. That means you can see what the person was doing rather than relying on them to describe it.
Collect user feedback with the context already attached
New accounts get Pro free for your first month: unlimited reports, screenshots, recordings, webhooks, and collaborators. No credit card. After the trial, Free forever: 3 sites, 150 reports/month, no credit card.
Start Free
No credit card required