Notes / Approvals / 4 min read
When the client goes quiet
WhizSuite · 2026-10-22
A client who vanishes on approval day is a scheduling problem you can write down before it happens.
Pick a rule before you need it
You have three honest options. The post waits. The post publishes on a pre-agreed "no reply means yes" rule. Or the post is replaced by something already approved. Pick one in the contract. Do not invent it in the group chat at 6pm.
"No reply means yes" only works if the client agreed while they were calm, and if the version they ignored is the version you send. It is a sharp tool. Use it on routine posts, not on a new offer.
One nudge, then the rule
Send one clear reminder with the date, the file, and the consequence. A stack of "just bumping this" messages trains people to ignore you. The reminder should fit in a few lines and include the link again.
Copy the named approver, not the entire company. More inboxes do not create more courage. They create more places for the link to sink.
Do not fill the hole with guesses
Swapping in a different creative because you are embarrassed by an empty day is how you publish unapproved work. An empty slot is cleaner than a surprise. Tell the client the slot moved.
If this happens every month, the fee or the calendar is wrong. Slow approvals are scope. Price the waiting, or reduce the number of posts that need a fresh yes.
Keep a record of the wait
Note when you asked and when you nudged. You will need it when someone asks why a week looked thin. The record also shows whether the bottleneck is your delivery or their reply.
Bring that pattern to the quarterly conversation. "We lost four posts to a six-day reply" is a useful sentence. "Engagement was down" is not, if the posts never left the building.