You sent the draft on Tuesday. It is now the following Wednesday, you have sent a polite nudge, and there is nothing. The work is parked, the invoice is parked, and your team has quietly moved on to something else. Most people treat this as a waiting problem and wait harder. It is almost never a waiting problem. A client who has gone quiet is communicating, just not in words, and the useful skill is telling the four silences apart before you decide what to send next.
Silence is a status, and it is rarely neutral
The instinct is to read no reply as no news. In client work it is closer to the opposite. Every day a project sits unanswered, it gets more expensive for both sides: your team loses the context it had loaded, the client loses the momentum that made them hire you, and the eventual restart costs a meeting nobody wanted.
The cost is asymmetric, too. The client experiences the pause as one item slipping down a list. You experience it as a resourced project with a hole in it, staff assigned to nothing, and a payment milestone that will not trigger. That asymmetry is why the responsibility for breaking the silence sits with you, fairly or not.
So the question is not whether to chase. It is what you are chasing, because the right move is completely different depending on which silence you are in.
The four silences
Almost every quiet client falls into one of four categories. They look identical in your inbox and they need opposite responses.
- Buried. Nothing is wrong. Your contact has a bad month, your email is on page three, and they genuinely intend to reply. This is the most common silence by a wide margin, and the one people over-read.
- Blocked. They cannot answer without someone else, and that someone is a director, a board, a committee, or a legal review. They are quiet because they have nothing to say yet and telling you that feels like an admission.
- Unhappy. Something in the last delivery missed, and they have not decided how to say it. Silence here is avoidance, and it hardens the longer it runs. This is the rarest of the four and the most expensive to misdiagnose.
- Gone. Priorities shifted, budget moved, or your contact is on the way out of the organization. The project is not paused, it is over, and nobody has wanted to make that call out loud.
Chasing all four the same way is what turns a buried client into an irritated one and lets a gone client run for another six weeks on your forecast.
Read the silence before you break it
Five minutes of looking will usually tell you which one you are in. You are looking for evidence, not vibes.
- Check whether the silence is only yours. Are they active elsewhere? Publishing, hiring, posting, replying to your colleague about something unrelated? An organization that is visibly moving while your thread is dead is a different situation from one that has gone quiet everywhere.
- Look at what you sent last. Re-read it as they would. If it ended with an open question, three options and no recommendation, or an ask that required them to make a decision above their pay grade, you may have built the silence yourself.
- Count the approvals your ask requires. If the answer needs a budget holder, a legal read, or a committee that meets monthly, you are almost certainly blocked rather than ignored, and the calendar is the real constraint.
- Check the last delivery against the brief. Be honest. If something shipped late, missed a requirement, or quietly ignored feedback they gave, treat unhappy as the working assumption until proven otherwise.
- Look at the relationship, not just the thread. How long has this account run, how many times have they gone quiet before, and how did those end? Past behaviour is the single best predictor here, and most teams never look.
A follow-up that asks for a reply gets ignored. A follow-up that makes the reply one word gets answered.
The message that actually gets a reply
The failed nudge is always the same: it checks in, it apologizes for chasing, and it asks whether they have had a chance to look. It puts all the work on the recipient, which is exactly why a buried person skips it again.
Whatever silence you are in, the message that works does four things in about eighty words.
- States where things stand, factually. “The homepage design has been with you since the 12th and the build is holding.” No blame, no sigh, just the position.
- Names the consequence with a date. “If we get sign-off by Friday the launch holds at the 30th. After that it moves to the 14th.” Consequences make a reply worth more than silence.
- Reduces the reply to a choice. Offer two or three options they can pick between with a single word. Never ask an open question of someone who is already overloaded.
- Gives them a graceful exit. “If this has moved down the priority list, say so and I will park it properly rather than keep chasing.” This one line does more work than the other three combined.
That last line is the part most people cannot bring themselves to write, because it invites the answer they fear. That is precisely its value. It converts a gone client into a resolved one in a single email, and it converts an unhappy one into a conversation, because you have made it safe to say the awkward thing.
When there is still nothing
Three attempts is a reasonable ceiling: the original, one nudge, and one message built the way above. After that, escalate sideways rather than louder.
- Change the channel. A two-line message on the platform they actually live in, or a phone call, will resolve in a minute what a fourth email will not resolve at all.
- Change the person. Go to the other contact you were introduced to at kickoff. This is one of the strongest arguments for insisting on a second name in every account from day one.
- Send a closing summary, not a warning. Restate what was delivered, what is outstanding, what it will cost to restart, and say the project is being moved to paused as of a date. Written calmly, this is not an ultimatum. It is a record, and records get replies.
- Release the capacity. Take the hold off your schedule and tell your team it is off. Keeping a slot open for a client who has not spoken in a month is a decision to lose that time twice.
Build the system that prevents most of it
The silences you can prevent are mostly the buried and blocked kind, and you prevent them at the start of the relationship rather than in the middle of it.
| Set this up at kickoff | What it prevents |
|---|---|
| A named second contact on the account | A project that stops dead when one person is on leave |
| A stated response window, both directions | Ambiguity about when quiet becomes a problem |
| Approval chain written down, by name | Discovering the board meets monthly in week nine |
| A standing fifteen-minute check-in | Silence lasting longer than a week without notice |
| Decisions logged in one shared place | Re-litigating a choice nobody can find evidence of |
| A written pause and restart clause | Absorbing the cost of a stalled project yourself |
The mechanical half of this belongs in whatever system holds the account rather than in someone’s memory. If every client sits in one place with their contacts, their approval chain, the decisions made, and the next scheduled touch, then a project going quiet surfaces as a visible gap instead of a nagging feeling someone has on a Thursday. That is most of what a client and project system is actually for, and it is why the teams that never seem to lose accounts to drift are rarely the ones with the best memory.
Key takeaways
- Silence is data, not an absence of it. Diagnose which of the four silences you are in before you decide what to send.
- Most quiet clients are buried, not unhappy. Read your own last message before assuming the worst, because you may have caused it.
- Make the reply one word. Give a status, a dated consequence, two options, and an honest way out.
- Escalate sideways, not louder. Change channel or contact before you send a fourth email, and release the capacity you are holding.
Questions to ask your team
How long should I wait before the first follow-up?
Two business days past whatever response window you agreed at kickoff, and if you agreed none, three business days. Waiting a week to be polite mostly guarantees your email is now unfindable in their inbox.
Does giving them an exit make it easier for them to leave?
It makes it easier for them to tell you they have left, which already happened. The clients that line loses were never going to come back, and you find out in a week instead of a quarter.
Should I keep working while I wait for sign-off?
Only on work that is genuinely independent of the decision. Building forward on an unapproved direction is how a two-week delay turns into two weeks of rework, and clients rarely accept a bill for that.
Is it worth charging for delays caused by the client?
A pause and restart clause is more useful than a penalty. Say that a project paused beyond a set period returns to the schedule at the next available slot, and that restarting carries a re-mobilization fee. It changes behaviour without making anyone feel fined.
What if the quiet client is a long-standing, valuable account?
Then pick up the phone on day three instead of day fifteen. The size of the relationship is an argument for less email formality, not more patience.
