What To Do When a Client Goes Silent During Onboarding
They signed the contract. You sent the welcome email. And then... nothing.
No intake form response. No access granted. No reply to the kickoff confirmation. Just silence.
This happens more often than agencies want to admit. And the way most agencies handle it — either chasing constantly or going quiet themselves — makes the problem worse.
Here's how to handle client silence during onboarding without damaging the relationship or destroying the project timeline.
Why clients go silent after signing
Before you send that third follow-up, it helps to know what you're actually dealing with.
Scenario A: They're just busy. The person who signed your proposal is almost never the person managing day-to-day logistics. Your email about Google Analytics access landed in an inbox owned by someone who also has 40 other things to do. They mean to respond. They haven't.
Scenario B: They're avoiding a conversation. They realized something is missing — access they don't have, a stakeholder who needs to approve something, a question they don't have the answer to — and they haven't figured out how to tell you yet.
Scenario C: They're having second thoughts. Rare, but it happens. The silence is a soft way of slowing down before they have to say something uncomfortable.
Scenario D: Your first email was too long or vague. If your welcome email asked for ten different things without clear prioritization, the client may have read it, felt overwhelmed, and closed it without acting. This is more common than agencies realize.
Most of the time, it's Scenario A or D. Your follow-up approach should assume that first.
The response sequence: what to send and when
Day 1: The access request (with built-in next steps)
This is the email you sent at the start. If you haven't already, make sure it has:
- A specific list of what's needed (not "send us access to everything")
- The exact permission level for each tool
- Clear instructions for how to share it (no technical guessing required)
- One named person on your team who is the point of contact
A single clear ask is more likely to get a response than a six-item list.
Day 3: The specific follow-up
Don't send "just checking in." That phrase does nothing. Send something specific:
Subject: Re: [Project Name] — two items outstanding
Hi [Name],
Following up on the access requests from Monday. We're still waiting on:
- Google Analytics (Editor role to team@youragency.com)
- Meta Business Suite (Editor access)
Once we have these, we can start the audit and have preliminary findings to you by [date]. No action needed on the others — just these two to unblock us.
Best,
[Your Name]
Name what's missing. Name the impact. Make it easy to reply to.
Day 7: The timeline impact email
If you've heard nothing by day 7, the tone changes slightly. This is not aggressive — it's factual:
Subject: Re: [Project Name] — updated timeline note
Hi [Name],
We're 7 days into the project and still missing [specific items]. I want to be transparent: this delays the start of [deliverable] from [original date] to [new date].
If there's something on your end that's making this difficult — IT approval, the right person to ask, or something else — let me know and we'll figure it out together.
If it's easier, I can jump on a 15-minute call to walk through access sharing. Available [specific times].
[Your Name]
This email does three things: states the timeline impact factually, offers help rather than blame, and provides a call as an easy off-ramp.
Day 10: The decision-point email
If you still haven't heard back by day 10, you need to create a decision point:
Subject: Re: [Project Name] — decision needed
Hi [Name],
I've reached out a few times about access for [project]. At this point, I want to check in to make sure everything is still on track from your end.
Can you give me a quick status by [date]? Even a one-line reply helps us know whether to hold, adjust the timeline, or get on a call to sort something out.
If I don't hear back by [date], I'll follow up with [specific next step — e.g., contact the secondary stakeholder you listed in the intake form, or reschedule the kickoff].
[Your Name]
The phrase "I'll follow up with [specific next step]" creates a consequence without being threatening. It signals that you have a process and you'll follow it.
What to do when there's still no response
At this point, you have four options:
Option 1: Contact the secondary stakeholder. If your intake form captured a second contact, use it. A brief, neutral message: "Hi [Name], I've been trying to reach [primary contact] about [project] and haven't heard back. Are you the right person to connect with about getting started?"
Option 2: Call instead of email. Some clients respond better to a phone call. A quick, low-pressure check-in that assumes goodwill rather than avoidance is often enough to break the silence.
Option 3: Pause the project formally. If you've made multiple reasonable attempts and received no response, send a project pause notice. Not a threat — a factual statement: "We've been unable to reach you for [X days]. We're pausing the project timeline until we hear back. Please contact us when you're ready to proceed."
Option 4: Review your contract terms. If silence continues beyond a reasonable window (typically 14-21 days for onboarding delays, depending on your contract), review what your contract says about project abandonment, milestone-based billing, and timeline extensions. Don't ignore this step.
The systemic fix: prevent this in the first place
Most client silence during onboarding is preventable. A solid onboarding system removes the ambiguity that causes it.
Set expectations before you need access. Your welcome email should include a note: "To start on schedule, we need the items below within 48 hours. If any require IT approval or coordination on your end, let us know now so we can build that into the timeline."
Build a pre-onboarding call into your proposal process. A 30-minute "kickoff prep" call within 24 hours of signing — before you send any access requests — creates momentum and identifies blockers before they become silences.
Track access status in a shared doc. When your client can see exactly what's outstanding, they're more likely to move on it. Something as simple as a shared Google Sheet with columns for "Access needed / Status / Who's responsible / Due date" is enough. Clients who can see the status don't need to be chased — they update it themselves.
Make responding easy. Long, dense emails are easy to close and forget. Short emails with one clear ask and instructions for how to act are harder to ignore.
The right frame for handling client silence
Client silence during onboarding feels personal. It rarely is.
The most effective way to handle it is to be factual about impact, specific about what's needed, and consistent about following a process. Agencies that have a documented response sequence — day 1, day 3, day 7, day 10 — handle this far better than those improvising each follow-up. Because they don't second-guess when to send the next email, or how firm to be, or whether to escalate.
The sequence exists. They follow it. The client either responds or gets a pause notice.
That's not cold — it's professional. And professional is exactly the impression you want to make in the first two weeks.
If you want the full access request sequence, follow-up templates, and onboarding tracker as a ready-to-use system, Agency Onboarding OS has it all packaged with 38 practical docs for small agencies.
Top comments (0)