LinkedIn DM Reply Handling Scripts: 12 Scenarios
Word-for-word reply scripts for every response a prospect sends after you connect on LinkedIn. Covers 12 real scenarios from curious to hostile, with a signal read, response goal, and named failure mode for each.
How to use it
Keep this open in a second tab while you work your LinkedIn inbox. Match the prospect's reply to the nearest scenario, adapt the bracketed fill-ins to your context, and send. If a reply sits between two scenarios, use the signal reads to judge which goal fits better.
What's inside
- 12 word-for-word reply scripts with bracketed fill-ins for name, company, and context
- One-line signal read for each scenario explaining what the prospect's reply actually means
- Stated response goal for each script so you know what you are trying to achieve
- Named failure mode per scenario, the specific mistake most reps make in that moment
- Coverage of both warm inbound and cold outreach reply contexts
- Honest notes on when to slow down, when to push, and when to walk away
- A quick-reference scenario index at the top for fast inbox triage
How to use this resource
This is an inbox tool, not reading material. Scan the scenario index, find your match, read the signal, check the failure mode, send the script. Adapt the brackets. Do not over-personalise at the expense of speed.
Scenario index
| # | Reply type | Your goal |
|---|---|---|
| 1 | "Tell me more" | Qualify and move toward a call |
| 2 | "Send me a deck / brochure" | Redirect to a conversation |
| 3 | "Not interested" | Leave the door open without begging |
| 4 | "Call me" | Confirm and set the agenda |
| 5 | "Who gave you my details?" | De-escalate and re-establish trust |
| 6 | "We already use [Competitor]" | Probe without attacking |
| 7 | "Try me in Q3" | Pin down a real date |
| 8 | "What's this about?" (suspicious) | Earn five more seconds |
| 9 | "Can you send pricing?" | Hold value before quoting |
| 10 | "Forwarding you to my colleague" | Keep momentum, do not restart |
| 11 | No reply after an initial warm signal (they liked your post or accepted fast) | Re-engage without nagging |
| 12 | A hostile or rude reply | Exit cleanly, protect the relationship |
The scripts
Scenario 1: "Tell me more"
Signal read: Genuine curiosity, low commitment. They want enough to decide whether to invest ten minutes, not a sales pitch.
Goal: Qualify in one exchange, propose a short call.
Failure mode: Over-explaining. Reps dump three paragraphs of features here and kill the momentum.
Hi [Name], glad it landed. The short version: we help [type of company] [specific outcome, e.g. reduce their onboarding time by 30%] without [common painful trade-off, e.g. rebuilding their tech stack]. Worth a 20-minute call to see if there's a fit? I have [day] or [day] free this week.
Scenario 2: "Send me a deck / brochure"
Signal read: Either genuine interest with a preference for async, or a polite brush-off. You cannot tell yet. Treat it as real until proven otherwise.
Goal: Redirect to a conversation without refusing the request outright.
Failure mode: Sending the deck. Once it is in their inbox you have zero control, and "did you get a chance to look at it?" is one of the weakest follow-up messages in sales.
Happy to, though in my experience the decks make more sense once I know a bit about your situation, otherwise it's twenty slides that may not connect at all. Can we do 15 minutes first? I'll share whatever's relevant and send you anything useful afterwards. [Day] or [day] work?
If they repeat the request after this, send a short two-to-three slide summary, not the full deck, and attach a single clear CTA.
Scenario 3: "Not interested"
Signal read: Could be genuine, could be a reflex. Either way, they have not said "never", they have said "not now" or "not obviously relevant."
Goal: Leave without burning the bridge. Do not grovel or argue.
Failure mode: Asking "Can I ask why?" It reads as desperate and puts them on the spot.
Understood, [Name]. No pressure at all. If anything shifts on [relevant topic, e.g. your headcount planning or your stack review] later in the year, feel free to come back to this thread. Good luck with [something genuine from their profile, e.g. the Series B].
Scenario 4: "Call me"
Signal read: High intent. They want to move fast. Do not slow this down.
Goal: Confirm the call quickly and set a light agenda so you show up prepared and they know what to expect.
Failure mode: Booking too fast without any pre-qualification. You land on a call with no context and waste both parties' time.
Great, looking forward to it. A couple of quick things so I come prepared: roughly how many people are affected by [problem area], and is this something you are actively looking to address this half, or more exploratory at this stage? [Scheduling link or two specific slots]. Either work?
Scenario 5: "Who gave you my details?"
Signal read: GDPR anxiety, privacy concern, or genuine annoyance. Not necessarily hostile. They want to feel safe before they engage.
Goal: De-escalate immediately, be transparent, re-earn the right to a conversation.
Failure mode: Getting defensive or vague. "I found you through LinkedIn" without explanation makes it worse.
Fair question. Your profile is public on LinkedIn and came up when I was looking for [job title / role type] at [company type]. No list, no data broker, just your public profile. If you'd rather I did not reach out again, say the word and I'll leave you alone. If you're open to it, I was reaching out because [one-line specific reason relevant to them].
Scenario 6: "We already use [Competitor]"
Signal read: Not a closed door. It is information. They may be unhappy, locked in, or perfectly happy. You do not know yet.
Goal: Probe without attacking the competitor or sounding desperate to displace them.
Failure mode: Competitor bashing. It makes you look insecure and puts the prospect in the position of defending a vendor they may actually like.
[Competitor] is a solid option for a lot of teams. How long have you been running with them, and is it doing what you need it to, or are there gaps you are working around?
If they say it is working fine, use Scenario 3's close. If they surface a gap, you have a conversation.
Scenario 7: "Try me in Q3"
Signal read: Genuine timing constraint or a soft stall. You will not know until you test it.
Goal: Pin down a real date and a real reason, without being pushy.
Failure mode: Going silent and hoping they remember. They will not.
Noted. Is Q3 a budget cycle thing, a project milestone, or just a quieter period for you? I ask because it changes what I should prep for that conversation. If it helps, I can send one thing between now and then to keep it on your radar, or I can just put a placeholder in my diary for [specific month], whichever is less annoying.
Scenario 8: "What's this about?" (suspicious tone)
Signal read: They accepted your connection but did not read your original message closely, or your opener was unclear. Low trust, open channel.
Goal: Earn five more seconds of attention with a clear, honest one-liner.
Failure mode: Repeating your opener word for word. It signals you are running a script and not listening.
Good question, I should have been clearer. In short: [one sentence on what you do and who you help]. The reason I reached out to you specifically is [one sentence on why they, not someone else]. Does that land or should I leave it there?
Scenario 9: "Can you send pricing?"
Signal read: High intent on the surface, but pricing without context is dangerous. They may be benchmarking, getting a number for a business case, or genuinely ready to buy.
Goal: Understand their situation before you quote. Hold value.
Failure mode: Sending a price list. You anchor low, invite comparison shopping, and lose all discovery leverage.
I can do, though pricing varies quite a bit depending on [team size / usage / contract length / etc.]. Without knowing your setup I'd just be sending you a number that may be 40% off in either direction. Ten minutes on a call would let me give you a figure that's actually accurate. Worth it?
Scenario 10: "I'm forwarding you to my colleague"
Signal read: Either a genuine referral to the right person, or a polite way of getting out of the conversation. Treat it as real.
Goal: Keep momentum. Do not restart the entire outreach process with the colleague as if it is a cold contact.
Failure mode: Going silent and waiting. The colleague has no context and your message will land cold.
Thanks, [Name]. Really appreciate it. When you forward it, would you mind giving [colleague] a one-line heads up on why you think it is relevant? It helps them engage straight away rather than getting a cold message from a stranger. If it is easier, I can drop them a note directly and mention you suggested it. Either works.
Scenario 11: Re-engaging a warm but silent prospect
Signal read: They accepted your connection quickly, liked a post, or opened your first message, but went quiet. Not rejection. Just noise.
Goal: Re-engage without sounding needy or passive-aggressive.
Failure mode: "Just checking in." It is the most common and least effective message in LinkedIn sales.
Hi [Name], not looking to be a nuisance. I noticed [specific thing: e.g. you posted about [topic] last week / you are hiring [role] at the moment] and it reminded me of what I had reached out about. Still worth a quick conversation, or has the situation changed? Either answer is fine.
Scenario 12: A hostile or rude reply
Signal read: Something in your message triggered them. Over-personalisation, a bad assumption, or just a bad day. Do not escalate.
Goal: Exit cleanly. Protect your reputation and your company's brand on a public-adjacent platform.
Failure mode: Defending yourself or apologising excessively. Both prolong a conversation you should close.
Apologies for the interruption, [Name]. Not my intention. I'll leave it here.
One sentence. Send it. Do not add "I hope you have a great day." Do not explain yourself. Move on.
Quick rules across all 12 scenarios
- Keep every reply under 100 words where possible. LinkedIn DMs are not email.
- One question per message. Two questions halves your response rate.
- If they reply at all, you have permission to reply back. Use it.
- Speed matters. Replying within an hour of their message keeps the thread alive.
- Never follow up more than twice on silence after a reply exchange. After that, wait for a trigger event.