What to send when a new client stops replying
Stop the onboarding ghosting cycle with specific scripts. How to move a signed B2B client from silence to active delivery using low-friction nudges.
Get startedShort answer
When a client goes quiet during onboarding, stop asking for their time. Send a piece of finished work or one blocker question they can answer in ten seconds, then give them a default so doing nothing still moves the project forward. If two weeks pass, send a pause notice that gives them permission to stop.
Why clients go quiet after signing
The silence usually starts a few days after the contract is signed. During the sales conversation the client had a reason to show up: they were deciding something. Once the decision is made, your project becomes one more item on a list that already includes their actual job.
Founders read that silence as regret. Most of the time it's admin. The client still wants the result. What they don't want is another document to read, another call to schedule, or another portal login to set up before anything happens.
There's a guilt loop too. The longer they leave it, the more awkward a reply feels, so they leave it longer. Your messages have to make replying cheaper than staying quiet.
The clients who ghost hardest are often the ones who were most enthusiastic on the sales call. They said yes early, skipped the details, and now have to make decisions they didn't think about. That's not a lost account. It's an unfinished handoff.
High-friction requests
- Can we jump on a 30 minute call to walk through the onboarding document?
- Let me know when you have some time this week to sync on next steps.
- Just checking in to see if you've had a chance to look at the portal.
- Following up on my last email in case it got buried.
Low-friction requests
- I've drafted the month one roadmap. Is the main goal still more demo bookings, or has that changed?
- I can start setup today. Should I pull the logo from your website or do you have a hi-res file?
- I'm blocked on step 3 until I have the API key. A one-line reply with the key is enough.
- I've put the kickoff in for Thursday at 10. If that's wrong, send a better time and I'll move it.
The first nudge: show work instead of asking for time
Send the first nudge within two business days of signing, before the silence gets comfortable. Attach something real: a draft plan or a first pass at the setup. The point is to show the project is already moving without them.
If you have nothing built yet, send the plan for what you'll build. A short outline with dates is enough. The client needs to see a next step that isn't theirs.
Then ask for one confirmation, not a meeting or a document review. If the client can reply 'yes, that's right' from their phone in a lift, you'll get a reply that day.
Don't open with an apology. 'Sorry to bother you again' makes the delay the subject of the message and invites an explanation instead of an answer. Say what you've done and ask the one question.
Example
- You
Hi Sarah, I've drafted the month one roadmap from our sales calls. I need one confirmation before I finalise it: is the main goal still more demo bookings, or has that shifted?
- Prospect
Yes, that's exactly it. Sorry for the delay, it's been a mad week.
- You
No problem. I'll finalise the roadmap today and send the kickoff invite for Thursday. Nothing needed from you until then.
The second nudge: a question they can answer in ten seconds
If the first nudge gets nothing, wait three business days and change the shape of the ask. The client probably read it. It looked like it needed ten minutes they didn't have that afternoon.
Pick one thing that is genuinely blocking you. A logo file, an API key, a choice between two options, the name of whoever signs off content. Ask about that and nothing else.
Give them a default. 'If I don't hear back by Thursday I'll go with the shorter option' works because it lets them do nothing and still move forward. People correct a wrong default faster than they answer an open question.
- 1
Wait out the gap
Three business days, no messages. Chasing sooner makes the second nudge feel like pressure rather than progress.
- 2
Name one real blocker
Something that actually stops your next task. If you can finish the work without them, finish it and tell them you did.
- 3
Offer a default
Say what you'll do if you hear nothing. The default should be reversible and cheap for them to correct.
- 4
Stay on one channel
Send it where the client already talks to you. If the deal ran through LinkedIn messages, don't switch to email for the nudge and make them hunt for context.
Never ask whether they saw your last message. They did. The question turns a small delay into something they have to admit.
The third nudge: give them permission to stop
Two weeks of silence needs a different message. By then the client is avoiding you because replying means admitting they dropped the ball, and every normal follow-up makes that worse.
The message that works gives them an exit. Say you're pausing, say why, and leave the door open. Replies often come within the hour, because you've removed the thing they were dreading.
Don't soften it into a check-in. 'Just floating this back to the top of your inbox' keeps the ball in their court, which is exactly where it's been stuck for two weeks.
Mean it when you send it. Actually pause the work, stop the clock on any timeline you promised, and write the date in the account notes so whoever touches the account next knows why it's quiet.
Paste this job
Hi Sarah, I haven't heard from you since the kickoff, so I'm going to pause the onboarding and free up the slot. Nothing is lost: the roadmap and the setup work are saved. When the timing is better, reply here and I'll restart within a day or two. If someone else on your team should own this, send me their name and I'll reach out to them instead.
What to do when they reply, and when they don't
When the reply lands, don't dump the backlog on them. Pick the single next action, do the part you can do alone, and ask for one thing. Keep the first reply small so there's a reason for a second one.
If they apologise, take it once and move on. 'No problem, here's where we are' is the whole response. Long reassurances make the delay bigger than it is.
If they come back with 'let's push this to next quarter', get a date and a trigger. 'Fine, I'll come back to you in the first week of April, or sooner if the new hire starts before then' beats an open-ended 'whenever you're ready'.
If nothing comes back after the pause message, put a real date in your calendar three or four weeks out and stop messaging until then. Weekly check-ins on a paused project are how a delay turns into a lost account.
First nudge
- Nudge
- Within two business days of signing
- When to send
- A real draft or the plan for one
- What it contains
- One confirmation that the direction is right
Second nudge
- Nudge
- Three business days later
- When to send
- One specific blocker and a default answer
- What it contains
- A ten second reply
Third nudge
- Nudge
- About a week after that
- When to send
- A pause notice with the door left open
- What it contains
- Either a restart or silence
Reactivation
- Nudge
- Three to four weeks later
- When to send
- Something new: a result, a change, a trigger
- What it contains
- A restart date or a short call
Fix the handoff so the silence stops happening
Most onboarding ghosts are created in the last ten minutes of the sales call. The client says yes, everyone is pleased, and nobody agrees what happens next or who does it.
Before the call ends, get four things and repeat them back:
- The first step in plain language: 'we need your product feed and 20 minutes with whoever runs paid'
- The date that step happens, not 'early next week'
- The person on their side who owns it, by name, who may not be the person who signed
- What you'll do in the meantime, so the client isn't the only one holding the project up
The internal owner matters more than the kickoff date. If your contact has to borrow time from three other people, the project stalls the first week they get busy.
Doing this with Kinlead
If your clients come from LinkedIn, Kinlead can keep the nudges moving without you watching the clock. Import a CSV of profile URLs for signed clients into their own lead group, so onboarding messages never mix with prospecting.
Build a campaign that points at that group and put your nudge scripts in the sales playbook. Kinlead sends at most one action every five minutes per account, inside the daily limits and send window you set, so a quiet client gets a normal-looking message rather than a burst.
Set the campaign to hand off at the first reply and the conversation lands in your inbox alongside everything else, classified by intent. You can book a demo to see it on your own account.
What to send when the client comes back
The reply after a long silence is usually short and slightly embarrassed. Match the length. A three line reply that says where things stand and what happens next is easier to answer than a full recap of everything they missed.
Give them the state of the project in one sentence, then the next action with a date, then stop. If you need something from them, ask for it in that same message rather than opening a second thread.
Over-explaining the gap
- So as you know we had the kickoff booked, then it moved, and I sent two follow-ups, and the roadmap has been sitting ready since the 14th, so there's quite a lot to catch up on.
- No worries at all, honestly it happens all the time, don't worry about it, I completely understand, these things are always busy.
- I'll send over the full onboarding pack again so you have everything in one place.
Short and forward-looking
- Roadmap is done and the feed is connected. Next step is your call with Priya on Thursday. I'll send the invite now.
- Nothing lost. I'll restart setup today and you'll have the first report by Friday.
- One thing I still need: the API key. Everything else is moving.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? What to send when a new client stops replying.md