How to respond to no thanks on LinkedIn
Turn reflexive LinkedIn brush-offs into real conversations. Scripts for too busy, already have a tool and not interested, plus when to walk away.
Get startedShort answer
Stop treating a no thanks as a closed door. Most LinkedIn rejections are reflex brush-offs sent to clear a notification. Acknowledge it and ask one specific question, and you'll find out whether the no was real.
Why the first no is usually a reflex
Most people read LinkedIn on a phone between other things. A pitch lands, they tap not interested to clear the notification, and they go back to what they were doing. That tap is about the interruption. It says nothing about your offer.
A real no rests on a fact. They signed with a competitor last quarter, hiring is frozen, the project that needed you got cancelled. A reflex no rests on nothing. Your second message exists to find out which one you got.
You can usually tell within one reply. Reflex nos come back fast, often within minutes, and they're short. Real nos come back slower and usually carry a reason, even a vague one.
If it's a real no, you stop and you've lost a minute. If it's a reflex, the reply you get back is the first honest sentence of the conversation. That's the whole reason to follow up once, and only once, before you decide.
The reflexive response
- But our tool saves teams 10 hours a week!
- Are you sure? Just 15 minutes of your time.
- I understand, but I think you'd really like this one feature.
The pattern interrupt
- Fair enough. Is it a bad time, or is this not a priority for the team right now?
- No problem. Do you already have a process for this, or is it not a focus?
- Makes sense. Most people I talk to are buried in Q3 reporting. Is that the case for you too?
Handling the too busy brush-off
Too busy means their current load is heavier than the value they see in your offer. Asking for a meeting adds to the load, which is why the calendar link usually ends the thread.
Guess the reason out loud instead. Naming something specific, like a hiring push or a board audit, gives them something to correct, and people would rather correct you than explain their calendar to a stranger.
Then stop. One question, no ask, no link. If they correct you, you've got a real problem to talk about. If they don't reply, you've lost nothing.
The guess has to be plausible for their role. A head of sales is probably wrestling with pipeline coverage. A finance lead is probably in a close or an audit. A guess that fits their week gets a correction. A guess pulled from your own pitch gets ignored.
Example
- Prospect
Not interested right now, too busy.
- You
Totally get it. Most people I talk to are underwater with hiring and onboarding this quarter. Is that what's eating your time, or is it something else?
- Prospect
Actually it's the audit we're doing for the board. It's a nightmare.
Stop selling the meeting and start naming their week. It's easier to agree with a specific guess than to explain a schedule to a stranger.
Responding to we already have a tool for this
The mistake here is arguing that your tool is better or cheaper. That forces them to defend a decision they already made, and nobody enjoys doing that with a stranger on LinkedIn.
Ask about the gap. Every tool has one thing the user wishes worked differently, and most people will name it if the ask is small. The ask is small: describe the one thing that annoys them. Nobody has to change tools today.
Watch the wording. We already have something is softer than we're locked in until 2027. The first invites a question. The second is a fact, and you should treat it as one.
If they say the tool is fine and they mean it, believe them and leave. Some teams are well served, and pushing past that gets you blocked.
Arguing
- Approach
- Our tool is faster than Northwind. Want a demo?
- What you send
- They defend the purchase and the thread dies.
Asking about the gap
- Approach
- Makes sense. Are you getting everything you need from it, or is there one thing you wish worked better?
- What you send
- They name a frustration you can talk about.
Leaving it
- Approach
- Fair enough, thanks for the reply.
- What you send
- You keep the door open for a later campaign.
The plain not interested script
A bare not interested gives you nothing to work with. You need one question that sorts the answer into a category you can act on.
Agree first, then ask something with two possible answers. Binary questions are easy to answer on a phone, and easy answers get replies.
Whatever comes back, you now know which objection you're dealing with and whether another message is worth sending.
Don't run the same line on everyone. Swap the problem in the question for the one your lead actually owns, or the message reads like a template and gets treated like one.
- 1
Agree and step back
Start with no problem at all and nothing else. The short line removes the pressure that made them tap no in the first place.
- 2
Ask a binary question
Just curious, is lead gen not a priority this quarter, or do you already have it handled? Two answers, both one tap away.
- 3
Sort the answer
Already handled is a competitor objection. Not a priority is timing. Silence is a no for now, so move them to a longer list.
- 4
Reply once more, then stop
Timing gets a month. A competitor gets one question about what would have to change. Nothing else gets a reply.
Paste this job
No problem, {first_name}. One question so I don't waste your time later: is {problem} not a priority right now, or do you already have it covered?What to do with the answer you get back
The reply is more useful than the objection. Someone who says we already use Northwind has told you they buy software in your category. Someone who says not before the new year has told you when to come back.
Sort the answer before you write anything. The next message depends on which one you got, and sending the same follow-up to all of them wastes the one thing the objection gave you.
One more thing about timing answers. Write the month down in your notes, because the lead will not remember telling you, and a campaign that pitches them again in three weeks undoes the whole exchange.
- Already handled: ask what would have to change. Makes sense. If the renewal comes up and something's missing, is it worth a short call then?
- Not a priority: ask for a month, not a meeting. Understood. Worth me checking back in September, or is that still too early?
- No reason given: leave it. A second message with no new information reads as pressure, and pressure gets you blocked.
Writing the second message so it doesn't read like a pitch
Second messages fail for the same reason first ones do: they're about you. Long sentences, a feature, a calendar link, a question that needs a paragraph to answer.
Keep it under about 40 words. Ask one thing. Make the easiest answer a word or a short phrase, and leave out links, attachments and anything that looks like a deck.
Send it the same day if you can. A reply that arrives two days later reads like a sequence. A reply that arrives an hour later reads like a person who was already at the keyboard.
Read it back and check who it's for. If the message would work for any lead in the list, it isn't a reply to this one.
Reads like a sequence
- Thanks for getting back to me. I completely understand, and I'd love to share how Acme helps teams like yours fix reporting once and for all.
- I hear you. Would Tuesday at 2pm or Thursday at 10am work for a quick intro call?
- No worries at all. So I can tailor my next message, could you tell me about your current process, team size, budget and timeline?
Reads like a person
- Fair enough. Is reporting a mess this quarter, or is it handled?
- Makes sense. Worth checking back after the audit, or is this a permanent no?
- Understood. Do you already have someone for this, or is it just not on the list this year?
One question per message. Two questions means the lead answers the easier one and ignores the other.
Doing this with Kinlead
Put your objection replies in a sales playbook. Kinlead writes messages and follow-ups from the campaign goal, the tone you pick and that playbook, so the second message sounds like the first one.
If you'd rather handle the objection yourself, set the campaign to hand off at the first reply. Replies from every campaign land in one inbox sorted by intent, with interested ones first, and you get an email when someone replies. Queued messages can be read and edited on the Actions page before they send.
Sending runs from your own LinkedIn account through Unipile at one action every 5 minutes, inside the daily limits and send window you set. When LinkedIn pushes back on an account, Kinlead pauses invites there and emails you. The reply handling options are on reply drafts.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to respond to no thanks on LinkedIn.md