{"id":1073,"date":"2026-04-03T23:45:11","date_gmt":"2026-04-03T18:15:11","guid":{"rendered":"https:\/\/dealsflow.co\/blog\/?p=1073"},"modified":"2026-04-16T13:03:43","modified_gmt":"2026-04-16T07:33:43","slug":"linkedin-connection-request-message-templates","status":"publish","type":"post","link":"https:\/\/dealsflow.co\/blog\/linkedin-connection-request-message-templates\/","title":{"rendered":"LinkedIn Connection Request Message: 20 Templates With High Accept Rates"},"content":{"rendered":"<p>Your LinkedIn connection request message has one job: get accepted. Not start a conversation, not explain your product, not establish credibility. Just get accepted. Everything else happens after.<\/p>\n<p>Most connection notes fail because they try to do too much in 300 characters. They pitch before trust exists, compliment before context is established, or explain the sender&#8217;s business when the prospect has not asked. The result is a 20-25% acceptance rate when a well-written note on the same list, to the same personas, would produce 40-50%.<\/p>\n<p>This article covers the principles behind high-acceptance notes, the specific patterns that kill acceptance rates (and why they are everywhere), and 20 LinkedIn connection request message templates organized by scenario, each with a brief explanation of why it works. There is also a section on how to personalize at scale without spending 10 minutes per lead, and on how the note connects to the first message after acceptance.<\/p>\n<p>The templates here are frameworks. Use them as starting points, not copy-paste scripts.<\/p>\n<h2>What Makes a LinkedIn Connection Request Actually Get Accepted<\/h2>\n<p>A LinkedIn connection request is a social action before it is a sales action. The person receiving it is making a quick judgment about whether accepting has any cost to them. If the answer is no obvious cost and some plausible upside, they accept. If the note reads as a sales pitch, the calculation shifts: accepting means more sales messages. Most people opt out.<\/p>\n<p>Understanding this changes how you write the note entirely.<\/p>\n<h3>The One Question Every Prospect Asks<\/h3>\n<p>When someone sees an unknown connection request, they are asking one implicit question: &#8220;Why is this specific person reaching out to me?&#8221; Not &#8220;what does this company do&#8221; and not &#8220;what are they selling.&#8221; The note that answers that question briefly and genuinely, with no ask attached, has the highest probability of getting accepted.<\/p>\n<p>A note that references something real: a post they wrote, a mutual connection, a shared group, a recent company announcement, or even a clearly relevant professional overlap, answers the question directly. A note that says &#8220;I came across your profile and thought it would be valuable to connect&#8221; answers nothing. It signals that you are reaching out to many people with the same message, which is accurate but counterproductive to say.<\/p>\n<h3>The 300-Character Limit Is a Feature, Not a Constraint<\/h3>\n<p>LinkedIn caps connection notes at 300 characters. Most people treat this as a limitation. It is not. It forces clarity. A note that fills all 300 characters is almost always too long. The best-performing notes use 150-220 characters: enough to say something specific and genuine, short enough to read in under five seconds.<\/p>\n<p>A useful way to think about it: the note should be what you would say if you bumped into this person at an industry event and had ten seconds before they were pulled into a conversation. Brief, relevant, no ask.<\/p>\n<h3>Blank Note vs. Written Note: When to Use Each<\/h3>\n<p>This question gets debated in outreach circles more than almost any other. The data from teams running high-volume LinkedIn outreach at scale points to a nuanced answer.<\/p>\n<p>A specific, well-written note outperforms a blank request for most B2B cold outreach. The reason is signal: a note tells the prospect this is a deliberate, targeted outreach, not an algorithm recommendation they should ignore. Specificity is the differentiator.<\/p>\n<p>A blank note, however, outperforms a generic note. If your note says something that could have been sent to 10,000 people without changing a word, removing it entirely and relying on your profile strength performs better. Generic notes actively hurt acceptance rates by signaling mass outreach with poor effort.<\/p>\n<p>The practical rule: if you have something specific and genuine to say in under 200 characters, say it. If you do not, send without a note and let your profile and mutual connections do the work.<\/p>\n<h2>The 5 Connection Note Patterns That Kill Your Acceptance Rate<\/h2>\n<p>Before the templates, here is what not to write. These patterns appear in the majority of LinkedIn outreach being sent right now, which is exactly why they perform poorly.<\/p>\n<h3>1. The Immediate Pitch<\/h3>\n<p>&#8220;Hi [Name], I help companies like yours increase revenue through [solution]. Would love to connect and share how we&#8217;ve helped [Company Type] achieve [outcome].&#8221;<\/p>\n<p>This note does not ask for a connection. It asks for a sales conversation. The prospect has not agreed to be prospected yet. Accepting this request means accepting that they are now in your funnel, which most people are not willing to do with a stranger.<\/p>\n<h3>2. The Vague Compliment<\/h3>\n<p>&#8220;Hi [Name], I&#8217;ve been following your work and find it really impressive. Would love to connect with such an accomplished professional in the [industry] space.&#8221;<\/p>\n<p>Flattery without specificity is transparent. If you cannot name what you found impressive or what you actually read, the compliment reads as a template opener. It is worse than nothing because it implies you are running a charm-first sales script.<\/p>\n<h3>3. The Company Name Drop<\/h3>\n<p>&#8220;Hi [Name], I noticed you work at [Company] and wanted to connect. We work with companies in your space and think there could be some interesting synergies.&#8221;<\/p>\n<p>Mentioning someone&#8217;s employer is not personalization. Everyone who works at that company gets this same note. &#8220;Interesting synergies&#8221; is the phrase that has killed more acceptance rates than any other in the history of LinkedIn outreach.<\/p>\n<h3>4. The Credential Dump<\/h3>\n<p>&#8220;Hi [Name], I&#8217;m a [Title] at [Company] with 10+ years of experience in [field]. We&#8217;ve worked with [Client List] and recently [Achievement]. Would love to add you to my network.&#8221;<\/p>\n<p>This note is about you. The prospect does not yet have a reason to care about your credentials. There is no hook that connects your background to any benefit for them.<\/p>\n<h3>5. The Wall of Text<\/h3>\n<p>Any note that uses all 300 characters to explain a value proposition, tell a short story, ask multiple questions, or describe a process. At 300 characters, a wall of text looks like a wall of text. The prospect reads the first line, sees more text, and declines. The note format is not built for explanation. It is built for a sentence or two.<\/p>\n<h2>20 LinkedIn Connection Request Message Templates With High Accept Rates<\/h2>\n<p>The templates below are organized by scenario. Each one is under 220 characters. Each includes a brief note on what makes it work and where to use it.<\/p>\n<p>For every template, the variables in brackets are the 20% you fill in. The rest is the fixed frame.<\/p>\n<h3>Scenario 1: They Recently Posted Something Relevant<\/h3>\n<p>These are the highest-converting connection notes in B2B outreach, consistently. The prospect published something publicly. Referencing it is not surveillance; it is what LinkedIn posts are for.<\/p>\n<p><strong>Template 1<\/strong><\/p>\n<blockquote><p>&#8220;Saw your post on [specific topic] this week \u2014 your point about [specific detail] is something we&#8217;re dealing with too. Sending a connect.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> It proves you read the post. &#8220;We&#8217;re dealing with too&#8221; creates peer parity rather than a buyer\/seller dynamic. No ask.<\/p>\n<p><strong>Template 2<\/strong><\/p>\n<blockquote><p>&#8220;Your post on [topic] came up in a conversation I was having with [relevant peer role] last week. Good timing to connect.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> The social proof of someone else referencing their post signals reach and relevance. Plausible and flattering without being hollow.<\/p>\n<p><strong>Template 3<\/strong><\/p>\n<blockquote><p>&#8220;Disagreed with part of your post on [topic] but it made me think differently about [specific angle]. Thought that was worth a connect.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> Honest intellectual engagement is memorable. Most notes are 100% agreeable and forgettable. Mild, genuine disagreement makes this one stand out. Use only when you actually disagree with something specific.<\/p>\n<h3>Scenario 2: You Have a Mutual Connection<\/h3>\n<p>Second-degree connections accept requests at a 15-20 point higher rate than third-degree. Referencing the mutual connection explicitly pushes that rate higher.<\/p>\n<p><strong>Template 4<\/strong><\/p>\n<blockquote><p>&#8220;Noticed we&#8217;re both connected to [Mutual Name] \u2014 we worked together at [Company\/context]. Seems like enough reason to connect directly.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> The mutual connection is named, giving the prospect a way to verify. The framing is social (peer network) rather than sales.<\/p>\n<p><strong>Template 5<\/strong><\/p>\n<blockquote><p>&#8220;[Mutual Name] mentioned you&#8217;re doing interesting work on [topic\/initiative]. Wanted to connect and follow what you&#8217;re building.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> The referral is explicit. The focus is on their work, not yours. Only use this if [Mutual Name] is genuinely aware you are reaching out.<\/p>\n<h3>Scenario 3: You Were at the Same Event or Are in the Same Group<\/h3>\n<p>Shared context is the easiest reason to connect that needs no explanation.<\/p>\n<p><strong>Template 6<\/strong><\/p>\n<blockquote><p>&#8220;We were both at [Event Name] last [month\/week] \u2014 didn&#8217;t get a chance to connect in person. Sending one here.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> Shared experience creates instant common ground. Short, factual, zero pressure.<\/p>\n<p><strong>Template 7<\/strong><\/p>\n<blockquote><p>&#8220;Fellow member of [LinkedIn Group Name] \u2014 been following your contributions there. Good to connect directly.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> Group membership is a self-selected signal of shared interest. Referencing their contributions (if they have made any) is genuine without being over-the-top.<\/p>\n<p><strong>Template 8<\/strong><\/p>\n<blockquote><p>&#8220;Saw you registered for [Event\/Webinar] coming up on [topic]. Same here \u2014 good to connect ahead of it.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> Forward-looking shared context. Creates a natural follow-up conversation point after the event.<\/p>\n<h3>Scenario 4: They Just Changed Jobs or Got a Promotion<\/h3>\n<p>Job change notifications are one of the most reliable behavioral triggers in B2B outreach. Someone new in a role is evaluating their tools, vendors, and processes. Your timing is better than it will be in six months.<\/p>\n<p><strong>Template 9<\/strong><\/p>\n<blockquote><p>&#8220;Saw you recently joined [Company] as [Title] \u2014 congrats. The first few months in a new role are always interesting. Sending a connect.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> Acknowledges the milestone without fawning over it. &#8220;First few months are always interesting&#8221; signals you understand the situation without making it about your pitch.<\/p>\n<p><strong>Template 10<\/strong><\/p>\n<blockquote><p>&#8220;Congrats on the move to [New Company]. I&#8217;ve worked with a few people navigating [relevant challenge new role faces] \u2014 would be good to connect.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> The vague reference to a relevant challenge plants a seed without pitching. The prospect can ask more if curious, or just accept and move on.<\/p>\n<p><strong>Template 11<\/strong><\/p>\n<blockquote><p>&#8220;Noticed you stepped into the [Title] role at [Company]. We&#8217;ve helped a few teams in similar transitions \u2014 connecting in case it&#8217;s ever relevant.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> &#8220;In case it&#8217;s ever relevant&#8221; removes pressure entirely. It is an open-ended offer with zero commitment asked of them.<\/p>\n<h3>Scenario 5: Cold B2B Outreach (No Shared Context)<\/h3>\n<p>When there is no post, no mutual, no event, and no trigger: these notes rely entirely on specificity of targeting and a genuine reason for the reach-out.<\/p>\n<p><strong>Template 12<\/strong><\/p>\n<blockquote><p>&#8220;We work almost exclusively with [specific role] at [company type\/size]. Your profile came up and it seemed worth connecting directly.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> &#8220;Almost exclusively&#8221; signals specialization and targeting. The prospect understands they were found deliberately, not randomly. Honest and brief.<\/p>\n<p><strong>Template 13<\/strong><\/p>\n<blockquote><p>&#8220;Building a network of [role type] in [industry] \u2014 your background in [specific area] made you an obvious add. Connecting.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> Framing a sales outreach as network building is not deceptive if you genuinely want to build a peer network. The compliment is specific to their background, not generic.<\/p>\n<p><strong>Template 14<\/strong><\/p>\n<blockquote><p>&#8220;You popped up in my Sales Navigator feed for [role] at [company type]. Figured I&#8217;d connect rather than just view the profile.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> Transparency about the source of the outreach is disarming. Most people appreciate the honesty. It also explains the cold nature of the request without apologizing for it.<\/p>\n<p><strong>Template 15<\/strong><\/p>\n<blockquote><p>&#8220;Working on a project in the [industry\/niche] space and your name keeps coming up. Good to be connected.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> Social proof without a specific source creates curiosity. Use carefully \u2014 it should be at least partially true.<\/p>\n<h3>Scenario 6: Recruiting and Talent Outreach<\/h3>\n<p>Recruiting notes need to communicate opportunity without over-promising, and they need to distinguish themselves from the dozens of generic recruiter requests the prospect receives weekly.<\/p>\n<p><strong>Template 16<\/strong><\/p>\n<blockquote><p>&#8220;Building out the [Team\/Function] at [Company] \u2014 your background in [specific skill\/experience] is exactly the profile we&#8217;re looking for. Worth a connect to share more?&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> Specific about the role and the match. The question at the end is low-commitment and acknowledges they may not be interested.<\/p>\n<p><strong>Template 17<\/strong><\/p>\n<blockquote><p>&#8220;Not a mass recruiter message \u2014 we&#8217;re specifically looking at [very specific background] and you came up. Happy to share the role details if you&#8217;re open to it.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> Pre-empting the &#8220;this is a mass recruiter message&#8221; skepticism directly. The specificity claim needs to be true to be credible.<\/p>\n<h3>Scenario 7: Partnership and Business Development<\/h3>\n<p>Partnership outreach on LinkedIn has higher natural acceptance rates than sales outreach because the value exchange is implied to be mutual.<\/p>\n<p><strong>Template 18<\/strong><\/p>\n<blockquote><p>&#8220;We serve [audience] and so do you \u2014 just from a different angle. Seems like the kind of overlap worth having a connection for.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> The shared audience framing positions both parties as peers serving a common customer base. No ask, no pitch.<\/p>\n<p><strong>Template 19<\/strong><\/p>\n<blockquote><p>&#8220;Been following [Their Company] for a while \u2014 we&#8217;re building something adjacent in the [space] and think there&#8217;s a natural conversation to be had at some point. Connecting.&#8221;<\/p><\/blockquote>\n<p><em>Why it works:<\/em> &#8220;At some point&#8221; removes any immediate pressure. It signals long-term thinking rather than a pipeline-filling exercise.<\/p>\n<h3>Scenario 8: When No Note Is the Right Move<\/h3>\n<p>Not every connection request needs a note. These are the situations where going blank performs better.<\/p>\n<p><strong>Template 20 (No Note)<\/strong><\/p>\n<p><em>When to send without a note:<\/em><\/p>\n<ul>\n<li>Your profile is strong, specific, and immediately signals relevance to the prospect&#8217;s industry<\/li>\n<li>You share 10+ mutual connections and your name may already be familiar<\/li>\n<li>The prospect is very active on LinkedIn and accepts most requests based on profile alone<\/li>\n<li>You are targeting a persona that sends so many outreach messages themselves that they are desensitized to notes<\/li>\n<\/ul>\n<p>Blank requests work best when your profile does the talking. If your headline says &#8220;Helping SDR teams at B2B SaaS companies book more meetings,&#8221; a VP of Sales at a B2B SaaS company understands the relevance without a note. The note would add nothing.<\/p>\n<h2>How to Personalize Connection Notes at Scale<\/h2>\n<p>Running 40 connection requests per day means you cannot spend 10 minutes researching each one. You also cannot send the exact same note to everyone without it performing like a generic note. The solution is a variable-frame system: a template where 70-80% is fixed and 20-30% changes per lead based on a fast research signal.<\/p>\n<h3>The Three Signal Types Worth 60 Seconds Per Lead<\/h3>\n<p><strong>Signal 1: Recent post (check their LinkedIn activity tab).<\/strong> Did they post in the last 30 days? If yes, what was the topic? One sentence referencing the topic (not the post in detail) takes 20 seconds to write and converts the note from generic to specific.<\/p>\n<p><strong>Signal 2: Job change in the last 90 days.<\/strong> Visible on their profile directly. If they recently changed roles or got a promotion, Template 9-11 applies immediately. No further research needed.<\/p>\n<p><strong>Signal 3: Shared group, event, or connection.<\/strong> LinkedIn surfaces this automatically when you view a profile. &#8220;12 mutual connections&#8221; or &#8220;Both members of [Group]&#8221; takes zero research time and powers Templates 4-8 directly.<\/p>\n<p>If none of these three signals are present in 60 seconds, send without a note or use Template 12-14 with their role and company type filled in. Do not spend more time than this on a cold third-degree contact.<\/p>\n<h3>Building the Variable-Frame System in Practice<\/h3>\n<p>Here is how to structure a variable-frame note for cold B2B outreach at volume:<\/p>\n<p>Fixed frame: &#8220;We work almost exclusively with [ROLE] at [COMPANY TYPE]. [SIGNAL LINE IF AVAILABLE]. Figured it made sense to connect.&#8221;<\/p>\n<p>Variable slot 1: Role \u2014 pulled from their title, standardized to your ICP label (e.g., &#8220;VP of Sales,&#8221; &#8220;Head of Growth,&#8221; &#8220;Founder&#8221;).<\/p>\n<p>Variable slot 2: Company type \u2014 pulled from their company description or size filter (e.g., &#8220;Series A SaaS companies,&#8221; &#8220;B2B agencies,&#8221; &#8220;mid-market logistics firms&#8221;).<\/p>\n<p>Variable slot 3 (optional): Signal line \u2014 one sentence if a relevant post or trigger exists. If not, drop this slot and the note is still specific enough to perform.<\/p>\n<p>Tools like Clay can populate Variable slots 1 and 2 automatically from enrichment data, letting you review and confirm rather than write from scratch. For high-priority accounts, a human reviews and adds the signal line manually. For the broad list, slots 1 and 2 are enough.<\/p>\n<h3>The Acceptance Rate Impact of Variable Personalization<\/h3>\n<p>The performance gap between a fully templated note and a variable-frame note is meaningful. Fully identical notes sent to a large list typically produce 20-28% acceptance rates. Variable-frame notes with role and company type filled correctly produce 32-38%. Notes that also include a relevant signal line (post reference, trigger event, mutual connection) produce 42-50%.<\/p>\n<p>The 10-12 point lift from adding a signal line when one exists is worth the 30-60 seconds it takes. The 8-10 point lift from variable framing alone is worth building the system even when no signal is available.<\/p>\n<h2>What Happens After They Accept: Connecting the Note to the First Message<\/h2>\n<p>The connection note and the first message are one sequence. Most people treat them as unrelated. That disconnection costs acceptance-to-reply conversion.<\/p>\n<h3>The Note Sets Up the First Message<\/h3>\n<p>If your note referenced a post they wrote, your first message should continue from that reference. &#8220;Following up on the connect \u2014 I mentioned your post on [topic] was relevant to what we&#8217;re working on. Here&#8217;s the specific context:&#8221; opens a conversation the prospect is already oriented to. They accepted partly because of that post reference. Acknowledging it in the first message closes the loop.<\/p>\n<p>If your note was a cold outreach note with no specific hook, your first message needs to create the hook. The note did the job of getting accepted. The message now does the job of starting a conversation. These are different things requiring different approaches.<\/p>\n<h3>Timing: When to Send the First Message After Acceptance<\/h3>\n<p>Send within 24 hours of acceptance. Ideally within the same day. Acceptance is a warm signal that goes cold quickly. A prospect who accepted your request this morning is more likely to read and reply to a message tonight than to one you send four days from now when they have forgotten the connection entirely.<\/p>\n<p>The single biggest mistake in LinkedIn outreach sequencing is treating connection acceptance as a milestone to record and a message to schedule for next Tuesday. It is not. It is a window.<\/p>\n<h3>What the First Message Should Never Do<\/h3>\n<p>Do not repeat the connection note. If your note said you saw their post on scaling SDR teams, do not open the first message with &#8220;As I mentioned in my connection note, I saw your post on scaling SDR teams.&#8221; They know. Move forward.<\/p>\n<p>Do not thank them for accepting. &#8220;Thanks for connecting!&#8221; is filler that uses the first line \u2014 the only line that gets read before the message is cut off on mobile \u2014 on zero information content.<\/p>\n<p>Do not pitch in the first message the same way you would in a cold email. LinkedIn message norms are conversational. The first message should read like the start of a professional conversation, not the opening of a sales deck. Three lines. Pain framed from their perspective. A question or a low-commitment offer. Nothing more.<\/p>\n<p>The note got you in the door. The first message earns the reply. Keep that job separation clear and both will perform better.<\/p>\n<h2>Conclusion<\/h2>\n<p>A LinkedIn connection request message that gets accepted is not clever. It is specific. It answers one question in under 200 characters: why this person, why now. Everything else is noise that reduces the probability of acceptance.<\/p>\n<p>The 20 templates in this article are not scripts. They are structures. The variable slots are where the work happens: the post reference, the trigger event, the mutual connection, the role and company type. Fill those with something real and the note performs. Leave them generic and you are sending the same note as everyone else.<\/p>\n<p>Pick the two or three templates that match your most common outreach scenarios. Build a variable-frame version of each. Test them against 100 connection requests each before drawing conclusions. Let the acceptance rate data tell you which to keep, which to iterate, and which to cut.<\/p>\n<p>The note is the first step. Once they accept, send the first message the same day.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3><strong>What should I write in a LinkedIn connection request?<\/strong><\/h3>\n<p>Write something specific to the person you are contacting. The best connection notes reference a post they wrote, a mutual connection, a shared group or event, or a clearly relevant professional overlap. Keep it under 200 characters, make no ask, and give them a clear reason why you are reaching out to them specifically. Avoid generic openers like &#8220;I came across your profile&#8221; or any variation of a sales pitch.<\/p>\n<h3><strong>Should I send a LinkedIn connection request with or without a note?<\/strong><\/h3>\n<p>Send a note when you have something specific and genuine to say in under 200 characters. Skip the note when your only option is a generic message, because generic notes perform worse than no note at all. A strong profile with relevant positioning can carry a blank request effectively, especially when you share 10+ mutual connections with the prospect.<\/p>\n<h3><strong>What is the character limit for a LinkedIn connection note?<\/strong><\/h3>\n<p>LinkedIn connection notes are limited to 300 characters. The best-performing notes use 150-220 characters: enough to say something specific, short enough to read in under five seconds. Notes that fill all 300 characters are almost always too long and tend to read as a wall of text on mobile.<\/p>\n<h3><strong>What is a good LinkedIn connection acceptance rate?<\/strong><\/h3>\n<p>A well-targeted LinkedIn outreach campaign with specific, personalized notes typically produces a 35-50% connection acceptance rate. Generic notes on a targeted list produce 20-28%. Notes that include a relevant signal (post reference, mutual connection, trigger event) on a targeted list produce 42-50%. Below 25% is a reliable indicator that either the targeting is too broad or the notes are generic.<\/p>\n<h3><strong>Can I use templates for LinkedIn connection requests?<\/strong><\/h3>\n<p>Yes, but only if the template has variable slots that get filled with prospect-specific information. A fully identical note sent to hundreds of people performs like a generic note regardless of how well-written the base text is. The most effective approach is a variable-frame template where 70-80% is fixed and 20-30% changes based on the prospect&#8217;s role, company type, recent activity, or a relevant trigger event.<\/p>\n<h3><strong>Why is my LinkedIn connection request acceptance rate low?<\/strong><\/h3>\n<p>Low acceptance rates (below 25%) are usually caused by one of three things: targeting that is too broad (reaching people outside your ICP who have no reason to connect with you), notes that are generic or pitch-heavy (signaling mass outreach), or a LinkedIn profile that does not clearly communicate who you work with and why connecting has value. Fix targeting first, then the note, then the profile. Most teams go straight to rewriting notes when the problem is the list.<\/p>\n<h3><strong>What happens if I send a LinkedIn connection request without a message?<\/strong><\/h3>\n<p>Blank connection requests rely entirely on your profile strength, your mutual connections, and whether the prospect recognizes your company or name. For highly active LinkedIn users with strong profiles, blank requests often perform as well as generic notes. For cold outreach into unfamiliar personas where your profile is not immediately self-explanatory, a specific note will outperform a blank request.<\/p>\n<h3><strong>How many LinkedIn connection requests can I send per day?<\/strong><\/h3>\n<p>For accounts that have been properly warmed up over 3-4 weeks, the safe range is 30-40 connection requests per day. New accounts should start at 10-15 per day and scale up gradually. Sending more than 50 requests per day on a single account increases the risk of LinkedIn flagging the account for automated behavior, particularly if the acceptance rate is low.<\/p>\n<h3><strong>How do I personalize LinkedIn connection requests at scale?<\/strong><\/h3>\n<p>Use a variable-frame template system where the role, company type, and any available signal (recent post, job change, mutual connection) are filled in per lead. Tools like Clay can populate role and company type automatically from enrichment data. For the signal layer, spend 30-60 seconds per high-priority lead checking their recent activity tab. For the broader list, variable role and company type alone produce a meaningful lift over fully static templates.<\/p>\n<h3><strong>What should I do immediately after someone accepts my LinkedIn connection request?<\/strong><\/h3>\n<p>Send a first message within 24 hours of acceptance, ideally the same day. The acceptance is a warm signal that fades quickly. The first message should continue from whatever context your note established, frame a specific problem relevant to their role, and make a low-friction ask. Do not thank them for accepting, do not repeat the connection note, and do not open with a pitch. Three lines maximum for the first message.<\/p>\n<h3><strong>What LinkedIn connection request note gets the highest acceptance rate?<\/strong><\/h3>\n<p>Notes that reference something the prospect published or did publicly, such as a post they wrote or an event they attended, consistently produce the highest acceptance rates, typically 42-55% on well-targeted lists. These notes work because they demonstrate that the outreach is targeted and deliberate, not automated. The second-highest performing category is mutual connection references, which produce 40-50% acceptance rates when the mutual connection is named specifically.<\/p>\n<h3><strong>Is it against LinkedIn&#8217;s terms of service to use connection request templates?<\/strong><\/h3>\n<p>LinkedIn&#8217;s terms of service prohibit automated connection requests sent via bots or third-party tools that violate their policies, but writing templated messages manually or using tools that operate within LinkedIn&#8217;s rate limits is not prohibited. The relevant constraint is behavioral: LinkedIn monitors for patterns that look automated (high volume, identical messages, low acceptance rates) and may restrict accounts that trigger detection. Keeping acceptance rates above 30% and staying within daily limits is the practical compliance standard.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Your LinkedIn connection request message has one job: get accepted. Not start a conversation, not explain your product, not establish [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":1415,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[54],"tags":[],"class_list":["post-1073","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linkedin-hacks"],"acf":[],"_links":{"self":[{"href":"https:\/\/dealsflow.co\/blog\/wp-json\/wp\/v2\/posts\/1073","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dealsflow.co\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dealsflow.co\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dealsflow.co\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/dealsflow.co\/blog\/wp-json\/wp\/v2\/comments?post=1073"}],"version-history":[{"count":4,"href":"https:\/\/dealsflow.co\/blog\/wp-json\/wp\/v2\/posts\/1073\/revisions"}],"predecessor-version":[{"id":1418,"href":"https:\/\/dealsflow.co\/blog\/wp-json\/wp\/v2\/posts\/1073\/revisions\/1418"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dealsflow.co\/blog\/wp-json\/wp\/v2\/media\/1415"}],"wp:attachment":[{"href":"https:\/\/dealsflow.co\/blog\/wp-json\/wp\/v2\/media?parent=1073"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dealsflow.co\/blog\/wp-json\/wp\/v2\/categories?post=1073"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dealsflow.co\/blog\/wp-json\/wp\/v2\/tags?post=1073"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}