← All resources

LinkedIn Connection Request Messages That Get Accepted

Quick answer

The note has almost no effect on whether someone accepts your request, that comes down to your profile and how well you targeted the list. The note's real job is what happens after acceptance: it roughly doubles your reply rate versus a blank request. Write one when there is a genuine reason to (a shared context, a specific trigger, a warm-ish signal), skip it when there isn't, and stop treating the invite note as your main lever.

Why the note matters less than you think

I'm Hlib Storchak. I build outbound systems for B2B founders and sales teams, and most of what follows comes from running LinkedIn as a channel for clients, not from a single case study I read once. Cold email gets most of the deliverability debate, but LinkedIn connection notes get more folk wisdom per word than almost anything else in outbound: "always personalize," "never pitch," "mention something specific about their post." Most of it treats the note as the thing that decides whether someone accepts you.

The data does not agree with that. Acceptance is decided mostly upstream of the note, by your profile and by who you are asking. The note decides something else, whether the connection turns into a conversation. That is a useful distinction because it changes what you should actually spend time optimizing.

What the data actually shows

Three independent datasets point the same direction, so I'm citing all three rather than picking the one that sounds best.

Leadriver analyzed more than 50,000 LinkedIn connection requests and found campaigns cluster into bands: below 25% is poor, 25 to 40% is standard B2B performance, above 40% is high, and only tightly targeted, deeply personalized campaigns clear 55% or higher. Rates under 20% signal a profile or targeting problem, not a copywriting one. Source: Leadriver's benchmark analysis.

Botdog analyzed 16,492 real invitations and found a 37% overall acceptance rate, comfortably inside Leadriver's "standard" band. The detail that matters most for this article: in that dataset, requests sent with no note at all outperformed requests sent with a personalized message on raw acceptance. The same analysis found 63% of all acceptances happen within the first day and 88% within a week, so a request that is going to land, lands fast. Source: Botdog's acceptance-rate study.

Expandi's 2026 outreach benchmarks, built from 13.2 million data points, put the platform-wide average acceptance rate at 28.5%, again landing in the same standard band. The more interesting number is on replies: the reply rate to the connection note itself fell from 3.5% in May 2025 to 2.2% by April 2026, a steady decline, while the reply rate to a message sent after acceptance held steady around 10.4% over the same period. Source: Expandi's 2026 benchmark report.

Read this straight. None of these three sources agree on an exact number, and I'm not pretending they do. What they agree on is the shape: acceptance sits somewhere in the mid-20s to high-30s for most B2B senders, the note is not the main acceptance lever, and the note's real value has shifted toward the reply it earns after someone says yes, not the yes itself.

Step 1: fix the profile first

Before you write a single note, look at what the person sees when they get your request: your photo, your headline, your current title, and whether your profile reads like a real operator or an obvious lead-gen account. Leadriver's own risk threshold, sub-20% acceptance, is almost always a profile or list problem, not a message problem. A generic sales headline ("Helping companies grow revenue") reads as spam before your note is even opened. A specific, human headline that states what you actually do reads as a person.

This is the highest-leverage step in this whole playbook and it is the one people skip because it feels like admin, not strategy.

Step 2: narrow the list

Acceptance rate is mostly a function of relevance. A tightly scoped ICP list, the right seniority, the right industry, ideally a real trigger (they just posted about a problem you solve, they just changed roles, their company just raised or hired), will out-accept a broad list every time, note or no note. If your acceptance rate is stuck below 25%, tighten the list before you touch the copy.

Request typeTypical acceptanceTypical reply after acceptWhen to use it
Blank, no noteSimilar to, sometimes above, a noteLowestBroad list building, no time to personalize each one
Generic templated noteSimilar to blankLow, reads as automatedRarely worth it, adds effort for little gain
Specific, context-led noteSimilar to blank on average, higher for warm-ish targetsMeaningfully higherNamed accounts, warm-ish signals, small target lists

Step 3: decide if you need a note

Given the data above, treat the note as optional by default, not mandatory. I write one when at least one of these is true: there is a genuine shared context (mutual connection, event, group), there is a real trigger tied to your offer (a job change, a hiring post, a funding announcement), or the account is small enough in your total list that the extra minute per note is worth it. I skip it when I'm running volume against a broad, well-targeted list and the marginal minute is better spent elsewhere, like the message I'll send after they accept.

Step 4: four frameworks that work

When I do write a note, I use one of four shapes, depending on the trigger.

1. The mutual-context note. Name the actual shared thing, a group, an event, a mutual connection, in one clause, then stop. "Saw we're both in [group], following your posts on [topic]." No pitch.

2. The trigger note. Reference something that just happened to them, specifically. "Congrats on the [role] move, curious how you're thinking about [relevant problem] in the new seat." Specific enough that it could not have been sent to anyone else.

3. The peer note. Position yourself as doing adjacent work, not selling. "I work with [role]s on [problem], would like to stay in each other's network." This works best account to account, not as a disguised pitch.

4. The zero-ask note. No CTA at all, just a reason to connect. Counterintuitively this often gets the highest reply rate after acceptance, because it does not put the other person on the defensive on message one.

Step 5: write it line by line

Whichever framework you pick, the mechanics are the same. Open with the specific reason, one clause. Do not pitch, do not mention your product, do not ask for a call in the invite note itself, that conversation belongs in the message after they accept. Keep it under 300 characters, LinkedIn's own note limit forces this anyway, but shorter reads more human regardless of the limit. Sign off with your first name only if it does not read as a template. Read it back and ask: could this exact sentence have been sent to a random stranger? If yes, cut it and start over.

Step 6: timing and follow-up

Since most acceptances happen fast, most within a day and nearly all within a week per Botdog's data, do not follow up on a pending request for at least a week, and consider letting it expire rather than re-sending, which can flag your account. Once accepted, send your first real message within 24 to 48 hours while the context is still fresh. Waiting longer drops your reply odds noticeably, people forget why they said yes.

What to do after they accept

This is the step the "get the note right" obsession quietly skips past, and it is where the real reply-rate gain sits per Expandi's data: a 10.4% steady reply rate on the post-accept message versus a 2.2% and falling reply rate on the note itself. Send a short, no-pitch first message that references the same context as your note (or introduces one if you sent blank), and only make an actual ask on message two or three, once there has been some back and forth. This is the sequence I build for clients: connect, light-touch message, value or relevance point, then the ask, spread over several days rather than crammed into the first hour.

Mistakes that quietly tank acceptance

The mistake I see most often when I take over a client's LinkedIn seat is a profile optimized for the person's ego (job title, company logo, a headline that reads like a resume) instead of for the stranger deciding whether to accept a request from them. Close behind: pitching in the invite note, which several of the datasets above tie to lower reply rates even when it does not tank acceptance outright. Third: running volume against a broad list and blaming the message when the real problem is targeting. Fourth: following up on a pending request too soon, which reads as pushy and can trigger LinkedIn's own automation flags. Fifth: treating every note like a template, when the entire value of a note, when you use one, is that it could not have been sent to anyone else.

Key takeaways

  • Acceptance is decided mostly by profile and targeting, not by the note. Fix those first if you're under 25%.
  • Across three independent datasets, blank or lightly personalized requests perform close to, sometimes better than, heavily personalized ones on raw acceptance.
  • The note's real value shows up after acceptance: reply rates to post-connect messages held around 10.4% while reply rates to the note itself fell to 2.2% in Expandi's 2026 data.
  • Write a note only when there's a genuine trigger or shared context. Otherwise spend the time on your first post-accept message instead.
  • Most acceptances happen within a day, nearly all within a week. Don't chase a pending request, let it expire.

FAQ

What is a good LinkedIn connection request acceptance rate in 2026?

Based on Leadriver's analysis of 50,000+ requests and Expandi's 13.2-million-data-point benchmark, 25 to 40% is standard B2B performance, with anything under 20% signaling a profile or targeting problem rather than a copy problem.

Do personalized connection notes actually get accepted more often?

Not reliably, according to Botdog's analysis of 16,492 invitations, which found blank requests performed as well as or better than personalized ones on raw acceptance. Personalization's bigger effect shows up in the reply rate after someone accepts, not in whether they accept.

Should I skip the note entirely on LinkedIn connection requests?

For broad-list volume, it's a reasonable default. Add a note when there's a genuine shared context or trigger, since that's when personalization earns its keep, mainly through a better reply rate once the person is connected.

How long does it take for a LinkedIn connection request to get accepted?

Per Botdog's data, 63% of acceptances happen within the first day and 88% within the first week. If a request hasn't landed within a week, it's unlikely to convert, so don't burn effort chasing it.

What should I send after someone accepts my connection request?

A short, no-pitch message within 24 to 48 hours that references the same context as your note, or introduces one if you connected blank. Save the actual ask for message two or three, after some back and forth.

Want your LinkedIn motion built and run properly?

There are three ways I work with B2B teams on this: done-for-you outbound, where I build and run the engine end to end; fractional Head of GTM, where I plug in as your GTM lead across channels; or building the function inside your own team, so your people can run it without me once it's live.

Book a call

Hlib Storchak has booked 2000+ meetings for B2B clients across cold email and LinkedIn, and runs a Salesforge-based stack for sending, Leadsforge for lead data. If you want a second opinion on your LinkedIn or multichannel outbound mix, book a call or browse the resources hub.