A single reason for the connect — not a pitch.
A connection note is not the place to sell. The reader has not opted in yet. The note exists only to give them one reason to accept. Save the pitch for the post-accept DM.
Connection request templates
LinkedIn connection request templates that fit in 200 characters.
Fourteen real LinkedIn connection notes, organized by the relationship type that earned the send. Every template is under LinkedIn's 200-character note limit and includes a breakdown of why the copy earns the accept.
200-character limitLinkedIn's connection-note field caps at 200 characters including spaces. Every template here counts the character total so you know exactly what fits.
What this page covers
A LinkedIn connection request note is the short message attached to a connect invite, capped at 200 characters. It is the highest-leverage real estate in LinkedIn outreach — a strong note can lift acceptance rates from the network baseline of about 20% to 40–60%, and a weak note converts worse than sending no note at all.
Reference shared context: a person, an event, a post, a group.
Acceptance rates for notes with a referenced piece of shared context (mutual, event, post, group) run 2x higher than notes without. The reader's question is "do I know this person?" — shared context is the answer.
Match the relationship type.
A founder-to-founder note reads differently than a recruiter-to-candidate note. The templates below are organized by relationship type for a reason — using the wrong frame is more damaging than using no frame.
Always count characters.
LinkedIn silently truncates at the 200-character boundary on the recipient's preview. A note that says "Hi Sarah — I saw your post about pipeline forecasting and would love to compare notes on how Stripe is thinking about it next ye" has already failed.
01
Shared context: mutuals, events, groups
The highest-converting category. Notes that lead with a real piece of shared context — a mutual person, an event you both attended, a group you both belong to — accept at 40–60%.
Mutual connection mention
156 charsScenarioYou have a strong mutual who you can credibly invoke (not a 1st-degree they barely know).
Hi Devon — Marcus Liu mentioned you as the sharpest person he knows on B2B pricing. Working on a related problem at Notion — would love to be connected.
Why it works
Naming the mutual in the first three words anchors the entire note. The compliment ("sharpest person he knows on X") is third-party so it doesn't read as flattery. The closer ("working on a related problem") gives a reason to connect without pitching.
Shared event (conference, summit)
155 charsScenarioYou both attended the same conference, even if you did not meet.
Hi Priya — also at SaaStr this week. Your "growth at the seams" panel was the only one that didn't feel like a vendor pitch. Would love to keep in touch.
Why it works
Specific event reference establishes shared context. The compliment is concrete (one specific panel, one specific positive — "not a vendor pitch") rather than generic. No ask, no pitch — just an honest reason to connect.
Shared LinkedIn group
156 charsScenarioYou both belong to the same active LinkedIn group, especially one with under 10k members.
Hi Sam — fellow Modern Sales Pros member here. Your comment on the "is BDR-to-AE still working?" thread reframed how I think about the model. Connect?
Why it works
Naming the specific group ("Modern Sales Pros") and the specific thread proves you actually participate in the group rather than scrape it. Reacting to their idea ("reframed how I think") gives them credit and a reason to accept.
02
Content engagement
Notes built around something the prospect published, commented on, or wrote about. The opener references the content, not the person.
Post-engagement after they commented on your post
159 charsScenarioThey left a substantive comment on something you posted.
Hi Maya — thanks for the thoughtful comment on the GTM-budgeting post. The point about board pressure flattening Q4 hit the nail on the head. Let's connect?
Why it works
Specific acknowledgment of which post and which point in their comment makes it impossible to mistake this for a templated reply. The phrase "hit the nail on the head" affirms their take without overclaiming.
Reference to a post they wrote
144 charsScenarioThey wrote a post — could be from this week or six months ago — that you genuinely found valuable.
Hi Tomi — your post on the "boring math problems hiding under ML infra" is the best thing I've read on feature stores this quarter. Connect?
Why it works
Quoting a specific phrase from their post is the strongest possible proof you actually read it. The compliment is bounded ("this quarter") so it reads as honest evaluation, not flattery.
Reference to a podcast or talk they appeared on
152 charsScenarioThey were a guest on a podcast or gave a conference talk you watched.
Hi Renee — listened to your Topline appearance on rep behaviors as a forecast signal. Working on the same problem at Pylon. Would love to connect.
Why it works
Naming the specific show and the specific topic shows real consumption, not "I googled you." The "working on the same problem" line gives a reason to accept without making the note about you.
03
Persona-to-persona
Notes that lean on shared role identity — founder-to-founder, ops-to-ops, head-of-sales-to-head-of-sales. Works because the reader sees "this is someone in my world."
Founder to founder
156 charsScenarioYou are both founders, ideally at similar stages.
Hi Sam — fellow seed-stage founder, building in the dev-tools space too. Always trying to swap notes with other operators at this exact stage. Connect?
Why it works
Stating the shared category in the first 10 words establishes peer status. The closer ("swap notes") frames the relationship as bilateral, not extractive — the founder isn't being pitched, they're being invited into a peer group.
RevOps to RevOps
167 charsScenarioYou are both in the RevOps/sales-ops function.
Hi Jordan — fellow RevOps lead, mid-Series-B SaaS. Working on the same HubSpot ↔ Salesforce reconciliation problem you posted about. Would love to compare notes.
Why it works
Shared function plus shared problem is the strongest possible peer hook. Naming the post they wrote makes it a specific problem, not a generic one. "Compare notes" is bilateral — they have something to gain from the connect, not just give.
Recruiter to candidate (soft, role-mention)
158 charsScenarioYou are sourcing for a role and the candidate fits well. Save the pitch for the DM — the note just needs to earn the accept.
Hi Ana — sourcing for a staff infra role that I think actually maps to your Vitess work at Datadog. Won't bug you with anything till you accept. Connect?
Why it works
Naming the specific role type ("staff infra") and the specific candidate work ("Vitess at Datadog") makes the relevance immediate. The "won't bug you till you accept" line is unusual restraint that signals the recruiter respects the candidate's inbox.
04
Soft, no-pitch connects
Notes where there is genuinely no agenda beyond connecting. Works for influencers, peer-network building, and early relationship moves where any pitch would be premature.
Pure no-pitch admiration
168 charsScenarioYou admire their work and there is no business angle today.
Hi Lena — long-time follower of your work on operator-led marketing. No pitch, no agenda. Just want to be connected to the people whose ideas I keep stealing.
Why it works
Explicit "no pitch, no agenda" disarms the suspicion every senior person feels with a connect request. "Ideas I keep stealing" is honest, self-deprecating, and complimentary in one phrase — that combination is rare and memorable.
Future-relevance connect (no ask today)
168 charsScenarioThey're a future buyer or partner but the timing isn't right today.
Hi Pat — not pitching anything today (you're mid-implementation of a competitor — bad timing). But wanted to be in your network for the day that changes. Connect?
Why it works
Showing you researched their current state ("mid-implementation of a competitor") proves the connect is informed. Explicitly disowning a pitch and acknowledging bad timing is the rarest possible move and earns disproportionate respect.
Recently-met IRL follow-up
161 charsScenarioYou met at a meetup, dinner, or coffee. The IRL meeting was brief but real.
Hi Alex — great chatting after the OpenView dinner last night about post-PMF GTM teams. Would love to stay connected as both companies move into next year.
Why it works
The specific event ("OpenView dinner") and the specific topic ("post-PMF GTM teams") trigger the memory. The closer ties the connect to a future moment ("as both companies move into next year") that gives the relationship a forward direction.
05
Timely / signal-driven connects
Notes tied to something that happened in the prospect's world recently — a job change, a funding round, a launch. Highest acceptance rates of any category.
Job-change congratulations
167 charsScenarioThey started a new role in the last 30 days.
Hi Lila — congrats on the VP Marketing role at Sprig. Watching closely — your move from product to GTM at this stage is exactly the bet I'm betting on. Connect?
Why it works
The congrats line is specific to the role and company. The "exactly the bet I'm betting on" framing makes their career move feel validated by a peer rather than just celebrated by a fan.
Funding round congrats with stage context
163 charsScenarioTheir company just announced a funding round.
Hi Aaron — congrats on the Series B. Genuinely hard round to raise right now — the bar got brutal. Would love to be connected as you build out the next phase.
Why it works
Acknowledging the difficulty of the current funding market shows market awareness and differentiates from the 200 "huge milestone!" comments. The closer commits to the relationship, not the transaction.
Copywriting principles for linkedin connection request templates
The reasons the templates above work. Apply these and you can write your own without ever touching a template library again.
- 1
The 200-character ceiling is your editor.
Every word you cut to fit forces the note to do more work per word. The 200-character constraint is what makes connection notes harder to write than DMs — and what makes the good ones disproportionately effective. Count characters before you hit send.
- 2
Reference shared context in the first 10 words.
The recipient decides whether to accept in under three seconds. The reason to accept must be in line one. "Hi Devon — Marcus Liu mentioned you" earns an accept by word 6. "Hi Devon — I work at Notion and saw you're at..." has already lost half the readers.
- 3
Never pitch. Save it for after they accept.
A connection note is permission-seeking, not selling. Asking for a meeting in the note is the single fastest way to tank acceptance. The pitch goes in the post-accept DM, where the reader has already opted in.
- 4
Specificity over flattery.
Generic compliments ("loved your work") read as templated. Specific compliments ("your post on X reframed Y for me") read as human. The difference between specific and generic is the difference between a 50% acceptance rate and 20%.
- 5
Read the note out loud before you send.
Connection notes are short enough to read in 8 seconds. If you wouldn't actually say the words out loud to a peer at a coffee shop, rewrite. "I wanted to reach out and connect with you on LinkedIn" reads fine on paper and absurd out loud.
- 6
For high-stakes targets, write the note manually.
For your top 50 target accounts, never use a templated note. The 90 seconds it takes to write a manual one will dramatically outperform the bulk send, and these are the accounts where the marginal accept matters most. Templates are for the long tail.
Frequently asked questions
What is the LinkedIn connection request character limit?
LinkedIn caps connection-request notes at 200 characters including spaces. The character counter on LinkedIn's native interface shows you the remaining count. Notes longer than 200 characters are silently truncated on the recipient's preview, so every word past the limit is wasted.
Should I send a connection request with or without a note?
With a note — almost always. The data is consistent across studies: a well-written note lifts acceptance rates from the network baseline of 18–22% to 35–55%. A weak note is worse than no note, so if you cannot say something specific in 200 characters, send no note rather than a generic one.
What is a good acceptance rate for cold connection requests?
With a personalized note and a well-defined ICP, 35–55% acceptance is realistic. Highly-targeted senders with strong notes regularly hit 60%+. Notes sent without personalization typically run 18–25%. Notes that include a pitch run lower than notes that include nothing.
How many connection requests can I send per week?
LinkedIn enforces a soft weekly cap of about 100 connection requests per account. Most safe automation tools default to 15–20 invites per day per sender. Multi-sender teams scale by adding senders, not by trying to push one account above the weekly cap — see our /linkedin-connection-request-automation page for the safe setup.
Should I include a pitch in the connection request note?
No. The note exists only to earn the accept — the pitch belongs in the post-accept DM. Adding a pitch ("would love to show you our product") to the connection note measurably tanks acceptance rates. Save the sales motion for after they've opted in.
Can I use AI to write connection request notes?
AI works well as a personalization layer that adapts a human-written template to each prospect's recent activity. AI-generated notes from scratch read worse than templates because they have the worst of both worlds — neither the editorial control of human writing nor the personalization of real research. See /ai-personalization-for-linkedin for the working pattern.
What should I do after someone accepts my connection request?
Wait 2–4 days before sending the first DM — sending immediately after the accept reads as automation. The first DM should reference the angle from your connection note and offer a low-friction next step (a Loom, a one-pager, a free template) — not a calendar link. See our /linkedin-cold-dm-templates page for the post-accept DM library.
Send these templates at scale, the safe way.
Connect a LinkedIn sender, paste any template above into a campaign, and launch with per-sender daily caps and AI personalization on every send. Free for 7 days. No credit card required.