Sent Video Link to Wrong Person? How to Shut It Down in Five Minutes
I've pasted a confidential cut into the wrong chat too. This is the five minute playbook I use to kill the link, check who watched, and reset things with the client.
Most video teams handle a link that went to the wrong person with a quick "please ignore that" message and a whole lot of hoping, right, and that's the uncomfortable truth about how this niche deals with it. I've sent a video link to the wrong person myself, a confidential cut pasted into the wrong chat because two client groups sat next to each other in my list, and my first instinct was to type an apology and get straight back to the edit.
The catch here is that hoping only works until the one time it doesn't, and when the video is an unreleased launch film or a campaign still under embargo, one curious tap can cost you more trust than the whole project is worth. So over time I stopped treating it as an embarrassing moment and started running it like a small incident, with a sequence simple enough that I can do it half asleep.
That sequence is basically four moves done in about five minutes, where you kill the link, check whether anyone actually opened it, send a fresh protected link to the right person and then tell the client honestly. I'll show you how each move works inside PlayPause, since that's what my agency runs its client reviews on.
The first five minutes after sending the wrong link
The order you do things in matters really really a lot more than people think, right, because the natural reaction is to message the wrong recipient first and write a long careful explanation, and all of that burns minutes while the link is still live and still forwardable. For instance, say a producer on your team drops the MV3 of a product launch video into the email thread of a different client. Somebody in that office taps the thumbnail out of pure curiosity, and your window for a clean fix shrinks with every minute you spend drafting.
So the rule I follow is simple, the link dies first and every conversation happens after, because once the link is dead, forwarding it achieves nothing. Email tricks don't really save you here, since Gmail's undo send gives you thirty seconds at most and message recall in most corporate mail setups is unreliable at best, so I go straight to the thing I actually control, which is the link itself.
A worked example, minute by minute
Let me put real times on it, right, so you can see how tight this gets. Say the wrong link goes out at 3:10 and I spot it at 3:13 when the wrong client replies with a confused emoji. By 3:14 the link is revoked, by 3:15 I've checked the who-watched record, by 3:16 the right person has a new password-protected link with the password on its way over WhatsApp, and by 3:18 the client whose cut it is has a short note from me.
I'm pretty sure most people underestimate how quickly chat apps help a mistake along, because WhatsApp groups, Slack threads, email clients and so on turn a pasted link into a big friendly preview card that basically invites a tap. The playbook also depends on the cut living behind a link, since an attached file can't be pulled back once it lands, which is one more reason my team moved to sending a browser link instead of raw files. And if the link came from a general cloud drive, the same principle holds, you switch link access off on that file before anything else.
How to revoke link access instantly
In PlayPause, instant link revoking is on every plan, so the first move takes seconds, right, you open the project, find the share link you sent and revoke it. From that moment the link stops working for anybody who has it, including anyone the wrong recipient already forwarded it to. Nobody should be searching how to disable a video share link or cancel a shared link at eleven at night with their heart racing, and to be very honest that's the whole point of having revoke sitting right there on the link.
Revoking doesn't touch your footage either, because PlayPause plays reviews in the browser from a streaming copy, so the Apple ProRes master you exported sits untouched and your version stack stays where it was. And since clients comment without an account, the link basically is the access, so closing the link closes access and the fix stays really clean.
Revoking stops the link working for everyone from that moment on. It cannot undo a view that already happened, which is exactly why you check the analytics next.
This is the same move I use when someone leaves the team, and I wrote up the longer version of revoking access when a contractor leaves, because at the end of the day both are the same problem with different emotions attached. If you want everything the sharing side of the product covers in one place, our sharing and security page lays it all out.
a please ignore message, a lot of hoping, and no idea who saw the cut
the link is revoked in seconds and you can see whether anyone opened it
Checking whether anyone opened it and from where
Once the link is dead, the next question is the one your client will ask anyway, right, did anybody actually see it. This is where who-watched analytics comes in, which is on Creator and up, and it shows you who opened a link, when they opened it and from which city, so you're looking at an actual record instead of guessing. I've written a full walkthrough on seeing who watched your video if you want the detail, but for incident response I only look at a few things.
First I check whether there are any views at all between the moment the link went out and the moment I revoked it, because if that window is empty you got lucky, and you can tell your client that plainly. Then I look at timing, since a single view two minutes after sending, from the city where the wrong recipient's office sits, usually means one person tapped the preview out of curiosity and moved on.
Geography is the one that tells you whether it travelled, right, because a view from a city that has nothing to do with the wrong recipient suggests the link got forwarded before you killed it. I hold that loosely, since city level location on any analytics tool is approximate and a VPN can easily put someone a city or two away. Analytics also only records opens, so it can't tell you what someone thought or whether they recorded their screen, and I call it the best record we have without dressing it up as proof that nothing happened, does that make sense, right.
Sending a fresh password-protected link to the right person
Now you still owe the right person their cut, so I create a brand new link rather than reusing anything, and for anything confidential I make it a password-protected link, which is on every plan. The small habit that matters here is sending the password through a different channel than the link, so if the link goes by email the password goes by WhatsApp or a quick call, and one misdirected message on its own is never enough to open the video. I've got a full guide on how to password-protect a review link if you haven't set one up before.
For the right person the new link works the way a review link should, they open it in a browser with no account and no install, their comments stick to the exact frame and they can draw on the frame. When you push the next version it stacks on the same card as MV4, so nobody gets confused about which cut they're looking at. If your editors cut in Adobe Premiere Pro, those notes land inside Premiere through our Premiere Pro panel, and if your team is new to review links, my walkthrough on uploading a video for client review covers the basics.
Link lifetime is worth a thought at this point too, right, because a link that lives forever is a link that can go wrong forever. On Creator, links and files expire after 30 days, on Agency links last 90 days, and on Enterprise links never expire, which is why the revoke habit matters most there. You can read more about how expiring share links work if you want to plan around those windows.
What to tell your client, and when
This is the part most people skip, and to be very honest it's the part that decides whether the client still trusts you next month, right. In my experience clients forgive the mistake itself quite quickly, and what really really hurts is finding out about it later from someone else. So my rule is that the client whose content went astray hears about it from us within the hour, even if the analytics showed zero views, because a short honest note costs a bit of pride and saves the relationship.
A client forgives a wrong link far faster than they forgive hearing about it from somebody else.
The note covers what happened, when you revoked the link, what the who-watched record showed and what you've changed so it doesn't repeat. Something like this works for me: "Quick heads up, at 3:10 today we sent the review link for your launch cut to the wrong contact by mistake. We revoked it at 3:14, and our viewing record shows one open before that. We've sent you a new password-protected link and added a recipient check to our sending routine. Happy to talk it through on a call." There's no drama in it and no grovelling, it's basically a status report written by a human being.
For the wrong recipient, keep it light, a one line message asking them to disregard the link and not forward it, plus a thank you, because making a big deal of it tends to make people more curious. If the content sits under a real embargo, bring in whoever owns legal or communications on the client's side, and teams that live with that pressure every day will find our page for corporate communications teams a useful reference.
Habits that make the wrong link less likely
I've covered prevention elsewhere, including how we go about keeping a draft from leaking before launch day, but a few habits came straight out of cleaning up these incidents in my own agency. The biggest one is making password protection the default for anything confidential, right, so that even when a link goes to the wrong place, it arrives locked.
The second is a small pause before pasting, and in my agency we write the client name and version number in the message just above the link, so if the name doesn't match the chat you're in, you notice before you hit send. We also agreed that only the account manager on a client sends that client's review links, which is a people rule rather than a software setting, and it keeps the circle of senders small.
On Agency and up, Playbooks help as well, because a folder playbook can carry a checklist that isn't done until it's ticked, so "confirm recipient and password" can sit on the checklist for every confidential folder. The brand playbook then holds the permanent rules for that client, like whether anything leaves without a password at all.
- Password on by default for confidential cuts
- Password sent on a separate channel
- Client name and version written above every link
- Recipient check ticked in the folder playbook
- Who watched record checked after every send
Frequently asked questions
Can I undo a video link I already sent to the wrong person?
You can't unsend the message itself, right, but you can make the link inside it useless. In PlayPause, instant link revoking is on every plan, so once you revoke it the link stops working for everyone who has it, including anyone it was forwarded to. Then you create a fresh link for the right person, ideally password-protected, and the video and its version stack stay exactly where they were in your project.
Does revoking a link delete my video?
No, revoking only closes that one link. PlayPause plays reviews from a streaming copy and leaves your original upload untouched, so the footage and the version stack stay put. I think of it as changing the lock on one door rather than knocking the house down, and that's why I never hesitate to revoke first and ask questions after.
How do I know if the wrong person actually watched it?
Who-watched analytics, which is on Creator and up, shows who opened the link, when, and from which city. I compare the view times against the moment I revoked the link, and I check whether any city looks out of place, since that hints the link was forwarded. It records opens and nothing more, so I share what it shows with the client plainly.
Which PlayPause plan do I need for this playbook?
Revoking links and password-protected links are on every plan, and who-watched analytics comes with Creator and up, where Creator is $9 a month for a workspace with 10 members, so it already covers the full five minute playbook. Agency at $19 a month adds Playbooks for the checklist habit, and Enterprise at $27 adds a custom share domain, with pricing flat per workspace rather than per person.
Should I tell the client even if nobody opened the link?
I always do, in two or three lines, because the client would rather hear that we caught it, revoked it within minutes and nobody opened it than find out some other way later. It shows you run a proper process around their material, which at the end of the day is a big part of what they pay you for.
If you'd like this whole playbook ready before you ever need it, take a look at PlayPause pricing and start the 7-day free trial on whichever plan fits your team, and trust me on any level, the first time you revoke a wrong link in ten seconds you'll be glad you set it up on a calm day.
So yeah. That's my way of saying it.
Saumyajit co-founded PlayPause after years watching review and approval quietly eat creative teams' deadlines. He writes about the workflow side of video, feedback, versioning, and getting to a clean sign-off.
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