LinkedIn connection requests in 2026: 8 templates and one measured acceptance rate

Connection-request posts often quote precise acceptance rates from datasets they do not name. This one does not. It gives eight note structures, and it cites one acceptance rate whose cohort is published.

The only acceptance rate this post cites is on the LinkedIn outreach benchmarks page. Across 967 connection requests sent through Crispy, from 19 sending accounts, between 60 and 365 days ago, excluding requests the sender withdrew and invitations imported from LinkedIn's outstanding list, 41% were accepted. No single account is more than a fifth of that cohort. The page dates the snapshot to August 2026. It is not a universal LinkedIn average. The cohort is not split by note, seniority, industry, note length, or time of day, and it does not set a restriction threshold.

A connection note has to fit in 300 characters. That is the cap Crispy enforces on an invite note, not a measured performance band. Use it for one specific, true detail, or send the request with no note when you have nothing specific to say.

What the templates treat as a real detail is a post, a role change, a funding event, a mutual, or a shared group. A first name by itself is not that detail. This post does not cite a lift for any of those choices.

Here are eight templates, organized by the situation you are in. None of them is a measured winner, and none is meant to be pasted verbatim. The bracket is the content. If that detail is not real, do not send the note.

1. Engaged with their content. "Your post on [specific topic] stuck with me, especially the point about [specific detail]. Been following your thinking on this, glad to connect." The note names a real post.

2. Shared group or event. "We're both in [group / at event] and your take on [specific topic] stood out to me. Would like to stay connected beyond it." Name the group or the event, and the specific point.

3. Trigger-based (funding, role change, launch). "Congrats on [the raise / the new role / the launch], the [specific relevant angle] caught my eye. Keen to follow what you build next." Name the event. Do not add a pitch.

4. Mutual connection. "[Mutual name] and I were just talking about [topic], and your name came up as someone deep in it. Would value connecting." The mutual and the topic have to be real.

5. Peer or community. "Fellow [role] here. Your point on [specific topic] matched something I've been wrestling with. Connecting to keep learning from your posts." Name the shared role and the specific point.

6. No note. When you have nothing specific to say, send the request with no note. Do not fill the box with a generic pitch.

7. Post-decline soft re-approach. "No worries if the timing's off, I mainly wanted to connect because of your work on [specific thing]. Either way, enjoying your posts." Name the work. Leave the door open.

8. Re-engaging a dormant connection. "It's been a while, [name]. Saw your [recent post / news] and it reminded me we'd lost touch. Would be good to reconnect." Name the recent post or the news.

These templates only work when the bracketed detail is real. A generic pitch is not a stand-in for that detail. Crispy can read a prospect's recent posts and profile and draft a note that cites something specific, or leave the note off, inside the account's configured daily limits. See how the AI SDR workflow runs, explore prospecting, or start with Crispy.