← Blog
    linkedin

    LinkedIn Connection Request Message Examples: 7 (2026)

    Adding a note to a LinkedIn connection request barely changes whether it is accepted. Acceptance is nearly identical with a message and without it, 26.42% versus 26.37%. But the note nearly doubles what happens next: reply rate is 9.36% with a message and 5.44% without.

    Ashish RathodHead of GTM·8 min read·September 3, 2026

    Adding a note to a LinkedIn connection request barely changes whether it is accepted. Acceptance is nearly identical with a message and without it, 26.42% versus 26.37%. But the note nearly doubles what happens next: reply rate is 9.36% with a message and 5.44% without.

    So send the note for the conversation, not the connection. Keep it under 200 characters, personalize it to something specific, and never put a pitch in it. This post has seven examples and the acceptance-rate benchmarks to measure against.

    A LinkedIn connection request message is the optional note, capped at 300 characters, sent with a request to connect. It has little effect on whether the request is accepted but roughly doubles the recipient's reply rate afterward. Effective notes are under 200 characters, reference something specific about the person, and contain no sales pitch.

    Do LinkedIn connection request notes work?

    For acceptance, no. For starting a conversation, yes. Adding even a brief message lifts the reply rate to 9.36%, against 5.44% with no message, and personalized messages get 44% more acceptances and 67% higher response rates than generic ones.

    The takeaway: if your goal is just a bigger network, skip the note. If your goal is to talk to the person, always include one. And because the note barely affects acceptance, there is no downside to always sending one for sales outreach, where a reply is the whole point. The only way the note hurts is if it is a pitch, which suppresses the reply rate it was meant to raise.

    Acceptance rate benchmarks

    • Average for cold, personalized B2B: 28% to 37%, holding stable across 13.2 million requests from May 2025 to April 2026.
    • Good: 30% to 45%.
    • Strong: past 50% when you share a group, a post, or a mutual contact.
    • Red flag: below 20%, which signals targeting problems, a weak profile, or over-automation and typically triggers a reduction in your weekly sending capacity.

    The character limit

    The cap is 300 characters. Aim under 200, ideally around 160, because notes get truncated in mobile notifications and a message that reads cleanly without a "click to see more" lands better.

    The 7 examples

    1. The mutual-connection note

    `` Hi [Name], we're both connected to [Mutual]. I work with [role]s on [problem] and would like to follow your work. `` Why this works: a shared connection is the strongest single acceptance lever, and it makes the request feel warm.

    2. The shared-group note

    `` Hi [Name], fellow [Group Name] member here. Your take on [topic from the group] matched how we see it. Happy to connect. `` Why this works: a shared group is public proof of a common interest, and it pushes acceptance past 50%.

    3. The content-engagement note

    `` Hi [Name], your post on [specific topic] was the clearest version of that argument I've read. Would like to connect. `` Why this works: it proves you actually read something of theirs, and it asks for nothing.

    4. The trigger-event note

    `` Hi [Name], saw [Company] just [funding / hire / launch]. I work with teams navigating that stage. Open to connecting. `` Why this works: the trigger explains why you are reaching out now, which reads as relevant rather than random.

    5. The peer note

    `` Hi [Name], we work with a lot of [company type] teams on [problem area]. Looks like we're in the same world. Connect? `` Why this works: it establishes category relevance without naming names or pitching.

    6. The honest-value note

    `` Hi [Name], I help [role]s reduce [problem]. Not pitching in a connection request, just would value being connected. `` Why this works: stating the reason plainly and explicitly disclaiming the pitch disarms the "this is a salesperson" reflex.

    7. The no-pitch curiosity note

    `` Hi [Name], quick question if you connect: how is your team handling [specific challenge] these days? Genuinely curious. `` Why this works: it opens with a real question, which is an invitation to reply, not to be sold.

    What not to put in the note

    • A pitch of any kind.
    • A calendar link.
    • "I'd love to connect and share how we can help you with..."
    • Anything that reads as templated: "I came across your profile and was impressed."
    • Emojis or excessive enthusiasm.

    After they accept

    The connection is not the goal. The first message after acceptance is, and it should not be a pitch either. Reference why you connected, ask a light question, and let the conversation develop. Pitching in the first message after a fresh connection is the most common way to get a new connection to ignore you or disconnect. See linkedin prospecting messages and how to prospect on LinkedIn without InMail.

    The multi-channel sequence

    A connection request is one touch in a sequence, not a standalone play. The pattern top teams run: connection request day 1, email day 3, LinkedIn message day 7, email follow-up day 10. See InMail vs email, LinkedIn InMail templates, and email sending schedule for cold outreach for the other touches.

    How to personalize a note at scale

    The seven templates are frames; the personalization is a single specific detail dropped into the frame. Sources for that detail, in order of effort:

    • A recent post or comment. Read one, quote the specific point. Highest quality, lowest scale.
    • A trigger event. Funding, a new hire in their department, a product launch. See what are buying signals in B2B sales.
    • A shared group or connection. Public, easy to check, and a strong acceptance lever.
    • Their headline. The weakest option, because everyone uses it and it reads as a merge field.

    Build a short list at a time, personalize each note with a real detail, and keep daily volume modest. LinkedIn watches send velocity and acceptance rate together, and a spike in requests with a falling acceptance rate is what triggers a capacity cut. See how to build an ICP list for outbound sales and how to find B2B leads on LinkedIn.

    Automation and connection requests

    Tools can send connection requests at volume, but LinkedIn actively detects and penalizes automation, and a low acceptance rate from automated, weakly personalized requests is a fast route to a restricted account. See is LinkedIn automation safe and LinkedIn automation tools. The safer approach is manual or lightly assisted sending inside daily limits, with a real detail in every note. See how to use LinkedIn for lead generation and database vs LinkedIn for prospecting for where LinkedIn fits alongside other channels.

    The Note-for-Reply Rule

    The Note-for-Reply Rule: a connection request note barely changes acceptance, 26.4% with, 26.4% without, but it nearly doubles the reply rate afterward, 9.4% versus 5.4%. Send the note for the conversation, not the connection.

    Acceptance: the note does nothing. Reply rate: the note does almost everything.

    The rule matters because it changes what you optimize the note for. If you thought the note drove acceptance, you would write it to be impressive and credential-heavy. Since it drives reply rate instead, you write it to be easy to respond to: short, specific, curious, and pitch-free.

    It also means a bad note has a real cost. A templated, salesy note does not hurt acceptance much, but it kills the reply rate the note was supposed to lift, so you end up worse off than sending no note at all. The quotable version: "Nobody accepts you because of your note. But they reply because of it."

    Under 200 characters, one specific detail, a light question, no pitch.

    Where InboundLabs fits

    A connection request only starts a useful conversation if it goes to the right person, and a LinkedIn-only workflow leaves you without an email or phone to continue the sequence off-platform.

    InboundLabs is a sales intelligence platform built on a database of 280M verified B2B contacts with verified direct dials, not switchboard numbers, and 98% email deliverability on verified contacts. It layers buyer intent signals on firmographic data and lets you filter by industry, headcount, region, and title, so the people you connect with on LinkedIn are also people you can email and call in the same sequence. Monthly plans, no annual lock-in. Free to start, no credit card required.

    See how InboundLabs finds verified contacts instantly → inboundlabs.app

    The bottom line

    A LinkedIn connection request note barely affects acceptance, which sits at 28% to 37% for cold personalized B2B requests, but it nearly doubles the reply rate, from 5.4% to 9.4%. So always include a note if you want a conversation, keep it under 200 characters, reference one specific thing, and put no pitch in it. Use the seven examples for a mutual connection, a shared group, content engagement, a trigger event, category relevance, an honest reason, or a genuine question. After acceptance, do not pitch in the first message, and treat the connection request as one touch in a multi-channel sequence.

    Frequently Asked Questions

    Do LinkedIn connection request notes increase acceptance?

    Barely. Acceptance is almost identical with and without a note, around 26.4% either way, across millions of tracked requests. The note's real effect is on what happens after: it nearly doubles the reply rate, from 5.44% without a message to 9.36% with one. Send a note if you want a conversation, not just a connection.

    What is a good LinkedIn connection request acceptance rate?

    For cold, personalized B2B requests, 28% to 37% is average and 30% to 45% is good. It climbs past 50% when you share a group, a post, or a mutual contact. Below 20% is a warning sign of targeting problems, a weak profile, or over-automation, and LinkedIn typically cuts your sending capacity.

    How long should a LinkedIn connection request message be?

    The cap is 300 characters. Aim for under 200, ideally around 160, because notes get truncated in mobile notifications. A message that reads completely without a "click to see more" performs better than a longer one that gets cut off.

    What should I not include in a connection request note?

    A pitch, a calendar link, "I'd love to share how we can help," anything templated like "I came across your profile," and excessive enthusiasm or emojis. A salesy note does not hurt acceptance much but it kills the reply rate the note is supposed to lift.

    What should I send after someone accepts my connection request?

    Not a pitch. Reference why you connected, ask a light question, and let the conversation develop. Pitching in the first message after a fresh connection is the fastest way to get ignored or disconnected. The connection is the start of a relationship, not permission to sell.

    How does a connection request fit into a sales sequence?

    As one touch among several. A common pattern is connection request on day 1, email on day 3, a LinkedIn message on day 7, and an email follow-up on day 10. Running LinkedIn and email together in one coordinated sequence produces higher total reply rates than either channel alone.

    LSI keywords: LinkedIn connection request, connection note, acceptance rate, reply rate, personalized message, 200 characters, mutual connection, shared group, trigger event, over-automation, multi-channel sequence, no pitch

    Sources

    • Expandi: LinkedIn Outreach Benchmarks 2026, 13.2M Data Points (checked August 2026)
    • LeadRiver: LinkedIn Connection Request Acceptance Rate Benchmarks, Data from 50,000+ Requests (checked August 2026)
    • Overloop: 23 LinkedIn Connection Request Templates 2026 (checked August 2026)

    Try our data quality
    for free.

    No commitment. No credit card. Just 50 free verified contact lookups.

    Start Free Trial
    No credit card required Cancel anytime GDPR compliant Setup in 2 minutes