What to do when a client goes quiet on website feedback
You sent the review link, gave a date, and heard nothing. A client not responding to feedback is one of the most common ways a website project stalls. Here is how to follow up without nagging, when to set a firm deadline, and how to pause the project fairly if it comes to that, with four messages you can copy.
Why clients go quiet
Most of the time it isn't personal. A website review is an easy task to put off: it has no meeting attached, it needs some thinking, and it competes with everything else in the client's week. The common reasons:
- They're busy. The review is on their list, just not at the top.
- They're waiting on someone else. A partner, a manager or a board member hasn't looked yet, and they don't want to send half the feedback.
- They don't know how to start. The site is in front of them and they aren't sure what you want them to check.
- They aren't happy. Something feels wrong and they can't put it into words, so they say nothing.
- They missed the email. It went to spam, or to an inbox they check once a week.
Each of these has a different fix, which is why your first follow-up should be friendly and open, not firm. You'll get firmer only if the quiet continues.
Check what you can before you chase
Before writing anything, look at what you already know. Did the link reach them at all? If you share the review with HTMLAnnotate, the Activity view shows whether the link was opened on every plan, and on Pro and Team you can see open counts and when each named reviewer last looked. That changes the message you send:
- Not opened. The email may have been missed. Resend the link and keep it short.
- Opened, no comments. They've looked but haven't acted. Ask if anything is unclear, or whether they're waiting on someone.
- Opened several times, no comments. They may be unsure or unhappy. Offer a short call.
Also check your own side. Did your first email give a clear date, say what the round was for, and make the link the only thing to click? If not, the follow-up is a good chance to fix that. Our feedback request email templates cover the first email for each round.
A simple follow-up timeline
A pattern that stays polite and still moves the project along:
- One or two working days after the deadline: a gentle nudge with the link and one new date.
- Three to five working days later: a deadline reminder that says what happens to the schedule if you don't hear back. Try a phone call around now too.
- Another three to five working days later: a last message before pausing, with a clear date the pause starts.
- When they come back: a short, warm restart message with a new plan.
Adjust the gaps to your project. A two-week site can't wait as long as a four-month one. What matters is that each message has one date, and the client always knows what happens next.
Four follow-up messages to copy
Swap the parts in curly brackets for your own details. Each one is short on purpose: a long chaser is easier to put off than a three-line one.
2. Deadline reminder
When the nudge gets no reply.3. Last call before pausing
When the reminder date has passed.4. Restarting after a pause
When the client gets back in touch.Make replying easy
The smaller the ask, the faster the reply. A few ways to lower the effort:
- Offer a call. Fifteen minutes on a call, going through the page together, often gets more done than a week of emails. Write up what was agreed straight after.
- Narrow the question. "Are you happy with the homepage?" is easier to answer than "Any feedback?"
- Give them a one-click answer. In HTMLAnnotate, reviewers can press Approve on a version, or Ask for changes with a note. You get an email alert either way, so you don't have to keep checking.
- Find out who's blocking. If they're waiting on a colleague, ask whether that person can review the link directly. Our guide to feedback from many stakeholders covers how to set that up.
Pausing a project fairly
Pausing isn't a punishment. It's a way to stop a project sitting half-open, where you keep the slot free and the client feels no urgency. Done well, it protects both sides.
- Say it in writing, with a date. "We'll pause from Friday 28th" is clear. "We may need to pause at some point" isn't.
- Say what a pause means. Is their work saved? Does the timeline reset? Does any billing change?
- Say exactly how to restart. One step, like replying to the email, and how quickly you'll get going again.
- Stick to what you agreed. Billing during a pause, restart fees and treating silence as approval all depend on your contract. Check what yours says before you mention any of them, and if it says nothing, don't invent terms in the email. This guide isn't legal advice.
- Keep the tone warm. Plenty of paused clients come back, and how you handled the quiet patch is part of what they remember.
When the project restarts, treat it as a fresh round with a clear scope and date. If the site has moved on since the pause, publish the latest work as a new version on the same review link, so earlier comments stay with the earlier version and the client starts from a clean page.
Preventing it next time
Most stalled projects can be headed off at the start, before anyone has gone quiet.
- A clause about delays. Agree in the proposal what happens if feedback doesn't arrive, for example: "If we don't receive feedback within 10 working days of a request, the project will be paused and rescheduled when feedback arrives." Have whoever handles your contracts check the wording.
- Agreed review windows. Set a window for every round, such as five working days, and put the dates in the project plan on day one. Our guide to revision rounds covers how to define a round so the window holds.
- One client lead. Name one person on the client side who gathers their team's views and sends the feedback. If that person is busy, you know who to call, and the project doesn't wait on five inboxes.
- A clear finish line. Agree up front how sign-off works, so the last round doesn't drift. Our guide to client website approval walks through it.
If you manage several clients, write these into your standard process so every account manager follows the same steps. Our guide to setting up an agency client feedback process shows how the pieces fit together.
Questions
How long should I wait before following up on client feedback?
A day or two after the deadline you gave is fair. If you never gave a deadline, wait about a week after sending the link, then follow up with a specific date. Waiting longer rarely helps: the review only slips further down their list.
How many times should I follow up before pausing a project?
Three messages is a sensible pattern: a gentle nudge, a deadline reminder that says what happens next, and a last message before you pause. Space them a few working days apart, and try a phone call before the last one.
Can I treat silence as approval?
Only if your contract or proposal says so and the client agreed to it. Even then, tell them in writing before you act on it. If your agreement doesn't cover it, ask for an explicit approval instead. This is not legal advice, so check your own contract.
Is it fair to charge a restart fee after a pause?
It can be, if it was agreed up front. A paused project often needs rescheduling and a refresh of where things were. Whether you can charge for that depends on what your contract says, so check it before you mention a fee.
What if the client is quiet because they are unhappy?
Silence sometimes means they don't like the work and don't know how to say it. Make it easy: ask one open question, such as whether something isn't feeling right, and offer a short call. Our guide to vague client feedback helps once they start talking.
Send your next review link with HTMLAnnotate. See when it was opened, and let clients approve or ask for changes in one click.
Start a free review