Resumer

Skip to article
5 min read

LinkedIn connection requests: messages that don't get ignored

Most LinkedIn connection requests are sent without a note. The ones with notes are mostly bad. Here's what actually gets accepted and replied to.

linkedinnetworkingtemplates
LinkedIn connection requests: messages that don't get ignored
On this page
  1. 01What recruiters and peers actually accept
  2. 02Templates that work
  3. 03What flops, and why
  4. 04When to send no note
  5. 05The "I'm looking" version
  6. 06What to do after they accept
  7. 07Volume vs. quality
  8. 08What this isn't
  9. 09Sources

LinkedIn connection requests are the most-used tool in modern job search and the most-misused. Most candidates default to the platform's prompt ("I'd like to add you to my professional network") or, slightly better, a vague one-liner about "wanting to learn from your experience." Neither is actively bad. Neither does much, either.

This post is what actually gets accepted and replied to: specific, small, and not asking for anything in the first message.

What recruiters and peers actually accept

Acceptance rates by approach

What recruiters and peers actually accept
0%100%
25%

Cold connection request with no note — accepted, but no reply follow-on.

0%100%
55%

Cold request with a specific, non-asking note — accepted, often replies.

0%100%
80%

Warm request mentioning a mutual contact by name — accepted with reply.

A useful baseline. No-note connection requests get accepted at roughly 25% in cold cases — the connection happens but no real conversation follows. A specific note that's not asking for anything (referencing a post, a shared employer, a piece of writing) pushes acceptance to around 55%, and crucially, gets actual reply-text in a meaningful fraction of cases. Warm requests that mention a mutual contact land closer to 80% acceptance with replies.

The pattern: specificity helps the most, and the absence of a direct ask in the first message helps almost as much. A connection request that asks for a job, a referral, or a call in the first 200 characters reads as cold-pitch and gets ignored.

Templates that work

Four working templates by relationship

Use the one that fits
Cold + content-based
Saw your post on X

'Hi [name] — saw your post on [specific topic]. The bit about [specific point] matched what I've been working on in my own team. Connecting.' Works best with someone who posts publicly. Reference the actual content, not the existence of content.

Cold + shared context
We both worked at X

'Hi [name] — we both worked at [company] (different teams). Connecting in case our paths cross again.' Works on alumni, former coworkers, anyone with overlapping orgs in their history.

Warm + mutual contact
X mentioned your work

'Hi [name] — [mutual contact] mentioned your work on [topic]. Wanted to connect — would love to hear more about that work.' Single most effective opener. Mention the contact by name.

Conference / event
Met at X

'Hi [name] — enjoyed your talk at [event] / chat about [topic] at [event]. Connecting.' Within 48 hours of the event. Be specific about what you remembered.

Four templates cover most situations:

Cold + content-based. "Hi [name] — saw your post on [specific topic]. The bit about [specific point] matched what I've been working on. Connecting." Works on anyone who posts publicly. Reference the actual content; the existence of content is not enough.

Cold + shared context. "Hi [name] — we both worked at [company] (different teams). Connecting in case our paths cross." Works on alumni connections, former coworkers, anyone with overlapping orgs.

Warm + mutual contact. "Hi [name] — [mutual contact] mentioned your work on [topic]. Wanted to connect — would love to hear more about that work." Single most effective opener available. Use the mutual contact's full name; vague references ("a friend in common") underperform.

Conference / event. "Hi [name] — enjoyed your talk at [event] / chat about [topic] at [event]. Connecting." Within 48 hours of the event. Be specific about what you remembered.

For the longer-form conversation that follows a successful connection, see informational-interview-script.

What flops, and why

Templates that work vs. templates that flop

Side by side
Templates that work (specific + small)
  • 'Hi [name] — saw your post on [topic]. The bit about [specific point] matched what I've been thinking. Wanted to connect.'
  • 'Hi [name] — we both worked at [company] (different teams). Connecting in case our paths cross.'
  • 'Hi [name] — read your piece on [topic]. Sharp take on [specific thing]. Connecting.'
  • 'Hi [name] — [mutual contact] mentioned your work on [topic]. Worth connecting.'
  • (No note) — for casual peer / industry connections, no note is fine
Templates that flop (vague + asking)
  • 'Hi [name] — I'd love to connect and learn from your experience.'
  • 'Hi — I'm looking for opportunities at [their company]. Could we chat?'
  • 'Hi [name] — would love to add you to my professional network.'
  • 'Hi [name] — I think we'd be great connections!'
  • (Note that pitches a product/service in line 1)

The patterns that flop share three properties: they're generic enough to be sent to any of 10,000 people, they imply an unstated ask in the first message, or they pitch something.

"I'd love to connect and learn from your experience" is the canonical bad request. It's harmless, but it signals you have no specific reason to be reaching out. Acceptance is OK; reply rate is near zero.

"I'm looking for opportunities at [their company]" is too direct an ask for a first message. The recipient feels obligated to either help with something they don't know if you're qualified for, or to politely deflect. Most pick the latter.

Pitching a product or service in line 1 is the fastest path to a decline-and-block. LinkedIn users have been trained to recognize this pattern within five words.

When to send no note

A specific case worth naming: for casual peer or industry connections — people in your field at your level, people you'd recognize at a conference, people who follow some of the same accounts you do — no note is fine. The platform's prompt is fine. The acceptance rate is decent and there's no reason to over-engineer the message.

The cases that require a note: anyone senior to you by more than one level, anyone you've never interacted with before, anyone who could plausibly be receiving 20+ requests per week, and anyone you'd like to actually reply to you.

The "I'm looking" version

A common subcase: you're job searching and want to signal it via your connections. The wrong way is to put it in the first message ("I'm looking for X, can you help?"). The right way is to make your profile do the work — LinkedIn's "Open to work" feature, your headline, your About section — and then send a connection request that's not about your search. Once they accept, your profile carries the signal.

For the broader question of how to position yourself for inbound discovery, see linkedin-headline-patterns-that-work. For the existing recruiter outreach script, see recruiter-outreach-script.

What to do after they accept

The biggest mistake people make after a successful connection is to immediately follow up with a long pitch. Don't. The connection alone is the unit of progress.

If you do want to follow up — and it's reasonable to within a week or two — keep the second message proportional to the first. "Thanks for connecting — saw you also worked on [project]. Curious what your read on [specific thing] is, when you have a minute" is fine. "Now that we're connected, I'd love to set up a call to discuss opportunities" is not — it converts a low-cost interaction into a high-cost ask before the relationship has earned it.

Volume vs. quality

A common candidate question: should I send 50 cold connection requests a week or 5 thoughtful ones? The honest answer is closer to the second. The reply rate on 5 thoughtful requests typically outperforms the reply rate on 50 templated ones, and the relationships that come out of the thoughtful path are usually more useful.

LinkedIn also rate-limits aggressive senders — going above ~50 requests in a short window can trigger account warnings or restrictions, especially if acceptance rates are low. The thoughtful approach is both more effective and less risky.

What this isn't

A few clarifications:

  • It's not a script to copy verbatim. The specificity is the point; copying the exact words drops the specificity.
  • It's not a substitute for actual reasons to connect. Reaching out to someone you have no real reason to know rarely leads anywhere. Start with people whose work you've actually engaged with.
  • It's not the place to share your resume. Don't attach files in a connection request. Don't paste your resume into the message field. The connection is the first step, not the last.

The short version: be specific, be small, don't ask for anything in the first message. Mention a real piece of their work or a real shared context. The note is the difference between accepted-and-forgotten and accepted-with-a-real-reply.

More to read