Almost every LinkedIn connection request template you find online has the same problem: it is a complete message with a blank where the personalisation should be. Fill in the blank and you have written the same note as everyone else using the same template.
So here are fifteen, but the useful part is the reasoning underneath each one. Steal the structure, never the sentence.
The three patterns that get ignored
Worth naming first, because most requests fall into one of them.
The blank envelope. "I'd love to add you to my professional network." Zero information. It gets accepted occasionally by people who accept everything, which teaches you nothing about whether your targeting works.
The unearned compliment. "I was really impressed by your work at Northgate!" Impressed by what? The recipient knows immediately that you looked at a job title and nothing else. This performs worse than the blank envelope, because it is a small lie.
The pitch in the doorway. "Hi Sarah, we help logistics companies reduce costs by 30%, would love 15 minutes." You have asked for a meeting from someone who has not yet agreed to know you.
The fix for all three is the same: say one thing that is true, specific and checkable.
Cold outreach
1. The visible operational fact
Hi Sarah, saw you're running ops across three Northgate depots. We work with logistics teams on coordinating across sites without adding headcount. Happy to connect either way.
The detail comes from their profile. The relevance is one sentence. The exit removes the obligation.
2. The recent change
Hi Tom, congratulations on the move to Head of Ops. First 90 days in that seat are usually equal parts firefighting and inheriting other people's decisions. Happy to be a useful connection while you sort out which is which.
Job changes are the single best trigger in B2B outreach, because the new person is actively re-evaluating everything. This note earns acceptance by being sympathetic rather than opportunistic.
3. The hiring signal
Hi Aisha, noticed you're hiring two more field techs. Usually that means demand is ahead of capacity, which is a good problem and an annoying one. We work with facilities teams on exactly that squeeze. Open to connecting.
A job posting is a public statement about a company's pressure points. It is also completely verifiable, which is what makes the note land.
4. The shared customer type
Hi Marcus, we both spend our time with independent pharmacy groups, which is a small enough world that connecting seems sensible. No agenda.
Works well for adjacent vendors and potential partners. "No agenda" is doing real work here.
5. The specific content reference
Hi Priya, your comment on the RFP thread last week about scoring criteria being written after the shortlist was the most honest thing I have read about procurement all year. Would like to follow your stuff.
Only send this if it is true. The specificity is the entire value.
6. The geography
Hi Dan, Manchester-based and working with a lot of the same trades businesses you seem to. Always useful to know who else is operating locally. Happy to connect.
Under-used, and genuinely effective for local and regional service businesses.
7. The honest cold open
Hi Sarah, this is a cold connection request, so: I work with operations leads at mid-size logistics firms and yours is exactly the profile I learn most from. No pitch coming. Ignore freely if not useful.
Naming what you are doing disarms the reflex. It works far better than it should, and it stops working the moment it becomes a template you send to everyone.
Warm and semi-warm
8. After a real meeting
Hi Tom, good to meet at the Manchester logistics breakfast. Your point about depot handovers being where the schedule actually breaks stuck with me. Connecting so I can keep up with what you're doing.
Reference something specific from the conversation. It is the difference between "we met" and "I was listening."
9. The mutual connection
Hi Aisha, James Whitfield suggested we connect, he thought our work on field scheduling would overlap with what you're building at Vantage. Happy to be introduced properly if easier.
Only use a name if that person would actually vouch for you. Getting caught on this is unrecoverable.
10. Same event, no meeting
Hi Marcus, we were both at the ops summit last week and I did not manage to say hello. Your session question about maintenance backlogs was the one everyone was talking about afterwards. Connecting belatedly.
11. The customer's colleague
Hi Priya, we already work with your colleague Sam on the Leeds site. Not looking to expand anything, just sensible to be connected with the wider team.
Explicitly disclaiming the sales motive is what makes this acceptable rather than presumptuous.
Events, communities and hiring
12. Before an event
Hi Tom, I see you're speaking at the logistics summit next month. Planning to be there for your session on depot automation. Connecting ahead so I am not a stranger in the queue afterwards.
13. Shared group
Hi Sarah, both in the Ops Leaders group and your answers in there are consistently the practical ones. Connecting to keep them in my feed.
14. Recruiting
Hi Aisha, not recruiting you today, but we hire field ops people regularly and your background is exactly the shape we look for. Worth being connected for whenever the timing is right.
The honesty about timing is what stops this reading as a bait and switch.
15. Re-engaging a dormant lead
Hi Marcus, we spoke about eighteen months ago when the timing was not right. No agenda now either, just keeping the door open in case things changed.
What separates a template from a real message
Take template one and hold it up next to a version that has lost the specificity:
| Version | What the reader concludes |
|---|---|
| "Saw you're running ops across three Northgate depots" | This person looked at my profile |
| "Saw you work in operations" | This person filtered a list by job title |
| "Impressed by your work in operations" | This person is running a script |
Same length, same structure, wildly different acceptance rates. The variable is not the template. It is whether the fact you inserted required any effort to find.
That is also the honest limit of scale on LinkedIn: you can automate the sending, the timing, the follow-up schedule and the record of who has already been contacted, but the moment you automate the observation itself, you are back to "impressed by your work."
Tools that help here are the ones that keep the discipline while leaving the judgement with you. Leads Ranger's LinkedIn campaigns build target lists from searches you already run, merge notes from each person's real role and company, and let you rehearse the entire campaign so you read every message before a single one is sent.
After they accept
An accepted connection with no follow-up is a rounding error. A rhythm that works:
- Day 1 to 2: short message referencing why you connected. Still no pitch.
- Day 5 to 7: something useful with nothing attached.
- Day 12 to 14: one clear ask that is easy to decline.
- Then stop.
If you want to go deeper on the follow-up half, our guide to multichannel outreach covers how LinkedIn touches sit alongside email and WhatsApp without the same person hearing from you three times in a week.
The one-line version
Write the note only you could have written to only that person. If you cannot, you have not researched enough to be sending it yet.
