Follow Up Email After No Response From Client: A Playbook
A follow up email after no response from client contacts is a different animal from chasing a cold prospect: there is a relationship, usually money, and often your deliverable stuck behind their silence. The stakes are higher and so is the awkwardness - which is why most people either wait too long (resenting quietly) or write the passive-aggressive "just circling back again..." that damages the relationship they're trying to protect. The skill is tone calibration: client silence comes in four distinct situations, and each one licenses a different firmness. Here are the four, with scripts and the reasoning behind each.
A follow up email after no response from client starts by reading the silence
| Situation | Wait before touch 1 | Tone license | Escalation path |
|---|---|---|---|
| Proposal sent, no answer | 4-5 business days | Warm, zero pressure | Two emails, then park it |
| Awaiting materials/approval mid-project | 2-3 business days | Project-status neutral | Email ×2, then call |
| Invoice overdue | 1 day past due | Procedural, escalating | Three notices, then terms |
| Full ghost after engagement | ~2 weeks of attempts | Professional closeout | One closure letter |
One diagnostic before any of them: confirm your original email actually arrived. A typo'd address or a spam-foldered attachment explains more "ghosting" than anyone admits - thirty seconds checking beats a week of narrative-building.
1. The unanswered proposal
They asked for the proposal; you sent it; silence. The temptation is to re-sell. Resist - they have the pitch. Touch one (day 4-5), in the same thread:
Hi Dana - checking in on the proposal from last Tuesday. Happy to walk through any part of it on a quick call, or adjust scope if the shape isn't quite right. If timing's moved, no problem - just let me know where it stands.
The logic: you're lowering the reply threshold by offering three easy answers (question, adjustment, delay) - silence usually hides one of them. Touch two (a week later) may add one honest scarcity fact: "I'm holding the March start slot through Friday - after that the next opening is May." Only if literally true; fabricated urgency reads instantly and permanently. After two touches, a proposal chase converts to a quarterly check-in, not a weekly drip.
2. Mid-project: waiting on their materials or sign-off
Here silence blocks their own outcome, which hands you the correct frame: you are not nagging, you are reporting project status. Blame the calendar, never the person:
Hi Dana - status note on the site build: we're on track for the June 3 launch, with one dependency - the product photography and final copy for the pricing page. To hold June 3, I need those by Thursday the 22nd; after that the launch shifts roughly a week per week of delay. Anything I can do to make gathering them easier?
Deadlines-as-physics is the whole trick - consequences stated as scheduling facts, not threats, plus an offer to help. If two emails go quiet on an active project, switch channels: a two-minute call resolves what six emails cannot, and "easier to grab five minutes?" is a legitimate escalation with a client in a way it never is cold. Keep every such email forwardable - your contact may be silent because they're waiting on their boss, and a clean status note is ammunition they can pass upward verbatim.
3. The unpaid invoice
The one where politeness gets miscalibrated most. You are not asking a favor; you are administering an agreement. Escalate procedurally:
Notice one, the day after due: assume oversight. "Hi Dana - flagging that invoice #214 for $4,800 came due yesterday; copy attached. Could you confirm it's in the queue?" Attaching again matters - make paying require zero archaeology.
Notice two, +7-10 days: reference terms, stay flat. "Following up on invoice #214, now 10 days past due. Per our agreement, terms are net-30 with 1.5% monthly late interest after that. Can you confirm receipt and an expected payment date?" Asking for a date converts vague intent into a commitment you can reference next time.
Notice three, +3 weeks or per contract: consequences, still procedural. "Invoice #214 is now 21 days past due. Per our agreement I'll be pausing work on the current phase until it's resolved - I'd much rather not; a payment date this week keeps everything on schedule." No apology, no anger. Every escalation should read, to a third party in accounts payable or a courtroom, like a professional following a process - because that's the audience these emails may eventually have.
4. The full ghost
When someone who was engaged vanishes across weeks and channels, send one closeout, not an eleventh bump:
Hi Dana - I haven't been able to reach you since April, so I'll close out the project on my side this Friday: I'll archive the working files (available anytime for 90 days), invoice the completed phase per our agreement, and free up the remaining scheduled time. If things went sideways on your end, no explanation needed - reply anytime and we'll pick it back up.
Closure emails get replies for the same reason breakup emails do - a closing loop prompts action, and the grace ("no explanation needed") makes replying cheap. And if no reply comes, you've converted an open wound into a filed project, on record, without burning the relationship a future quarter might revive.
The rules underneath all five
Never guilt ("I've reached out several times now..."), never apologize for asking for what's owed, keep each message shorter than the last, and stay in one thread per topic so the paper trail assembles itself. A note on the legal layer: relationship and transactional messages like these sit largely outside CAN-SPAM's commercial-email requirements, but honesty in subject lines and honoring any request to stop remain the floor everywhere - and with clients, the floor is also just good business. Silence handled with calibrated firmness, three times out of four, turns out to have been a busy week on their end - and the fourth time, you'll be glad every email you sent was one you'd stand behind.
Frequently asked questions
How long should I wait to follow up with a client who hasn't responded?
Calibrate to the situation: 2-3 business days when their silence blocks an active project, 4-5 days on an unanswered proposal, and the day after the due date for an invoice. Waiting weeks to be polite usually reads as not urgent.
How do I chase an unpaid invoice without sounding rude?
Escalate procedurally: day-one assumes oversight and re-attaches the invoice; day-ten references terms and asks for a payment date; week-three states the contractual consequence, like pausing work. Flat, factual, forwardable.
When should I stop emailing and call instead?
On active projects, after two quiet emails - a five-minute call resolves what email threads cannot, and with an existing client it's legitimate escalation rather than pressure.
What do I send when a client completely ghosts?
One professional closeout: summarize the state, name what happens by a specific date (files archived, completed phase invoiced, schedule freed), and leave the door open without demanding an explanation. It often gets the reply ten bumps couldn't.