A blank LinkedIn connection request says one of two things to the recipient.
Either "we already know each other, so this is obvious" — or "I couldn't be bothered to write a single sentence about why I'm here."
For everyone outside your immediate circle, it reads as the second.
And yet, the average LinkedIn user still hits "Connect" on profiles they've never met, with no note attached, expecting acceptance. Acceptance rates for blank requests from strangers have been falling for years — and the people most likely to ignore them are exactly the kind of people you'd most want in your network.
This is a guide to writing the kind of connection request that gets accepted: short, specific, honest, and easy to say yes to. With real examples.
Why Most Connection Requests Fail
Connection requests fail for a handful of repeatable reasons.
No context. The recipient has no idea why you're reaching out, so the safest move is to ignore.
Pitch-coded language. "I help companies like yours do X" in the connection note is a strong signal that a sales sequence is about to follow. Recipients delete to avoid the inevitable follow-up.
Generic flattery. "I was impressed by your background" / "Your work caught my eye" — these phrases trigger the "template" pattern-match instantly. The recipient stops reading at sentence one.
Too long. LinkedIn's connection notes cap at ~300 characters. Filling the whole field with a paragraph that reads as a pitch is worse than writing nothing.
No reason to accept. Every connection request is a small ask. If the recipient can't see why they should say yes, the default answer is no.
The fix isn't a clever opener. It's a small amount of honest specificity that proves you've thought about the person you're reaching out to.
The Anatomy of a Connection Request That Works
A connection note that gets accepted has four traits.
It's short. One to three sentences. Under 250 characters is a good rule. The full 300-character limit is too long.
It says how you found them. A mutual connection, a recent post, a talk, a project, a shared community. This single piece of context removes 80% of the "who is this person and why are they messaging me" friction.
It says why now. A specific, time-bound reason — not a vague hope to "stay in touch."
It doesn't pitch. The connection request is for getting connected. Not for selling, hiring, pitching, or asking for a call. Save that for after the connection is accepted.
That last point is the one most people get wrong. The connection note and the first DM are different moves. Combining them dramatically lowers acceptance rates.
Examples by Scenario
Below are five common scenarios with examples that work. Adapt to your situation; specificity is the whole point.
Example 1: After a Conference or Event
Bad:
Hi Marcus, it was great connecting at SaaStr. Looking forward to staying in touch!
This is fine if you actually met. If you didn't — and "great connecting at" is shorthand for "I saw your name on the attendee list" — recipients can tell.
Better:
Marcus — caught your panel on enterprise PLG on Wednesday. The bit on freemium ceilings was sharp. Would love to stay in touch.
Why: Names something specific from the panel. Doesn't claim a relationship that doesn't exist. No ask attached.
Example 2: After Reading Their Content
Bad:
Hi Priya, I came across your profile and was impressed by your background. Would love to connect.
Almost every recipient has seen this exact opener fifty times. They skim past it.
Better:
Priya — read your piece on rebuilding the data platform at Acme last week. The migration approach was unusually pragmatic. Hoping to follow more of your work.
Why: Proves you actually read the piece (specific reference to migration approach). Doesn't try to start a conversation — just wants to follow. Low-friction, easy to accept.
Example 3: Through a Mutual Connection
Bad:
Hi James, we have several mutual connections. I'd love to add you to my network.
"Several mutual connections" is the social equivalent of "to whom it may concern."
Better:
James — Sarah Chen mentioned you when we were talking about ClickHouse last month. She said your write-up on query routing was the clearest she'd seen. Adding you here.
Why: Names a real mutual connection and a real context. The recipient can verify with Sarah if they want. Establishes credibility through someone they trust.
If you don't have a real mutual to reference, don't fake one. Use a different scenario.
Example 4: In Their Industry / Adjacent Space
Bad:
Hi Aisha, I work in the same space as you and would love to connect to share ideas.
Vague, indistinct, signals nothing specific.
Better:
Aisha — also working in vertical SaaS for healthcare RCM, on the buy-side. Curious how your team handles the Medicare Advantage reform timeline. Adding you here, no pressure.
Why: Names the exact intersection. Floats one specific topic of mutual interest. The "no pressure" tag tells the recipient there's no immediate pitch coming.
Example 5: After They Replied to Your Post or Comment
Bad:
Hi Tomás, thanks for engaging with my post. Let's connect!
True, but lazy.
Better:
Tomás — your comment on the build-vs-buy thread was the most useful one in there. Would love to keep the conversation going.
Why: Names what specifically about their reply stood out. Treats the connection as a continuation of an actual exchange, which it is.
A calmer LinkedIn inbox is one click away.
Labels, follow-up reminders, Kanban pipelines, and AI screening — built for targeted outreach.
Scenarios Where You Should Not Add a Note
There are a few cases where blank connection requests are fine — even better than a note.
- People who already know you. Colleagues, classmates, friends-of-friends you've actually met. A note here feels formal and awkward.
- People you've worked with before. Same logic. If they don't remember you, no note is going to help.
- People you've already had a conversation with elsewhere (email, Twitter, in-person) — they have context.
The note-required line is: would the recipient have any reason to know who I am or why I'm here without an explanation? If yes, blank is fine. If no, write the note.
Patterns That Compound Across Hundreds of Requests
A few habits raise acceptance rates noticeably over time.
Reference one specific thing per request. A piece they wrote, a talk they gave, a project they shipped, a person you both know. Vague compliments fail; specific ones work.
Lead with where you found them. "Caught your panel," "read your piece," "saw you in the [community]" — anchoring the request in a real context immediately makes it feel less random.
Don't pitch in the note. The note is for getting connected. The DM after acceptance is for everything else.
Match the tone of their profile. If their profile reads casual, write casual. If they're an executive at a Fortune 500, write more formally. Mismatched register is a quiet rejection signal.
Be honest about why. "Adding you here" is more accepted than "would love to learn more about your work" — because the first one tells the truth (you're connecting), and the second one telegraphs that an ask is coming.
After They Accept: The Actual First Message
This is where most people accidentally damage what they just built.
The recipient accepts. Five minutes later, they receive a 400-word pitch in their DMs. The whiplash is jarring — and increasingly common, because automation tools have made the "accept → pitch" sequence cheap.
A better cadence:
- Don't message immediately on acceptance. Wait at least a day.
- Send a short, no-ask first message. Something like "Thanks for connecting — glad to have you in the network. If our paths cross at [event/space], would be great to grab coffee." That's the whole thing.
- Save the actual ask for the second or third exchange, after you've earned the right.
This sounds slow. It is. And it converts far better than the alternative — because it doesn't burn the trust you built in the connection step.
If you're sending more than a handful of these a week, holding the post-acceptance state in your head will break. This is where a LinkedIn CRM helps — tagging new connections by source (event, content, intro) and setting a follow-up reminder for the right moment. Inside Narrow, each new connection can be labeled and queued for follow-up so the post-acceptance step doesn't get dropped.
What to Stop Doing
A short list of habits that hurt acceptance rates:
- Adding everyone in your industry "just to grow the network." LinkedIn's algorithm rewards quality of engagement, not raw connection count.
- Connecting without reading the profile. Recipients can tell when you didn't look.
- Recycling the same template note across hundreds of requests. They show up in the recipient's feed alongside identical notes to their peers; the pattern is visible.
- Connecting to and DMing within the same minute. Reads as a bot sequence.
- Using emoji as the entire note. "👋" tells the recipient you didn't even type a word.
- Following "Connect" with "I'd love to hop on a quick call." This is the single most common pattern that makes people decline.
The Acceptance Rate Math
If you're sending a meaningful number of connection requests — say, 10+ a week — small changes compound.
A 20% acceptance rate (typical for generic, blank requests to strangers) gives you 2 new connections per 10 sent.
A 60% acceptance rate (achievable with short, specific notes) gives you 6.
Over a year, that's the difference between ~100 new useful connections and ~300. The 200-person delta is, for most professionals, the bulk of their relevant network growth.
You don't get there by sending more.
You get there by sending better — and never sending a blank request to someone who has no idea who you are.
Final Thought
The connection request is the smallest piece of LinkedIn outreach.
It's also the easiest one to mess up.
A blank request to someone outside your circle reads as low-effort. A pitch-coded note reads as the start of a sequence the recipient doesn't want. A generic compliment reads as a template.
What works is what works for almost every form of outreach: one to three sentences, a real reason, a specific reference, and no immediate ask.
Do that consistently and the right people will say yes — at rates that compound across your entire career.
Narrow is the LinkedIn CRM for people who care which connections they make — labels, follow-up reminders, and a clean inbox built around real relationships. Try it free.