LinkedIn InMail Scripts That Get Replies
8 proven InMail openers mapped to buyer persona and trigger event, for the senior or gatekept accounts where a connection request isn't realistic and every InMail credit has to earn its reply.
What's inside
- 3 rules that affect InMail reply rate more than the copy itself
- Script for a VP of Sales new to the role
- Script for a Head of RevOps after a funding round
- Script for a Sales Enablement leader with an open req posted
- Script for a Founder/CEO on an expansion signal
- Script for a CRO in a team-growth phase
- Script for a CHRO/L&D leader announcing a new initiative
- Script for a Director of Sales after a soft quarter
- Script for a VP Customer Success in renewal season
- The single-follow-up rule for unanswered InMails
8 InMail scripts mapped to buyer persona plus trigger event, for accounts where a connection request isn't realistic — senior buyers who don't accept cold connections, 2nd/3rd-degree gatekeepers, or accounts on a deadline.
3 rules that change reply rates more than the copy does
- Subject line under 5 words, specific, no mention of your own company.
- Body under 500 characters — reply rate drops sharply past 3 short paragraphs.
- One question at the end, never two. Two questions give the reader an easy way to answer neither.
1. VP of Sales — New to the role (first 90 days)
Subject: Question for your first 90 days Body: "Hi [First Name] — congrats on stepping into VP of Sales at [Company]. Most new sales leaders I talk to in month one are trying to get a clean read on where the team's skill gaps actually are before they touch quota or headcount. Is that on your radar yet, or still too early?"
2. Head of RevOps — Recent funding round
Subject: Post-raise ramp question Body: "Hi [First Name] — saw [Company] closed [round]. Congrats. Rounds like that usually mean a hiring ramp, which means a wave of new reps who all need to get productive fast. How are you thinking about ramp time for the next cohort?"
3. Sales Enablement Leader — Open req for SDRs/AEs posted
Subject: Saw the [role] posting Body: "Hi [First Name] — noticed [Company] is hiring for [role]. Curious how the current ramp-to-productivity process handles a new cohort that size — is onboarding keeping pace with the hiring, or is that the part that's stretched thin right now?"
4. Founder/CEO, SMB — Expansion signal (new market, office, product line)
Subject: [Company]'s move into [new market] Body: "Hi [First Name] — saw [Company] is expanding into [market/product]. Usually that means the team selling it needs to get sharp on a new motion fast, without the luxury of a slow ramp. Is that part of what's on your plate right now?"
5. CRO — Team growth phase (headcount doubling, new region)
Subject: Scaling the team question Body: "Hi [First Name] — [Company]'s sales team growth this year has been hard to miss. Past a certain size, most CROs tell me consistency of coaching becomes the harder problem than hiring itself. Curious if that's showing up for you yet."
6. CHRO / L&D Leader — New learning & development initiative announced
Subject: Re: your L&D announcement Body: "Hi [First Name] — saw the note about [Company]'s new [L&D program/initiative]. For revenue teams specifically, the programs that stick tend to tie skill development to measurable outcomes rather than completion rates. Is that a lens you're building in already?"
7. Director of Sales — Missed number last quarter (public earnings/press signal)
Subject: Quick question on Q[X] Body: "Hi [First Name] — saw [Company]'s Q[X] update. When a number comes in soft, the root cause is sometimes pipeline, sometimes it's execution consistency across the team. Which one are you and your team digging into first?"
8. VP Customer Success — Renewal season / churn signal
Subject: Renewal season question Body: "Hi [First Name] — heading into renewal season, most CS leaders I talk to are looking hard at which reps consistently handle expansion conversations well versus which ones need support. Is that visibility something your team has today, or a gap?"
The follow-up rule
If no reply in 5 business days, send one follow-up InMail — never more than one. Reference the same trigger, add one new detail, and close with a lower-commitment ask ("worth 15 minutes, or should I check back next quarter?").
How to use it
Match the account's persona and most recent trigger event to one script, swap in the real details, and spend your InMail credits only on accounts where a connection request genuinely isn't viable.