A LinkedIn connection request gets accepted when the recipient can answer one question in two seconds: why you, and why now. The format that wins is a single concrete cue (a post, a role, a tool, a shared event), one short credibility line, and a low-pressure ask, all under the 300-character limit. If your note reads like networking or smells like a hidden pitch, it gets ignored no matter how strong your title is. The 23 templates below are sorted by intent so you can grab the right one and send it in under a minute.
Disclosure: I am the CEO of Overloop, an outbound platform that runs LinkedIn and email sequences together. These templates work whether you send them by hand or at scale. I will flag where a tool earns its keep, but the copy here is yours to use either way.
The short version
- Match intent to template. Sales, recruiting, networking, alumni, event, and cold each need a different opener.
- One verifiable cue, then stop. A real post line beats a paragraph of flattery.
- Stay under 300 characters. That is the LinkedIn note limit, and the preview is where people decide.
- No pitch in the request. Save the product, deck, and calendar link for after they accept.
- Track acceptance weekly. Keep what beats your baseline, rewrite what does not.
What gets a LinkedIn connection request accepted
A strong connection request message includes four parts, in this order. Keep all four and you stay well inside the character limit while giving the recipient everything they need to say yes.
- Personalization cue: one concrete detail (a post, role, tool, or event).
- Reason to connect: why this person, why now.
- Credibility: one proof point (your role, a shared contact, a relevant outcome).
- Next step: one low-friction action (connect, a quick question, swap notes).
The gap between a request that gets accepted and one that gets ignored is almost always specificity. Compare these two:
Relevance is not a soft factor. Personalized, relevant outreach consistently outperforms generic blasts: LinkedIn's own sales research finds that buyers respond far more to outreach that references their role and priorities than to one-size-fits-all messages. The note is your first and cheapest chance to prove relevance.
The 300-character rule (and why the preview matters)
LinkedIn caps the note on a connection request at 300 characters, per LinkedIn's own Help Center. That is the hard ceiling. The practical ceiling is lower, because the recipient often decides from the truncated preview in their notification before they ever open the full note.
- Aim for 200 to 250 characters. It reads in one glance and survives the preview.
- Front-load the cue. Put the specific detail in the first line so it shows before any cutoff.
- Free accounts are rationed. LinkedIn limits the number of personalized invitations free members can send per month, so spend them on warm, specific targets and lean on note-free requests for obvious peer connects.
Sales & prospecting templates (1-6)
The rule for every sales request: no product, no calendar, no "opportunity" inside the note. You are earning the right to a first message, not closing. Pick the angle that matches the signal you have.
Hi [Name], liked your post on [topic], especially the point about [specific detail]. I am [role] at [Company] working on [relevant area]. Mind if I connect?
Make it work: quote one real line (a stat, framework, or example). Keep credibility to six to ten words. Never mention your product in the request.
Hi [Name], congrats on [trigger: new role / Series A / hiring SDRs / launching X]. I work on [specific area] for teams like yours. Thought it would be useful to connect since [one concrete reason tied to the trigger]. Open to connecting?
Make it work: a trigger creates relevance without sounding like networking. New role: "onboarding sets the cadence for the first 30 days." Funding: "teams revisit ICP right after a round."
Hi [Name], saw you use [Tool] for [use case]. I am [role] at [Company] comparing setups for [workflow]. Quick one: are you on [feature/integration] or doing it via [alternative]? Open to connecting?
Make it work: tool-based context is verifiable and practical. You are asking about their workflow, not their budget. Save anything adjacent you sell for after they accept.
Hi [Name], not trying to sell you anything. I am comparing notes on [topic] for [role/segment] and can share a 2-sentence benchmark we are seeing (reply rates, ramp time, demo-to-close). Open to connecting?
Make it work: state intent, then offer a tiny useful share. If they accept, send the benchmark in the first message and stop. Earn the next question.
Hi [Name], reaching out about [specific scope: lead routing in HubSpot / SOC2 renewal / SDR hiring] at [Company]. Are you the right owner, or is that [team/role]? Happy to redirect. Open to connecting?
Make it work: name one concrete scope item and give an easy redirect option ("RevOps vs Marketing Ops?"). It routes you without sounding like you scraped a list.
Hi [Name], noticed you work with [industry/team]. We recently helped a [peer type: mid-market SaaS] cut [outcome] from [X] to [Y] by [one tactic]. Curious if [problem] is on your radar for 2026. Open to connecting?
Make it work: use believable, specific numbers ("onboarding from 21 to 14 days"), not "we 10x'd revenue." Match the proof to their company type.
Sending these one by one?
Overloop writes the personalized first line from each prospect's profile and posts, then runs the LinkedIn request and the email follow-up as one sequence, so a good template scales without turning into copy-paste spam.
Try Overloop free →Recruiting & hiring templates (7-10)
Recruiter and candidate requests get ignored when they read like a template: "exciting opportunity," "quick call," vague comp. Lead with fit, show you read the profile, and give an easy out.
Hi [Name], hiring a [Role] at [Company]. Your work on [verifiable detail: GCP cost optimization / enterprise SOC2 programs] stood out. Open to connecting? If timing is off, tell me a better month and I will circle back.
Make it work: name a real skill from their profile, not "your impressive background." The timing-out makes it feel respectful, not pushy.
Hi [Name], I applied for the [Role] at [Company]. I [proof: built self-serve onboarding that cut time-to-value 30% / owned renewals at 92% GRR]. Ok if I connect and share a 2-sentence note on why I fit [requirement]?
Make it work: one proof point, one permission check. No portfolio dump, no "following up," no meeting ask inside the request.
Hi [Name], saw you are hiring a [Role] at [Company]. I have built a few [Role] hiring kits. Want me to send a 1-page [scorecard / interview questions / 30-60-90] that has worked for [team type]?
Make it work: hiring is a clean trigger. Offer one specific artifact that reduces their work. One resource, one sentence, no meeting ask.
Hi [Name], [Mutual] suggested I reach out and said it is fine to mention them. I am [role] at [Company] working on [specific area], and [Mutual] thought your background in [skill] stood out. Open to connecting?
Make it work: only use this when the mutual contact gave explicit permission. Avoid "I told [Mutual] I would message you," which reads as pressure.
Networking & peer templates (11-15)
Peers can smell fluffy praise from a distance. Lead with a shared context or a concrete problem you both face in the same job.
Hi [Name], saw you in the [Group] group. I am deep in [topic] too and liked your take on [specific thread]. Open to connecting?
Make it work: use a context you genuinely share (group, webinar, thread). Two lines, one clear reason.
Hi [Name], I am a [Role] at [Company] too. Saw you focus on [specific area: deliverability / MEDDICC / PLG handoffs]. I am comparing how teams handle [one issue]. Open to connecting and swapping notes?
Make it work: pick one swap-notes angle: "your reply-rate benchmark for [segment]?" or "Sales Navigator lists or intent tools?" Keep it to one question.
Hi [Name], quick question: for [situation], do you prefer [Option A] or [Option B]? Comparing approaches for [context]. If you are open to it, I would love to connect.
Make it work: keep the ask binary or one number. A micro-ask gives a 10-second win and a clear reason to connect. Avoid anything that needs a paragraph to answer.
Hi [Name], liked your work at [Company], especially [specific thing: the X launch and how you handled Y]. I work on [related area] at [Your Company]. Would love to connect and follow what you ship next.
Make it work: use nouns, not adjectives. "Your Figma-to-Webflow workflow doc" reads real. "Your impressive leadership" reads automated.
Hi [Name], enjoy [Podcast/Newsletter], especially the issue on [topic]. I am [role] at [Company]. If you book guests on [theme], I can share a tight story on [proposed topic]. Open to connecting?
Make it work: keep the topic specific. "AI in sales" gets ignored. "What changed in LinkedIn outreach after the 2026 UI updates" gets booked.
Alumni, local & community templates (16-17)
A shared place, school, or community gives you a human reason to connect without pretending you already have business together.
Hi [Name], saw you are also a [School] alum / based in [City]. I am [role] at [Company] working on [relevant area]. Always good to connect with fellow [alumni/local] folks. Open to connecting?
Make it work: use a tie you can verify on their profile. Keep the reason neutral (learn, follow, swap notes). Skip any pitch language entirely.
Hi [Name], fellow [Pavilion / RevGenius / Women in Product] member here. Liked your take on [specific topic] in the community. I am [role] at [Company] focused on [area]. Open to connecting?
Make it work: reference a specific group and, if you can, one thing they posted there. Membership alone is a weak hook; membership plus a real detail is strong.
After an event templates (18-19)
Event follow-ups work when you reference a specific moment they remember, then make the next step tiny. "Great event" gets ignored. "Your slide on pipeline math" gets accepted.
Hi [Name], enjoyed [Event] and your point about [specific moment: slide, question, quote]. I am [role] at [Company] working on [related area]. Open to connecting? If yes, I will send the [resource] you mentioned.
Make it work: anchor to a real moment ("your answer to the Q about [topic]"). Keep the ask inside LinkedIn. Save the meeting request for after they accept.
Hi [Name], we were both at [Webinar] today. Your point about [specific moment] was useful for my work in [area]. Open to connecting?
Make it work: send it the same day while the session is fresh. One specific reference does more than three lines of "great session."
Cold & follow-up templates (20-23)
These cover the harder cases: a truly cold target, a declined request, the first message after they accept, and a re-connect after silence.
Hi [Name], saw your [token: post on [topic] / role owning [area] / comment about [detail]]. I am [Role] at [Company] focused on [relevant area]. Open to connecting?
Make it work: use one verifiable token (6 to 12 words) and stop. Stacking "love your content" plus a pitch plus a meeting ask is what reads automated.
Hi [Name], thanks for taking a look, totally fair. I reached out because [one reason: your post on X / your new role at Y]. I will step back. Ok if I reconnect in [30/60/90] days if I have something relevant to [their priority]?
Make it work: treat a decline as a boundary, not a defeat. Leave a clean, specific reason to reconnect when timing changes.
Thanks for connecting, [Name]. Quick follow-up on [their post/trigger]. I am collecting how [role] teams handle [situation]. Do you do [Option A] or [Option B]? Happy to share a 5-bullet summary of what I am seeing.
Make it work: start with context, not your product. Ask for a binary answer and offer a useful artifact before asking for time. Only then: "Worth a 10-min call next week?"
Hi [Name], quick bump with a new angle: saw [trigger: you are hiring for X / you posted about Z]. Yes or no, is [specific priority] still on your list this quarter? If yes, I can share [one asset]. If no, I will close the loop.
Make it work: skip the apology. A yes-or-no question lets them respond in one tap. If they say no, stop. If yes, send the asset before asking anything else.
How to personalize LinkedIn requests at scale
If your first line sounds automated, the recipient assumes a pitch and ignores it. Personalize fast by pulling three cues and writing one sentence.
- Role and scope from the headline and About section (for example, "RevOps owning attribution").
- A fresh signal: a post, comment, job change, hiring, funding, or launch in the last 30 days.
- Proof of relevance: one shared tool (HubSpot, Salesforce, GA4), community, or mutual contact.
Then write: cue plus why connect plus low-friction ask. Example: "Saw your post on lead routing in HubSpot. I am building similar workflows for PLG teams. Open to connecting?"
This is easy for 10 requests and impossible by hand for 500. AI LinkedIn outreach tools exist to bridge that gap, and the honest tradeoff is that most of them automate volume at the cost of relevance. The point of a tool is the opposite: keep every request specific while you reach more people. Overloop generates a compliant, specific first line from profile and post context, then drops it into a sequence that runs the LinkedIn request and the email follow-up together, so a connection that accepts flows straight into a real conversation. For the full system around it, see our LinkedIn outreach playbook, and if you build prospect lists in Sales Navigator, our guide on how to use LinkedIn Sales Navigator covers the targeting side.
Frequently asked questions
What is a good LinkedIn connection request message?
A good LinkedIn connection request message is short (well under the 300-character limit), names one concrete reason to connect, and ends with a low-pressure ask. It includes four things in order: a personalization cue (a post, role, tool, or event), the reason to connect, one credibility line (your title and company), and a single low-friction next step. Skip the pitch, the calendar link, and the word "opportunity." Example: "Saw your post on pipeline hygiene. I lead SDR ops at Acme and would love to compare notes on what is working in 2026. Open to connecting?"
How long can a LinkedIn connection request message be?
The note on a LinkedIn connection request is capped at 300 characters, and that limit is the same on every plan, free or paid. What differs is volume, not length: free accounts are limited to roughly 5 personalized (noted) invites per month, while paid plans raise that allowance. Treat 300 characters as the hard ceiling and aim for 200 to 250 so the message reads in one glance. Anything longer gets truncated in the notification preview, which is where most people decide whether to accept or ignore.
What is a good LinkedIn connection request acceptance rate?
Acceptance rates vary widely by relevance and personalization, but a useful working benchmark is 30 to 40 percent for cold, personalized requests in B2B. Generic invites to people you have no context with often land below 20 percent, while requests tied to a shared group, recent post, or mutual contact can climb past 50 percent. Track your own acceptance rate weekly and treat anything above your baseline as a template worth keeping.
Should you send a LinkedIn connection request with or without a note?
It depends on context. For warm targets (someone who just posted, a mutual connection, an event attendee), a short note with one specific reason lifts acceptance. For pure peer networking where you share an obvious context like the same role or alma mater, a note-free request can sometimes perform as well, because some users distrust unsolicited notes. The safe default for sales and recruiting is a tight, specific note. Test both against your own list and keep the version that wins.
How do I personalize LinkedIn connection requests at scale?
Pull one verifiable cue per person (a recent post, a job change, a tool they mention, a hiring signal) and write a single sentence around it, then stop. Stacking praise plus a pitch plus a meeting ask is what makes a request read as automated. At volume, a tool like Overloop generates a specific first line from profile and post context and drops it into a LinkedIn-plus-email sequence, so each request stays short and human while you reach more people.
What should you avoid in a LinkedIn connection request?
Avoid five things: generic openers like "I'd like to add you to my network," a pitch or product mention inside the request, a calendar or demo link before they accept, vague flattery such as "love your content," and anything longer than 300 characters. Each one signals a template and pushes the recipient toward ignore. Lead with one concrete detail they can verify in two seconds and ask only to connect.
The bottom line
Hyper-specific first lines help, but your results come from matching intent to the right ask. Pick one template, swap in one verifiable detail, keep it under 300 characters, and send it to a tight list today. Track acceptance and reply rate weekly, keep what beats your baseline, and rewrite what does not. When you are sending more than you can personalize by hand, that is the point where a sequence tool earns its place, not before.