How to respond when a prospect asks to be removed
What to say when someone on LinkedIn asks you to stop messaging, how to remove them from every list, and how to keep a report off your account.
Get startedShort answer
Reply once, confirm the removal in the first sentence, and stop. Don't ask why, don't offer one more resource, and don't send another follow-up. Then take them out of every list and campaign you own so nothing else reaches them.
Why an opt-out request is not a sales objection
A message that says 'please remove me' is an instruction, not an objection you can work through. The person has told you what they want. The only job left is to do it quickly and get out of their inbox. Every sentence you add after the confirmation reads as an argument.
The practical reason to move fast is your account. Every LinkedIn member has a report button, and people who feel ignored reach for it. LinkedIn doesn't publish how many reports trigger a review, so treat each opt-out as the one that could. A restricted account costs you weeks of outreach. One lost lead costs you a lead you had already lost.
There's a second cost that's harder to see. Your reply is the last thing that person will associate with your name. If they change roles in a year and need what you sell, they'll remember whether saying no was easy or whether they had to say it three times. People who ask to be removed sometimes come back, and they come back to whoever didn't make it awkward.
None of this means you did something wrong by messaging them. Cold outreach gets nos. The mistake is treating a no as a negotiation.
Trying to save the sale
- I understand, but can I send one short video first?
- No problem, but can I ask what put you off?
- Happy to remove you. Before I do, is the timing just bad?
The clean exit
- Understood. You're removed. All the best.
- No problem, I've taken you off the list.
- Apologies. You're removed and you won't hear from me again.
Rules for the reply itself
The reply has one job: close the loop so the person stops feeling chased. Anything you add after the confirmation works against that, including the friendly line you're tempted to tack on the end.
Write it yourself the first few times. Templates drift into sounding like templates, and someone who just asked to be left alone can tell when the reply came out of a file. Once you have a version that reads like you, save it and stop rewriting it.
Length is the tell. Two lines say the request was routine and handled. A paragraph says you had to think about it, which makes the person wonder what you're deciding.
- Confirm the removal in the first sentence, not the last.
- Keep it to two sentences at most.
- Match their tone. Blunt gets plain, polite gets warm.
- Skip the apology paragraph. 'Sorry to bother you' admits you knew the message was an intrusion.
- No links, no attachments, no calendar.
- No emoji and no exclamation marks.
Never ask why. A question turns your exit into another thing they have to answer, and an unanswered question is exactly what pushes someone toward the report button.
What to do after you hit send
The reply ends this conversation. The cleanup stops the next one, and the next one is where people get reported.
Most opt-outs happen inside a sequence, which means something is almost always already scheduled for that person. Find it before you close the tab.
- 1
Send the confirmation the same day
Same hour if you can. A delay reads as 'he's deciding whether to honour it'.
- 2
Cancel anything queued for that person
Open the campaign and check for pending follow-ups and scheduled messages. A message that lands tomorrow undoes your reply.
- 3
Pull them out of the list the campaign points at
If your leads live in groups or segments, remove the lead from the group, not just from the thread.
- 4
Add the profile URL to a do-not-contact file
One sheet, one column of URLs, checked before every import. Keep it somewhere you'll actually open.
- 5
Decide about the connection
Keep it if the request was polite. Remove it if they were hostile or if you don't trust your own lists to leave them alone.
Paste this job
profile_url,date,reason linkedin.com/in/dana-reyes,2025-03-04,asked to be removed linkedin.com/in/marcus-hale,2025-03-11,asked twice
The follow-up that was already queued
Most opt-outs land in the middle of a sequence. You reply, close the tab, and the third follow-up you wrote two weeks ago sends itself the next morning. That second message is the one that gets you reported, because now you've broken a promise you made in writing.
The recovery is the same every time. Name what happened, don't blame the tool, confirm that nothing else is scheduled, and then actually check that it's true. People forgive a queued message. They don't forgive being told it's handled when it isn't.
If your setup can't cancel a message for one person, pause the whole campaign until you've checked it. Pausing costs you a day of sending. A report costs you the account.
This is also why the confirmation should be specific. 'You're removed' is a promise. 'I've taken you off this sequence and cancelled the follow-ups' is a promise you can keep and they can verify.
Example
- You
Hi Dana, I work with agencies on their outbound and had a question about how yours is set up.
- Prospect
Please take me off your list.
- You
Done, you're removed. Sorry for the interruption.
- Prospect
I thought you said you removed me.
- You
You're right, and that was a message already scheduled before your reply. It's cancelled now and nothing else is queued. Sorry.
When 'not now' is not an opt-out
'Not right now' and 'we already have something in place' are information. 'Remove me' and 'stop messaging me' are instructions. Treating the first pair like the second throws away leads you spent time finding.
The test is whether they told you to stop or told you why the timing is wrong. A stop gets the removal reply. A reason gets one short acknowledgement and then a long silence.
Silence does more work than it looks. A prospect who says 'not now' and gets a two-line reply with no pitch attached has a reason to remember you when the contract comes up. A prospect who gets three check-in messages has a reason to block you.
There's one exception worth planning for. If someone says 'remove me' and asks a question in the same message, answer the question in one line and remove them. Don't treat the question as permission to keep the thread alive.
Pushing after a soft no
- Totally understand. Can I check back in two weeks?
- What would need to change for this to be a priority?
- I'll send one more thing so you have it on file.
Leaving the door open
- Makes sense. I'll leave it there.
- Fair enough. Good luck with the quarter.
Doing this with Kinlead
Replies from every campaign land in one unified inbox, sorted by intent with interested replies first, and you get an email when someone replies. A 'remove me' is easy to catch before it turns into a report.
Set the campaign to hand off at the first reply and the AI stops talking the moment someone answers, so your confirmation is the only message they get from you. Then remove the lead from the group that campaign points at, so nothing else reaches them. Kinlead has no separate do-not-contact list, so keep that sheet yourself and check it before you import a CSV of profile URLs.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to respond when a prospect asks to be removed.md