LinkedIn Connection Request Message Templates
That Get Accepted

What makes a LinkedIn connection request get accepted

A request that lands has four parts, and it fits in a sentence or two. Hook, context, reason, tiny ask. That's the whole anatomy.

• Hook. One real detail. Their post, a mutual connection, the event you both attended.
• Context. Who you are in one phrase, so you're not a stranger.
• Reason. Why you want to connect, in plain words.
• Tiny ask. "Would like to connect." Not "Can we hop on a call?"

LinkedIn gives you 300 characters in the "Add a note" box. Don't use all of them. The sweet spot is under 180 characters, roughly 75 words, so the note doesn't get truncated on mobile where most people read it. Short and specific beats long and polished every time.

Does it actually move the number? Yes. A note that names something specific (their post, your mutual connection, the event you both attended) lands far more often than a blank request or a generic "I'd love to add you to my network." The detail is what does the work, not the word count. One real line beats four polished ones.

The 5 rules before you copy any template

Templates are a starting point, not a send button. Break these five rules and even a good template gets ignored or reported.

1. Personalize one real detail. Not just {{first_name}}. That's a mail merge and everyone can tell. Name a post, a company change, a shared group.
2. Never sell in the request. The note opens a door. It doesn't close a deal. Pitch in the request and you get the "Ignore" button.
3. Never paste a link. A URL in a connection note reads as spam and tanks acceptance. Save it for later, after they've said yes.
4. Never ask for a meeting. "Can we hop on a 15-minute call?" to a stranger is too big an ask. The only ask in the note is the connection itself.
5. Send on a trigger. A job change, a new post, a funding round, a comment they left. Reaching out because something just happened beats reaching out for no reason.

Here's the do and don't side by side, because the difference is small but it's everything.

12 connection request templates that get accepted (by scenario)

Copy these, swap the placeholders in brackets for one real detail, and keep them short. Each one names when to use it.

1. Mutual connection

Use when you share someone in common. The name does the trust work.

Hi [Name], we're both connected to [Mutual]. I work in [field] too and liked your take on [topic]. Would be glad to connect.

2. Recent-post engagement

Use right after they post something you actually read.

Hi [Name], your post on [specific point] matched what we're seeing on a small team. Would like to follow your stuff and connect.

3. Alumni

Use when you went to the same school or program.

Hi [Name], fellow [School] grad here. Saw you're now in [role] at [company]. Always happy to connect with people from [School].

4. Event or webinar

Use within a day or two of the event, while it's fresh.

Hi [Name], we were both at [event] this week. [One thing from a session] stuck with me. Would like to connect and keep comparing notes.

5. Recruiter to candidate

Use when you're hiring and want to open a low-pressure line.

Hi [Name], your [skill] background fits a [role] we're growing at [company]. No pitch yet, just would like to connect and share more later.

6. Candidate to recruiter

Use when you're job-hunting and want to be on their radar.

Hi [Name], I'm a [role] focused on [niche] and saw you hire in this space. Would like to connect in case the right [role] opens up.

7. Former colleague

Use to reconnect with someone you actually worked with.

Hi [Name], we overlapped at [company] back in [year]. Saw you're at [new company] now. Would be good to reconnect properly.

8. Industry peer

Use for someone doing the same job at a different company.

Hi [Name], we're both [role] in [industry] and run into the same [problem]. Would like to connect and trade what's working.

9. Thought-leader appreciation

Use for someone whose content you genuinely follow. Be specific, not gushing.

Hi [Name], your breakdown of [specific idea] changed how I run [task]. Would like to connect and keep learning from your posts.

10. Career transition

Use when you're moving into a new field and building it out.

Hi [Name], I'm moving from [old field] into [new field] and you've done it well. Would like to connect and learn from your path.

11. Problem-solver / value-first

Use when you can offer something small and useful, not a pitch.

Hi [Name], noticed [specific thing] on your team's [page or post]. I've solved that exact thing before. Happy to connect and share what worked.

12. Cold but specific

Use when you have no warm tie but did your homework. The detail carries it.

Hi [Name], saw [company] just [specific move]. I work with [similar companies] on [related thing]. Would like to connect, no agenda.

Trigger-based templates: the highest-acceptance play

The single best way to lift acceptance isn't better wording. It's better timing. A trigger is a real event that just happened: a job change, a funding round, a new post, a comment they left. When you reach out the day after the trigger, the personalization writes itself, and the timing makes you look like a person paying attention, not a list working through names.

Evergreen templates work for outreach you can send any week. Trigger templates work because of when you send them. The job change is fresh. The funding is news. That's why a trigger note beats a "saw your profile" note nearly every time.

Three that pull well:

Job change: Hi [Name], congrats on the move to [company]. First [X] days in a new [role] are a lot. Would like to connect as you settle in.

Funding round: Hi [Name], saw [company] just closed your [round]. Scaling [team or function] right after is the hard part. Would like to connect.

Their comment: Hi [Name], your comment on [poster]'s post about [topic] said exactly what I think. Would like to connect and keep the thread going.

The catch: triggers are time-sensitive. A "congrats on the new role" note three months late is worse than no note. The whole point is you caught it while it mattered.

What to send after they accept (the part that converts)

Acceptance is the start, not the win. Most people either say nothing after a connect, or they pitch within the hour. Both waste it. The job of the first message after they accept is to open a conversation, not to sell.

A simple sequence that works:

1. Day 0 (right after accept): a one-line thank-you tied to why you connected. "Thanks for connecting, [Name]. Loved your point on [topic]."
2. Day 2 to 3: a genuine question about their work. No ask, no link. You're learning, not selling.
3. Day 5 to 7: if it's relevant, offer something small and useful. A resource, a quick observation, a name they should meet.

Notice there's no pitch in the first three touches. If what you do is relevant, the conversation gets there on its own. Lead with the pitch right after they accept and most people stop replying. You won the connection and lost the conversation.

Why great templates still get ignored: the account problem nobody mentions

Here's the part every template listicle skips. Your copy can be perfect and your requests still underperform, because acceptance isn't only about the words. It's about whether LinkedIn is even letting your requests land at full strength.

A new, cold, or flagged account gets quietly throttled. Push past the weekly invitation cap and you don't get a pop-up. You get soft-restricted: requests go out slower, show up less, and your acceptance rate drops for reasons that have nothing to do with the template. The exact ceiling is covered in our weekly invitation limit guide.

One trap is specific to requests and worth flagging here: the withdraw-and-wait trap. Withdraw an invite and you can't re-invite that person for up to 3 weeks. Pending requests also auto-expire after 6 months. Yanking invites to "clean up" can lock you out of the exact people you wanted to reach.

So before you blame the copy, check the account. For the daily and weekly numbers plus a calculator, see our LinkedIn connection limits guide. The short version: a great template can't save a restricted account.

How to scale personalized requests without getting flagged

We run automation on more than 1,000 LinkedIn accounts, so this isn't a guess. The accounts that send personalized requests at volume without getting throttled all do the same handful of things: they warm up before volume, keep one dedicated residential IP, skip the browser-extension footprint, and send on human-paced gaps instead of a fixed daily count.

Two of those are deep topics in their own right. The day-by-day warm-up ramp is covered in our safe automation guide, and why a residential IP plus cloud tooling stays invisible while extensions get caught is in our cloud vs browser-extension breakdown.

One honest caveat: automation breaks LinkedIn's User Agreement, which bans third-party tools and bots. No tool removes that risk, ours included. The steps above lower it, they don't erase it. If you want the full picture on what actually triggers a ban, we wrote that up separately. For this article, the takeaway is simple: the template and the account both have to be right.

Personalization at scale: templates plus intent signals

Sending more requests usually means sending worse ones. The fix isn't to write 200 notes by hand. It's to keep the messages specific while you scale, which comes down to two things done right.

First, merge fields with one real anchor, not just a name. Pull a recent post, a job change, or a shared group into the variable so each note has a detail that could only apply to that person. Second, segment by intent signal so you only reach out when something actually happened, like a job change, a funding round, or post engagement. That's what makes the trigger templates above work at volume instead of degrading into spray-and-pray. We cover the full list of buying signals in our LinkedIn intent signals guide.

This is exactly where Linkedify's intent-signal targeting fits. The AI watches LinkedIn for those buying signals and fires the right template at the right moment, on warmed accounts with a dedicated residential IP included, from $25 a month for an automation seat. Personalized copy and a protected account, doing the work together instead of fighting each other.