Most advice about the LinkedIn connection request message treats it as a miniature cold email. That is precisely why so many of them fail. The invitation note is not a pitch, a value proposition or an elevator speech. It has exactly one job: to make clicking accept feel like a low-risk, mildly interesting decision made in under two seconds.
This guide covers what the note is really doing, the character limit that decides your structure, five templates that survive contact with a real list, the openers that quietly destroy acceptance, and how to measure whether your copy or your targeting is the problem. There is also an honest section on when sending no note at all beats sending a good one.
What a LinkedIn connection request message actually has to do
Your prospect sees the LinkedIn connection request message inside a stack of other invitations, usually on a phone, usually while doing something else. They are not evaluating your offer. They are answering one question: is accepting this going to cost me anything?
Every element of a strong LinkedIn connection request message reduces perceived cost. Relevance signals you are not spraying. Brevity signals you will not be a burden. The absence of an ask signals there is no trap. Conversely, anything that hints at a sales sequence raises the cost, and the invitation is declined or ignored.
This reframing has a practical consequence. Your note should not mention your product, your results, a meeting, a demo or a calendar. Those belong in the message you send after acceptance, once you have earned a thread.
The character limit that shapes every LinkedIn connection request message
The note field caps at 300 characters, and free accounts are limited in how many personalised invitations they can send each month, alongside the separate commercial use limit on searching. Three hundred characters sounds generous until you write one. It is roughly two sentences and a sign-off.
More importantly, mobile truncation means the first 100 to 140 characters carry the decision. Anything after that is read only if the opening earned attention. Write to 180 characters as a working target, not 300.
| Length | Reads as | Typical outcome |
|---|---|---|
| 0 characters | Ordinary networking | Strong baseline, often the control to beat |
| 60–180 characters | A person who did five seconds of research | Best performing band |
| 180–300 characters | A prepared paragraph | Acceptable if genuinely specific |
| 300 characters, dense | A pitch in disguise | Worst performing, often reported |
Length is a proxy for effort in the wrong direction. A long note does not read as thorough; it reads as templated, because nobody writes three hundred characters by hand to a stranger.
Five LinkedIn connection request message structures that work
Each LinkedIn connection request message below is a structure rather than a script. Copy the shape, then fill it with something only you could have written about that specific person. The bracketed fields must be replaced with researched detail, not job titles pulled from the record.
1. The trigger note
The strongest structure available, because the reason for contact is external and verifiable.
“Hi [Name] — saw [Company] is hiring three [role] people this quarter. Usually means [specific consequence] lands on your desk. Following what you do here, would be good to connect.”
Triggers are the difference between a note that feels observed and one that feels generated. Funding rounds, job changes, hiring patterns and tooling shifts all work. Our guides to job postings as a buying signal and sales trigger events cover which ones predict a purchase rather than merely activity.
2. The content note
Reference something they published, and be specific enough to prove you read it.
“Hi [Name], your post on [specific point, not the topic] made me rethink how we handle [related thing]. The bit about [detail] especially. Connecting so I don’t lose the thread.”
The failure mode is naming the topic instead of the argument. “Great post about AI” proves nothing. Quoting the one claim you disagreed with proves everything.
3. The shared-context note
Mutual connections, groups, events, former employers and alma maters all lower perceived risk sharply.
“Hi [Name] — we both worked with [Mutual] at [Company], and I keep running into [Company] in [specific context]. Happy to connect.”
4. The peer-problem note
Useful when you have no trigger and no content to work with. It positions you inside their world without pitching.
“Hi [Name], I spend most of my week with [specific role] at [company type], and [specific problem] comes up in nearly every conversation. Curious whether it’s the same at [Company]. Worth connecting.”
Note the restraint. The question is genuinely open, and there is no product anywhere in it.
5. The plain note
Honest, short, and surprisingly effective on senior buyers who have seen every technique.
“Hi [Name] — I work in [space] and follow what [Company] is doing closely. No agenda, happy to be a useful contact. Would like to connect.”
Openers that quietly kill acceptance
These appear in most template roundups and each one signals a campaign. Cut them from every LinkedIn connection request message you send.
| Phrase | What the reader hears | Use instead |
|---|---|---|
| “I’d love to connect and share ideas” | Template, thousands sent | One specific observation |
| “I help [role] achieve [outcome]” | A pitch before hello | Nothing about you at all |
| “Quick question for you” | There is no quick question | Ask nothing in the note |
| “Expanding my network in [industry]” | Volume outreach | Why this person specifically |
| “Noticed we have shared interests” | Automation output | Name the actual shared thing |
| “Open to a quick 15 minutes?” | A meeting request from a stranger | Save it for after acceptance |
One rule underpins the whole table: if a phrase would work equally well sent to any of the two thousand people on your list, delete it. A note that fits everyone convinces no one.
When to send no LinkedIn connection request message at all
Blank invitations frequently beat written ones, and the reason is structural rather than psychological. An invitation with no note looks like ordinary networking, which is the most common thing on the platform. An invitation with a mediocre note looks like outreach, which is the thing people have learned to decline.
Send no note when the list is broad, when your personalisation would be a merge field, or when the prospect is senior enough to have seen every opener. Write one when you have a genuine trigger, a genuine mutual connection or a genuine reaction to something they published.
Test it properly: split one segment in half, keep everything else identical, and run at least 200 invitations per side before drawing a conclusion. Anything smaller is noise.
What happens after acceptance matters more than the LinkedIn connection request message
A high acceptance rate with no follow-through is a vanity metric. The connection is the door; the conversation is the room. Two mistakes destroy most of the value teams create at the invitation stage.
The first is pitching within minutes of acceptance, which retroactively confirms the note was bait. The second is waiting a fortnight, by which point they have forgotten who you are.
- Day 1–2: Thank them and reference the same specific thing from the note. Ask nothing.
- Day 4–6: Share something genuinely useful and unbranded, tied to their situation.
- Day 9–12: Make the first soft ask, framed as a question about relevance rather than a meeting request.
- Day 16–20: Move the thread to email or phone, where the conversation has room to develop.
That spacing is deliberate, and it mirrors the principles in our guide to sales cadence design. LinkedIn threads tolerate fewer touches than email, so each one has to be worth the interruption.
How to tell whether copy or targeting is the problem
Teams rewrite notes when they should be rebuilding lists. Diagnose it with two numbers rather than instinct.
| Acceptance | Reply after acceptance | Diagnosis |
|---|---|---|
| Low, under 20% | — | Targeting or profile, not the note |
| Healthy, 30%+ | Low, under 10% | Follow-up copy is the failure |
| Healthy, 30%+ | Healthy, 20%+ | Working; scale volume carefully |
| High, 50%+ | Very low | List is friendly but not in-market |
That last row catches out a lot of teams. Peers and adjacent roles accept readily and buy nothing. Check the fit of the list itself before congratulating yourself on the copy, and keep the underlying records clean, since stale titles produce notes addressed to the wrong job. Our guidance on B2B data accuracy covers the decay rates involved.
Volume also has a hard ceiling here. Whatever your copy achieves, the LinkedIn connection request limit governs how many people ever see it, which is why the note is one component of a wider sequence rather than a channel of its own.
A worked rewrite
Principles are easier to apply against a concrete example. Here is a LinkedIn connection request message of the kind most teams send, followed by the same intent rewritten.
Before, 268 characters: “Hi Sarah, I’d love to connect and share ideas. I help Heads of Operations at logistics companies reduce manual data entry by up to 40% using automation. We’ve worked with several businesses in your space. Would you be open to a quick 15-minute chat this week?”
Four separate problems. It opens with the most templated phrase on the platform, pitches a capability before any relationship exists, cites an unverifiable percentage, and asks a stranger for a meeting. Nothing in it could not have been sent to two thousand other people.
After, 171 characters: “Hi Sarah — saw you’re hiring two more ops coordinators for the Leeds site. That usually means the manual side has outgrown the team. Curious how you’re handling it. Worth connecting.”
The rewrite is a third shorter and asks for nothing. It names a specific, verifiable fact, draws an inference a practitioner would recognise, and expresses curiosity rather than intent. The product is absent entirely, which is why it works as an invitation rather than as an advertisement.
Personalisation that scales: what to automate, what to write
The practical tension is obvious. Genuinely individual notes take three or four minutes each, which caps a rep at a few dozen a day. Merge fields take seconds and read like merge fields. The resolution is not to pick a side but to segment the list.
| Tier | Share of list | Approach | Time per note |
|---|---|---|---|
| Tier one, named accounts | ~10% | Written individually after real research | 3–4 minutes |
| Tier two, strong trigger | ~30% | Structure plus one researched detail | 45–60 seconds |
| Tier three, ICP match only | ~60% | No note at all | Zero |
That distribution reflects where the return actually sits. Spending four minutes on a tier-three prospect produces a slightly better note to someone unlikely to buy; spending it on a tier-one account produces a conversation. Sending no note to tier three is not laziness, it is the correct allocation, and it usually performs at least as well as the template you would otherwise have used.
The variables worth automating are the ones carrying real information: a funding round, an open role, a technology in the stack, a recent move. The ones that add nothing are first name, company name and job title, all of which the reader can already see.
Frequently asked questions about the LinkedIn connection request message
How long should a connection note be?
Aim for 60 to 180 characters. The field allows 300, but mobile truncation means the opening 100 or so decide the outcome. Two sentences is usually the right shape.
Can I automate personalised notes?
You can insert variables, but understand the trade-off. Merge fields produce notes that read as templates, and automation of any kind sits outside the LinkedIn user agreement. Variables that reference a trigger or a published post do real work; variables that insert a first name and a company do not. Our review of LinkedIn automation tools explains the risk profile.
What acceptance rate should I expect?
Between 25% and 40% on a well-targeted cold list. Warm lists with mutual connections or trigger relevance run higher. Below 15% you should stop sending and fix the list, because low acceptance is also what draws restrictions.
Should I mention my company in the note?
Only if the company name itself is the credibility, such as a shared customer or a well-known former employer. Otherwise leave it out. Your profile already carries that information for anyone who wants it.
Is it worth following up on an unanswered invitation?
You cannot message someone who has not accepted, so the follow-up has to happen elsewhere. This is exactly where email and phone earn their place, and where a multichannel outreach sequence outperforms a LinkedIn-only motion.
Write fewer notes, write them properly
A good LinkedIn connection request message is short, specific to one person, and asks for nothing. It survives the two-second test because it costs the reader nothing to accept. Everything else you want to say has a better home in the thread that follows.
ZenBee pairs verified contact data and live buying signals with LinkedIn and email sequencing, so the detail in your note comes from a real trigger rather than a merge field. Request a demo or explore ZenBee for sales teams.