Beta mumus is in public beta: free while we test it with real teams. Found something odd? Tell us.

How to collect website feedback from clients

Client feedback is where many website projects lose time. Not because clients give bad feedback, but because it arrives in too many places and without the details needed to act on it. This guide shows a process that works for agencies and freelancers.

Why website feedback goes wrong

Most feedback problems have the same causes. Feedback arrives through several channels at once (e-mail, chat, calls, comments in documents). It describes the problem but not where it happens ("the button is wrong"). It lacks the device and browser. And it mixes bugs, content changes and new wishes in one long message.

Each of these costs time. Someone has to collect the messages, find the page, guess the device, ask follow-up questions and split the list into tasks. A good process removes those steps instead of making people faster at them.

Step 1. Agree on the rules at kick-off

Before the first review round, agree with the client on how feedback is given. Put it in writing, ideally in the project plan.

  • One channel for feedback. Everything outside it is a conversation, not a task.
  • One item per report. Do not mix three problems in one message.
  • Feedback rounds with dates, and who on the client side gives feedback.
  • The difference between a bug (does not work as agreed), a change (works, but should be different) and a new wish (not part of the scope).

Step 2. Collect feedback where the problem is

The most reliable feedback is given on the page itself. When the client can point at the element, there is no doubt about which button or which paragraph is meant. Visual feedback tools let clients click on the live or staging website and create a task with a screenshot, the page address and the browser details.

If a tool is not possible, ask for a screenshot with the problem marked, the page address and the device for every item.

Step 3. Give clients a simple template

Clients are not testers. A short template helps them give useful feedback in one go.

Where: page address (or "home page, top banner")
What I see: the price shows "12.9" without the euro sign
What I expected: "€12.90"
Device and browser: MacBook, Chrome (or "iPhone, Safari")
How important: must be fixed before launch / nice to have

Step 4. Triage feedback every day

Look at new feedback daily during review rounds. For every item, decide whether it is a bug, a change within scope or a new wish, set a priority, and assign it. Answer questions in the item, not in a separate e-mail, so the history stays in one place.

Out-of-scope wishes are not bad news. Collect them in a separate list or epic and discuss them as a change request with an estimate.

Step 5. Close the loop

Clients want to know that they were heard. Tell them when an item is fixed and ask them to check it. A board the client can see, or notifications on status changes, replace most status calls. At the end of a round, the list of open items is the agenda for the next meeting.

Tools that help

For small projects a shared spreadsheet with the template columns can work. As soon as more than one person gives feedback, a visual feedback tool saves time, because the screenshot, the page and the technical details are captured automatically and each item lands on a board.

mumus is such a tool. Clients join as free guests, report by clicking on the website, and follow the status of their items. Your team works on the same reports on a Kanban board.

Frequently asked questions

What is the best way to collect website feedback from clients?

Agree on one feedback channel at kick-off, collect feedback on the page itself with a screenshot and the page address, use one item per problem, triage daily, and tell clients when their items are fixed. A visual feedback tool automates the screenshot and technical details.

How do I stop clients from sending feedback by e-mail?

Agree on one channel in writing at kick-off and make it easier than e-mail, for example by letting clients click on the website to report. When feedback still arrives by e-mail, add it to the channel yourself once and reply with a link to the item.

More questions in the help centre

Turn website feedback into tasks your team can fix.