A connection request is a strange little document. It's forty words long, it's the first thing a prospect ever reads from you, and most people write it as though nobody's reading. Get it right and you've opened a channel to a future client, referral partner, or door-opener. Get it wrong and you've spent your one first impression proving you weren't worth a first impression.
The good news: the bar is on the floor. Almost every request in your prospect's queue fails in one of three predictable ways, so a message that simply avoids them is already unusual.
Key takeaways
- Requests fail three ways: the blank click (no note), the pitch in disguise, and the padded note that says nothing a hundred other notes didn't.
- A request that gets accepted passes three tests: it's specific (it could only have been written to this person), it's short, and it's about them — the reason to connect is theirs, not yours.
- When you send matters as much as what you send. Send while the interaction is still warm — the evening of the event, the day of the comment thread — not "when things calm down."
- For strangers in your ICP, earn the context before you ask for it: a couple of weeks of real engagement with their posts changes the request from an intrusion into a formality.
- Housekeeping: withdraw requests still pending after a month. LinkedIn lets you send a fresh one three weeks after a withdrawal.
The three ways requests fail
The blank click. The bare "connect" with no note. It isn't offensive, it's invisible — zero effort spent, so zero reason to say yes. Busy people in your ICP dismiss these without thinking, which is exactly the amount of thought that went into them.
The pitch in disguise. "I'd love to connect and share how we help companies like yours…" This is the worst option, not merely the laziest. It confirms every suspicion a decision-maker already holds about salespeople on LinkedIn, and it can get you reported — which degrades your ability to send requests at all.
The padded note. The quiet failure, and the most common among people who are actually trying: a note that's polite, grammatical, and completely interchangeable. "I'm always looking to expand my network with fellow professionals in the space." Nothing in that sentence required knowing who they are. If your note would survive a find-and-replace of the recipient's name, it's padding, and it reads as padding.
The three tests
Forget checklists of adjectives. A request that gets accepted passes three tests, and the first one does most of the work.
1. Could this have been written to anyone else? If yes, rewrite it. Specificity is the whole ballgame — their post from Tuesday, their session at the conference, the thing they said in someone else's comment thread that you actually thought about. Specificity is the only proof of attention that can't be faked at scale, which is precisely why it lands. Its opposite is not rudeness; it's the padded note above.
2. Is it short? Two or three sentences. Under 300 characters. Length reads as a demand on the recipient's time, and a demand is a strange thing to make of someone who owes you nothing. Brevity is a form of respect that costs you nothing to give.
3. Whose reasons is it built on? People accept requests to serve their own interests, not yours — obvious when stated, ignored constantly in practice. A request framed around what you're hoping to sell, learn, or get has answered the wrong question. The right frame is: why would they want this name in their network? Sometimes the honest answer is "because I've been usefully engaged with their work for a month," which is a fine answer — but you have to have done the month.
A note on compliments, since they're the most abused tool here: a specific one ("your take on pricing last week reframed how I think about it") creates real goodwill. A generic one ("Great profile!") lands cold, and an AI-flavored one lands worse than silence. Everyone can smell butter.
Nine templates by scenario
Adapt the wording — a template pasted verbatim reads like a template. These are skeletons, not scripts.
After meeting someone (event, call, intro):
[Name], I enjoyed our conversation at [event] — your take on [topic] stuck with me. I'd like to stay connected here.
Before an event you'll both attend:
[Name], I saw you're speaking at [event] next month. I'll be there and I'm looking forward to your session on [topic]. Let's connect beforehand.
After a sales or discovery call:
[Name], thank you for the conversation today — I enjoyed learning how you're approaching [challenge]. I noticed we weren't connected here yet, so I'm fixing that.
Via a mutual connection:
[Name], I noticed we're both connected to [mutual]. Since we're both working in [space], it seemed like a connection worth making.
They viewed your profile:
[Name], thanks for stopping by my profile. I read yours in turn — given your work on [topic], I'd be glad to be connected.
You've been engaging with their content (the warm stranger):
[Name], your recent post on [topic] gave me a genuinely fresh angle on [takeaway] — I've been following your writing for a few weeks now. I'd love to stay connected and keep learning from it.
They engaged with your content:
[Name], I appreciated your comment on my post about [topic] — you're right about [their point]. Seemed like a conversation worth continuing as connections.
Podcast / talk / article author:
[Name], your episode on [show] about [topic] was strong enough that I sent it to a client the same day. Connecting so I don't miss what you publish next.
Shared community or group:
[Name], we're both in [community], and your answers in the [topic] thread have been consistently the sharpest in the room. I'd like to connect here too.
The warm-up: how to connect with total strangers
The templates above all lean on some existing context. But the people you most need — ICP decision-makers who've never heard of you — offer none. Sending even a well-written request cold means asking a stranger to let a salesperson into their feed.
The fix is to manufacture the context before you need it. For two or three weeks before the request: react to their posts, leave short comments that add something real, reply to their comments on other people's threads. None of this is a trick. Attention is genuinely scarce, and paying someone attention they didn't ask for and can't repay is one of the few things on this platform that still registers as sincere. By the time your request arrives, you're not a stranger — you're the person with the thoughtful comments, and the request is a formality rather than an intrusion.
Then the request writes itself — it's the "warm stranger" template above, and it's true.
This warm-up is the single highest-leverage change most solo operators can make to their outreach. It's also the most tedious to track by hand across dozens of prospects, which is exactly the class of problem we started building Quarz to solve. But a spreadsheet and discipline work too.
Timing: send while it's still warm
A perfect message sent at the wrong moment still dies. Whatever goodwill an interaction generates begins evaporating the second it ends, and the request has to arrive before it's gone.
Met someone at an event? Send it that evening, not "when things calm down." Good comment exchange this morning? Send it today. The failure mode is always the same: the card goes in a pocket, you mean to follow up, and six weeks later you're a stranger with a vaguely familiar name — which is worse than a clean stranger, because now they have to work out why they half-recognize you before they can even decide.
Housekeeping helps too. Check your sent requests monthly (My Network → Invitations → Sent) and withdraw anything pending over a month; the recipient is never notified. LinkedIn then lets you send a fresh one after three weeks, which is a genuine second chance — use it to arrive warmer and more specific than you did the first time, not to send the same note again.
What happens after they accept
One rule: do not pitch. The fastest way to convert a new connection into a block is the instant pivot — "thanks for connecting, here's my calendar link" — which takes the goodwill they just extended you and spends it, in full, on nothing. Say thank you, engage with their content, and let the relationship do its slow work. We cover the full post-acceptance playbook in how to send LinkedIn messages that get replies.
FAQ
Should I add a note to every LinkedIn connection request? Yes, with rare exceptions (someone you know well, or immediately after meeting in person). A good note is the difference between a request that gets evaluated and one that gets skimmed past.
How long should a connection request message be? Under 300 characters — two to three sentences. Brevity is part of politeness; long messages read as demands on the recipient's time.
What acceptance rate should I expect? With personalized, relevant requests to people who've seen you before, well over half. Cold requests to strangers with no warm-up will always underperform, no matter the wording.
Is it OK to connect with someone I've never interacted with? Yes — but do the two-week warm-up first. Engage with their content until your name is familiar, then send a request referencing that engagement.