Why clients ghost your feedback requests, and how to get replies
An open question is a chore. Three small questions with a date are not.
On this page
Clients usually ignore feedback requests because an open question is a lot of work to answer. "Any thoughts?" asks them to open a file, judge a dozen things and write it all down. Ask two or three named questions with a date, make the answer a one-word reply, and replies tend to arrive in hours, not days.
Why "any thoughts?" stalls
Picture the client's side. You sent the draft on Friday with "Let me know what you think!" It is Wednesday and there is no reply.
To answer, the client has to open the file, spend time looking at it, form an opinion across copy, layout, colour, tone and whether the boss will like it, decide which of those matter, write it up and send it. That is not a question. It is a task, and it is an unstructured one.
People put off tasks that feel vague and effortful. The email sits unread, then sits in a mental pile of things to do tomorrow. It looks like ghosting, but it is closer to postponing.
There is research on how people react to too many options. In the well-known jam experiment, shoppers were more likely to buy when offered 6 jams than when offered 24 or 30, according to the abstract of Iyengar and Lepper's 2000 paper. The same pattern showed up with chocolates and optional class essays.
Be careful with that result, though. It is contested. A 2010 meta-analysis of 50 experiments (5,036 participants) found an average effect of virtually zero, with big differences between studies. A 2015 meta-analysis of 99 observations found that overload does occur, but depends on four things: how complex the set is, how hard the decision is, how unsure the person is of their own preferences, and whether they are trying to minimise effort.
Read that last list as a description of your client on a busy Friday. The task is complex, the decision is hard, they may not be sure what they want, and they want to spend as little effort as possible. Those are the conditions where choice overload shows up.
You do not need the jam study to know the practical point. Make the reply cheap.
Why open questions fail
"What do you want for dinner?" gets "anything is fine." "Indian or Thai?" gets "Thai." The same logic applies to feedback.
If you ask "any thoughts?", the client does not know which category to think in. If you ask "does the headline say what we agreed, yes or no?", they can answer in ten seconds.
This is not manipulation. It lowers the cost of giving you the answer you need. The UK Behavioural Insights Team's EAST framework puts it as the first rule of changing behaviour: make it Easy. Of its four principles (Easy, Attractive, Social, Timely), two are in your control here, because you can make the reply easy and you can make the request timely.
The four-step fix
Ask two or three named questions
Replace "let me know what you think" with specific questions tied to decisions you need:
- Does the headline say what we agreed? Yes or no.
- Is the colour direction right for the brand? Yes, no or needs adjusting.
- Would you click this call to action? Yes or no.
Keep it to three at most, and keep the answers short. The client is now answering a quiz, not writing an essay.
Point at the exact thing
Do not ask about "the design." Ask about the headline, the palette, the button. The more specific the target, the cheaper the answer. If your tool lets the client respond to a specific file or version, use that, so they do not have to describe what they are looking at.
Give a date, and make it about your schedule
"Take your time, no rush" is kind and it kills replies. With no date, the request has no deadline, and tasks with no deadline slip.
Tie the date to your own plan, which is true and easy to accept: "I'm booking revisions for Tuesday. Could you send these three answers by Monday evening? If not, I'll keep moving on the parts already agreed."
Say what happens if they stay quiet
State a default and write it into your terms, for example: "If I do not hear back by Monday evening, I will continue on the current direction, and we can revise at final review."
A caution is needed here. Silence does not reliably count as agreement. Under general contract principles, acceptance is judged objectively and is usually shown by words or conduct, and the rules differ by country. So treat this as a project-management default, not a legal trap. Put the wording in your contract and have a lawyer check it. Used that way, it keeps work moving and gives you a written record that you asked.
What to do after you have been ghosted
Do not send a second "any thoughts?" Reset with a smaller ask:
Hi [name],
>
Quick reset on Friday's homepage draft. I want to keep momentum so you have version two by Wednesday.
>
Three questions, about two minutes in total:
>
1. Does the headline land? Yes or no. 2. Is the green and cream palette the right feel? Yes or no. 3. Should the button say "Start a project" or something else?
>
If I do not hear back by Monday evening, I will continue with the current direction, and we can adjust at final review.
>
[Your name]
This works because it admits the gap without blame, cuts the cost of replying to three short answers and tells the client what happens next. For more wording, see our templates for asking a client to approve work.
Put approvals on record
Feedback that arrives by email, chat and a phone call is hard to find later. That matters when a client says months on that they never approved a version.
Keep one record of who approved what and when. Our post on documented client sign-off covers how to do this without turning the project into paperwork, and the guide to a revision policy explains how to limit rounds so feedback requests do not drag on.
How Delivvo makes feedback a one-click reply
Delivvo moves feedback out of your inbox and into the client portal, where the file, the question and the answer sit together.
This is the flow:
- You upload the draft to the client's portal as a new version, so version one stays intact.
- You request an approval on that file and write your named questions in the message beside it.
- The client opens the portal with a one-time code and no password. There is no account to create, which removes one reason to put it off.
- They approve or ask for changes on that file, and the approval is recorded with their name and the time.
- Their message stays attached to that version, so "go back to the one from last Tuesday" means opening version two.
- You see the response in the project, with no email thread to dig through.
Two details make this useful for ignored requests. The portal shows the client a list of what is waiting on them, so the open item is visible each time they open it. And the record settles later disputes, since the approval is dated and tied to a specific file version.
If you work with a team, the structure helps there too. Tasks in the team workspace carry an assignee, a brief, a due date and files, and the client only sees the file you have approved to show them, under your business name. That stops half-finished drafts from reaching the client and prompting the wrong kind of feedback.
You can also keep your questions consistent. Write the three-question format once as your standard message, and use it on every file. Clients get used to the rhythm, and answering becomes a habit on their side too.
The Free plan covers three clients and has no card requirement. Read more on client approvals and the client portal.
Next, look at client approvals or how the CRM fits around it.
FAQ
Why do clients not reply to my feedback emails?
Usually because the request is a big, vague task. They have to review, form an opinion and write it up. Make the reply short and specific, and they are far more likely to answer.
How many questions should I ask?
Two or three. Make each one answerable with yes, no or a single choice, and tie each to a specific part of the work.
Is it fine to say silence means approval?
As a working default, with care. Silence is not a reliable legal approval in every country, so state it in your contract, follow up in writing and have a lawyer check the wording.
How long should I wait before following up?
Set the date in your first message, and follow up the day after it passes with the smaller reset email. Waiting longer lets the project go cold.
Delivvo runs the whole client cycle for service businesses, from the first inquiry to the quote, contract, deposit, invoice and delivery, so client feedback is a recorded one-click approval instead of an unanswered email. Clients pay you directly through your own gateway, and Delivvo takes 0%. Start free