How to Write LinkedIn Connection Requests That Get Accepted
Most LinkedIn connection requests get ignored. Not because people are rude, but because the messages are generic, self-serving, or just plain boring. "I'd like to add you to my professional network" has been the default for so long that it's become invisible.
The good news: a well-written connection request stands out immediately. Here's how to write one.
Why Most Requests Get Ignored
Before writing better messages, it helps to understand why people decline or ignore requests in the first place.
No context. The person doesn't know why you're reaching out. Without a reason, the default is to ignore.
Obvious pitch. If the note reads like the opening line of a sales email, people know what's coming. They'd rather not.
Too long. LinkedIn's connection request note has a 300-character limit. People don't read walls of text in a tiny modal window.
No relevance. The person can't figure out why you specifically chose them. Generic messages feel like spam even when they're not.
The fix for all of these is the same: be specific, be brief, and make it about them.
The Character Limit
LinkedIn connection request notes are capped at 300 characters. That's roughly two to three short sentences. You don't have room for a full pitch, a long introduction, or a list of reasons to connect.
This constraint is actually helpful. It forces you to identify the single most relevant thing to say. If you can't explain why you're reaching out in 300 characters, you probably haven't thought it through clearly enough.
A good rule of thumb: aim for 150-200 characters. Leave some breathing room. Short messages feel more confident than ones that push right up against the limit.
The Psychology of Acceptance
People accept connection requests from people who seem relevant, credible, and non-threatening. A few things that trigger acceptance:
Familiarity. If they recognize your name (from a comment you left, a mutual connection, or a shared community), they're far more likely to accept. Engage with someone's content before sending a request.
Specificity. A message that references something specific about them signals that you actually looked at their profile. It's harder to ignore than a generic note.
Mutual connection. Mentioning a shared connection adds instant social proof. "We're both connected to [Name]" is a simple but effective opener.
Shared context. Same industry, same event, same community, same problem. Any shared context creates a reason to connect.
No immediate ask. Requests that don't ask for anything feel safer. If your note ends with a question or a pitch, people know there's a follow-up coming. Sometimes that's fine, but it raises the stakes.
The Formula
A strong connection request note has three parts:
- Who you are or how you found them (one phrase)
- Why you're reaching out to them specifically (one sentence)
- Optional: a soft reason to connect (one phrase)
You don't always need all three. Sometimes one sentence is enough.
Examples by Use Case
Reaching Out to a Potential Customer
Weak: "Hi [Name], I'd love to connect and tell you about what we do at [Company]."
Strong: "Hi [Name], saw your post on scaling SDR teams. We help companies in that exact situation. Would love to connect and swap notes."
Why it works: References something specific, implies relevance without a hard pitch, and frames the connection as mutual.
Reaching Out After Meeting at an Event
Weak: "Hi [Name], great meeting you at [Event]. Let's connect!"
Strong: "Hi [Name], enjoyed our conversation about outbound strategy at [Event]. Wanted to stay connected."
Why it works: Specific reference to the conversation, not just the event. Shows you were paying attention.
Reaching Out to a Mutual Connection's Contact
Weak: "Hi [Name], I noticed we're both connected to [Mutual]. Thought I'd reach out."
Strong: "Hi [Name], [Mutual] mentioned you're building out your sales team. I work in that space and thought it'd be worth connecting."
Why it works: The mutual connection is a warm intro, and there's a clear reason for the connection beyond "we know the same person."
Reaching Out to a Thought Leader or Creator
Weak: "Hi [Name], I love your content. Would love to connect!"
Strong: "Hi [Name], your breakdown of [specific topic] changed how I think about [thing]. Would love to follow your work more closely."
Why it works: Specific reference to their content shows you actually read it. Flattery works when it's earned.
Reaching Out for a Job or Career Opportunity
Weak: "Hi [Name], I'm looking for opportunities at [Company] and would love to connect."
Strong: "Hi [Name], I've been following [Company]'s work on [specific thing]. I'm exploring roles in [area] and would love to learn more about your team."
Why it works: Shows genuine interest in the company, not just a job. Positions the connection as informational rather than transactional.
Reaching Out to a Peer in Your Industry
Weak: "Hi [Name], we work in the same industry. Let's connect!"
Strong: "Hi [Name], both working in [niche]. Your take on [topic] resonated. Would be great to have you in my network."
Why it works: Specific shared context, references their perspective, and keeps it simple.
Personalization at Scale
If you're running outreach campaigns and sending dozens of connection requests per day, full manual personalization isn't realistic. But you can still personalize at scale with the right approach.
Use dynamic variables. Tools like Outly let you insert variables like first name, company, job title, or industry into your connection request templates. A message that says "Hi [First Name], I work with a lot of [Job Title]s in [Industry]" feels more personal than a fully generic note.
Segment your audience. Write different templates for different segments. A message for startup founders should sound different from one for enterprise VPs. Segmenting by job title or company size lets you write templates that feel relevant to each group.
Reference recent activity. If someone posted recently, referencing that post is the highest-signal personalization you can do. It shows you're paying attention right now, not just pulling from a database.
Keep it short. Shorter messages are easier to personalize because there's less to fill in. A 100-character note with one specific detail beats a 280-character template with five generic variables.
What to Do After They Accept
The connection request is just the opening. What you do next matters more.
Wait at least 24 hours before sending a follow-up message. Sending a pitch the moment someone accepts is the fastest way to get unfollowed.
When you do follow up, keep it conversational. Ask a question, share something relevant, or reference why you connected in the first place. The goal of the first follow-up is to start a conversation, not close a deal.
If they don't respond to your first follow-up, one more message after a week is reasonable. After that, let it go. Persistence is good; pestering is not.
The One Rule That Covers Everything
Write the message you'd want to receive. If you got this exact note from a stranger, would you accept? Would you respond?
If the honest answer is "probably not," rewrite it. The bar isn't high. Most people are sending terrible connection requests. A specific, brief, relevant note puts you in the top 10% immediately.
