LinkedIn Connection Request Templates That Get Accepted

LinkedIn connection request templates are reusable, fill-in-the-blank message frameworks for the short note you can attach when you invite someone to connect. The best ones name a specific, genuine reason to connect in one or two sentences, stay under the platform's note limit, and make the next reply easy. Below are 23 templates organized by scenario, plus the 2026 rules, length data, and follow-up structure that decide whether your invitations actually turn into conversations.

What is a LinkedIn connection request template?

A LinkedIn connection request template is a pre-written framework for the optional note attached to an invitation. You keep the structure and swap in the details: the person's name, a shared interest, a specific trigger, and a clear reason to connect. Templates exist because the note field is short and the stakes are high. A vague request gets ignored or, worse, marked "I don't know this person," which hurts your future invitations.

A good template does three things. It signals you are a real person with a real reason. It references something specific to this recipient. And it leaves an obvious, low-friction opening for the conversation that follows once they accept. The template is the scaffold; personalization is what makes it land.

What is the LinkedIn connection request character limit in 2026?

In 2026, the connection request note limit is 300 characters on Premium and Sales Navigator accounts, and 200 characters on free accounts. Spaces and emojis count. Free accounts are also capped at a small number of personalized invitation notes per month; once you pass that, you can still send invitations, but without an attached note.

Two practical takeaways. First, do not write to the limit. Analysis of large invitation datasets consistently finds that notes in the 120 to 180 character range outperform notes that try to fill all 300. Brevity reads as confidence; a wall of text reads as a pitch.

Second, the limit shapes the template. You have room for a hook, a reason, and a soft close, and not much else. Every template below is built to fit comfortably inside 200 characters so it works on any account tier.

Should you send a connection request with or without a note?

The honest answer in 2026 is: it depends on what you measure. Multiple studies find that blank invitations often match or beat noted ones on raw acceptance rate, sometimes by a wide margin. People accept faces and titles they recognize, and a missing note removes any "this is a pitch" friction.

But acceptance is not the goal. Replies are. The same research shows that requests sent with a relevant note produce meaningfully higher post-acceptance reply rates, because the note starts a conversation instead of leaving an awkward silence. If you connect blank, you still have to break the ice from a cold start.

Our recommendation: use a note when you have a specific, true reason to connect with this person, and keep it short. Skip the note only when you genuinely have nothing personal to say and would otherwise force a generic line. A weak note is worse than no note.

What makes a connection request note get accepted?

High-accept notes share a repeatable structure. Once you internalize it, you can write a strong request in under a minute without leaning on a template at all.

• A specific trigger. Reference something real: their post, a mutual connection, the same event, a shared group, a recent role change. Generic flattery ("love your content") reads as automated.
• A reason that serves them, not you. Frame the connection around their interests or work, not your quota.
• No pitch in the invite. The note's job is to get accepted and open a door, not to sell. Save the ask for after they connect.
• A light, human close. "Would love to connect" or "Thought it made sense to be connected" beats a hard call to action.
• Brevity. Aim for 120 to 180 characters. If you cannot say it short, you do not yet know why you are reaching out.

For context, platform-wide acceptance rates hover around the high-20s percent, with strong B2B outbound landing in the 30 to 40 percent range. A well-targeted, well-written note paired with good list selection is how you move toward the top of that band.

LinkedIn connection request templates for cold outreach

These are for prospects who do not know you. The shared thread is a concrete reason plus zero pitch. Replace bracketed fields before sending.

1. Post engagement: "Hi [Name], your post on [topic] put words to something my team has been wrestling with. Would be glad to connect and follow your thinking."
2. Shared problem: "Hi [Name], I work with [role] teams on [problem] and noticed you lead that at [Company]. Would love to connect and trade notes."
3. Industry peer: "Hi [Name], we are both deep in [industry/niche] and I do not have many peers here. Thought it made sense to connect."
4. Specific role trigger: "Congrats on the move to [Company], [Name]. The first 90 days in [role] are a lot. Happy to connect if useful down the line."
5. Curiosity, no pitch: "Hi [Name], I keep seeing [Company] come up for [thing they do well]. Would be great to connect and learn how you approach it."

Cold outreach is also where channel choice matters. If LinkedIn invitations stall, the same prospect may be far more reachable by email. That is why teams increasingly run sequences that span LinkedIn and inbox together. See our take on cold email outreach for how the two channels reinforce each other.

LinkedIn connection request templates for warm and mutual contacts

When there is a real connection point, your acceptance rate climbs sharply. Lead with the shared context.

1. Mutual connection: "Hi [Name], we are both connected to [Mutual] and I have heard good things about your work at [Company]. Would love to connect directly."
2. Same event: "Hi [Name], I was at [Event] too. Wish we had crossed paths there. Connecting so we can stay in touch."
3. Same group: "Hi [Name], fellow member of [Group]. Always trying to connect with people who post thoughtfully there. Glad to link up."
4. Met briefly: "Great chatting at [place], [Name]. Connecting here so the conversation does not get lost in email."
5. Re-engage a dormant contact: "Hi [Name], it has been a while since [context]. Would love to reconnect and hear what you are working on now."

LinkedIn connection request templates for recruiting and job search

Recruiters reaching candidates, and candidates reaching hiring managers, both benefit from specificity about the role and the fit.

1. Recruiter to passive candidate: "Hi [Name], your [skill] background at [Company] stood out for a [role] I am working on. No pressure, just keen to connect."
2. Candidate to hiring manager: "Hi [Name], I am exploring [role] roles and [Company]'s work on [thing] is exactly my space. Would love to connect."
3. Candidate to team member: "Hi [Name], I am interviewing for [role] at [Company] and would value connecting with someone on the team. Thanks for considering."
4. Alumni angle: "Hi [Name], fellow [School/Company] alum here. Always glad to connect with people who took a similar path into [field]."

LinkedIn connection request templates for sales and business development

The cardinal rule holds: the invitation does not sell. It earns the right to a conversation. Keep the pitch for after they accept.

1. Value-first observation: "Hi [Name], noticed [Company] is scaling [function]. We see a lot of [role] teams hit [challenge] at that stage. Would be glad to connect."
2. Trigger event: "Congrats on [funding/launch/expansion], [Name]. Exciting time for [Company]. Connecting to follow along."
3. Peer referral path: "Hi [Name], we work with teams like [similar company] on [outcome]. Thought it made sense to be connected even if the timing is off."
4. Content-led: "Hi [Name], your point about [topic] matched what we hear from [audience] daily. Would love to connect and compare notes."

What happens after the accept is where most outreach falls apart. Replies arrive across LinkedIn, email, and sometimes WhatsApp, and they get lost. Running your follow-up through multi-channel sequences keeps the thread moving on whichever channel the prospect actually answers on.

LinkedIn connection request templates for networking and community

Pure relationship building, no ask. These are the easiest to get accepted because the motive is transparent.

1. Admiration, specific: "Hi [Name], the way you build [community/product] is genuinely impressive. Connecting so I can keep learning from it."
2. Same career stage: "Hi [Name], we are both early into [role/path]. Would be great to have peers to compare notes with along the way."
3. Geography: "Hi [Name], not many people doing [field] here in [city]. Would love to connect with someone local in the space."
4. Gratitude: "Hi [Name], your [resource/talk] saved me real time on [task]. Connecting to say thanks and stay in your orbit."
5. Open invite: "Hi [Name], I make a point of connecting with thoughtful people in [niche]. You are clearly one. Glad to link up."

How long should a LinkedIn connection request note be?

Aim for 120 to 180 characters, roughly one to two sentences. This range consistently outperforms longer notes across large invitation samples, and it fits inside the 200-character free-account limit so a single template works on every account tier.

Short notes win for two reasons. They are read fully on mobile, where most invitations are reviewed, and they signal that you respect the recipient's time. A note that fills all 300 characters reads as a sales script before the person has even accepted. If your draft runs long, cut the setup and keep the trigger plus the reason. The connection request is an opener, not the conversation.

When is the best time to send a connection request?

Timing matters less than relevance, but it still moves your numbers. The strongest moment is right after a genuine trigger: they posted, changed roles, spoke at an event, or engaged with your content. Reaching out within a day or two of that signal makes your note obviously relevant rather than random.

On cadence, LinkedIn enforces a weekly invitation limit that generally falls in the 100 to 200 requests per week range, varying by account age, network size, and acceptance history. Accounts with higher acceptance rates tend to keep more headroom over time, while requests that get ignored or marked "I don't know this person" can pull your ceiling down. The lesson is not to chase volume. Send fewer, better-targeted invitations to people likely to recognize the value, and your acceptance rate, and your effective limit, both stay healthy.

How to follow up after a connection is accepted

Acceptance is the start, not the win. Most invitations die here because there is no plan for the message that follows. Build a simple, reusable follow-up sequence.

• Message one (within a day): Thank them and reference the same trigger from your note. No pitch. "Thanks for connecting, [Name]. Really enjoyed your post on [topic]."
• Message two (a few days later): Offer something useful or ask a genuine question about their work. Still no hard ask.
• Message three (after value is established): Make a light, specific suggestion or invitation to talk, framed around their context.

The hard part is doing this at scale without forgetting who is at which step or which channel they last replied on. A unified inbox pulls every reply, across LinkedIn and email and messaging apps, into one place so nothing slips, and event-driven workflows can pause a sequence the moment someone replies so a human takes over at the right moment.

How Klovis turns accepted connections into pipeline

Templates get the door open. The system behind them decides whether anything comes of it. Klovis is a multi-channel outreach CRM: you run sequenced campaigns across LinkedIn, email, WhatsApp, Instagram DM, and Telegram from your team's own connected accounts, so a LinkedIn invitation and an email follow-up live in the same flow.

Every reply, from every channel, lands in one unified inbox, attributed to the right person. Your CRM updates itself as people and companies respond, and replies convert into deals so connection requests roll forward into real pipeline. Event-driven workflows handle the in-between, pausing a sequence when a prospect replies, tagging based on behavior, and even booking meetings, so your reps spend time on conversations instead of bookkeeping.

If you are weighing tools, our comparisons break down how Klovis stacks up against single-channel LinkedIn automation and standalone CRMs. The short version: templates are table stakes, and the advantage comes from running them across channels with one inbox and a CRM that keeps itself current.

Frequently asked questions

Do personalized connection requests get accepted more than blank ones?

Not always. In 2026 data, blank invitations frequently match or beat noted ones on raw acceptance rate. But noted requests produce higher reply rates after acceptance, because the note opens a conversation. Use a short, specific note when you have a real reason; skip it rather than send a generic one.

What is the connection request character limit?

It is 300 characters on Premium and Sales Navigator accounts and 200 on free accounts, including spaces and emojis. Free accounts also have a monthly cap on personalized notes. Regardless of the limit, notes of 120 to 180 characters tend to perform best.

How many connection requests can I send per week?

Roughly 100 to 200 per week, depending on account age, network size, and your acceptance history. Strong acceptance rates protect your ceiling over time. Prioritize relevance over volume so fewer requests get ignored or flagged.

Should I pitch in the connection request note?

No. The note's only job is to get accepted and open a door. Pitching in the invitation lowers acceptance and feels automated. Save any ask for the follow-up after they connect, once you have given some value first.

How do I scale templates without sounding robotic?

Keep the trigger field genuinely personalized for each person, even when the structure is reused, and run follow-ups through a system that tracks where each prospect is. Multi-channel sequencing with a unified inbox lets you stay personal at volume because the tooling handles the bookkeeping, not the message.