- A note only helps if it's specific. Generic note < no note < specific note.
- First message under 400 characters, no pitch, one easy question.
- Merge tags are not personalization. Recipients read
{{firstName}}as a robot. - Two or three follow-ups, then stop. Add value each time.
- Rewrite every template below. The reasoning is the reusable part.
Every template on this page will stop working eventually. That's not false modesty, it's arithmetic: a published template gets copied by thousands of people, lands in the same inboxes, and becomes recognisable within months. The people you're messaging have seen more cold outreach than you have.
So the useful part of any template is the structure underneath it, what each line is doing and why. Read the reasoning under each block, then rewrite the words in your own voice. A mediocre message in your voice beats a polished one in someone else's, because the second one is recognisable and the first one isn't.
The connection request: the note question
"Always personalise your connection request" is the most repeated advice in LinkedIn outreach, and the data behind it is a genuine mess. Rather than pick the study that makes the cleanest story, here is what the published figures actually say.
| Source | Acceptance: no note | Acceptance: with note |
|---|---|---|
| ~20M requests (largest published) | 26.37% | 26.42% |
| ~64M campaigns | 34.3% | 32.3% |
| ~16k invitations | Higher | Lower |
Two things stand out. The largest dataset finds a difference of five hundredths of a percentage point, which is another way of saying no difference at all. And where a gap does appear, it favours the blank request, modestly, a couple of points, not the transformation the advice implies.
On what happens after acceptance, the sources contradict each other outright. One reports blank requests replying at 20% against 15% for noted ones. Another, on a larger sample, reports the reverse and more emphatically: 9.36% with a note against 5.44% without. Both cannot be right, and neither publishes enough about how their campaigns were targeted for the difference to be resolvable from outside. Treat anyone quoting either number as settled fact, including us, before we checked, with suspicion.
Which gives a rule that doesn't depend on whose data you believe: if you can't fill 300 characters with something true only of that person, send it blank and spend the personalization on the first message instead. A blank request is ambiguous, and ambiguity is cheap to accept. A note that could have been sent to five hundred people removes the ambiguity and replaces it with a sales approach that arrived before you earned any attention.
Hi Priya, we both know Alex Grant, he mentioned your team rebuilt onboarding last quarter. Been down that road myself, would be good to connect.
Hi Tom, your post on killing the SDR-to-AE handoff stuck with me, particularly the bit about context loss. We tried something similar and got it half right. Happy to compare notes.
The first message after they accept
This is the message that decides everything, and the most common way to lose it is to treat an accepted connection as buying intent. It isn't. They accepted an ambiguous request. You have roughly one screen of a phone to give them a reason to care.
Three jobs, in order:
- Prove you looked. One clause that could only be written about them.
- Say what you noticed. An observation about their situation, not a description of your product.
- Ask something easy. A question they can answer in under ten words, ideally about their own opinion.
Thanks for connecting, Priya. Noticed you're running outbound across four reps' accounts, most teams that size are still doing it from one and wondering why volume caps out. Curious how you're splitting it. Territory, or by persona?
Thanks for the add, Tom. We spent most of last year trying to get reply rates above 8% on LinkedIn and mostly failed until we cut send volume in half. Counter-intuitive, still true. Are you seeing the same thing, or is volume still working for you?
Thanks for connecting, Sam. We pulled together the actual weekly invite ceilings by LinkedIn account type after getting three accounts restricted learning it the hard way. Happy to send it over if it's useful, no strings, it's a public page.
Follow-ups: add, don't ask
Most follow-ups fail for the same structural reason. "Just following up" and "bumping this to the top of your inbox" ask the recipient to do the work, to remember your first message, reconstruct why it mattered, and decide. That's a lot to ask of someone who has already implicitly declined once.
A follow-up that works brings something new, so it stands on its own even if the first message was never read.
One thing I forgot to mention: the reason volume caps out isn't usually the tool, it's LinkedIn's weekly invite ceiling. It's per account, so a second sender doubles your ceiling and a bigger daily number doesn't move it at all. Might be irrelevant to you, figured it was worth 20 seconds either way.
Last one from me on this, Priya. A team about your size was running 4 accounts at 25 invites/day each and hitting the weekly wall by Thursday every week. Dropping to 15/day and adding a fifth sender got them more total volume, not less. Worth a look at your numbers?
Closing the loop, Tom. I'll stop here. If outbound volume becomes a problem later, the weekly-ceiling thing is the first place I'd look. Good luck with the quarter either way.
| Touch | Timing | Job |
|---|---|---|
| Connection request | Day 0 | Get accepted. Blank unless you can be specific |
| First message | 1–2 days after accept | Give them a reason to care |
| Follow-up 1 | +3 days | New angle, teach something |
| Follow-up 2 | +5 days | Specific example or proof |
| Close-out | +7 days | End it honestly |
Five touches over roughly two weeks. If you are tempted to add a sixth, the honest read is that the targeting is wrong rather than the persistence insufficient.
Situational messages
Re-engaging someone who went quiet
Hey Sam, you mentioned Q3 was the realistic window when we last spoke. That's about now, so figured I'd check whether it survived contact with reality. No pressure if it slipped, most things do.
They changed jobs
Congrats on the move to Northwind, Priya. New role, so this is probably the wrong month to be thinking about outbound tooling, but it's usually also the one month you get to change how things work before the habits set. Worth a conversation in a few weeks?
Asking for a referral, not a meeting
Thanks for the reply, Tom, sounds like this isn't your area. Rather than guess, is there someone on the revenue side who'd actually care about LinkedIn sending limits? Happy to take it off your plate either way.
When InMail is the right call
InMail costs credits, arrives in a visually distinct inbox that senior people have been trained to ignore, and carries no relationship context. It earns its place in two situations: the person can't accept invites (a full queue, a closed profile), or you need to reach someone whose invite you'd rather not spend a slot on.
Subject: your weekly invite ceiling, not your daily one Priya, quick technical note rather than a pitch. If your team's LinkedIn sending has plateaued around 28 invites/day/account no matter what you set, that's the rolling weekly cap, not your tool. It's fixable, but not by raising the daily number. Happy to explain in three lines if useful. If not, ignore me and the credit's on me.
Personalization that actually works
The merge tag is the most over-rated tool in outbound. Recipients have learned to read "Hi {{firstName}}, I see you're at {{company}}" as exactly what it is, because they receive fifteen of them a week and the shape is unmistakable. A first name in the greeting is table stakes, not personalization.
| Tier | What it looks like | Reply-rate effect |
|---|---|---|
| Merge tags only | Name, company, job title | None, reads as automation |
| Segment-level | A line true of their role or industry | Modest, better than nothing |
| Trigger-based | Job change, funding, hiring, a post | Strong, implies a reason to write now |
| Genuinely specific | Something only true of that person | Strongest, and doesn't scale past ~30/day |
The practical resolution: segment tightly enough that a segment-level line is nearly as good as an individual one. Two hundred people who share one specific, painful problem can receive the same message and each feel it was written for them. Two thousand people who share only a job title cannot.
A checklist before you launch
Where the message meets the machine
Good copy and safe sending are the same project. A message that gets ignored lowers your acceptance rate, and a lower acceptance rate tightens the invite ceiling LinkedIn gives your account, so bad copy literally reduces how much you're allowed to send. This is why "send more" and "write better" aren't alternatives.
In Outvelo, each message step can carry variants that split evenly and report reply rate separately, so the question of which opener works is answered by the data rather than by argument. Sequences branch on whether someone replied, so a person who answers stops receiving follow-ups written for someone who didn't. How to structure the sequence covers the mechanics.
Where these numbers come from
Every acceptance and reply figure on this page is published by an outreach platform measuring its own customers' campaigns. Nobody in this category runs a controlled experiment: the populations differ, the targeting differs, and each vendor's number is partly a measure of how good their particular customers are at writing. That is why the studies disagree, and why we show the disagreement rather than averaging it into a single confident figure.
Reply rates vary enormously by market and list quality, treat everything here as direction, not a benchmark you should be hitting. If you have data that contradicts a number on this page, we would genuinely like to see it: [email protected].