Why WhatsApp is the worst place to collect website feedback (and what to do instead)

Every web agency in India has lived this. You share the staging link on the client's WhatsApp group. Over the next three days you get eleven screenshots, four voice notes, a forwarded message from the client's cousin who "knows websites", and one call at 9:40 pm that starts with "bhai, ek chhota sa change hai". By Friday nobody can say which changes are done, which were cancelled, and which page the "make it bigger" note was even about.

WhatsApp is brilliant for talking to clients. It is terrible as a system for website feedback. Here's why, and what works better.

The five problems with feedback on WhatsApp

1. Screenshots lose the page

A cropped screenshot of a button doesn't say which page it came from, whether it was the mobile or desktop layout, or which browser showed it. Your developer spends the first ten minutes of every fix just finding the thing.

2. Voice notes can't be searched or ticked off

A two-minute voice note might contain five separate requests. Nobody can tick off half a voice note, and nobody re-listens to them a week later.

3. Requests get buried

A change request sent on Monday is forty messages up by Wednesday, below the photos of the new office and the "ok 👍" replies. Things get missed, and the client remembers that, not the forty things you did.

4. Too many people, no owner

Groups grow: the owner, the marketing manager, someone's nephew. When two people ask for opposite changes, there's no record of who decided what, and no clear person to approve the final version.

5. No proof of approval

When the final invoice goes out and the client says "but we never approved the homepage", scrolling back through a chat is not a great position to argue from.

What a good feedback system needs

You don't need a heavy project-management tool. You need five things:

• Feedback pinned to the exact spot on the exact page, so "this" always means something.
• Context captured automatically: page address, screen size, device and browser. Clients should never have to answer "which phone?".
• One list of changes with a status for each: open, in progress, waiting for the client, done.
• No logins for clients. If they have to create an account, they'll go back to WhatsApp.
• A written approval with a name and a date.

A simple process that works

1. Agree the rule at kick-off: "WhatsApp is for quick questions; changes go on the review link." Put it in your proposal, so it isn't awkward later.
2. Send one review link per website, not a new message for every round.
3. Let clients click on what they want changed and type the change there. One comment per change.
4. Work through the list, moving each item to "awaiting review" when it's fixed so the client can check it.
5. Ask for a formal approval once the list is empty, and keep it on record.

You can still use WhatsApp for what it's good at: sending the review link, and nudging the client when changes are ready. Just don't let it be where the changes live.

How MarkFeed does this

We built MarkFeed for exactly this problem. You share a review link; the client opens it on their phone or laptop, taps the element they want changed and types the comment. MarkFeed saves a screenshot, the page, device and browser, and turns it into a task on your board. When everything's fixed, the client marks the page approved, and you get their name, the version and the time on record.

Read more about website feedback and client approvals, or try it free on the Starter plan.