How to Follow Up with Clients Who Went Silent (Scripts + System)

You sent the proposal three days ago. Or you delivered the work last week and you're still waiting on feedback. But nothing. No questions, no approval, not even a quick "I'll get back to you." That silence can be uncomfortable, especially when your next move depends on the client's answer.

Here's the short version of how to follow up with clients: match your follow-up to the specific situation, use a script that removes friction instead of adding pressure, and build a system so you're not deciding whether to follow up every single time.

In this guide, you'll get scripts for seven common follow-up situations, a system for triggering follow-up automatically instead of relying on memory, and a rule for knowing when to stop.

Why clients go quiet (and what it usually means)

Before reaching for a follow-up script, figure out what that silence is most likely telling you. Otherwise, you risk responding as though it were a relationship problem.

The most common reasons clients go silent

Think about the client who receives your design draft on Tuesday. They intend to review it Wednesday, but first they need input from their marketing director. But the director is in meetings, then Thursday gets busy. So by Friday, your email is probably halfway down the inbox.

Most of the time, the explanation is pretty straightforward. Replying to you simply slipped down their priority list. And that can happen for a bunch of perfectly ordinary reasons:

• They're busy. Your message got buried in meeting notes, deadlines, customer issues, and dozens of other messages.
• Your contact may be waiting for approval from a founder, finance lead, legal team, or another stakeholder before they can give you an answer.
• They don't know how to clearly communicate their feedback, so they delay responding.
• They simply forgot. They opened your message at the wrong time, planned to return to it, and never did.
• Your project is not their priority this week. A project that is urgent to your delivery schedule may only be secondary to whatever is happening inside the client's business.

There’s one case where silence means something serious, though. That’s when a client has raised a concern and hasn’t heard back from you. Maybe they questioned an invoice. Maybe they said a deliverable missed the brief. Maybe they asked when a delayed project would be finished.

If they then go quiet, another "Just checking in!" message can make matters worse. Check the communication history first. Look at the project thread, client portal, email, and any internal handoff between team members.

The right mindset before you follow up

Following up is a normal part of delivering a service because client work often depends on things you can't accomplish without the client. Things like feedback, approvals, files, answers, payments, and decisions should all come from the client side.

Following up isn't automatically "chasing" or bothering a client. It's part of keeping the project moving. 67% of agency leaders point to effective communication as a factor in strong client relationships. A good rule is to reduce the response burden with every follow-up.

The 7 follow-up scenarios and what to say in each

The best follow-up removes whatever is making the response difficult. That's why there's no universal "just checking in" email worth saving as your go-to. Match the message to the moment. Here are seven situations you will run into, and what to say when you do.

1. After sending a proposal

Situation: You sent the proposal two to four days ago. The client was engaged on the call, maybe even sounded ready to move forward. Then, silence.

What your follow-up should be: Your follow-up should be designed to reopen the conversation because your contact could be comparing options, waiting for budget approval, or trying to get a decision from someone who was not on your original call.

Script: Hi [Name], just checking in on the proposal I sent over on [date]. Happy to answer any questions or walk through anything in more detail if that would help. Let me know where you're at when you get a chance.

2. After delivering work and waiting for feedback

Situation: You delivered the homepage design (or video draft or campaign copy) on Monday. Your agreed review window has passed, and you need the client's feedback before your team can move to the next stage.

What your follow-up should be: Your follow-up should bring the review back to the client's attention. They could be collecting feedback from other stakeholders, unsure how to explain the changes they want, or simply taking longer to review the work than expected.

Script: Hi [Name], following up on the [deliverable] I sent over on [date]. Wanted to make sure it landed and see if you have any feedback or revisions before we move to the next step. Let me know what you think.

3. After a client misses a scheduled call

Situation: The client didn't show up for your scheduled call, and they haven't reached out to reschedule.

What your follow-up should be: Your follow-up should result in getting another call on the calendar. The client could have run into an unexpected calendar conflict. They could have double-booked or simply lost track of time.

Script: Hi [Name], looks like we missed each other on [day]. No problem at all. Happy to find another time that works for you. Here are a couple of options: [time 1] or [time 2]. Let me know which works, or feel free to suggest another slot.

4. After a client misses a payment

Situation: A subscription renewal or invoice has passed its due date but the payment has not come through.

What your follow-up should be: Your first follow-up should make resolving the payment easy rather than assuming the client is deliberately withholding it. Chances are they have an expired or declined card, missed the original payment notification, or simply overlooked the invoice. Often, the client is just your point of contact and they just forwarded your invoice to their finance department.

Script: Hi [Name], just a heads up that the payment for [month/plan] due on [date] hasn't come through yet. This might just be a card issue. You can update your payment details directly in your portal here: [link]. Let me know if you run into any issues, and I'm happy to help sort it out.

5. After a project goes quiet mid-delivery

Situation: Your team is ready to keep working, but the project cannot move forward because you're waiting for an answer, asset, feedback, or approval from the client.

What your follow-up should be: Your follow-up should make that dependency clear. The client could be dealing with competing priorities, waiting for information or approval internally, or unaware that your team cannot move forward without their input.

Script: Hi [Name], I just wanted to check in on [project name]. We're at the [stage] and need [specific input or approval] before we can move forward. Once we have that, we can turn around [next deliverable] by [date]. Is there anything on your end that's holding things up?

6. After a project ends (re-engagement or upsell)

Situation: The project wrapped up successfully, but you haven't heard from the client since then.

What your follow-up should be: Your goal is to restart the relationship before trying to sell another service. After all, the client could have moved straight on to another business priority, assumed the relationship ended when the project did, or have another need that they haven't thought to bring to your agency yet.

Script: Hi [Name], hope things are going well. It's been [timeframe] since we wrapped up [project]. Wanted to check in and see how things are tracking on your end. We've been working on a few things lately that might be relevant to what you have coming up. I would love to catch up if the timing makes sense.

7. After a client says "let me think about it"

Situation: The client was interested but wanted to take some time before making a decision. The agreed upon or reasonable decision window has now passed.

What your follow-up should be: This isn’t about selling, as you have already discussed your offer. Your follow-up should help them reach a decision because they could be weighing the cost against other priorities, discussing the decision with someone else, or missing one piece of information they need before committing

Script: Hi [Name], just circling back from our conversation on [date]. Wanted to give you time to think it over and check in to see if you have any questions I can help answer. No pressure either way. Just want to make sure you have everything you need to make a call.

The follow-up system that removes the guesswork

The easiest way to get better at following up is to stop deciding when to follow up. Decide once, build the rules into your workflow, and let those communication rules tell your team when action is needed.

Following up reactively means you follow up only when you happen to notice that a client hasn't responded. And if you don't have a set follow-up process, your team will follow up differently, inconsistently, or forget altogether.

Define your follow-up triggers

Manage your client experience and expectations by making follow-up consistent whether you have five clients or 20. A simple starting system looks like this:

• No response to a proposal after 3 business days: follow up.
• No feedback on delivered work after your stated review window: follow up.
• Missed call with no reschedule within 24 hours: follow up.
• Payment overdue by more than 2 business days: follow up.
• No client activity on an active project for 5 business days: follow up.

Your contracts, payment terms, project timelines, and client expectations should determine the final timing. What matters is that the timing is decided before someone goes silent.

Build templates into your workflow

Once you know when to follow up, standardize what your team sends. Start with the seven scripts above, then adapt them to your agency. Save the finished versions somewhere everyone responsible for client communication can access.

These shouldn't turn your team into copy-and-paste robots, though. A template should standardize the structure, not remove the context.

Automate where you can

A system should handle the predictable reminders. A human should follow up when judgment or context is required. You shouldn't make your team manually follow up when software can handle predictable, repetitive updates automatically, like:

• a payment is due
• a request changes status
• work has been delivered
• a subscription is about to renew

The system gives clients the information or reminder they need before your team has to step in.

Good to know: ManyRequests takes some of that follow-up off your plate. Clients can check the status of their requests without emailing your team for an update. Payment and renewal reminders can go out automatically, too. Agencies can also schedule messages in advance.

Client communication best practices that prevent ghosting

Good client communication reduces the need for unnecessary follow-ups. Unclear communication leads to a client who doesn't know what to do, which delays their response, which means you have to follow up, and prolonged silence can become "ghosting."

1. Set response time expectations at onboarding

Set the rules at the beginning of the engagement. Your onboarding process should explain both sides of the communication agreement: how quickly your team typically responds and when you need a response from the client.

For example:

• We'll respond to project questions within one business day.
• When we submit work for review, we'll ask for feedback within three business days so we can keep your scheduled delivery dates.
• Now, if three business days pass, your follow-up is the next step in a process the client already understands.

2. Use one communication channel and stick to it

The more channels a client can talk to you, the easier it becomes to lose the conversation. Choose one primary place for project communication and establish it during onboarding. For a productized agency like yours, that's the client portal, because the conversation can live alongside the request it relates to. If an important decision ever happens somewhere else, bring it back into the portal.

3. Schedule structured check-ins

For ongoing clients, schedule a brief check-in at predictable intervals. It could be monthly for a retainer or around the 30-day mark for a new engagement.

Don't turn it into another status meeting. Instead, use the conversation to learn what the status board can't tell you: is there anything we could do differently this month?

4. Define your deliverable review window explicitly

If you don't tell clients when feedback is needed, they have no reason to distinguish reviewing your deliverable today from reviewing it next Tuesday. Set a review window that fits the deliverable and your workflow, and state it every time you send work for approval.

For example: “Please send any feedback within 48 hours so we can keep the next milestone on schedule.” That framing gives clients a deadline without sounding demanding.

5. Give clients visibility into delivery status

If a client has to ask whether their request has been received, who's working on it, or whether it's ready for review, your team becomes the unnecessary status dashboard. A client portal changes that. Clients can submit requests and track their progress as those requests move through your agency's workflow.

How to know when to stop following up

Following up a few times is part of doing your job, but there comes a point when continuing to message an unresponsive client becomes excessive.

The 3-attempt rule

For most non-urgent situations, three follow-up attempts over two to three weeks is a sensible outer limit. A simple cadence is:

• First follow-up: around three business days after the original message
• Second follow-up: around the one-week mark
• Third follow-up: around the two-week mark

The first can be a reminder. The second can restate exactly what you need. By the third, state the consequence of continued silence (the proposal will close, the project will pause, or the request will be archived). If you've sent three reasonable messages and received nothing, a fourth isn't the answer. It may be time to close the loop.

How to write a closing email that keeps the door open

A closing email is when you're stopping the follow-ups, not necessarily ending the client relationship. You leave the door open for them to come back and restart the conversation.

Script: Hi [Name], I've tried reaching out a few times and haven't heard back. I understand things can get busy. I'm going to go ahead and [close the proposal / pause the project / mark this as complete] on my end. If anything changes and you want to pick this back up, just reach out and we can go from there. Wishing you well in the meantime.

What to do with a stalled project in your system

Once you decide to stop following up with a silent client, you should also update whatever tool you use to manage that client or project. For example, after sending your final closing email, you might mark the request as closed or on hold, update the client's status, and remove any pending follow-up reminders

Don't leave stalled work sitting beside work your team can actually deliver. Stalled projects can distort how you judge workload, turnaround time, capacity, and what's genuinely at risk.

And if the client eventually comes back? You haven't burned the bridge. You've simply stopped reserving an indefinite place in your active workflow for someone who isn't currently participating.

Build the follow-up into your workflow

Clients will go quiet sometimes. That’s a normal part of client work, not an awkward conversation you need to psych yourself up for.

Most of the time, you're not chasing anyone. You're giving them the nudge that gets the decision made, the feedback sent, or the project moving again.

So don't leave follow-up to memory. Automate the predictable nudges, then give your team a clear trigger for everything that still needs a human. Have the message ready, too.

Waiting for feedback? Approval? Payment? Files? Nobody should have to figure out what to send from scratch.

Better yet, remove the reasons for unnecessary follow-up in the first place. Provide a branded client portal where clients can submit requests, track progress, access deliverables, and manage billing in one place. ManyRequests is a client portal built for productized agencies and supports recurring billing.

Try ManyRequests free.

Frequently asked questions

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

For most situations, three business days is a reasonable window of time. After sending a proposal, wait roughly three to five days. After delivering work, use the review window you gave the client. If they miss a scheduled call, follow up within 24 hours. The bigger goal is consistency: decide your timing in advance so your team isn't guessing client by client.

How do you follow up with a client without being annoying?

Keep the message short, useful, and easy to answer. Avoid sending multiple follow-ups in the same week unless a deadline requires it. Don't make the client feel guilty for being slow. Just remind them what you need and give them a reason to respond.

What do you do when a client stops responding entirely?

Follow up three times over two to three weeks, then close the loop if you still hear nothing. Space those attempts out rather than repeatedly nudging the client. Your final message should explain what you're doing next, such as closing the proposal or pausing the project, while making it easy to return later. Then change the project's status in your system so stalled work isn't sitting indefinitely beside genuinely active client work.

How do you follow up after sending a proposal?

Wait about three business days, then send a short, low-pressure message asking whether the client has questions. Don't resend your pitch or walk them through the entire proposal again. Your job is simply to reopen the conversation. If they remain silent, follow up again around the one-week mark, then make your third attempt the final one. After that, close the proposal on your side while leaving the door open for them to return.

Can a client portal reduce how often you need to follow up?

Yes. A client portal can remove many of the routine situations that create manual follow-up in the first place. Clients can check request progress themselves instead of asking for status updates, while billing tools can handle recurring payment communication. ManyRequests, for example, lets clients track requests and manage invoices and billing details from their portal, while its billing features support automated payment reminders. Your team can then focus on conversations that actually need a person.

‍