LinkedIn Connection Request Message Templates That Get Accepted (2026)

Most connection request messages fail for the same reason: they sound like a pitch, not a person.

You know the ones. "Hi {first_name}, I'd love to connect and show you how our platform can 10x your pipeline." Delete. Ignore. Move on. The person on the other end has seen a hundred of those this month, and they have learned to pattern-match them in under a second.

The good news is that the bar is low. Because so many requests are obvious pitches, a request that sounds like a real human being noticing a real reason to connect stands out immediately. This guide gives you ten LinkedIn connection request message templates organized by use case, the personalization variables that make them scale, and the first message to send after someone accepts. Copy them, adapt them to your voice, and test relentlessly.

Why most connection requests fail

There are really only three reasons a connection request gets ignored:

1. It is obviously automated. Generic language, no specific reference to the person, and the unmistakable smell of a template that went to 500 people. Ironically, the fix is not to stop using templates. It is to use them as a starting point and personalize the part that matters.
2. It leads with the ask. The first message is not the place to sell. It is the place to earn a connection. Pitching before you have a relationship is like proposing on a first date.
3. There is no reason to connect. If the recipient cannot answer "why is this person reaching out to me specifically?" in the first line, they will not accept.

Fix those three things and your acceptance rate climbs on its own. Worth noting: the note itself is optional. Plenty of requests get accepted with no note at all, especially when your profile is strong and there is an obvious shared context. But a sharp, short note gives you control over the framing, so it is worth getting right.

The anatomy of a request that gets accepted

Strong connection notes tend to share a simple structure:

• A specific hook. One concrete thing about them: a post they wrote, a mutual connection, a shared group, a detail from their role at {company}.
• A reason that is about them, not you. Why connecting makes sense from their side.
• No ask, or a tiny one. At the request stage, "would love to connect" is enough. Save the real conversation for after they accept.
• Brevity. LinkedIn caps connection notes at 300 characters. That constraint is a gift. It forces you to be human and direct.

Keep it short, keep it specific, and keep the focus on them. Now the templates.

10 connection request templates by use case

Each template below uses personalization variables like {first_name}, {company}, and {position} so you can drop them straight into a sequence. Replace the bracketed plain-text placeholders (like [their post topic]) with a real detail before sending.

Template 1: Cold prospect (no prior connection)

Hi {first_name}, I have been following what {company} is doing in [their space] and the approach stood out to me. I work with similar teams on [outcome] and would value connecting with people doing the work. No pitch, just like to keep good people in my network.

Why it works: it names a specific reason, signals no immediate ask, and frames the connection as peer-to-peer.

Template 2: Mutual connection

Hi {first_name}, I noticed we are both connected to [mutual name]. [She/he] speaks highly of the work you are doing at {company}, so I thought it would be worth connecting directly. Always glad to expand the circle of people in [industry].

Why it works: borrowed trust. A shared connection is one of the strongest accept triggers there is.

Template 3: Same industry

Hi {first_name}, fellow [industry] person here. I am always trying to learn from others navigating the same challenges in {position} roles. Would be glad to connect and trade notes from time to time.

Why it works: positions you as a peer, not a vendor, and offers reciprocity.

Template 4: After they engaged with your post

Hi {first_name}, thanks for the thoughtful comment on my post about [topic]. You clearly think about this differently than most, and I would like to keep the conversation going. Connecting felt like the natural next step.

Why it works: it references a real, recent interaction. This is one of the highest-accept scenarios on the platform.

Template 5: Event or webinar

Hi {first_name}, we were both at [event name] this week. I did not get the chance to say hello in person, but [a talk/session] you might have caught lined up with a lot of what I think about. Would be glad to connect and continue the thread here.

Why it works: shared context plus a clear, time-bound reason.

Template 6: Alumni

Hi {first_name}, fellow [school] grad here. I always enjoy connecting with people from the [school] network, especially those who ended up in [industry] like you at {company}. Would be great to add you to my circle.

Why it works: shared identity is a fast trust shortcut, and it has nothing to do with selling.

Template 7: Recruiter to candidate

Hi {first_name}, your background in {position} at {company} caught my eye. I am not reaching out about a specific role today, just building relationships with strong [function] people for when the right opportunity comes up. Would be glad to connect.

Why it works: it is honest, low-pressure, and respects the candidate's time. The "not pitching a role today" framing lowers the guard.

Template 8: Founder to founder

Hi {first_name}, fellow founder here, building in [adjacent space]. I have a lot of respect for what you are doing with {company}, especially [specific detail]. Always glad to connect with people in the trenches. The road is more fun with company.

Why it works: peer recognition plus a specific, genuine compliment.

Template 9: Re-connect (lapsed contact)

Hi {first_name}, it has been a while since we [how you met/last spoke]. I came across your profile and saw you are now at {company} doing {position}, which looks like a great move. Would love to reconnect and hear how it is going.

Why it works: warmth and genuine interest in their progress, with zero ask.

Template 10: Value-first

Hi {first_name}, I put together [a resource/guide] on [topic relevant to them] that I think would be useful for someone in your role at {company}. Happy to share it once we are connected. No strings attached.

Why it works: it leads with something useful to them, which reframes the entire interaction as generosity rather than extraction.

Personalization variables that scale

The tension in outreach is always the same: personalization works, but personalizing one message at a time does not scale. Variables are how you resolve it.

In a tool like InstaLeadSync, fields such as {first_name}, {company}, and {position} are pulled automatically from each lead record and merged into the message at send time. That means a single template can go to hundreds of people and still address each one by name, at their company, in their role.

A few rules for using variables well:

• Always provide a fallback. If {first_name} is missing or malformed (an all-caps name, a company name in the wrong field), your message can read like a bug. Clean your list before you send, and prefer variables you trust.
• Do not over-stuff. A message that uses {first_name}, {company}, {position}, and {industry} in two sentences reads like a mail merge gone wrong. One or two well-placed variables feel natural; four feel robotic.
• Reserve the deepest personalization for the manual layer. Variables handle the scalable part. The truly specific hook, a comment on their post, a detail from their about section, is best added by hand for high-value prospects. The templates above are built to flex between both.

The goal is messages that feel one-to-one even when the structure is one-to-many.

What to say after they accept (the first message)

Acceptance is not the finish line. It is the start. And this is exactly where most people blow it: the request was human, then the moment the connection lands, out comes the pitch. The whiplash kills the relationship.

Your first message after connecting should do one thing: open a genuine conversation. Try one of these:

Thanks for connecting, {first_name}. I meant what I said, no pitch coming. What is keeping you busy at {company} these days?

Appreciate the connect, {first_name}. Curious, what is the biggest priority for your team this quarter? Always interested in how people in {position} roles are thinking about it.

Notice what these do not do: they do not mention your product, book a meeting, or send a link. They ask a question that is genuinely about the other person and invites a reply.

This is also where structure pays off. A good outreach tool lets you branch your follow-ups based on whether someone accepted and replied, versus accepted and stayed silent. Mapping out those paths in advance, rather than improvising, is what turns scattered messages into a real conversation. We go deep on this in our guide to branching LinkedIn sequences.

Testing and iteration

No template is universally the best. The best template is the one that works for your audience, your offer, and your voice, and you only find it by testing.

Here is a simple loop:

1. Pick one variable to test at a time. The hook, the length, the presence of a note at all. Change one thing so you can attribute the result.
2. Send to a meaningful sample. A handful of sends will not tell you anything. Give each variant enough volume to read a real signal, while staying inside safe daily limits. Sending too many requests too fast is the fastest way to a restriction, so pace matters. See our breakdown of LinkedIn connection request limits in 2026 before you scale volume.
3. Track acceptance rate, then reply rate. Acceptance tells you if the request worked. Reply rate tells you if the relationship is actually forming. In our experience, a strong, well-targeted request often lands well above a generic pitch, but your baseline depends entirely on list quality and how warm the audience is.
4. Keep a swipe file. When a message overperforms, save it. When one flops, note why. Over a few months you will build a library of what actually works for your market, which is worth more than any list of templates someone hands you.

Personalize the hook, lead with them, and never pitch in the request. Do that consistently and your connection requests will start sounding like a person, because they will be coming from one.

Frequently asked questions

Should I always include a note with my connection request?

Not always. Requests without notes can perform well, especially when you share an obvious context (same company, same event, mutual connections) and your profile clearly signals who you are. That said, a sharp note gives you control over the framing and is worth using for prospects who matter. Test both for your audience.

How long should a connection request message be?

LinkedIn limits connection notes to 300 characters, and shorter is usually better. One specific hook and one reason to connect is plenty. If your message needs three sentences to explain why you are reaching out, the reason probably is not strong enough yet.

Can I personalize connection requests at scale?

Yes. Personalization variables like {first_name}, {company}, and {position} let one template address each recipient individually. For high-value prospects, layer in a manual, specific hook on top of the variables. Keep volume inside safe daily limits so personalization at scale does not turn into spam at scale.

What is the biggest mistake in connection requests?

Pitching. Leading with what you sell, before you have earned any relationship, is the single fastest way to get ignored or marked as spam. The request stage is for earning a connection, not closing a deal. Save the conversation for after they accept.

How do I know which template is working?

Track two numbers: acceptance rate (did they connect?) and reply rate (did the conversation start?). Test one variable at a time, give each variant enough volume to read a real signal, and keep a swipe file of your winners. The right template for your market reveals itself over a few weeks of disciplined testing.

---

Want a system that personalizes at scale, branches your follow-ups, and keeps every send inside safe limits, using your own real LinkedIn session rather than a risky cloud server? Book a call and we will show you how InstaLeadSync puts these templates to work.