What to Do When a Client Goes Quiet (Without Chasing or Panicking)

Published July 29, 2026

Disclosure: Some links below are affiliate links. If you sign up through them we may earn a commission at no extra cost to you. We only recommend tools we'd genuinely suggest to a friend. See our full disclosure.

There is a lot of advice about the difficult client — the one who keeps adding “just one more thing,” argues over the invoice, or blows up at a small change. There is much less about the client who does something far more common and far stranger: nothing at all.

You send the proposal, and it is read, and nothing comes back. You hand over the first draft and ask three questions, and a week goes by. You deliver the work, they say “amazing, thank you!”, and then never answer the email about the next phase. Nobody is being unreasonable. Nobody is being rude. There is simply an absence where a reply should be, and it turns out that an absence is much harder to respond to than a complaint.

This guide is about that absence: how to read it, what to send, what to stop doing, and when to close the file. It is the companion to dealing with difficult clients — which handles the ones who are present and hard work — and to invoicing, which handles the specific case where what has gone quiet is your money. Worth noting too that some silences were predictable: a project with no single decision-maker goes quiet whenever it reaches the person who was never in the conversation, which is one of the things worth checking before you take the job.

Silence is a scheduling problem, not a verdict

The first thing that happens when a client goes quiet is that you reread your last message. Then you reread it again, looking for the sentence that caused this. Was the price too blunt? Was the tone off? Did the question sound pushy?

This is the wrong activity, and it is the one that eats the most time. Silence almost never carries the meaning you are assigning to it, because silence is not a message — it is the absence of an action on someone else’s to-do list. The most likely explanations are dull:

• They are busy, and replying to you requires a decision they have not made yet.
• The decision is not theirs alone. Somebody else has to sign off, and that person is on holiday.
• The project has slipped down the priority list, and telling you that feels awkward, so nobody says anything.
• Your email arrived on a bad day and is now forty emails deep.

Notice that in every one of those, the correct response from you is a practical one — make replying easier, or make the next step happen without them — and none of them are improved by rereading your own sentences. Treat silence as a scheduling problem you can act on, not a verdict you have to interpret.

First, spend two minutes checking it actually arrived

Before you follow up, rule out the boring failure. It happens more often than people expect and it is embarrassing to send a wounded second email about a first email that was never delivered.

• Did it send? Check your sent folder, not your memory. A draft that never left is a classic.
• Right address, right thread? A reply typed into the wrong thread — or to the person who introduced you rather than the person deciding — goes to a dead end. So does a message sent to someone who has since left the company.
• Did you attach something that gets blocked? Large attachments, zip files and some link shorteners get quarantined by corporate filters. If your proposal went as an attachment and nothing came back, try a plain link or paste the key points into the body.
• Are they simply away? An out-of-office that did not fire, a public holiday you do not share, a school break. If you work across countries, this alone explains a lot of silence.

Two minutes here saves you from building an entire narrative on a delivery failure.

Where the silence happened decides everything

This is the part most advice skips, and it is the part that actually matters. “A client went quiet” describes four completely different situations that need four different responses. Locate yours before you do anything.

1. They never replied to your first approach. This is not silence — it is a non-answer to a stranger, and it is the normal outcome of most outreach. Nothing has gone wrong and nothing is owed to you. Handle it with ordinary cold-email follow-up rhythm and spend your energy on the next prospect, not this one.

2. They went quiet after your proposal or quote. A decision is pending, and it is theirs to make. Your job is to make the decision smaller and to give it a date. Nothing is at stake for you yet except a pipeline slot, so the tone is light. (The one time that slot is genuinely expensive is when you are already full and holding it open — see what to do when you have more work than you can take.)

3. They went quiet mid-project, and you are blocked. This is the expensive one, because your time is committed and your calendar is being held open at your cost. It needs the fastest response and the clearest structure.

4. They went quiet after delivery, and you are owed money. This is not a communication problem; it is a payment problem wearing a communication problem’s clothes. It has its own escalation ladder, in how to invoice a client, and it is the one case where you eventually get formal.

The rest of this guide assumes cases 2 and 3, because those are where good handling actually changes the outcome.

The follow-up that works gives them a new reason to reply

Almost every unanswered follow-up fails the same way: it is a reminder that you exist rather than a reason to respond. “Just checking in on this!” contains no information. It asks the recipient to reconstruct the whole context, decide the thing they have been avoiding deciding, and compose a reply — for no new reason. So it joins the first email in the pile.

A follow-up that works does three things:

It makes the reply tiny. Ask one question, and where possible supply the answers. “Is this still on for the spring, or has it moved?” can be answered in three words. “Let me know your thoughts on the proposal” cannot be answered in under ten minutes, which is precisely why it will not be.

It carries something new. A relevant example, a fresh idea for their project, a note that a slot has opened, a heads-up that your rates change next quarter (only if true). This is what makes it a message rather than a nudge — you are giving them a reason to open it, not asking them to feel bad.

It contains a default. Say what will happen if they do not reply. “If I don’t hear back by Thursday I’ll assume the timing isn’t right and close it off for now — very happy to pick it up whenever it suits.” This is the most useful sentence in the whole toolkit. It removes the awkwardness of saying no, it puts a date on your own calendar, and it very often produces the reply, because “wait, no, we do want this” is easier to send than a decision.

And attach the deadline to your calendar, not their conscience. “I’m holding a start date in the first week of next month and can keep it until Friday” is a fact about how your business works. “I really need an answer” is a demand. The first is easy to respond to; the second is uncomfortable, and discomfort produces more silence, not less.

A spacing that respects both of you

Three messages, spaced out, is plenty — and the third one is the one that works.

After a proposal. Wait three to five working days for the first nudge. It is short, warm, and adds one thing: “Sent this over last week — happy to walk through any part of it. One thing I’d add: [small, specific, useful]. Is the timing still roughly right for you?” Then leave a week or so before the second, which is the one with the default in it. Then close the loop.

Mid-project, when you are blocked. Move faster — two working days, not five — and be concrete about the cost. “I’ve finished the homepage and I’m at a stop until I have the three product photos and a yes on the headline. I’ve got your slot held through Thursday; after that I’ll pause and re-book you into the next opening.” You are not being difficult. You are telling them how your calendar works, which they cannot know unless you say it.

Change the channel once, not five times. If two emails have gone unanswered, one short message on whatever other channel you legitimately share — a reply on the platform you were introduced through, a text if that is how you already speak — is reasonable and often works, because it lands somewhere less crowded. Doing it on every channel at once is not persistence; it reads as pressure and it is the fastest way to make a “later” into a “never.”

The close-the-loop message nobody sends

The third message is the one most freelancers skip, because it feels like giving up. It is the one that most reliably gets a reply.

It says, kindly and without any edge: I don’t want to keep landing in your inbox, so I’ll close this off for now. If it comes back around, just reply to this and we’ll pick it straight up — no need to start from scratch.

Three things make that work. It relieves the pressure the client has probably been feeling, which is often the actual reason for the silence — people avoid inboxes that contain a decision they have not made. It leaves the door visibly open, so returning later is easy and face-saving. And it is honest: you genuinely are closing the file, which is what makes it different from another nudge.

Send it, and then actually close the file. A close-the-loop message you follow up on two weeks later is just a fourth nudge with extra steps.

Mid-project silence: pause it properly

If you are stuck waiting for content, feedback or approval, there are only three things you can do, and two of them are bad.

Keep working and guess burns your hours on work that may be discarded, and it converts their delay into your loss. Wait quietly keeps your calendar hostage while you slowly get annoyed, and the client has no idea any of that is happening.

The third option is to pause on the record. One message, three parts: what is done, what you are waiting for, and what happens next.

Quick update: the layout and the first two sections are finished and ready for you to look at. I’m blocked on the copy for the services page and a yes on the pricing table. I’ve kept this week’s slot open for it — if I haven’t got those by Friday I’ll pause here and re-book us into my next free window, which is currently the week of the 12th. Nothing lost either way, just want to be straight with you about the timing.

That message is calm, it contains no reproach, and it converts an open-ended wait into a dated decision. Then keep to it — pause when you said you would, and re-book when they resurface. A pause you announce and never enforce teaches the client that your dates are decorative.

Two structural notes for next time. Your contract or written agreement should say what happens when a project stalls on the client’s side: how long you hold the slot, that a stalled project is re-booked rather than resumed instantly, and that staged payments fall due on their dates regardless. And staged payments or a deposit do more than protect your income — they give both sides a reason to keep the project moving.

Don’t confuse “hasn’t replied” with “hasn’t paid”

These feel like the same thing from the inside and they are not.

If the work is delivered and the invoice is unpaid, the conversation is no longer about interest, enthusiasm or timing. Being gentler will not help and the friendly follow-up rhythm above is the wrong tool. That situation has a proper escalation ladder — a polite reminder, then a firmer one referencing your agreed terms, then withholding what you can still withhold — and it lives in how to invoice a client.

The practical distinction: unanswered questions deserve patience and a graceful exit. Unanswered invoices deserve a process, dates, and no embarrassment about following it.

Five things not to do

Don’t send five messages in a week. Persistence gets rewarded; frequency does not. Rapid repeat messages transfer your anxiety to them, and a client who feels pressured goes quieter, not louder.

Don’t apologise for existing. “Sorry to bother you again!” tells the reader that contacting them is an imposition. It is not — you are a professional following up on a live piece of business. Warm and matter-of-fact beats apologetic every time.

Don’t drop your price to break the silence. This is the costliest mistake here. You do not know that price was the problem, and it usually was not. What a discount into silence reliably teaches is that waiting makes you cheaper — a lesson that outlives this project and shows up in every future negotiation with that client. If you want to lower the barrier, cut the scope, not the rate: a smaller first phase at a proportionally smaller price gets a “yes” without touching what you charge.

Don’t keep doing uninstructed work. Hours spent guessing at what they meant are hours nobody agreed to pay for, and they are the ones most likely to be redone.

Don’t burn the bridge on the way out. The sarcastic last email is briefly satisfying and permanently expensive. Quiet clients come back surprisingly often — after the reorganisation, after the budget unfreezes, after the other freelancer does not work out — and they come back to the person who left the door open. That is the same mechanic that makes repeat clients the cheapest work you will ever get.

Decide the write-off in advance

The real cost of a quiet client is not the lost fee, because the fee was never yours. It is two other things: the pipeline slot you are mentally reserving, and the attention you spend rechecking your inbox.

So put a number on it before you are emotionally involved. Three messages. A close-the-loop note. Then out of the active pipeline and into a “dormant” list with a date on it. That is not pessimism; it is what stops one non-answer from quietly occupying a corner of your head for a quarter.

And keep it somewhere outside your memory. A simple record of projects and clients with a “waiting on them since [date]” stage does two useful things at once: it tells you at a glance who is genuinely stalled rather than who feels stalled, and it means a dormant client can be revived on purpose in three months rather than resurfacing by accident at 11pm. If the pipeline is thinner than you would like once you have been honest about what is actually live, that is a signal to spend the freed-up attention on finding new clients rather than on refreshing an old thread.

Make the next one boring

Most client silence is not preventable — people get busy — but almost all of the pain of it is. Four things, each of which turns a mystery into a scheduled event:

• Put a decision-by date in the proposal itself. “This quote and the March start date hold until the 14th.” Then a non-answer is simply an expiry, not a snub, and you never have to ask for one.
• Take a deposit. A project with money in it goes quiet far less often, and when it does you are not the only one carrying the cost.
• Agree the response rhythm during onboarding. Say plainly what you will need from them, roughly when, and what happens if it is late. Clients are not being inconsiderate when they go quiet mid-project; usually nobody told them their input was on the critical path.
• Write the pause down once. Add the stall clause to your standard agreement and your standard process notes, and you never have to improvise the awkward message again — you just send the one you already wrote.

Where this fits

The mirror image of this article is worth reading too: sometimes the person who has gone quiet is you, and how to tell a client you are going to miss a deadline covers that direction — same principle, opposite side of the table, since what damages the relationship is the surprise rather than the delay.

The close-the-loop message also has a planned cousin. When a project reaches its natural end rather than fading out, the same “state the position and file it” instinct becomes a proper close-out — deliverables, access, support window, final invoice — and doing it routinely is what stops finished work drifting into the same unnamed limbo this whole article is about.

Silence also lands differently depending on who it comes from. A non-reply from a prospect costs you an hour of hope; a non-reply from the client who is most of your income costs you a week of reading tone into it. If you recognise that second one, the thing to fix is not your follow-up sequence — see client concentration risk.

Handling silence well is part of the unglamorous operational half of freelancing — the same half as contracts, invoicing and boundaries — and it belongs alongside the rest of the services path in starting an online business and making money without an audience. If you are early on and every non-reply feels personal, that is normal and it fades: see how to start freelancing with no experience for the wider picture. And the mental cost of unanswered threads is a real contributor to solopreneur burnout — which is the strongest argument for closing files rather than leaving them ajar.

The bottom line

A client going quiet is one of the most ordinary events in freelance life and one of the worst handled, because it feels like a message and is actually just an absence.

Check the boring things first — that it sent, that it arrived, that they are not on holiday. Work out where in the relationship the silence happened, because a quiet prospect and a quiet client mid-project need opposite speeds. Make every follow-up carry a new reason to reply, one small question, and a default that happens if they say nothing. Send the close-the-loop message that most people skip; it is the one that works, and it is the one that lets you stop thinking about it. If you are blocked mid-project, pause on the record and re-book rather than waiting or guessing. Never answer silence with a discount.

Then close the file and go and do live work. The client who comes back three months later — and a fair few do — will come back to the person who handled the silence like a professional, which mostly means the person who stopped chasing at the right moment.