---
title: "LinkedIn Connection Message Examples That Convert"
url: https://trysumora.com/blog/linkedin-connection-message-examples
markdown-of: https://trysumora.com/blog/linkedin-connection-message-examples
---

# LinkedIn Connection Message Examples That Convert

[Home](/)/[Blog](/blog)

Blog

# LinkedIn connection message examples

Nine connection message examples that actually get accepted — by intent (peer, customer, event, content fan) — plus the 300-character constraint, acceptance-rate mechanics, and what never to send.

By Devansh Ranjan · Published Aug 23, 2026

The connection request is the smallest unit of LinkedIn outreach and the one people get most wrong. The note has a 300-character cap — treat it as a feature. Nine examples that work, by situation:

## Peer / same-industry

> Hi \[Name\] — also building in \[industry\] and your take on \[specific post/topic\] was the best thing I read on it this month. Connecting with peers in the space.

## Potential customer (cold)

> Hi \[Name\] — work with \[niche\] teams in \[city\] and keep meeting \[their role\]s dealing with \[specific problem\]. No pitch attached to this request — just expanding the circle.

## After an event or webinar

> Hi \[Name\] — we were both in \[event\]'s session on \[topic\]. Your question about \[specific\] was exactly the one I had. Would like to stay connected.

## Content fan

> Hi \[Name\] — your \[newsletter/post series\] on \[topic\] is quietly the most useful thing in my feed. Connecting so I don't lose the thread.

## Shared group or alumni

> Hi \[Name\] — fellow \[group/alumnus\]. Noticed you moved into \[role/market\] recently and curious how you're finding it. (Congratulations, genuinely.)

## Referral-adjacent

> Hi \[Name\] — \[Mutual\] mentioned you're the person for \[topic\] at \[company\]. Connecting before I potentially waste their intro with a bad ask.

## After they engaged with your content

> Hi \[Name\] — saw your comment on \[your post/topic\]. You raised a point about \[specific\] that deserved more than a like. Connecting to continue it.

## Hiring-adjacent / collaboration

> Hi \[Name\] — not recruiting you! Your \[work/portfolio\] on \[project\] is the style we reference internally. Would value being connected.

## The graceful cold one

> Hi \[Name\] — no clever reason: I work with \[niche\] in \[city\], you run \[their thing\], and the overlap seemed worth a connection. Totally fine to ignore.

## Why these work

Pattern

Why it converts

Specific context first

Proves a human wrote it for them

Honest intent

Removes the "what do they want" delay

No ask in the invite

Acceptance is the only conversion target

Under 300 chars

Platform cap; forces clarity

What happens after the accept matters more — the sequencing is in our [LinkedIn outreach strategy playbook](/blog/linkedin-outreach-strategy-2026), and the pacing rules in [connection request limits](/guides/linkedin-connection-request-limits). More message patterns: [cold DM templates that book meetings](/blog/cold-dm-templates-that-book-meetings).

## Frequently asked questions

How long can a LinkedIn connection request note be?

300 characters. That cap is the design constraint: one specific sentence about them, one honest sentence about why you're connecting, nothing else.

Should I send a connection request with no note?

A blank invite from a stranger reads as automation. With a note, acceptance rates improve enough to matter at sequence scale — and every accept is a lead your follow-ups can reach.

How many connection requests should I send per day?

About 20/day on a warmed free seat, ~35 with Premium, inside weekly ceilings that ramp with account maturity — the full enforced table is in our LinkedIn connection request limits guide.

----

_Markdown twin auto-generated from the HTML page at build time. Source of truth: the HTML/_next data._