![\"Why](\"https:\/\/dealsflow.co\/blog\/wp-content\/uploads\/2026\/05\/Why-Most-LinkedIn-Recruiter-Messages-Get-Ignored-scaled.webp\")
<\/p>\nYou send fifty LinkedIn messages this week. You get four replies. Three of them are polite declines. That ratio is not a fluke \u2014 it is the baseline reality for most recruiters operating on LinkedIn today.<\/p>\n
According to LinkedIn’s own Talent Solutions data, the average InMail response rate sits at around 25%. That means three out of every four candidates you reach out to will never write back. Yet LinkedIn’s internal research also shows that InMails personalised to a candidate’s specific background \u2014 their projects, their career path, a post they wrote \u2014 can achieve response rates above 40%, and in some cases considerably higher. The gap between those two numbers is not luck. It is craft.<\/p>\n
The core problem is not that candidates are ignoring recruiters. It is that most recruiter messages give candidates no compelling reason to respond. They are generic. They lead with the company’s needs rather than the candidate’s interests. They use the same six opening phrases that every other recruiter uses. And they ask for a big commitment \u2014 a call, an interview, a “quick chat” \u2014 before establishing any value or trust.<\/p>\n
This post exists to close that gap. You will find twelve tested outreach templates covering every major recruiting scenario: cold connection requests, full InMails for specific candidate personas, follow-up sequences, and specialist use cases like executive search and early-career outreach. Alongside each template, you will find a clear explanation of why it works and the one mistake that most often undermines it. Before the templates, you will find the psychological framework that makes all of them effective \u2014 because copying a template without understanding its logic limits how well you can adapt it to your own candidates.<\/p>\n
The templates cover four message types: connection requests, InMail outreach, follow-up and nurture messages, and speciality scenarios. By the end, you will have everything you need to copy, personalise, and send today.<\/p>\n
<\/p>\n
Understanding why candidates delete your messages is the necessary first step to writing ones they read. The problem is not the platform \u2014 it is the mismatch between how recruiters write and how passive candidates read.<\/p>\n
The majority of candidates worth reaching out to are not actively looking for a job. They are employed, reasonably comfortable, and not monitoring their LinkedIn inbox with any urgency. When a recruiter message arrives, their default filter is scepticism:\u00a0Is this worth my time? Does this person actually know anything about me?<\/em>\u00a0Most messages fail that test in the first two sentences and get closed without a reply.<\/p>\n This matters because passive candidates have a fundamentally different psychology from active job seekers. An active candidate is motivated to engage even with imperfect outreach. A passive candidate needs a genuine reason to interrupt their day, consider disrupting their career stability, and invest time in a conversation with a stranger. A generic message does not provide that reason.<\/p>\n Every candidate reading a recruiter message is \u2014 consciously or not \u2014 asking “What’s in it for me?” Most recruiter messages answer this question too late, too vaguely, or not at all. They open with “I came across your profile and was impressed,” pivot to a description of the company, and only eventually arrive at what the role might offer the candidate. By that point, many readers have already moved on.<\/p>\n Effective outreach answers WIIFM within the first two sentences. Not with vague statements like “exciting opportunity” or “great culture,” but with specific signals: a meaningful technical challenge the candidate would work on, a compensation range that represents genuine progression, the kind of team they would join, or the career step the role enables. The specificity is what makes it credible.<\/p>\n There is a significant difference between surface personalisation and genuine signal-based personalisation. Surface personalisation sounds like: “I came across your profile and think you’d be a great fit.” Signal-based personalisation sounds like: “I noticed you wrote about the migration challenges in distributed systems last month \u2014 that’s exactly the problem our infrastructure team is working through right now.”<\/p>\n The second version demonstrates that the recruiter actually read something the candidate created, holds a view on their expertise, and has drawn a specific connection between that expertise and a real need. That takes thirty seconds of research. It produces a fundamentally different response from the candidate because it signals respect for their time and credibility in the recruiter.<\/p>\n LinkedIn’s own data shows that shorter InMails consistently outperform longer ones. Messages under 400 characters have higher response rates than messages above that threshold. This does not mean good outreach is always brief \u2014 it means every word needs to earn its place. Preamble, corporate boilerplate, and over-explanation are the primary length offenders.<\/p>\n Equally damaging is the multiple-CTA message: “Let me know if you’re open to chatting, or I can send a job description, or feel free to apply directly.” Giving candidates three decisions to make often results in them making none. One clear, low-friction ask \u2014 typically a yes\/no question or a request for a fifteen-minute conversation \u2014 performs better than a menu of options.<\/p>\n Before looking at the templates, it is worth naming the structure they share. Every high-performing LinkedIn outreach message \u2014 regardless of length, candidate persona, or message type \u2014 contains five components in sequence. Understanding these components lets you adapt any template to your specific context rather than copying it word for word.<\/p>\n The structure is:\u00a0Hook \u2192 Relevance \u2192 Role Signal \u2192 Value \u2192 Soft CTA.<\/strong><\/p>\n The hook is the opening one or two sentences. Its job is to clear the “delete” reflex by demonstrating that this message is not generic. A strong hook references something specific to the candidate: a post they wrote, a company they worked at, a skill they are known for, or a transition they recently made. A weak hook is any sentence the candidate knows could have been sent to a hundred other people without changing a word.<\/p>\n Do this:<\/em>\u00a0“Your work on the real-time fraud detection system at [Company] caught my attention \u2014 we’re solving a very similar problem at scale.”<\/p>\n Not this:<\/em>\u00a0“I came across your profile and was really impressed by your background.”<\/p>\n The relevance sentence bridges the hook to the reason you are reaching out. It explains why\u00a0this candidate<\/em>\u00a0is being contacted for\u00a0this role<\/em>, and it does so in a way that feels logical rather than promotional. The goal is to make the candidate feel selected rather than targeted.<\/p>\n Do this:<\/em>\u00a0“We’re building out the engineering team behind our payments infrastructure, and your background in high-throughput transaction systems is directly relevant.”<\/p>\n Not this:<\/em>\u00a0“We have an exciting opportunity and think you’d be a great fit for our team.”<\/p>\n The role signal gives the candidate just enough information to self-qualify. This is not a job description. It is the two or three facts a candidate needs to decide whether it’s worth their time to reply: the level of the role, the core technical or functional challenge, and the team context. Compensation range \u2014 even a broad one \u2014 dramatically increases response rates when included here.<\/p>\n Do this:<\/em>\u00a0“It’s a senior IC role leading the design of our event-streaming pipeline \u2014 \u00a390\u2013110k base, remote-first team of eight.”<\/p>\n Not this:<\/em>\u00a0“The role is a senior-level position with competitive compensation and excellent benefits.”<\/p>\n The value sentence speaks to something the candidate gains from the role beyond salary \u2014 career trajectory, technical challenge, team quality, company mission, or autonomy. This is where you address WIIFM explicitly. It should be specific to the role and company, not a generic claim.<\/p>\n Do this:<\/em>\u00a0“You’d be the first infrastructure hire with direct influence over architectural decisions as we scale from 10 to 100 million events per day.”<\/p>\n Not this:<\/em>\u00a0“It’s a great opportunity to grow your career in a fast-paced environment.”<\/p>\n The soft CTA closes the message with a single, low-commitment ask. The best-performing CTAs are framed as yes\/no questions rather than open-ended requests. They reduce the cognitive effort required to respond and signal that the recruiter respects the candidate’s time.<\/p>\n Do this:<\/em>\u00a0“Would a fifteen-minute conversation this week or next be worth your time?”<\/p>\n Not this:<\/em>\u00a0“Let me know your availability and we can set something up.”<\/p>\n Connection requests<\/strong>\u00a0are constrained to 300 characters. In this format, you can fit a hook and a soft CTA \u2014 but not all five components. Prioritise the hook and keep the CTA to a single brief question.<\/p>\n InMail<\/strong>\u00a0gives you more room to run all five components fully. The target length is still under 300\u2013400 words; every sentence should map to one of the five components.<\/p>\n Follow-up messages<\/strong>\u00a0have a different job. They are not repeating the original pitch. They add new value \u2014 an article, a development in the role, a piece of news \u2014 and re-open the door with a brief, low-pressure CTA. The hook in a follow-up acknowledges that you have already been in touch rather than pretending you haven’t.<\/p>\n Throughout the templates, you will see bracketed tokens:\u00a0 The templates below are organised into four categories: connection request messages, InMail templates for specific candidate personas, follow-up and nurture sequences, and speciality use cases. Each template includes the full message, a variable guide, an explanation of why it works, and the most common mistake that undermines it.<\/p>\n Use case:<\/strong>\u00a0Passive candidates whose skill set directly matches the role. Use when the candidate’s profile shows a clear, specific technical or functional expertise that is central to what you are hiring for.<\/p>\n The template:<\/strong><\/p>\n Hi [CANDIDATE NAME], your work in [SPECIFIC SKILL OR DOMAIN] caught my attention. I’m working on a [ROLE LEVEL] role at [COMPANY] that’s directly relevant \u2014 happy to share more if you’re open to it.<\/p><\/blockquote>\n Variable guide:<\/strong><\/p>\n Why it works:<\/strong>\u00a0The opening line does one critical job: it proves you read their profile. Candidates can tell the difference between “I saw your experience in software” and “I saw your experience in Kafka-based event streaming.” The former is noise; the latter is a signal that you have done your homework. Because the message also names the level and company, the candidate can self-qualify in ten seconds without needing to ask follow-up questions. The CTA is a soft opt-in (“if you’re open to it”) rather than a demand, which removes the pressure that often stops passive candidates from engaging.<\/p>\n The most common mistake:<\/strong>\u00a0Making the skill descriptor too broad. “Your experience in marketing” or “your background in engineering” is surface personalisation, not signal-based personalisation. The skill you name should be specific enough that it could not apply to every person in the candidate’s field.<\/p>\n Use case:<\/strong>\u00a0Candidates where you share a mutual LinkedIn connection, are both members of the same professional group, or both attended the same university or bootcamp. The social proof from a shared context dramatically reduces the cold-stranger friction of an unsolicited message.<\/p>\n The template:<\/strong><\/p>\n Hi [CANDIDATE NAME], we’re both connected to [MUTUAL CONNECTION NAME \/ both members of [GROUP NAME]] \u2014 I’m recruiting for a [ROLE LEVEL] [FUNCTION] role at [COMPANY] and your background looked highly relevant. Worth a quick message?<\/p><\/blockquote>\n Variable guide:<\/strong><\/p>\n Why it works:<\/strong>\u00a0Shared social context is one of the most reliable ways to reduce scepticism in cold outreach. Even a thin connection \u2014 a shared group, a shared alma mater \u2014 signals that you exist in the same professional ecosystem rather than reaching in from outside it. Research on social proof in sales and recruitment consistently shows that even indirect connections increase engagement rates. The message is also transparent about its purpose (recruiting) rather than pretending to be a networking note, which builds trust with candidates who have been burned by bait-and-switch outreach before.<\/p>\n The most common mistake:<\/strong>\u00a0Fabricating or exaggerating the shared connection. Candidates check. If the mutual connection is someone they have never spoken to, or the group is one they joined years ago and never engage with, the bridge feels hollow. Only use this template when the connection is genuine.<\/p>\n Use case:<\/strong>\u00a0Candidates who actively post or comment on LinkedIn. This is the strongest personalisation signal available in a connection request because it requires you to engage with something the candidate created or said publicly.<\/p>\n The template:<\/strong><\/p>\n Hi [CANDIDATE NAME], your post on [SPECIFIC TOPIC FROM THEIR CONTENT] made me think of the problem we’re trying to solve at [COMPANY]. I’m reaching out about a [ROLE LEVEL] role \u2014 would love to connect and share more.<\/p><\/blockquote>\n Variable guide:<\/strong><\/p>\n Why it works:<\/strong>\u00a0Referencing a candidate’s own published thinking is the single highest-signal personalisation move available on LinkedIn. It tells the candidate three things simultaneously: you follow their work, you found it interesting enough to act on, and you see a genuine connection between what they think and what you need. It also opens a natural conversation thread \u2014 the candidate may want to discuss the topic further, which lowers the barrier to engagement considerably. According to LinkedIn’s recruiting data, InMails that reference content the candidate has created consistently outperform generic outreach.<\/p>\n The most common mistake:<\/strong>\u00a0Vague reference to content without showing you actually understood it. “I loved your recent post” is worse than no personalisation at all because it is clearly a hollow gesture. You must reference the specific argument, finding, or observation the candidate made.<\/p>\n Use case:<\/strong>\u00a0Experienced individual contributors who show signs of a readiness or interest in moving into a leadership role. Signs to look for on their profile: increasing scope in recent roles, mentions of mentoring or team leadership in their experience descriptions, or content they have posted about engineering management or people leadership.<\/p>\n The template:<\/strong><\/p>\n Subject: Engineering leadership at [COMPANY] \u2014 relevant to your trajectory<\/p><\/blockquote>\n Hi [CANDIDATE NAME],<\/p><\/blockquote>\n I’ve been following your work at [CURRENT COMPANY], particularly your progression from [EARLIER ROLE] to [CURRENT ROLE]. The scope you’ve taken on \u2014 [SPECIFIC RESPONSIBILITY FROM THEIR PROFILE] \u2014 suggests you’ve already been operating at a leadership level, even if the title hasn’t caught up yet.<\/p><\/blockquote>\n We’re building out the [TEAM NAME] team at [COMPANY], and I’m looking for a [ROLE TITLE] who can both contribute technically and take ownership of team direction as we scale. The role sits at the intersection of hands-on architecture and people leadership \u2014 it’s not a pure EM role, and it’s not a pure IC role.<\/p><\/blockquote>\n Compensation is in the [SALARY RANGE] range, with equity on top. The team is [TEAM SIZE] people today and expected to reach [TARGET SIZE] over the next eighteen months.<\/p><\/blockquote>\n Would a fifteen-minute conversation be worth your time?<\/p><\/blockquote>\n [YOUR NAME]<\/p><\/blockquote>\n Variable guide:<\/strong><\/p>\n Why it works:<\/strong>\u00a0Senior ICs at the threshold of a leadership role are a uniquely receptive audience, but only if the message recognises where they actually are in their career. Telling a senior engineer that a role “offers the opportunity to grow into leadership” is condescending \u2014 they are already there. This template reflects their current reality back to them, which demonstrates genuine understanding. The description of the role as sitting between EM and IC is honest about its ambiguity, which builds trust. The salary and team growth context give the candidate everything they need to make a preliminary decision without a call.<\/p>\n The most common mistake:<\/strong>\u00a0Describing the role as “a great step up” or “perfect for someone looking to move into leadership.” This signals that the recruiter sees the candidate as junior, which is precisely the wrong message for a senior IC who has already been doing leadership work informally.<\/p>\n Use case:<\/strong>\u00a0Candidates in fields where demand dramatically exceeds supply \u2014 software engineering, machine learning, data science, product design. These candidates receive a high volume of recruiter messages and have very low tolerance for vague outreach. Their time is their scarcest resource.<\/p>\n The template:<\/strong><\/p>\n Subject: [ROLE TITLE] at [COMPANY] \u2014 [SALARY RANGE], [REMOTE POLICY]<\/p><\/blockquote>\n Hi [CANDIDATE NAME],<\/p><\/blockquote>\n I’ll keep this short because I know you get a lot of these.<\/p><\/blockquote>\n We’re hiring a [ROLE TITLE] to work on [ONE SPECIFIC TECHNICAL CHALLENGE IN TWO SENTENCES MAX]. The role is [REMOTE \/ HYBRID \/ ON-SITE], pays [SALARY RANGE] base plus [EQUITY OR BONUS STRUCTURE], and sits on a team of [TEAM SIZE] working in [TECH STACK OR DOMAIN].<\/p><\/blockquote>\n You’d be working on [SPECIFIC PROBLEM OR SYSTEM] \u2014 the kind of problem that doesn’t have a clean solution yet.<\/p><\/blockquote>\n If that’s interesting, I’d value fifteen minutes of your time. No pressure either way.<\/p><\/blockquote>\n [YOUR NAME]<\/p><\/blockquote>\n Variable guide:<\/strong><\/p>\n Why it works:<\/strong>\u00a0The explicit acknowledgement that the candidate receives many messages (“I know you get a lot of these”) does two things: it demonstrates self-awareness, and it signals that this message will be different \u2014 shorter, more respectful of their time, more direct. Putting salary and remote policy in the subject line means the candidate can pre-qualify before opening the message. Research from Greenhouse and LinkedIn’s own talent data consistently shows that candidates in competitive fields rank remote flexibility and compensation transparency as their top criteria when deciding whether to engage with outreach.<\/p>\n The most common mistake:<\/strong>\u00a0Burying the compensation. In a message targeting high-demand talent, “competitive compensation” in the body is not a value signal \u2014 it is a placeholder that tells the candidate nothing. Name the number, or name a range. Candidates in these fields have market data; vagueness signals that the offer will not meet their expectations.<\/p>\n Use case:<\/strong>\u00a0Candidates who show clear signals of values-driven career choices \u2014 those who have moved to mission-driven companies, written about purpose at work, or whose content reflects strong alignment with a cause, sustainability, social impact, or a specific type of company culture.<\/p>\n The template:<\/strong><\/p>\n Subject: [COMPANY] \u2014 [ONE LINE MISSION STATEMENT OR IMPACT DESCRIPTION]<\/p><\/blockquote>\n Hi [CANDIDATE NAME],<\/p><\/blockquote>\n I came across your background and was struck by the thread running through your career \u2014 [OBSERVATION ABOUT THEIR VALUES-DRIVEN CHOICES, e.g., “you’ve consistently moved toward companies working on climate infrastructure, even when the commercial upside wasn’t obvious”].<\/p><\/blockquote>\n We’re building [DESCRIPTION OF WHAT THE COMPANY DOES AND WHY IT MATTERS] at [COMPANY]. The [ROLE TITLE] role I’m recruiting for is central to that mission \u2014 [ONE SENTENCE ON HOW THE ROLE CONNECTS TO THE IMPACT].<\/p><\/blockquote>\n On the practical side: the role is [LEVEL], pays [SALARY RANGE], and the team works [REMOTE \/ HYBRID]. We’re a [COMPANY SIZE \/ STAGE] business, so the decisions you make will genuinely shape the direction.<\/p><\/blockquote>\n If any of this resonates, I’d be glad to have a fifteen-minute conversation.<\/p><\/blockquote>\n [YOUR NAME]<\/p><\/blockquote>\n Variable guide:<\/strong><\/p>\n Why it works:<\/strong>\u00a0Mission-driven candidates are not primarily motivated by compensation \u2014 they are motivated by the gap between where they are and where they want to be working. But they are also sophisticated enough to know that a company can claim a mission while delivering a mediocre working experience. This template earns credibility by demonstrating that you actually read their career history and drew a genuine inference about their motivations. The practical details (salary, remote policy, stage) are included because mission-driven candidates are still making pragmatic decisions; the template just puts mission first, as it should be for this audience.<\/p>\n The most common mistake:<\/strong>\u00a0Hollow mission language. “We’re changing the world” or “we’re making a real difference” are phrases candidates in this category have heard from companies whose actual practices did not match the rhetoric. Be specific about the impact, the mechanism, and the stage \u2014 or the mission framing will work against you.<\/p>\n Use case:<\/strong>\u00a0Outreach to candidates from underrepresented groups where the goal is to signal genuine inclusion \u2014 not check-box DEI. The distinction matters enormously. Candidates from underrepresented groups can identify performative diversity messaging immediately, and it reduces response rates rather than increasing them.<\/p>\n The template:<\/strong><\/p>\n Subject: [ROLE TITLE] at [COMPANY] \u2014 a few things worth knowing<\/p><\/blockquote>\n Hi [CANDIDATE NAME],<\/p><\/blockquote>\n I’m reaching out because your background in [SPECIFIC SKILL OR DOMAIN] is genuinely relevant to a [ROLE TITLE] role I’m filling at [COMPANY].<\/p><\/blockquote>\n A few things that might be useful context: we have [SPECIFIC ERG OR COMMUNITY, e.g., “an active Women in Engineering group with monthly programming”], [FLEXIBLE WORKING POLICY, e.g., “a fully flexible working schedule with no core hours”], and [SPECIFIC INCLUSIVE PRACTICE, e.g., “structured interview processes designed to reduce evaluation bias”]. These aren’t things I’ve added to hit a checklist \u2014 they’re practices I’ve seen in action and can speak to directly.<\/p><\/blockquote>\n The role pays [SALARY RANGE] and is [REMOTE \/ HYBRID \/ ON-SITE]. The team is [BRIEF TEAM DESCRIPTOR].<\/p><\/blockquote>\n Is it worth fifteen minutes to hear more?<\/p><\/blockquote>\n [YOUR NAME]<\/p><\/blockquote>\n Variable guide:<\/strong><\/p>\n Why it works:<\/strong>\u00a0The template leads with professional relevance, not group membership \u2014 the candidate is being contacted because of their skills, full stop. The inclusion signals are delivered as practical, specific facts rather than values statements because specific facts are verifiable and statements are not. The explicit acknowledgement (“These aren’t things I’ve added to hit a checklist”) addresses the scepticism that is entirely reasonable given how many companies use diversity language without backing it with practice. The recruiter also positions themselves as a credible source (“I can speak to directly”), which matters \u2014 candidates want to know that the person reaching out has actual knowledge of the culture, not just the company’s public DEI page.<\/p>\n The most common mistake:<\/strong>\u00a0Opening with any language that references the candidate’s membership in an underrepresented group. “I’m specifically reaching out to diverse candidates” or “as part of our diversity initiative” immediately signals tokenisation, regardless of your actual intentions. Lead with their professional qualifications, always.<\/p>\n Use case:<\/strong>\u00a0Candidates who declined an offer, withdrew from a process, or expressed disinterest in a prior outreach \u2014 but whose circumstances may have changed, or where the role or company has genuinely evolved.<\/p>\n The template:<\/strong><\/p>\n Subject: Things have changed since we last spoke \u2014 worth revisiting?<\/p><\/blockquote>\n Hi [CANDIDATE NAME],<\/p><\/blockquote>\n We spoke [TIMEFRAME, e.g., “about eight months ago”] about a role at [COMPANY], and at the time it wasn’t the right fit \u2014 [BRIEF HONEST REASON IF KNOWN, e.g., “the compensation wasn’t where it needed to be” or “the remote policy wasn’t flexible enough”].<\/p><\/blockquote>\n I’m reaching out again because a few things have changed: [SPECIFIC CHANGE 1, e.g., “the role now comes with a fully remote arrangement”], [SPECIFIC CHANGE 2 IF RELEVANT, e.g., “and the compensation band has moved to \u00a395\u2013115k”]. The team has also [RELEVANT TEAM CHANGE, e.g., “added two senior engineers with backgrounds in distributed systems, which changes the calibre of the technical environment significantly”].<\/p><\/blockquote>\n If your situation or priorities have also shifted, I think it’s worth a fresh fifteen-minute conversation. If the timing still isn’t right, I completely understand \u2014 and I’ll make sure any future outreach is genuinely relevant before reaching out.<\/p><\/blockquote>\n [YOUR NAME]<\/p><\/blockquote>\n Variable guide:<\/strong><\/p>\n Why it works:<\/strong>\u00a0Candidates who have already evaluated your company and declined have a specific mental model of why it was not right. The only way to re-open that conversation is to give them a credible reason to revise that model. This template does that by naming the previous contact, acknowledging why it did not work, and being specific about what has changed. The closing line \u2014 committing to relevance in future outreach \u2014 is a trust signal that works particularly well for candidates who felt their prior rejection was not fully heard.<\/p>\n The most common mistake:<\/strong>\u00a0Re-engaging without a genuine change to report. “Reaching back out as I thought of you for this role” with an identical offer signals that the recruiter is not listening and is simply recycling a list. Candidates remember.<\/p>\n Use case:<\/strong>\u00a0A candidate has not responded to your initial outreach within five to seven days. This follow-up is not a nudge \u2014 it is a second message that adds something the first did not have.<\/p>\n The template:<\/strong><\/p>\n Hi [CANDIDATE NAME],<\/p><\/blockquote>\n I sent a note [TIMEFRAME, e.g., “last week”] about the [ROLE TITLE] role at [COMPANY] \u2014 just wanted to follow up, and also share something that might add useful context.<\/p><\/blockquote>\n [NEW VALUE ELEMENT \u2014 one of the following approaches:]\u00a0Option A (relevant article or resource):<\/strong>\u00a0“I came across this piece on [TOPIC DIRECTLY RELEVANT TO THEIR BACKGROUND] \u2014 [ONE SENTENCE ON WHY IT’S RELEVANT TO THEM OR THE ROLE].”\u00a0Option B (role update):<\/strong>\u00a0“Since I reached out, we’ve had some movement \u2014 [GENUINE UPDATE ON THE ROLE, e.g., ‘the hiring manager has confirmed the scope includes architectural ownership from day one, not just delivery’].\u00a0Option C (team news):<\/strong>\u00a0“[COMPANY] announced [RELEVANT NEWS \u2014 funding, product launch, hire] this week, which changes the context for this role slightly \u2014 [ONE SENTENCE ON HOW].”<\/p><\/blockquote>\n If the timing isn’t right, no problem \u2014 happy to keep in touch for when it might be.<\/p><\/blockquote>\n [YOUR NAME]<\/p><\/blockquote>\n Variable guide:<\/strong><\/p>\n Why it works:<\/strong>\u00a0The most common follow-up in recruiter outreach is “just checking in to see if you had a chance to review my last message.” This accomplishes nothing except reminding the candidate that you are still waiting for them, which adds pressure rather than value. This template follows a different principle: every touch in a sequence should give the candidate something they did not have before. A relevant article, a role update, or a piece of company news all give the candidate a new reason to respond and signal that the recruiter is genuinely tracking their interests and the role’s evolution.<\/p>\n The most common mistake:<\/strong>\u00a0Sending the follow-up at 24 to 48 hours. For passive candidates, this is too fast \u2014 it signals impatience and can feel pressuring. Five to seven business days is the right spacing for the first follow-up. The exception is a role with a very short hiring timeline, in which case you should state that explicitly in the message.<\/p>\n Use case:<\/strong>\u00a0A candidate has not responded after two or three touches. This is the final message in the sequence before you close the loop on this particular outreach cycle.<\/p>\nThe WIIFM principle<\/h3>\n
The personalisation gap<\/h3>\n
Length, format, and the single CTA<\/h3>\n
The five hallmarks of a message that earns a response<\/h3>\n
\n
The Anatomy of a High-Response LinkedIn Outreach Message<\/h2>\n
![\"The](\"https:\/\/dealsflow.co\/blog\/wp-content\/uploads\/2026\/05\/The-Anatomy-of-a-High-Response-LinkedIn-Outreach-Message-scaled.webp\")
<\/p>\nHook<\/h3>\n
Relevance<\/h3>\n
Role signal<\/h3>\n
Value<\/h3>\n
Soft CTA<\/h3>\n
Adapting the framework by message type<\/h3>\n
Personalisation tokens<\/h3>\n
[CANDIDATE NAME]<\/code>,\u00a0[SPECIFIC SKILL OR PROJECT]<\/code>,\u00a0[COMPANY]<\/code>,\u00a0[ROLE]<\/code>,\u00a0[SALARY RANGE]<\/code>,\u00a0[MUTUAL CONNECTION]<\/code>. These are your personalisation variables. For each message, you need to fill at minimum the hook token with something genuinely specific to that candidate. The research required is typically a three-to-five minute scan of their profile, focusing on: their most recent role and what they built there, any content they have published or commented on in the last sixty days, any career transition or promotion in the last twelve months, and any shared connections or groups.<\/p>\n12 LinkedIn Outreach Templates That Actually Get Responses<\/h2>\n
Connection Request Messages<\/h3>\n
Template 1: The Skill-Specific Opener<\/h4>\n
\n
[SPECIFIC SKILL OR DOMAIN]<\/code>\u00a0\u2014 replace with something genuinely specific from their profile: a programming language they are known for, a methodology they have used, a domain they have worked in (e.g., “event-driven architecture” rather than “software engineering”)<\/li>\n[ROLE LEVEL]<\/code>\u00a0\u2014 senior, lead, principal, etc.<\/li>\n[COMPANY]<\/code>\u00a0\u2014 your company name<\/li>\n<\/ul>\nTemplate 2: The Mutual Connection \/ Shared Community Hook<\/h4>\n
\n
[MUTUAL CONNECTION NAME]<\/code>\u00a0\u2014 use only if you genuinely know the mutual connection and can reference them credibly; do not name-drop someone you have only passively connected with<\/li>\n[GROUP NAME]<\/code>\u00a0\u2014 name of the shared LinkedIn group, alumni network, or professional community<\/li>\n[ROLE LEVEL]<\/code>\u00a0and\u00a0[FUNCTION]<\/code>\u00a0\u2014 e.g., “senior product management” or “lead data engineering”<\/li>\n<\/ul>\nTemplate 3: The Content-Engagement Opener<\/h4>\n
\n
[SPECIFIC TOPIC FROM THEIR CONTENT]<\/code>\u00a0\u2014 name the actual topic or argument from a post or comment they made, not just the general subject area. “Your post on why zero-downtime deployments break under certain consistency models” is far stronger than “your post on DevOps”<\/li>\n[COMPANY]<\/code>\u00a0\u2014 your company name<\/li>\n[ROLE LEVEL]<\/code>\u00a0\u2014 keep this brief at connection-request length<\/li>\n<\/ul>\nInMail Templates (Role-Specific)<\/h3>\n
Template 4: Passive Senior Candidate (IC \u2192 Leadership Transition)<\/h4>\n
\n
[SPECIFIC RESPONSIBILITY FROM THEIR PROFILE]<\/code>\u00a0\u2014 name something concrete from their experience: “leading the migration to a microservices architecture” or “owning the technical roadmap for the checkout platform”<\/li>\n[TEAM NAME]<\/code>\u00a0\u2014 the specific team within your organisation<\/li>\n[SALARY RANGE]<\/code>\u00a0\u2014 include this; its absence is consistently cited by passive candidates as a reason not to engage<\/li>\n[TEAM SIZE]<\/code>\u00a0and\u00a0[TARGET SIZE]<\/code>\u00a0\u2014 growth context signals opportunity without hyperbole<\/li>\n<\/ul>\nTemplate 5: High-Demand \/ Competitive Talent (Engineering, Data, Design)<\/h4>\n
\n
[ONE SPECIFIC TECHNICAL CHALLENGE]<\/code>\u00a0\u2014 this must be genuine and specific. “Scaling our recommendation engine to handle 50 million daily active users” is a real problem; “working on exciting technical challenges in a fast-growing startup” is not<\/li>\n[EQUITY OR BONUS STRUCTURE]<\/code>\u00a0\u2014 even a rough description (“meaningful equity at Series B” or “10\u201315% annual bonus”) is better than leaving this blank<\/li>\n[TECH STACK OR DOMAIN]<\/code>\u00a0\u2014 name the specific technologies or domain, not a generic descriptor<\/li>\n<\/ul>\nTemplate 6: Culture \/ Mission-Fit Angle<\/h4>\n
\n
[OBSERVATION ABOUT THEIR VALUES-DRIVEN CHOICES]<\/code>\u00a0\u2014 this must be based on something specific you observed, not an assumption; draw from their career history, published content, or stated interests in their profile<\/li>\n[DESCRIPTION OF WHAT THE COMPANY DOES AND WHY IT MATTERS]<\/code>\u00a0\u2014 lead with impact, not the product category. “We’re making it cheaper to retrofit existing buildings for low-carbon heating” is better than “we’re a cleantech startup”<\/li>\n[COMPANY SIZE \/ STAGE]<\/code>\u00a0\u2014 Series A, B, C, or an employee count; gives the candidate a frame for the risk and opportunity<\/li>\n<\/ul>\nTemplate 7: Diversity Sourcing \u2014 Inclusive, Non-Tokenising Language<\/h4>\n
\n
[SPECIFIC ERG OR COMMUNITY]<\/code>\u00a0\u2014 name the actual group; do not claim one exists if it does not<\/li>\n[FLEXIBLE WORKING POLICY]<\/code>\u00a0\u2014 be specific; “flexible working” is vague, “no required core hours and full remote” is a fact<\/li>\n[SPECIFIC INCLUSIVE PRACTICE]<\/code>\u00a0\u2014 name something real: structured interviews, blind resume review, pay equity audits, returnship programmes<\/li>\n<\/ul>\nTemplate 8: Re-Engaging a Previously Declined Candidate<\/h4>\n
\n
[BRIEF HONEST REASON IF KNOWN]<\/code>\u00a0\u2014 only include this if you genuinely know why they declined; do not guess<\/li>\n[SPECIFIC CHANGE 1 and 2]<\/code>\u00a0\u2014 these must be real changes; re-engaging a declined candidate with an identical role and compensation is not re-engagement, it is repetition<\/li>\n[RELEVANT TEAM CHANGE]<\/code>\u00a0\u2014 a team composition change, a new engineering leader, a product direction shift, or a funding event are all credible change signals<\/li>\n<\/ul>\nFollow-Up and Nurture Sequences<\/h3>\n
Template 9: The 5-Day Follow-Up (Adds New Value)<\/h4>\n
\n
[RELEVANT NEWS]<\/code>\u00a0\u2014 only use Option C if the news is genuinely relevant to the candidate’s decision, not just promotional<\/li>\n<\/ul>\nTemplate 10: The “Break-Up” Message (Creates Urgency Without Pressure)<\/h4>\n