How to Get a Client to Respond When They've Gone Silent on Your Cut
A proven follow-up cadence for chasing a silent client through video approval, with scripts that get replies without sounding pushy or desperate.
You sent the cut on Tuesday. It's now Friday, the client has read the email (you can see the little "opened" timestamp if you're using something better than plain email), and there's nothing back. Not a "looks great," not a "few notes coming," not even a "still watching, give me till Monday." Just silence, and you're left wondering whether you should follow up again or whether that makes you look needy. Sound familiar? We hear this from editors and producers constantly, and it's one of the most common reasons projects stall out even after the hard creative work is already done.
Why Clients Actually Go Quiet at the Approval Stage
The instinct is to assume the client hates the cut and is avoiding the awkward conversation, but in our experience running review workflows for hundreds of teams, that's rarely what's happening. Most of the time the client just got buried, your video became one tab among forty open browser tabs, and there was no clear next action attached to it. They watched it on their phone during a commute, meant to come back to it at a laptop to leave real notes, and then three other fires showed up. The video itself isn't the problem, the lack of a forcing function is.
There's also a structural issue at play. When feedback lives in an email thread or a shared Drive folder, the client has to remember where the video even is, dig up the link, and then figure out how to leave a comment that makes sense (timestamp in the subject line? a separate doc?). Every one of those small frictions is a reason to put it off another day. This is exactly why we built PlayPause around a single link that always points to the current version, with comments pinned to the actual frame, because removing friction removes excuses.
In most cases a quiet client is a distracted client, not a dissatisfied one. Your follow-up should read as helpful, not accusatory.
The Follow-Up Cadence That Doesn't Feel Like Nagging
The mistake we see most often is either following up too aggressively (daily emails starting on day one) or not at all until the deadline has already blown past. Neither works. What does work is a cadence that escalates gently and always gives the client an easy way to respond in ten seconds or less.
Notice that none of these are "just checking in" with nothing else attached, because that phrase alone rarely gets a reply. Each touchpoint gives the client something concrete to react to, whether that's a deadline, a specific question, or an offer to jump on a five-minute call. At the end of the day, people respond to specificity a lot faster than they respond to vague nudges.
Why Email Threads Make the Silence Worse
If you're chasing feedback through a fifteen-reply email chain, you're fighting an uphill battle before you've even sent your first nudge. The client has to scroll to find the original video link, they can't tell which version is current, and half the time your follow-up gets buried under an unrelated reply-all. We've watched this happen on real projects, agencies losing three or four days purely to "wait, which cut are we even looking at" confusion.
Feedback scattered across email, Slack DMs, and text messages, no single source of truth for which version is current
One shareable link, timestamped comments, a visible status showing exactly who has and hasn't reviewed the latest cut
This is also where a client review portal earns its keep. Instead of a client hunting through their inbox, they get one bookmarkable place that always shows the newest version, and you get visibility into whether they've actually opened it. That visibility alone changes how you word your follow-up, because "just checking you got this" turns into "saw you opened it Tuesday, any notes so far" and that's a completely different, much less awkward message to send.
Writing a Nudge That Doesn't Sound Desperate
The words matter here almost as much as the timing. A follow-up that says "hey just floating this back to the top of your inbox" reads as apologetic, like you're sorry for taking up their time. A better version assumes competence and gives a reason tied to the project itself, not to your own anxiety about getting paid or getting the timeline back on track.
A deadline attached to a reason lands very differently than a deadline attached to nothing.
Try something closer to: "Wanted to flag that we're holding the edit slot through Thursday to keep the launch date intact, happy to jump on a quick call if anything in the cut needs discussion first." That's specific, it's not pushy, and it gives the client an easy out (the call) if the real issue is that they don't know how to articulate their notes. We go deeper on exactly this kind of consequence-backed deadline in how real deadlines stop endless revisions, which pairs well with the follow-up cadence above.
We've also watched the offer-a-call line perform noticeably better when it removes even the tiny friction of picking a time, attaching a direct scheduling link (a simple Calendly slot works fine) instead of asking the client to reply with their availability. That one change, dropping "happy to jump on a call" for "here's a link, grab whichever fifteen minutes works," lifts the reply rate on that specific line meaningfully in our own testing, because you've turned an open-ended offer into a single click instead of another decision the client has to make.
Matching the Nudge to the Client Type
Not every quiet client needs the same message, and treating a busy marketing director the same way you'd treat a first-time solo founder tends to backfire. A corporate stakeholder juggling five vendors usually just needs the deadline restated plainly, because they're not avoiding you, they're triaging. A first-time client, on the other hand, might be quiet because they genuinely don't know how to give useful feedback on a rough cut and feel embarrassed about it, so a nudge that offers a short call to "walk through it together" tends to unstick them faster than another written reminder ever will. Reading which situation you're in before you hit send saves you a round of guessing.
When Your Contact Is Waiting on Their Own Boss
Sometimes the silence has nothing to do with your video at all, it's that the person you're emailing loved the cut, forwarded it internally, and is now sitting exactly where you are, waiting on someone else to respond. This shows up constantly with agency accounts, where the person managing your project is really just a relay between you and their own client, and they can't give you real notes until their client gives notes to them. If you suspect this is what's happening, it's worth asking directly rather than guessing, something like "just so I can plan the schedule, is this still moving through approval on your end, or are you waiting on your own client to weigh in." That question does two things at once, it signals you understand their situation isn't necessarily in their control, and it usually gets you a straight answer about where the actual bottleneck sits, which is often a different fix entirely than another nudge to the same inbox.
When to Loop In a Second Contact
Sometimes the person you're waiting on genuinely isn't the final decision-maker, or they're sitting on the video because they're waiting on their own boss. If you've sent two or three nudges with no response, it's usually fine to loop in whoever brought you onto the project in the first place, framed as a scheduling question rather than a complaint. "Wanted to make sure this doesn't slip past our delivery window, is there anyone else who should weigh in on the cut" does the job without throwing anyone under the bus.
Numbers like that are consistent with what teams tell us when they switch from open-ended review windows to structured ones, and it tracks with broader research too. Wyzowl's video marketing statistics has repeatedly found that businesses cite turnaround and internal alignment, not creative disagreement, as the biggest source of delay on video projects, which matches almost exactly what we hear from the teams using PlayPause.
Building Urgency Without Being Pushy
One underrated tactic is making the review link itself feel time-bound rather than open-ended. If a client knows a link never expires and the video will just sit there forever, there's no cost to putting it off. Expiring share links create a soft, non-confrontational deadline baked right into the tool instead of you having to be the bad guy in every follow-up email. Pairing that with a real kickoff conversation up front, something we walk through in how a kickoff call prevents revision spirals, means the client already knows the review window is finite before you ever have to chase them.
- Attach a specific date and a specific reason to every nudge
- Give the client one clear action, not three
- Use a tool that shows read receipts so your follow-ups reference reality
- Offer a call as an escape hatch for clients who are stuck, not stalling
- Loop in a second stakeholder after two unanswered nudges
What We Built Into PlayPause for Exactly This Problem
We built this because we kept hearing the same complaint from freelance editors and small agencies: chasing sign-off eats more hours than the actual edit. So the platform shows you exactly when a client opened a version, lets you leave a note directly on a frame instead of a vague "see attached," and keeps the whole approval history in one thread so nobody has to ask "wait, did we already address this note." It replaces the twelve-email approval dance entirely, which is also why teams moving off a tool like PlayPause vs Frame Io tell us the client-facing side alone is worth the switch.
What This Looks Like on a Real Timeline
Say you're a two-person shop delivering a 90-second brand video with a three-round revision cap written into the scope. You send round one on a Monday, and by the following Monday you've heard nothing. Under the cadence above, you'd have sent a light check-in on Wednesday, a specific nudge referencing the following week's shoot date on Saturday, and by the second Monday you'd be offering a call rather than sending a fourth cold email into the void. In our experience that's the point where most clients either respond within the day or reveal that the real holdup is a stakeholder who hasn't seen the cut yet, which is useful information either way, because now you know what you're actually solving for instead of just guessing at silence.
The pattern holds at the other end of the spectrum too. A solo wedding videographer we talked with sends a single client one four-minute highlight film with a two-round cap and no committee involved at all, and even there silence shows up constantly, usually because the couple is mid-honeymoon or buried in thank-you cards and simply forgot the video existed until a nudge landed referencing the album delivery date tied to it. Same cadence, same specificity, completely different context, which is really the point, the fix isn't about company size or project budget, it's about attaching a real reason to the ask every single time.
Getting the Next Cut Answered Faster
Silence at the approval stage is rarely about the work, it's almost always about friction and missing urgency, and both of those are fixable with the right cadence and the right tool sitting underneath it. If you're tired of guessing whether a client has even watched your latest cut, see how PlayPause turns a vague follow-up into a five-minute reply.
Akash N. writes about post-production and editorial workflow for PlayPause. He focuses on version control, side-by-side compare, and the handoffs between edit, color, sound, and VFX that decide whether a cut ships on time.
Related resources
Keep reading
Bring your team into one review space
Centralize feedback, lock approvals, and deliver faster, start free today.
Sign Up for Free