Guides

How to Get Useful Website Feedback From Non-Technical Clients

A process for website feedback you can act on: kick-off expectations, what to ask, one channel, review rounds and deadlines, with examples.

A hand pointing at a browser window, a green dot where the finger lands and a speech bubble beside it.
A practical field guide
In this article 9 sections

“It looks a bit off.” That is the whole message. No page, no screenshot, no hint of which “it” your client means, and the launch is in nine days.

Non-technical clients are not bad at feedback because they do not care. They struggle because nobody showed them what good feedback looks like, and the tools they reach for (email, WhatsApp, a PDF with red circles) strip out everything a developer needs. Knowing how to get website feedback from clients is mostly process, set up before the first review, plus a tool that fills in the technical part for them.

Below: what to say at kick-off, what to ask, why one channel matters, and how rounds and deadlines keep feedback moving.

What useful feedback means (and what it does not)

Useful feedback is a note a developer or designer can act on without a follow-up question. In practice it answers four things:

  • Where: the page, and the exact spot on it.
  • What: what the client sees now.
  • What instead: what they expected or want.
  • In what setup: browser, device and window size, when the problem depends on them.

What it does not mean: you are not asking clients to write bug reports like a QA engineer, name CSS properties or know what a viewport is. A client who writes “the team photo is cut off, I want to see everyone’s heads” has given you perfect feedback.

“Where” and “in what setup” are the parts clients leave out most often, and they are also the parts a tool can capture without asking. If you want a structure for the rest, our website bug report template breaks it into fields a client can actually fill in.

Step 1: Set expectations at kick-off

Most feedback problems start at the kick-off call where nobody mentioned feedback at all. Spend ten minutes there on four things:

  1. How they will send feedback. Name the one channel and show it. A 60-second screen share of the feedback button beats a paragraph in the proposal.
  2. What a good note looks like. Show one vague and one useful example side by side. Clients copy what they see.
  3. Who decides. One person on the client side signs off. Others can comment, but the decision-maker settles conflicts before feedback reaches you, not after.
  4. When reviews happen. Dates for each round, and how long each window stays open.

Put all four in the kick-off summary email. You will point back to it later, usually around round two.

Step 2: Ask a question that fits the stage

“What do you think?” invites taste debates and an inbox full of adjectives. Narrow the question to the stage you are at:

  • Design review: “Does each page show information in the order your customers look for it? Mark anything missing or in the wrong place.”
  • Content review: “Is every text on the page correct and final? Mark each one that needs changing and paste the new version.”
  • Final check: “Click through every page on your own phone and your usual computer. Mark anything that does not work or looks broken.”

Each question tells the client what belongs in this round and what does not. A logo colour discussion during the final check is a sign the question was too open. The website launch QA checklist covers what your own team should test in that last week, so the client’s pass can focus on content and on their own devices.

Ask for one more thing explicitly: one note per issue. Five problems in one message turn into five follow-ups, because you cannot mark half a message as done.

Step 3: Pick one channel and close the others

Email, Slack DMs, WhatsApp voice notes, comments in a shared doc, a phone call on Friday afternoon. Each channel alone is fine. Five of them at once means someone on your team spends Monday copying feedback into a task list, and something always gets lost.

The rule: feedback that arrives anywhere else gets moved to the agreed channel, by you, with a friendly note. “Thanks, I have added this to the feedback board so it does not get lost. Next time you can drop it straight there.” After one or two of these, most clients switch.

Which channel should it be? For website feedback, the best one sits on the website itself. When the client reports from the page they are looking at, “where” and “in what setup” answer themselves. With a visual feedback widget like Zorko:

  • The client clicks the feedback button on the page. No account and no browser extension.
  • The widget captures the visible part of the page. The client drops a pin on the problem, or draws an arrow or a box, and can blur anything sensitive.
  • They type what they want changed and send it. An email address is optional.
  • The report arrives with the page URL, browser, operating system, window size and the pin’s exact position on the page, plus the last console errors and warnings, which your developer will care about more than the client ever will.

If you are still choosing a tool, our overview of website feedback tools compares the main approaches. For non-technical clients the deciding factor is simple: it has to work on the first try, with nothing to install and no password to remember.

Vague vs useful feedback, side by side

These are the kinds of notes agencies get every week, next to the same point sent with a pin and one short prompt (“what do you want instead?”).

VagueUseful
”The homepage looks off.”Pin on the hero: “The headline wraps into three lines on my laptop. Can it fit in two?"
"The contact form doesn’t work.”Pin on the Send button: “Clicked Send, nothing happened, no message.” Browser, device and console errors attached automatically.
”Make it pop more.”Arrow to the pricing buttons: “These blend into the background. I’d like them in our brand green."
"Fix the text on the about page.”Box around the second paragraph: “Replace with: We have looked after patients in Kraków since 2009."
"Mobile is broken.”Pin on the menu icon, sent from a phone: “The menu opens but I can’t close it.”

The client did not learn any technical vocabulary. The pin supplied the “where”, the widget supplied the setup, and the prompt supplied the rest.

For problems that resist words, like a form that fails only on the third step, let clients record their screen. In Zorko that is a recording of up to 3 minutes with optional voice, in desktop browsers.

Step 4: Run feedback in rounds, not a stream

Open-ended feedback (“send us anything, anytime”) feels generous but brings small batches every other day and no moment when a page counts as done.

Rounds fix that. A round is a window with a start date, an end date and a scope:

  • Round 1, structure and design (5 working days): layout, sections, navigation.
  • Round 2, content (5 working days): every text and image, final versions.
  • Round 3, final check (3 working days): only things that are broken or wrong. No new ideas.

Between rounds your team works through the list. When a round closes, walk through the reports with the client in one short call, or let them check the result on their own. In Zorko’s review mode every report shows as a pin on the live page with its status, so the client sees in place what was fixed. A review link works for people without a Zorko account and expires after 1, 7 or 30 days.

New ideas that arrive in round three are not ignored. They go on an “after launch” list, which is often all a client needs to hear.

Step 5: Put dates on everything

Feedback without a deadline arrives in the week you planned for something else. Two dates per round keep things moving:

  • Feedback closes: the last day the client can add notes to this round.
  • Changes delivered: the day your team will have worked through them.

Send a reminder two days before feedback closes. If a round ends with no feedback at all, say in writing that you treat it as accepted. Most clients are fine with that, as long as it was agreed at kick-off and not invented in week six.

The same goes for disagreements on the client side. If the CEO wants the video and marketing wants the slider, the conflict goes back to them with a date, not to your developer to guess.

An example: the same project, two processes

This is an illustration, not a case study. Say a three-person agency builds a 12-page website for a local dental clinic.

Without a process, feedback arrives by email and phone over five weeks. The team gets around 90 messages, many of them repeating or contradicting each other. About a third need a follow-up question (“which page?”, “which phone?”), and each question costs a day of waiting. Someone spends roughly an hour a day turning messages into tasks. That is about 25 hours of admin before anyone changes a line of code.

With the process above, the same clinic sends feedback in three rounds through a widget on the staging site. The team gets around 60 reports, one issue each, with a pin and the technical details attached. Follow-up questions drop to a handful, because each report already shows where and in what setup. Triage is a 20-minute pass per day while a round is open. Admin time lands somewhere around 6 to 8 hours for the whole project.

Your numbers will differ. What changes is where the time goes: in the first version, most of it is spent finding out what the client meant. In the second, it is spent doing it.

A checklist to copy into your next project

  • Kick-off: feedback channel shown live, one vague and one useful example, one decision-maker named.
  • Round dates in the kick-off summary email.
  • One question per round, matching its stage.
  • Widget on staging before the first review. If staging must stay private, set the widget to show only for people with the link.
  • Feedback from other channels moved to the agreed one, with a friendly note.
  • Reminder two days before each round closes.
  • An “after launch” list for ideas that arrive late.

Zorko is free for one project and 10 reports a month, no credit card needed. Create a free account and put the widget on your next staging site before the first review.

FAQ

How do I get clients to send feedback on time?

Agree the review dates at kick-off, send a reminder two days before each round closes, and treat a round with no feedback as accepted if that was agreed up front. A tool that takes a minute to use helps too: clients put off feedback that feels like homework.

Do clients need an account to leave feedback?

Not in Zorko. The client clicks the button on the page, marks the spot and writes a message. The email field is optional. Accounts are only for your team in the dashboard.

What if the client keeps sending feedback by email anyway?

Move it to the agreed channel yourself, reply that it is now on the board, and remind them where the next one goes. One or two gentle redirects are usually enough.

How many feedback rounds should a website project have?

Three work for most small and mid-size sites: structure and design, content, final check. More important than the number is that each round has a scope and an end date, written down before the project starts.

Can a non-technical client report a bug a developer can fix?

Yes, if the tool collects the technical part for them. A pin on the page plus the browser, device, window size and console errors attached automatically give a developer most of what a hand-written bug report would, without the client knowing any of those terms.

Zorko news in your inbox

Product updates and practical tips for agencies, about once a month. Nothing else.

Put it into practice

Give clients the right way to show what they mean.

Zorko keeps screenshot and desktop video feedback together with the page details your team needs to act.

Start free See how it works

Free includes 1 project and 10 feedbacks a month. No credit card required.