How to Follow Up With a Client Who Hasn't Responded (Without Being Pushy)

To follow up with a client who hasn't responded, work out what's blocking them, shrink your ask to one question, state a date, then send three short nudges on day 2, day 5 and day 8. This guide is for agencies, studios, freelancers and other client-service teams. You'll finish with a five-step method and three ready-to-send messages, in about 30 minutes, at beginner level.

Before you start

Gather these first so every message you send is specific:

• The original request and deliverable, open on your screen. You'll name the exact item in every nudge, so have it in front of you.
• Access to the same email thread. Replying in the original thread keeps the context visible and stops your nudge from looking like a new topic.
• A decision on your default. Decide what happens if there's no reply: the work counts as approved, or it pauses. Step 5 needs this, and it fits neatly into your wider client approval process.
• One person who owns the nudges. If three people each send one, the client gets three chasers in a day. Pick a name.
• What you're waiting on, and since when. Write down "homepage design v2, sent Monday" so you know which clock you're on.

Step 1: Check what's actually blocking them

A nudge can't fix an unclear ask, so spend five minutes finding out why the client is quiet before you write anything. Silence is rarely rudeness. It's usually a vague request, a busy week or a decision the client doesn't know how to make.

Punchlist's guide to unresponsive clients starts the same way: set expectations early and understand why the client may be unresponsive before following up.

Run this quick internal check:

1. Reread your original message as the client would. Is it obvious what you want from them, and by when?
2. Open the file the way they would. Does the link work without a login? Does the PDF load on a phone?
3. Check who actually received it. Was the person who can say yes on the thread?
4. Look for the likely cause. It's usually one of three: they're busy, they're unsure what they want, or there's internal red tape (someone else has to sign off).

Say you sent a logo round to a founder, but the CMO approves brand work. The founder isn't ignoring you. They're waiting for someone else, and your nudge should ask them who that is.

If the ask was fuzzy to begin with, fix that at the source. A creative brief clients fill in saves you from half of these silences. A client portal with a clear status on each request helps too, because the client can see what's waiting on them.

The usual mistake: assuming the client is ignoring you. Nine times out of ten the ask was the problem, and a firmer nudge makes it worse.

Step 2: Make the ask a single question

Replies get sent when they take almost no effort, so turn your ask into one question the client can answer in a few seconds. Advice from Rebecca Zucker on LinkedIn says the same: make a clear ask and give the other person an out.

Here's how to shrink an ask:

1. Pick the one thing you truly need. Approval, a choice, or a missing file. Not all three.
2. Phrase it as yes/no or A/B. "Thoughts?" invites a long think. "Is version B good to go, yes or no?" invites a one-word reply.
3. Name the exact item. "Homepage design v2, sent Monday" beats "the thing I sent." Skip "just checking in" and "bumping this up," because they say nothing the client can act on.
4. Keep it short. A few lines is plenty. Short messages get read on a phone between meetings.
5. Give an easy out. "If B isn't right, tell me what's off in a line and I'll fix it."

Compare two versions. The weak one: "Hi Sam, just checking in on the designs. Let me know your thoughts on the colors, the layout, the copy, and whether we should add a testimonials section." The strong one: "Hi Sam, is version B of the homepage good to go, yes or no? If not, one line on what to change is plenty."

Make it easy to answer from wherever the client lives. If they can reply from their inbox, they'll reply sooner, and tools with replies by email let that answer land on the right request. This also helps you limit design revisions: a single question about a single version keeps feedback from sprawling.

The usual mistake: bundling five questions into one email. The client answers none, because the whole message feels like homework.

Step 3: Set a date in the message

A date turns a vague wish into a deadline, so put one in every message. "Whenever you get a chance" gives the client permission to do it never.

Tie the date to something real: a launch slot, a printer cutoff, a developer's booking, or the start of the next sprint. "I need your yes or no by Thursday to keep our Tuesday launch slot" is a reason, not a demand.

On timing, Sayanchor suggests sending a good follow-up two to three business days after your first message, replying in the same thread. Small Business Expo gives the same 2 to 3 business day window. Treat that as guidance rather than a rule. A same-day turnaround for a launch tomorrow gets a faster clock, and a quarterly strategy review can take longer.

How to do it:

1. Choose your final date first. Work backwards from the real deadline. For this sequence, that's roughly day 8.
2. Write the date in plain words. "By end of day Thursday," not "soon" or "this week."
3. State the consequence in one line. "That keeps launch on Tuesday."
4. Reply in the original thread. The date and the earlier files stay one scroll away.

If you use one-click approvals, the date sits right next to the button, so the client sees both the ask and the deadline in one place.

The usual mistake: "Whenever you get a chance." It sounds polite, but it tells the client nothing happens if they wait.

Step 4: Send a three-message nudge sequence

Three short messages on day 2, day 5 and day 8 give you a calm, predictable rhythm, and the key is changing the angle each time. A generic bump repeats the problem. A smaller question and a clearer next step give the client something easy to answer. Fyxer frames it well: a dropped follow-up costs more than a reply, so protect the relationship with timing and tone.

Count days from your original message. Send each nudge in the same thread, in the morning.

Day 2 message

Friendly, specific, one question, one date.

Subject: Re: Homepage design v2

Hi Sam,

Quick one on the homepage design I sent on Monday: is version B good to go, yes or no?

If you can let me know by next Thursday, we'll keep the Tuesday launch slot. If something's off, one line on what to change is plenty.

Thanks, [Your name]

Day 5 message

Change the angle. Shrink the ask or add a summary so replying is even easier.

Subject: Re: Homepage design v2

Hi Sam,

I know it's a busy week, so here's the short version. Version B has the new headline and the shorter form. Everything else is as we agreed.

Reply "B is good" and I'll move to build. Or if someone else needs to see it first, tell me who and I'll send it over directly. Thursday still keeps launch on track.

Thanks, [Your name]

Day 8 message

Close the loop. State the default and the next step.

Subject: Re: Homepage design v2

Hi Sam,

I haven't heard back, so I want to make sure this doesn't stall your launch. If I don't hear from you by end of day Thursday, I'll treat version B as approved and start the build.

If you need changes, just reply with what to change and I'll turn it around. If it's easier to talk, I'm free for a five-minute call tomorrow.

Thanks, [Your name]

If there's still silence after day 8, switch channel or contact (a short call, a text, or the person who actually approves) rather than writing a fourth email.

An AI account manager like Dora can do the nudging for you: she follows up in the request's thread when a client goes quiet, twice at most, then tells your team. Weekly summaries keep what's waiting on clients visible at a glance. Doing it by hand works fine too.

Measure it. No two studios are alike, so test this yourself. For your last 10 requests awaiting feedback, record the days from sending to reply and how many needed three or more chasers. Use this sequence for the next 10, then compare median days to reply and chaser count after four to six weeks.

The usual mistake: sending the identical email three times. That's nagging, not following up.

Step 5: Use a default approval

A default approval means silence never stalls the work: if there's no reply by a stated date, the deliverable counts as approved. The key is that the client knows in advance.

Zucker's advice to give the recipient an out applies here. The client can always say "wait, I need changes," but they have to say it.

How to set it up:

1. Mention the default at kickoff. One line in your onboarding message: "If we don't hear back within 7 days, we'll treat the work as approved and move on."
2. Repeat it in each request. Add the date to the message, as in the day 8 example.
3. Leave a clear way out. Tell them how to ask for changes, whether by reply or a button.
4. Log what happened. Note when the default was applied, so there's a clear record.

For example, a studio sends a landing page for sign-off with a 7-day auto-approval. The client stays quiet through the nudges, and when the 7 days are up the page moves forward as approved. Nothing is lost, and nobody waits a month.

Dora has this built in: each request has one-click approval, nudges for quiet clients, and auto-approval after the days you choose (default 7). It all lives in a branded client portal that clients enter without a password.

The usual mistake: surprising the client with a default they never heard of. Say it early and say it twice, or it will feel like a trap.

Common mistakes

These are the problems that keep quiet clients quiet:

• Vague bumps. "Just checking in" gives the client nothing to answer. Name the item and ask the question.
• Too many asks. Five questions in one message get zero answers. Keep it to one.
• No date. Without a deadline, replying can always wait. Put a date and a reason in every message.
• Chasing in a new thread. A fresh email loses the files and context. Reply in the original thread.
• Never changing the angle. Same email, same result. Shrink the ask, add a summary, then state the default.
• Giving up instead of closing the loop. Silence isn't an answer. Day 8 should state what happens next, even if that's "pausing work."

Another common trap is running clients from your inbox: chasers pile up across threads, and nobody can see what's waiting on whom. Keep a single list of what's waiting on clients, wherever it lives.

Checklist

1. Check what's blocking them: reread your ask, test the file, confirm the right person has it.
2. Make the ask a single question: yes/no or A/B, naming the exact item.
3. Set a date in the message: tie it to a real consequence and reply in the same thread.
4. Send the three-message sequence: day 2 friendly question, day 5 smaller ask, day 8 default and next step.
5. Use a default approval: tell the client at kickoff, and give them an easy way out.

Keep the day 2, day 5 and day 8 messages saved as templates, ready to paste. Or let Dora nudge quiet clients and handle sign-off for you: try Dora free, because your first client is free, forever.

Frequently asked questions

How long should I wait before following up with a client?

About 2 to 3 business days for the first nudge, as guidance rather than a rule. Then send a second on day 5 and a final one on day 8, adjusting for how urgent the work is.

What if the client still doesn't reply after three messages?

Switch channel or contact: call, text, or reach the person who actually signs off. Then apply the default you stated (treat the work as approved), and pause work if the default doesn't fit the situation.