Examples
Website feedback your team can act on: 5 examples
By Piotr, founder of Voicedot
Useful feedback can use everyday words. Help the next person find the place, understand what happened and ask the right question.
The comments are not quotations from Voicedot customers or results of a comparative study.
1. “Make this clearer”
Vague
“Make this section clearer.”
More useful
“On the pricing page, the package description makes me think copywriting is included for every page. The agreement only includes the homepage. Can we make that distinction here?”
What changed: the place, interpretation and intended scope are clear. The copywriter knows what needs explaining.
2. “The button doesn’t work”
Vague
“The button doesn’t work.”
More useful
“On the invitation screen, I entered an email and selected Send invitation. I stayed on this view with no confirmation, so I can’t tell whether it was sent.”
What changed: the task and visible result are clear. Missing confirmation does not prove the backend failed.
3. “Use a different image”
Vague
“I don’t like this image. Use another one.”
More useful
“The image at the top of the services page looks like a large corporate team. This offer is for people running a business on their own. Can the image reflect that?”
What changed: the reason behind the preference gives the designer room to find a fitting solution.
4. “Add a calculator”
Vague
“Add a calculator to this page.”
More useful
“Customers often ask how the number of locations affects the final price. The price explanation on this page doesn’t help them estimate it. Could we discuss whether examples or a calculator would solve that?”
What changed: the feature request now has a problem to investigate. It still needs a scope decision and a check that a calculator would help.
5. “This is still wrong”
Vague
“This is still wrong.”
More useful
“I’m looking at the staging services page linked in today’s review. The package still says two consultation calls; we agreed one call in the previous discussion.”
What changed: the version and earlier decision are clear. The team can check the right page.
A pattern to borrow
On [page / element / state], I was trying to [task].
I noticed [what happened or what I understood].
I expected [result or correct information].
The reason it matters is [consequence].Use only what the comment needs. An on-page tool may already attach the location. Ask for the missing detail, not a form filled out twice.
Keep the explanation handy
The text, page context and discussion stay together. Your team can use them in the dashboard, an export or a coding agent.