12 LinkedIn Connection Request Message Templates That Get Accepted

A LinkedIn connection request message is the most under-optimized 300 characters in B2B outbound. Most reps leave the note blank or paste some variant of "I'd like to add you to my professional network" to 175 people a week — then wonder why acceptance is stuck in the low teens.

That note is the gate to every conversation that follows. Get it right and, in our experience, a relevant cold note lands in the 30s and a warm one runs from the mid-40s up into the 70s, while starting the relationship on the right foot. Get it wrong and you don't just get ignored — enough "I don't know this person" clicks and LinkedIn quietly throttles your account.

The good news: acceptance is mostly formulaic. It comes down to relevance, a specific reason to connect, and zero friction. Below are 12 copy-paste templates for the scenarios you actually run into, the psychology behind why they land, how to personalize them at scale without inventing familiarity you don't have, and the mistakes that get you ghosted or flagged.

Why your LinkedIn connection request message gets accepted or ignored

Before the templates, understand the levers. Every high-accepting note pulls at least two of these:

• Relevance. They can tell in one second why you, specifically, are messaging them, specifically.
• A reason that isn't a pitch. Give a human motive to connect, not a sales agenda. The note that sells gets declined.
• Zero friction. No question that requires homework, no link, nothing to schedule. The only ask is "accept."
• Specificity over flattery. "Great post" is noise; "your point about usage-based pricing" proves you actually read it.
• Ego and curiosity. People accept when a message makes them feel seen, or mildly curious about who you are.

The warmer the signal, the higher the ceiling. These are the ranges teams we work with typically see, not published research, and they move with your profile and your list:

The 12 LinkedIn connection request templates

Swap the {brackets} for real detail. Keep every note under the 300-character limit, and never send one without changing at least the name and one specific detail.

One rule sits above all twelve: every claim in the note has to be true for the person reading it. A mutual you barely know, a school that isn't on your profile, a newsletter you don't read, a conversation that never happened — each of these gets checked in one click, and at 25 requests a day per account a fabricated detail doesn't scale, it compounds. The templates that lean on familiarity carry an "only when true" guard below. The ones you can run at volume lean on facts you already hold: an engagement Sendpilot captured on your own post, a job change or funding round that's on their profile, a community you're both visibly in.

1. 01Cold ICP, relevance-first. "Hi {first name} — I work with {role}s at companies like {peer 1} and {peer 2} on {specific outcome}. Not pitching, just like to connect with people wrestling with {problem} this year. Open to it?"
2. 02They commented on or reacted to your post. "Hey {first name}, thanks for the comment on my post about {topic} — your point on {their point} stuck with me. Figured we should actually be connected." For people who only reacted, swap "thanks for the comment on my post about {topic}" for "thanks for the reaction on my post about {topic}" and drop the {their point} clause — a reactor didn't leave a comment, so don't thank them for one. This is one of the templates you can run at volume, because every fact in it comes from your own post: a Sendpilot inbound campaign captures everyone who engages with it and can transfer them into an outbound campaign. For the ones who only reacted, or who commented without hitting an Action Word, a connection request carrying this note is your first move — commenters who do trigger the automation get the public reply first, and the non-connections among them are asked to connect from their own side.
3. 03Mutual connection. "Hi {first name}, we're both connected to {mutual} — I worked with them at {company} for a few years, and your name came up when we were talking about {topic}. Thought I'd reach out directly." Only when true: send this only if you actually know {mutual} and that conversation happened. LinkedIn shows both of you the shared connection, so a made-up one is a single message away from being checked. Filter your list on shared connections you genuinely know before you attach this note; never rotate it into a cold sequence.
4. 04Same event or webinar. "Hi {first name}, we were both at {event}. Didn't get to say hi in person, but your question about {topic} was the best one in the room. Let's connect." Only when true: you were both there and they did ask that question. The event page makes the first half checkable in seconds; the second half is on you.
5. 05Competitor's customer. "Hi {first name}, noticed your team runs {competitor}. I talk to a lot of {role}s who've bumped into {known limitation} with it — curious how it's treating you. Happy to connect either way." "Noticed your team runs {competitor}" has to come from something you actually saw — a job post, a case study, their own post — not a guess.
6. 06Content compliment, specific. "Hi {first name}, your post on {topic} was the most useful thing in my feed this week — especially the bit about {detail}. Connecting so I don't miss the next one." {detail} is the proof you read it. If you can't fill it in, don't send it.
7. 07Shared background or alumni. "Hi {first name}, fellow {school or company} alum — I was there from {year} to {year}. Saw you're now leading {function} at {company}; would be good to have you in my network." Only when true: the school or company has to be on your own profile as well as theirs, because that is the first thing they will check. Build the list from that filter first — a LinkedIn or Sales Navigator search on school or past company, pulled with the Lead Extractor — rather than dropping this line into a general sequence and hoping.
8. 08Same group or community. "Hi {first name}, we're both in {community} and both weighed in on the {topic} thread — figured we should be connected here too." {topic} has to be a thread you both visibly posted in; the group feed shows it, so it's checkable in one click. If you can't name one, cut the middle clause and let the shared membership carry the note.
9. 09New role or promotion. "Congrats on the move to {company}, {first name}. The first 90 days running {function} are always a whirlwind. Sending a connect in case a fresh perspective on {area} is ever useful." The job change is on their profile, so this one runs at volume without a guard.
10. 10Growth signal: funding or hiring. "Hi {first name}, saw {company} just closed a round (or is hiring hard across {team}) — exciting stretch. I help teams grow {function} through exactly this phase. Would love to connect."
11. 11Podcast or newsletter follower. "Hi {first name}, I've been reading {newsletter or podcast} since {issue or episode} — your take on {topic} in {specific issue} changed how I think about {thing}. Had to connect." Only when true: name an issue or episode you actually read or listened to. If you can't, you are not a follower, and "I've followed you for a while" from a stranger reads as exactly what it is. This is a hand-written note for a handful of people, not a sequence step.
12. 12Re-connect after meeting. "Hi {first name}, we chatted briefly about {topic} back at {place} but never connected here. Fixing that — would be great to stay in touch." Only when true: you met. Name the place and the topic exactly so they can place you; if you can't, this is template 1 with a warmer opener, not template 12.

Notice what none of them do: pitch, drop a calendar link, run past three sentences, or claim something the reader can disprove. The note's only job is to earn the accept.

Personalization at scale without sounding like a robot

Personalization and volume feel like opposites. They aren't, as long as you personalize the right layer. Templatize the structure; personalize only the signal.

Trigger the request off a real signal

The highest-accepting requests aren't fired at cold lists. They go to people who just did something: commented on or reacted to your post, attended your webinar, changed jobs, closed a round. Warm the audience first, then reach out while you're still fresh in their memory.

This is where an All-Bound workflow earns its keep. Point a Sendpilot inbound campaign at one of your posts and set the Action Words. A comment containing one of those words is what starts the automation: Sendpilot replies to that comment publicly from your reply templates. Whether someone comments or only reacts, everyone who engages with the post is captured as a lead and scored against your ICP so you only spend requests on real buyers.

The DM behind that reply only reaches people you are already connected to. A commenter who isn't a connection gets the non-connection reply instead — the one that asks them to connect with you first — so the request arrives from their side, you accept, and the DM goes out. It is the one connection request you never have to write. For the engagers who don't act on that reply, and for the ones who only reacted, transfer the best-fit names into an outbound campaign and send template 2 as the connection request from your side, referencing the engagement you can both see. Either way your content becomes a self-refilling top of funnel, and every note in it is true.

Personalize the first line, templatize the rest

• The only variable that has to change is the opening reference: the post, the mutual, the trigger. Nail that and the rest can ride a proven skeleton.
• Rotate three or four templates per scenario so your outreach doesn't leave an identical footprint across hundreds of profiles.
• Send from a warmed, optimized profile. Your headline, photo, and banner do half the accepting before the note is even read.
• Keep daily volume human. Hold each account at about 25 connection requests a day — roughly 175 a week — and ramp a newly connected profile up to that over its first month rather than starting there. Ten established accounts give you around 1,750 requests a week without any one profile spiking. Sendpilot enforces that cap per account, gives every connected account a dedicated, geo-matched proxy and warms it up automatically; restrictions come from connecting one account to several tools at once or from sustained abuse, not from a steady 25 a day. The full ramp is in our guide to LinkedIn connection request limits.

Mistakes that get you ignored or flagged

• Pitching in the note. The connect is a handshake, not a demo request. Sell after they accept.
• The wall of text. 300 characters is the ceiling, not the goal. Three tight sentences win.
• Generic flattery. "Love your content" with no specifics reads as automated, because it usually is.
• Links in the request. A cold link is the fastest route to a decline, or a report.
• Ignoring fit. Blasting outside your ICP tanks acceptance and teaches LinkedIn to distrust your account. Score before you send.
• Faking familiarity. "We met at…", "{mutual} says hi" or "long-time reader" sent to people for whom it isn't true is the fastest way to a decline and a report, and it burns the template for the people it would have been true for. Filter the list on the fact first, then attach the note.
• Over-automating. Pushing one profile past about 25 requests a day, or running it through two tools at once, is how you earn a restriction. LinkedIn acts on behaviour: cap the volume per account, vary the copy, and spread the load across accounts instead of spiking one.
• Never testing the blank note. For pure-cold prospects, a request with no note sometimes out-accepts a mediocre one. Test it — but when you do write a note, make it one of the twelve above.

The bottom line

Acceptance rate is the cheapest lever in your entire funnel. A weak note is fixed with relevance, a reason and restraint, not with more volume. Rewrite your default request with one of the templates above — the one whose claim is actually true for your list — and watch the number move this week.

Where Sendpilot fits

The templates are the copy. Sendpilot's outbound campaigns are how you run them across accounts without hand-sending: build a sequence — a connection request carrying one of these notes, a follow-up message, a voice note, a profile view or a post like — and run it from every LinkedIn account you connect, each on its own dedicated, geo-matched proxy, warmed up automatically and held to the 25-a-day cap.

Feed the sequence from the Lead Database, the Lead Extractor or an inbound campaign, score every lead against your ICP before a request goes out, and answer the replies from one Unibox. Plans are priced per connected LinkedIn account — never per user — from $79/month, or $66/month billed annually, on Launch; the full grid is on /pricing. Start a free trial and put your best note into a sequence this week.