The difference between a 15% and a 45% LinkedIn connection acceptance rate usually isn't your product or your offer — it's what you write in the request. Most people send the default blank request or paste a generic template that signals zero research. The ones that get accepted treat the request as a social moment, not a sales pitch. Here are 20 templates that work in 2026, organized by ICP and context, plus how to run them at scale without a Chrome extension that bans your account.
Short answer: LinkedIn connection requests work best when they're under 200 characters, reference something specific about the recipient (their role, company, or recent activity), and contain no pitch or call-to-action. The goal of the request is to get accepted — the sales conversation starts after. Well-personalized requests to matched ICPs see 35-55% acceptance rates vs 15-20% for generic requests.
Why Most LinkedIn Connection Requests Get Ignored
The three patterns that kill acceptance rates:
- Blank requests: No message at all. You're asking someone to connect with a stranger based on nothing. Fine for warm connections; low-conversion for cold outreach.
- Copy-paste pitches: "Hi {FirstName}, I help companies like yours increase revenue by 300%..." The recipient's guard goes up immediately and they decline.
- Fake familiarity: "I've been following your work for years!" when you've never interacted. People recognize this pattern and it signals inauthenticity.
What works instead: a brief, genuine message that shows you know something specific about them, explains why connecting makes sense, and asks for nothing. The connection request is not where you pitch. It's where you earn the right to start a conversation.
The Rules Behind Connection Requests That Work
The rules: Keep it under 300 characters (LinkedIn's limit for mobile display). Include one specific hook — something about their role, company, or recent activity. No pitch, no link, no call-to-action. Write in first person, casual tone. One soft reason to connect ("I work with similar teams" or "I'm building in this space"). That's it.
The character limit matters for a practical reason: on mobile, LinkedIn truncates the preview at around 200 characters. If your key message is in the last sentence, it won't be seen until they tap to expand — and most people won't.
Personalization drives acceptance rates more than any copywriting trick. A template that references their actual role and company at a 35-word length outperforms a beautifully written 300-character generic message. The signal is: "this person actually looked at my profile." That's what earns the accept.
20 Templates Organized by ICP and Context
These templates use placeholder variables: {first_name}, {company}, {role}, {specific_hook}. The specific_hook is where personalization lives — a recent post they shared, a role change, a company milestone, or a mutual connection. Fill this in before sending.
For Founders and GTM Leads
Template 1 — Role context:
"Hey {first_name} — noticed you're building GTM at {company}. Running into similar challenges around outbound scaling with a few teams in {industry}. Would be good to connect."
Template 2 — Shared problem:
"Hi {first_name} — I work with {role} teams on the {specific_problem} side of outbound. Your profile came up and it looked like it might be relevant. Happy to connect either way."
Template 3 — Recent activity hook:
"Hey {first_name} — caught your post on {topic}. Good take. I work in the same space — would be worth staying connected."
Template 4 — Company signal:
"Hi {first_name} — saw {company} recently {milestone: raised/launched/expanded}. I work with teams at similar stages on {relevant_area}. Thought it made sense to connect."
Template 5 — Peer framing:
"Hey {first_name} — building something in the {space} space myself. Your work at {company} keeps coming up in conversations I'm having. Worth connecting."
Template 6 — Short and direct:
"Hi {first_name} — {role} at {company}. Working on similar problems in {industry}. Would be good to have you in the network."
For Agency Operators
Template 7 — Agency-to-agency:
"Hey {first_name} — running an agency myself in {niche}. Your work at {company} is interesting — especially {specific_thing}. Would be good to connect with other operators."
Template 8 — Prospect framing:
"Hi {first_name} — I work with {company_type} owners on {specific_outcome}. Your profile came up and it looked like a fit. Happy to connect and share what we're seeing."
Template 9 — Referral angle:
"Hey {first_name} — {mutual_connection} mentioned you're doing interesting work at {company}. Made sense to connect directly."
Template 10 — Service angle (soft):
"Hi {first_name} — I help {role} teams with {specific_deliverable}. Noticed {company} is growing fast — thought it might be relevant. Worth connecting?"
Template 11 — Community/event:
"Hey {first_name} — saw you at {event/community}. Running an agency in a similar space — would be good to stay connected."
For Recruiters
Template 12 — Role match:
"Hi {first_name} — your background in {skill/area} at {company} is exactly what a few teams I work with are looking for. Would be good to connect in case the timing ever works."
Template 13 — Career stage awareness:
"Hey {first_name} — {role} at {company} is a good spot. I work with {seniority} folks in {industry} when they're ready to explore what's next. Happy to connect now or later."
Template 14 — Passive framing:
"Hi {first_name} — not sure if you're looking, but your profile came up for a {role_type} opportunity I'm working on. Thought it worth connecting regardless."
Template 15 — Short and honest:
"Hey {first_name} — recruiter here, specializing in {space}. Your profile is strong. Would be good to have you in my network for when the right thing comes along."
Template 16 — Referral request:
"Hi {first_name} — I work with {company_type} teams on hiring {role}. You may know someone — would be helpful to connect and compare notes."
Template 17 — Warm (recent post):
"Hey {first_name} — your post on {topic} was useful. I work in the same space. Happy to connect."
Template 18 — Industry peer:
"Hi {first_name} — building a network of {role} professionals in {industry}. Your experience at {company} looks relevant. Would be good to connect."
Template 19 — Simple and genuine:
"Hey {first_name} — your background in {area} is interesting. I work with similar profiles. Happy to connect."
Template 20 — The honest ask:
"Hi {first_name} — I'll be direct: I help {company_type} teams with {specific_value}. Whether or not that's relevant, your profile is worth having in my network. Happy to connect."
What to Send After They Accept
Most connection requests that fail don't fail in the request — they fail in what comes next. The standard mistake: send a pitch within 24 hours of acceptance. This converts a social acceptance into a cold sales signal and damages the relationship you just started.
A better pattern for the first message after acceptance:
- Day 1-2 after acceptance: Nothing. Let the connection settle. Some people will message you first.
- Day 3-5: A brief message that continues the context you opened in the request. "Thanks for connecting, {first_name}. Quick question on your side — are you seeing [relevant thing] as a challenge at {company} right now?"
- Day 7+: If no reply, a light engagement sequence — comment on something they post, share something relevant to their role. Build familiarity before a second direct message.
The LinkedIn outreach strategy guide covers the full sequence structure from connection through conversion. And the LinkedIn connection request automation guide covers the technical setup for running requests through cloud-based tooling.
Automating Personalized Requests at Scale
Manually sending 20-30 personalized connection requests per day is sustainable for a solo founder. For an agency running outreach for multiple clients, or a sales team working a list of 500+ prospects, you need automation — but the wrong automation gets accounts banned.
The two approaches and their risks:
- Chrome extensions (Expandi, Phantombuster personal-browser tools): Run from your local browser, mimicking manual actions. LinkedIn detects unusual session patterns and flags accounts. The risk scales with volume — fine for low-volume testing, genuinely dangerous at 50+ requests per day.
- Cloud-native API tools (ACA via Unipile): Connect via official API channels, not browser automation. No browser fingerprint risk. Safer at volume and safe for multi-account management (agencies running outreach for multiple clients).
ACA's LinkedIn integration runs through Unipile's cloud API. You build your connection request templates in ACA, define personalization variables (role, company, specific_hook), and ACA sends requests through your LinkedIn account via compliant API routing — not a Chrome extension running on someone's laptop.
For agencies, this matters because you can run 5-10 client accounts from one platform without installing extensions on five different machines. The safe LinkedIn automation guide covers the full risk framework. And the LinkedIn outreach automation guide covers what compliant automation looks like at scale in 2026.
As I've observed running outreach systems for agencies: the volume limit that matters isn't what LinkedIn officially publishes — it's the pattern that triggers their ML-based detection. Cloud-based tools with proper session simulation stay safer because the behavioral pattern looks more like a human than a browser script running at consistent intervals.
FAQ
How long should a LinkedIn connection request message be?
Under 300 characters ideally — this fits within LinkedIn's mobile preview without truncation. The sweet spot is 100-200 characters: long enough to include a specific hook, short enough to read in a glance. Anything longer and you risk the recipient not reading the full message before deciding to accept or ignore.
Should I mention my product in a connection request?
No. A connection request is not a cold email. It's a social action that asks for permission to be in someone's network. Mentioning your product immediately signals "this is a sales pitch" and dramatically reduces acceptance rates. Save the product mention for a follow-up message after they've accepted and you've had at least one exchange.
What's a good LinkedIn connection request acceptance rate?
In our experience, personalized connection requests to well-matched ICP contacts achieve 35-55% acceptance rates. Generic requests to the same audience average 15-20%. Blank requests (no message) depend heavily on how strong your profile is — typically 20-35% for an established profile. Below 20% on personalized requests usually means the ICP targeting is off, not the message.
How many LinkedIn connection requests can I send per day?
LinkedIn's official limit is 100 per week for most accounts, but safe daily volumes depend on your account age and activity. In our experience: new accounts should stay under 10-15 per day. Established accounts (2+ years, active engagement) can handle 20-30 safely. Accounts approaching these limits regularly risk restrictions regardless of whether the requests are sent manually or via automation.
What's the difference between a connection request and an InMail?
A connection request requires no prior relationship and is free but limited in volume. An InMail reaches people you're not connected to and bypasses the connection step — but requires LinkedIn Premium credits and is typically less effective for cold outreach because recipients know it's paid. For B2B outreach at volume, connection requests + follow-up messages outperform InMail in reply rate and cost-efficiency.