LinkedIn Connection Request Messages: 18 Examples for Every Scenario

Updated March 8, 2026 · 17 min read

You have 300 characters to convince a stranger to let you into their professional network. That is roughly two sentences. One mediocre greeting and a generic ask, and you have used your entire budget on nothing.

The connection request is the single most important message in LinkedIn outreach. If it does not get accepted, everything downstream — your follow-up, your pitch, your relationship — never happens. And yet most people either skip the note entirely or paste in something so generic that it actively hurts their acceptance rate.

This guide gives you 18 connection request messages organized by the specific scenario you are in: reaching out to a prospect, a recruiter, a peer, a speaker, a hiring manager, or someone you met at an event. Every template fits within the 300-character limit, includes the exact character count, and explains the psychology behind why it works. We also cover what to do after they accept — because the connection request is not the destination, it is the door.

What you will learn

  1. The 5 rules of high-acceptance connection requests
  2. With a note vs. without: when each works better
  3. Connection requests for sales prospecting (4 examples)
  4. Connection requests for recruiters (3 examples)
  5. Connection requests for professional networking (4 examples)
  6. Connection requests for job seekers (4 examples)
  7. Connection requests for special scenarios (3 examples)
  8. What to say after they accept (the critical follow-up)
  9. 5 connection request mistakes that get you ignored
  10. FAQ

The 5 Rules of High-Acceptance Connection Requests

Before you look at a single template, internalize these five rules. They are the difference between a 30% acceptance rate and a 70%+ acceptance rate.

Rule 1: Answer the "why" in the first sentence

When someone gets your connection request, they ask one question: "Why is this person connecting with me?" If they cannot answer that question within the first line, they ignore it. Your first sentence should make the reason immediately obvious: a mutual connection, a shared event, a post they wrote, or a specific detail about their work.

Rule 2: Never pitch in the connection request

The connection request is the handshake, not the sales presentation. Trying to sell, book a meeting, or describe your product in 300 characters is the fastest way to get declined and reported. The only goal of the connection request is to get accepted. Everything else comes after.

Rule 3: Be specific or be silent

"I came across your impressive profile" is worse than no note at all. If you cannot name something specific — a post they wrote, a project they led, a company milestone, a mutual connection — do not fake it with vague compliments. A blank connection request (no note) has a higher acceptance rate than a generic note because at least the blank one does not actively signal laziness.

Rule 4: Keep it under 280 characters

The limit is 300, but the best-performing requests use 200-280 characters. This forces you to cut filler words and get to the point. On mobile (where most LinkedIn activity happens), shorter notes are fully visible without tapping "see more" — which means your entire message gets read in one glance.

Rule 5: Make accepting feel safe

People decline connection requests when they sense they are about to be spammed. Your note should feel like connecting with you is low-risk. Phrases like "no pitch, just want to follow your work" or "would love to trade notes" signal that accepting will not result in an immediate DM barrage.

Acceptance rate benchmarks: The average LinkedIn connection request (with no note) gets accepted roughly 30% of the time. A personalized note referencing something specific boosts this to 40-50%. A note that mentions a mutual connection pushes acceptance to 50-70%. The best-performing requests reference a specific detail and a mutual connection, consistently hitting 60-78% acceptance rates.

With a Note vs. Without: When Each Works Better

This is the most debated question in LinkedIn outreach. The answer is nuanced.

Scenario Best approach Why
You have something specific to reference Send a note A personalized note increases acceptance by 30-40%
You share a mutual connection Send a note Mentioning mutual connections is the strongest predictor of acceptance
They recently posted content you engaged with Send a note They may already recognize your name from their notifications
You have no specific reference point No note A blank request is better than a generic one — it at least does not hurt you
Your profile is strong and speaks for itself No note If your headline, photo, and recent activity are compelling, the request stands alone
You are sending high volume (15+ per day) No note for most, note for high-priority targets Reserve your personalization effort for the prospects who matter most

The bottom line: a great note beats no note. No note beats a bad note. If you cannot write something genuinely personalized in 2 minutes of profile scanning, skip the note and invest that time in the follow-up DM instead.

Connection Requests for Sales Prospecting

Sales connection requests are the trickiest because the recipient's guard is already up. Decision-makers receive dozens of pitchy requests per week. Your note needs to be obviously different from the mass-sent templates in their queue.

Example 1: The Trigger Event · 248 characters

Hi [Name], saw [Company] just [raised a Series B / launched in Europe / hired 10 engineers]. Exciting trajectory. I work with companies at that stage on [specific area]. Would love to follow your growth and connect.

Why it gets accepted: References a verifiable, timely event. Shows you know something specific about their company right now, not six months ago. Does not pitch — just expresses genuine interest in following their growth.

Example 2: The Mutual Connection · 232 characters

Hi [Name], we are both connected with [Mutual Name] — we worked together at [Company]. Your work in [their specialty area] caught my eye. Would love to connect and trade perspectives sometime.

Why it gets accepted: Mutual connections are the single strongest predictor of acceptance. The recipient thinks: "If they know [trusted person], they are probably credible." Keep the mutual connection reference brief but real.

Example 3: The Content Appreciator · 256 characters

Hi [Name], your post about [specific topic] last week was one of the few that actually made me stop scrolling. The point about [specific detail] is something we are dealing with firsthand. Would love to connect and follow your takes.

Why it gets accepted: References a specific post with a specific detail, proving you actually read it. The phrase "made me stop scrolling" is a genuine, non-generic compliment. No pitch, no ask — just a human reacting to their content.

Example 4: The Industry Peer · 218 characters

Hi [Name], we are both in the [niche, e.g., "B2B fintech"] space and I have been following [Company]'s approach to [specific challenge]. Would love to be connected and keep learning from what your team is building.

Why it gets accepted: Positions you as a peer, not a vendor. Mentioning a specific challenge their company faces shows industry knowledge. The "keep learning" framing is humble and non-threatening.

Connection Requests for Recruiters

Candidates are bombarded by recruiter requests. The ones that get accepted share one trait: they make the candidate feel seen, not targeted.

Example 5: The Skill-Specific Request · 262 characters

Hi [Name], came across your work on [specific project or repo]. Your approach to [technical detail] is exactly the kind of thinking we are building around at [Company]. No pitch — just impressed and would love to connect.

Why it gets accepted: References a specific project, not just their job title. "No pitch" preempts the candidate's instinct to decline recruiter requests. This reads like a message from someone who actually looked at their work, not someone who searched "senior engineer" and hit "connect" 200 times.

Example 6: The Passive Talent Scout · 244 characters

Hi [Name], I specialize in placing [niche, e.g., "senior product designers at growth-stage startups"]. I am not reaching out about a specific role — just building my network of strong people in this space. Would love to stay connected.

Why it gets accepted: Honest about intent (building a network, not filling a req). The niche specialization signals that you are not a mass-message recruiter. Passive candidates are more receptive when there is no pressure to respond about a specific job.

Example 7: The Alumni Connection · 228 characters

Hi [Name], fellow [University] alum here! I recruit for [type of roles] at [Company] and always love connecting with people from [University] who are doing interesting work in [field]. Would be great to be connected.

Why it gets accepted: Shared alma mater is one of the highest-performing connection hooks. It immediately creates a sense of community and in-group belonging. Even if the candidate is not looking, they are likely to accept a fellow alum.

Connection Requests for Professional Networking

Networking requests have the highest acceptance rates because they carry the least perceived risk. No one suspects a networking request is going to turn into a sales pitch (though many unfortunately do). Keep that trust by keeping it genuine.

Example 8: The Genuine Admirer · 242 characters

Hi [Name], I have been following your writing on [topic] for a while. Your piece on [specific article or post] changed how I think about [area]. Would love to connect and keep learning from your perspective. No agenda, just genuine respect.

Why it gets accepted: Specific, verifiable reference to their content. "Changed how I think" is the kind of compliment that resonates because it implies actual impact, not just casual reading. "No agenda" sets expectations clearly.

Example 9: The Same-Boat Peer · 236 characters

Hi [Name], we are both [role, e.g., "product leads at Series B startups"] trying to figure out [shared challenge, e.g., "how to scale without killing the culture"]. Would love to connect and compare notes. Always better with a peer group.

Why it gets accepted: Identifies a shared professional challenge, creating instant rapport. The "compare notes" framing positions you as a peer, not someone who wants something. The shared identity ("we are both...") makes them feel like part of a group.

Example 10: The Group/Community Member · 220 characters

Hi [Name], saw we are both members of [LinkedIn Group or Slack community]. Your comment on [specific thread or topic] stood out. Would love to connect here as well and keep the conversation going.

Why it gets accepted: Shared group membership provides context for the request. Referencing a specific comment proves you are an active participant, not just a lurker mass-connecting with the member list.

Example 11: The Conference Follow-Up · 252 characters

Hi [Name], great running into you at [Event]. Your point about [specific topic from their talk or conversation] stuck with me. I have been thinking about how it applies to [your context]. Would love to stay connected and continue the thread.

Why it gets accepted: Post-event requests have some of the highest acceptance rates because there is a shared experience anchoring the request. The specific reference to something they said shows you were paying attention, not just collecting badges.

Connection Requests for Job Seekers

Job seeker requests walk a fine line: you need something from them, but you cannot lead with that need. The best approach is to lead with genuine interest in their work and let the career conversation emerge naturally.

Example 12: The Targeted Applicant · 268 characters

Hi [Name], I just applied for the [Role] at [Company]. Your team's work on [specific project or product] is a major reason I am excited about the opportunity. Would love to connect regardless of outcome — the work you are doing is worth following.

Why it gets accepted: Shows you already applied (you are serious). References specific work the team has done. "Regardless of outcome" removes the pressure — you are not asking them to do anything, just expressing genuine admiration.

Example 13: The Informational Interview Seeker · 270 characters

Hi [Name], I am exploring roles in [area] and your career path from [previous role] to [current role] is exactly the trajectory I am working toward. I would love to connect and learn how you made that transition. No big ask, just genuine curiosity.

Why it gets accepted: Flatters without being generic — referencing their specific career trajectory shows you studied their profile. People enjoy sharing career advice because it positions them as experts. "No big ask" sets clear, low-pressure expectations.

Example 14: The Referral Seeker · 248 characters

Hi [Name], we worked together at [Company] / we both graduated from [University]. I saw [Their Company] has an opening for [Role] that aligns perfectly with my background in [area]. Would love to connect and catch up. Hope you are doing well!

Why it gets accepted: Leverages an existing relationship (former colleague or fellow alum). The referral ask is implicit, not explicit — you are reconnecting first, not demanding a favor. This warmth makes the eventual "any chance you could refer me?" much easier.

Example 15: The Industry Learner · 234 characters

Hi [Name], I am transitioning into [industry] and your work at [Company] in [specific area] is exactly what I am studying to understand. Would love to connect and follow your updates as I build my knowledge in this space.

Why it gets accepted: Humble and specific. You are not pretending to be an expert — you are openly learning, which is disarming. Asking to "follow your updates" is the lightest possible ask and feels flattering to the recipient.

Connection Requests for Special Scenarios

Example 16: Reconnecting With an Old Contact · 230 characters

Hi [Name], it has been a while! I saw you moved to [New Company] — congrats on the move. I have been [brief update about yourself]. Would love to reconnect and hear what you are working on these days.

Why it gets accepted: References a specific change in their career (proves you noticed). Shares a brief update about yourself (reciprocity). The casual, warm tone matches the existing relationship. Almost always gets accepted because they already know you.

Example 17: Connecting With a Speaker or Thought Leader · 276 characters

Hi [Name], watched your talk at [Event] on [topic]. Your framework for [specific concept] is something I have already started applying at my company. Results so far: [one brief result]. Thank you for sharing it publicly — would love to follow your work more closely.

Why it gets accepted: Goes beyond "great talk!" by showing you implemented their ideas and got results. This is the most compelling compliment a thought leader can receive. They will almost certainly accept and likely respond with curiosity about your results.

Example 18: The Partnership Inquiry · 258 characters

Hi [Name], I run [Your Company] — we do [brief, one-line description]. I think there is interesting overlap with what [Their Company] is building in [area]. Would love to connect and explore whether there is something worth discussing down the road.

Why it gets accepted: Concise, direct, and clearly states intent without pitching. "Down the road" signals patience and no pressure. Identifying specific overlap shows you thought about the connection before sending it.

What to Say After They Accept: The Critical Follow-Up

The connection request opened the door. Now you need to walk through it. What you send in the first 24-48 hours after acceptance determines whether this becomes a real relationship or just another dormant connection.

The 24-hour rule

Send your follow-up DM within 24 hours of acceptance. Why? Because your name is still fresh in their mind. They just saw your connection request, glanced at your profile, and decided to accept. If you wait a week, you are starting from scratch — they will not remember why they accepted you.

The follow-up formula

Your first DM after acceptance should follow this simple structure:

  1. Thank them (1 sentence)
  2. Add value — share a relevant resource, insight, or observation (1-2 sentences)
  3. Ask a low-commitment question (1 sentence)
Follow-Up Example: After a Sales Connection Request

Hi [Name], thanks for connecting! I noticed [Company] recently [specific observation about their business]. We have been working with a few companies in [their industry] on the same challenge and published some data on what is working: [link]. Curious — is [pain point] something your team is focused on this quarter?

Why it works: Thanks them briefly (not effusively). Adds value with a resource relevant to their situation. Ends with a question they can answer in one word. Total: under 500 characters. This is where the real conversation begins.

Follow-Up Example: After a Networking Connection Request

Hi [Name], appreciate the connection! Your post about [topic] last week actually prompted us to rethink our approach to [related area]. Quick question: how did you decide to [specific strategic decision they mentioned]? Genuinely curious about the thought process.

Why it works: Shows you are engaged with their content (not just collecting connections). Asks a thoughtful, specific question that most people enjoy answering. No ask for their time, no pitch — just a genuine conversation starter.

Automating follow-up timing with snooze

Here is the practical challenge: if you are sending 15-20 connection requests per day, acceptances trickle in over the next 1-7 days. Remembering who accepted when — and timing your follow-up DM accordingly — is a logistics nightmare.

The fix is simple: when someone accepts your request, send your follow-up DM immediately, then snooze the conversation for 4-5 days. If they reply, the conversation resurfaces when they do. If they do not reply, it resurfaces in 4-5 days for a follow-up message. Either way, nothing falls through the cracks.

With SuperLinkin, press H to snooze any conversation. The thread disappears from your inbox and reappears at the top on the day you set. Combined with a follow-up strategy, this turns your LinkedIn inbox into a self-managing pipeline without spreadsheets, calendar reminders, or mental overhead.

5 Connection Request Mistakes That Get You Ignored

Mistake 1: Pitching in the connection note

"Hi [Name], I help companies like yours increase revenue by 40% through our AI platform. Would love to show you a quick demo. When are you free?"

What is wrong: You are asking a stranger to book a demo before they have agreed to connect with you. This is like walking up to someone at a conference and handing them your product brochure before saying hello. Automatic decline.

Mistake 2: The generic compliment

"Hi [Name], I came across your impressive profile and would love to connect. Your experience is truly inspiring!"

What is wrong: What specifically is impressive? Which experience is inspiring? When everything is "impressive" and "inspiring," nothing is. This reads like a template — because it is. Recipients can spot it instantly because they receive 5-10 of these per week, all using the same words.

Mistake 3: The LinkedIn default message

"I'd like to add you to my professional network on LinkedIn."

What is wrong: This was LinkedIn's auto-generated default text for years. Using it tells the recipient you did not even take 10 seconds to type a custom note. It is the connection request equivalent of a form letter. Sending no note is better than this.

Mistake 4: Making it about you

"Hi, I'm a growth marketing expert with 10+ years of experience helping SaaS companies scale. I'd love to connect and share my insights with you."

What is wrong: Three sentences, and all three are about the sender. Nothing about the recipient, their work, or why connecting would benefit them. The phrase "share my insights with you" implies they need your help — an assumption that feels presumptuous from a stranger.

Mistake 5: The wall of text

"Hi [Name], I noticed that you work in the SaaS space and have extensive experience in product management. At my company, we have developed a revolutionary new approach to customer onboarding that reduces time-to-value by 60%. I have been following your..."

What is wrong: This message is going to get cut off at 300 characters, right in the middle of a sentence. On mobile, it looks even worse. The recipient sees an incomplete thought and a wall of tiny text. Even if the message is technically within the limit, filling all 300 characters with dense text feels overwhelming. White space is your friend — shorter notes look more approachable.

Turn Accepted Connections Into Real Conversations

SuperLinkin adds snooze, templates, labels, and keyboard shortcuts to your LinkedIn inbox. Time your follow-up DMs perfectly with snooze, insert templates with one keystroke, and track every connection by stage with labels. Free during early access.

Try SuperLinkin Free

Frequently Asked Questions

What should I write in a LinkedIn connection request?

Write a short, personalized note (under 300 characters) that answers three questions: how you found them, what you have in common, and why you want to connect. Reference something specific — a mutual connection, a post they wrote, or a shared industry. Do not pitch your product or ask for a meeting. The goal is to get accepted, not to make a sale.

What is the character limit for LinkedIn connection requests?

300 characters, including spaces and punctuation. Free accounts are further limited to approximately 10 personalized connection requests per month. LinkedIn Premium and Sales Navigator users can include personalized notes on all requests. Aim for 200-280 characters — short enough to read in a glance, long enough to include a specific detail.

Should I send a connection request with or without a note?

If you can write something genuinely personalized, send a note — it increases acceptance by 30-40%. If you cannot, send no note. A generic note like "I'd like to add you to my professional network" actually performs worse than a blank request because it signals zero effort.

How many connection requests can I send per day?

LinkedIn allows approximately 100 per week (~20/day). New accounts should start with 10-15 per day and ramp up gradually. Sending too many, especially if many are ignored, can trigger temporary account restrictions. Focus on fewer, well-targeted requests rather than hitting the daily maximum.

What should I do after someone accepts?

Send a follow-up DM within 24-48 hours. Thank them briefly, add value with a relevant resource or observation, and ask a low-commitment question. Do not immediately pitch. Keep the first DM under 500 characters. The connection request opened the door — the follow-up starts the relationship.

What if my connection request gets ignored?

Wait 2-3 weeks, then withdraw the request and try again with a different approach (or try engaging with their content first by commenting on a post). Do not send a follow-up message while the request is still pending — you cannot message someone who has not accepted you yet unless you use InMail. Pending requests that sit for more than 3 weeks are very unlikely to be accepted.

The Connection Request Mindset

The best connection request is not a message. It is an answer to a question the recipient did not know they were asking: "Is this person worth knowing?"

In 300 characters, you cannot explain your product, share a case study, or make a compelling pitch. You can do one thing: make the recipient curious enough to click "Accept." That is all you need. The real conversation — the value exchange, the relationship building, the eventual business discussion — happens in the DMs that follow.

Invest 2 minutes scanning their profile. Write something specific. Keep it short. Make accepting feel safe. Then do the real work in the follow-up.

Last updated: March 2026. Acceptance rate data is sourced from aggregated LinkedIn outreach reports and platform research.


Keep Reading

Free Tools: LinkedIn Message Character Counter | LinkedIn Connection Request A/B Test Planner | LinkedIn Outreach Volume Calculator