10 LinkedIn Connection Request Templates (Copy-Paste)
Why the connection request matters
Your LinkedIn connection request is the first touchpoint in your outreach funnel. A generic request with no context signals spam — and lowers your acceptance rate. Strong templates are short, personalized, and reference something specific from the profile.
The leverage is real: personalized requests are accepted roughly ~2–3x more often than blank ones, according to competitors and studies. So it pays to invest a few seconds of context in every note.
This guide gives you 10 templates that work in B2B outreach — plus rules for when to use a note and when to skip it. For limits and warmup, see our article on LinkedIn limits in 2026.
Rules for every connection request
- Max. 300 characters in the note (LinkedIn hard limit)
- Sweet spot: ~1–2 sentences / under ~125 characters — short enough that the note reads cleanly on mobile without being cut off (on top of the 300-character hard limit)
- One reason to connect — no pitch in the first line
- Personalization via role, company, or content — not just {{firstName}}
- No copy-paste patterns — slight variation per segment
- Timing: don't send 50 identical notes in one hour
If you automate, follow safe daily limits and test templates in small batches.
When to use a note — and when not to
| Situation | Recommendation |
|---|---|
| 2nd-degree with strong context | With note |
| Broad keyword search | Often without note (higher acceptance on warm profiles) |
| Event / shared group | With note (reference the context) |
| Tight ICP, high personalization | With note |
Skipping a note is not lazy — sometimes acceptance is higher because the recipient does not immediately expect a sales pitch.
As a rough guide (directional, not guaranteed): blank requests with no context often land below ~20% acceptance, while well-personalized requests often sit above 40%. The exact number depends heavily on targeting and industry — treat these as direction, not a promise.
10 templates that work
1. Content reference
*Filled-in example:* "Hi Sarah, your post on outbound sequences resonated — especially the point about reply rates. Happy to connect and see more from you on this."
When: The contact posts regularly about your topic.
2. Role match
*Filled-in example:* "Hi Mark, as Head of Sales at Acme you likely face similar challenges around scaling outbound without spam signals. Would be great to connect."
When: Clear ICP match, no direct pitch needed.
3. Mutual connection
*Filled-in example:* "Hi Julia, Tobias Berger and I were discussing lead routing — your profile came up. Happy to connect."
When: Genuine referral or shared connection exists.
4. Event / webinar
*Filled-in example:* "Hi David, saw you at SaaS Connect 2026 — great input on pipeline forecasting. Would love to continue the thread here."
When: Event attendees or webinar registrants.
5. Company trigger
*Filled-in example:* "Hi Lena, congrats on the Series A at Nordlys — exciting phase. I work a lot on early-stage outbound. Happy to connect."
When: Funding, hiring, or expansion as a trigger.
6. Industry exchange
*Filled-in example:* "Hi Anna, we both work in B2B SaaS — I'm collecting perspectives from sales-ops folks on CRM hygiene. Open to a quick exchange?"
When: Research or peer approach instead of hard sell.
7. Product user (lookalike)
*Filled-in example:* "Hi Patrick, we help teams like Helio with GDPR-compliant LinkedIn outreach. Your profile looks like a fit — happy to connect."
When: Clear use-case match, transparent but short.
8. Feedback ask
*Filled-in example:* "Hi Mira, I'm building a tool for outreach reporting and looking for feedback from SDR pros. Got 10 min for a quick chat? Happy to connect."
When: Founder-led sales with a genuine feedback angle.
9. Resource offer
*Filled-in example:* "Hi Jonas, we put together a guide on safe LinkedIn limits — thought it might be relevant for the growth team at Veluna. Happy to connect."
When: Content-led growth, no meeting pressure in the note.
10. Local context
*Filled-in example:* "Hi Stefan, I see you're active in Leipzig in SaaS — we work with several teams in the region on outbound setups. Would love to connect."
When: Regional focus, geo-targeted outreach.
Bonus: templates for job applications & recruiting
Not all outreach is sales. If you're job-hunting or reaching out to recruiters, the same principle holds — short, specific, one reason. Two segment templates for this intent:
Recruiter / after applying
*Filled-in example:* "Hi Carolin, I just applied for the Sales Development Rep role at Northwind — would love to stay in touch."
When: You've applied and want to stay on the recruiter's radar — without pressure.
Hiring manager / active job search
*Filled-in example:* "Hi Tim, I see your team at Acme is hiring in customer success — exactly my focus area. Would love to connect."
When: You're approaching the hiring manager directly, not just HR — reference the open role.
What to avoid
- "I'd like to expand my network" with no context
- Long pitches in the note (belongs in follow-up)
- Wrong personalization (generic company name, wrong role)
- Identical notes to hundreds of profiles the same day
More on outreach sequences and step-by-step setup.
A/B testing connection notes
Test systematically:
- With vs. without note in one segment
- Short (1 sentence) vs. medium (2 sentences)
- Question vs. statement at the end
- Content reference vs. role match
Measure acceptance rate over at least 100 requests per variant before scaling. If it stays below 25%, fix targeting — not volume.
Automation without spam signals
With a cloud-based tool like Inboundy, you can use templates as a base and review AI drafts per profile — instead of firing identical notes. Flow: Connect by Keyword → Lists → Messages with plan-based daily limits.
Frequently asked questions
How long should a connection note be?
Ideally 1–2 sentences, under 300 characters. Shorter is often better — context must be obvious immediately.
Should I include a call-to-action in the note?
No. The note should spark interest, not sell. Put the CTA in the first follow-up after acceptance.
Do emojis work in connection notes?
Use sparingly. In B2B, usually skip emojis — in creative industries one relevant emoji can work, but test rather than guess.
Can I use the same template for every industry?
Better: 3–5 segment templates (SaaS, agency, enterprise, etc.) instead of one universal template. Segment personalization beats one-size-fits-all.
What if acceptance rate stays low?
Check targeting first, then note quality, then timing/volume. See also LinkedIn automation safety.
Should I send a connection request after applying for a job?
Yes — it's one of the most natural reasons to connect. Send it shortly after submitting your application to the recruiter or hiring manager, with a clear reference to the role (see the "Recruiter / after applying" template above). Keep the note short and pressure-free: you want to stay on the radar, not follow up in the same breath. Save a status check or thank-you for the first follow-up after they accept.
Bottom line
Strong LinkedIn connection requests are short, contextual, and segmented. Use these 10 templates as a starting point, test with clear KPIs, and scale only what works. Next step: automate outreach or compare tools. Agencies: outreach for agencies.
Last updated: 2026-06-30