How to get useful website feedback from clients

· 6 min read

Every agency and freelancer knows the email. It arrives the night before launch, it has fourteen numbered points, three of them are about pages that do not exist any more, and point nine says “the thing on the right looks off”. Nobody did anything wrong. The client reviewed the site the only way they were given: by looking at it and writing down what they noticed somewhere else.

Better client feedback is mostly a process problem, not a people problem. This guide is about the process: where feedback should live, what to ask for, and how to stop translating descriptions back into the page they came from.

Why client feedback goes wrong

Clients are not testers, and they should not have to be. They know what their business needs, and they can tell at a glance when something feels wrong. What they lack is the vocabulary to point at it from a distance. “The button” is clear when you are looking at it and ambiguous in an email. Most of the friction comes from four places:

  • Distance from the page. Feedback is written in an email, a document or a chat thread, away from the thing it describes. Every note has to be mapped back to a page and an element by someone else.
  • Batching. Clients save notes up and send them all at once, often late, so problems found on day one are fixed on day ten.
  • Missing context. Which page, which device, which browser, logged in or not? A layout bug on a phone looks like nonsense on a desktop.
  • Mixed signals. Bugs, copy edits, design opinions and new ideas arrive in one list with no way to tell which are blocking launch.

Set up the review before you ask for it

Give feedback one home

Decide where feedback goes and say so at the start of the project. If notes can arrive by email, chat, phone call and a shared document, they will arrive by all four, and something will be lost. One channel also gives you one list to work through and one place to show what is done.

Make it happen on the page

The single biggest improvement is letting clients leave notes on the site itself rather than describing it from somewhere else. When a note is pinned to the element it is about, nobody has to ask “which button?”. Screenshots with arrows drawn on them are a step in this direction; a feedback tool on the staging site is a bigger one.

Ask for one note per problem

One problem, one note, one sentence is a good default. It is easier for a client than writing a long list, and it means each note can be fixed, checked and closed on its own. A long list stays open until the last item is done.

Tell them what kind of feedback you want, and when

Early in a project you want opinions about structure and tone. Close to launch you want broken things. Say which review this is. “This round is for anything that looks broken or reads wrong; design changes go on the list for after launch” saves a lot of scope arguments.

What a useful client note looks like

You do not need clients to write bug reports. You need each note to answer three questions: what is it about, what is wrong with it, and what should it be instead. Compare:

  • “The contact page looks weird on my phone.”
  • “On the contact page, the Send button is cut off on the right on my iPhone. It should fit on the screen.”

The second takes ten more seconds to write and saves a round trip. If you can capture the page, device and browser automatically, the client only has to write the middle part: what is wrong. When you do need a full report from someone technical, the bug report template covers every field.

Close the loop

Clients stop giving feedback when it disappears. Reply on each note when it is fixed, and ask the client to confirm. That confirmation is worth more than it looks: the person who raised a problem is the one who knows whether it is really solved, and asking them turns “we think it’s fixed” into “they agree it’s fixed”.

A simple status flow makes this visible to everyone: open (reported), in progress (someone is on it), resolved (the team thinks it is done) and approved (the person who reported it agrees). Keeping “resolved” and “approved” separate stops work being closed by the people who did it.

Don’t make clients create accounts

Every sign-up step between a client and a comment loses some feedback. Clients review on their phone between meetings; if the first thing they see is a registration form, they will send an email instead. Look for a way to let reviewers comment with as little ceremony as possible, and keep the dashboard and tracker for your own team.

How Jot handles client feedback

Jot was built for exactly this situation, so here is how it maps onto the process above. You add one script tag to the staging or live site (or the client installs the Chrome extension when you cannot touch the site’s code). A small tab sits at the edge of the page, collapsed until someone opens it.

  • The client clicks the thing that is wrong and types one sentence. The note is pinned to that element and stays attached to it when the page is resized.
  • Each note arrives with a screenshot, the URL, the element’s selector, and the browser, operating system and screen size. The client does not fill any of that in.
  • If something only goes wrong after a sequence of steps, the client can press Record, do it, and stop. The replay is attached to their note, with console and network beside it. Inputs are masked in the browser before anything is uploaded.
  • Clients sign in to the widget with a six-digit code sent by email, on the page itself, with no dashboard account. On projects you open to anonymous feedback, they do not sign in at all.
  • Your team replies and moves the status; the client sees the reply on their pin. Only the reporter approves.

Reviewers are free and unlimited on every plan, so you never have to decide which client stakeholders are worth a seat. See pricing for the plans, and the reviewer guide to send to clients.

A short version to send your client

If you only change one thing, send your client a note like this at the start of review:

  • Leave feedback on the page itself, one note per problem.
  • Say what is wrong and what you expected instead.
  • This round is for broken things and wrong words; ideas go on a separate list.
  • We will reply on each note when it is fixed; please confirm when you agree.

Specific, on-the-page feedback is faster for the client to give and faster for you to act on. Pair it with the website QA checklist for your own team’s pass before the client sees anything.