Connection Request Framework
When to add a note, how to write one under 300 characters, safe weekly pacing, and which tools automate without triggering a restriction.
TL;DR
Note vs blank: acceptance rate in 30 seconds
A specific note outperforms a blank invite. A generic templated note underperforms a blank invite. If you cannot make the note genuinely specific to the recipient, send blank.
When to add a note versus send blank · The 3-part note structure that increases acceptance rate · Connection request examples for 4 ICP scenarios · LinkedIn's 100/week invite limit and safe pacing · Which tools automate safely.
The Core Framework
Note vs no-note: the decision table
| Situation | Note or blank? | Why | Expected acceptance |
|---|---|---|---|
| Cold outreach to a specific ICP profile | Note: short and specific | A one-sentence specific reason outperforms a blank invite to a stranger | Higher than blank when genuinely relevant |
| Post-engagement: they liked or commented on your content | Note: reference the interaction | A known interaction creates immediate context and reduces friction | High: warm signal lowers the barrier |
| Trigger-based: job change, funding round, event | Note: reference the trigger | Naming a fresh trigger shows you did homework | Highest: relevance is self-evident |
| High-volume automated outreach | Blank or ultra-short note | Generic templated notes perform worse than blank: do not automate a bad note at scale | Blank: moderate · Generic note: below blank |
| Recruiter outreach to passive candidates | Note: mention the role and why them | Passive candidates want to know what is in it for them before accepting from an unknown | Higher than blank when role is relevant |
Writing the Note
3-part note structure: under 300 characters, higher acceptance
LinkedIn caps connection notes at 300 characters. That constraint forces the note to do one job: give the recipient a specific reason to accept. Three parts handle that without wasting characters on filler.
- Name the signal or reason (1 sentence)
Start with a specific reason about them: a trigger event, shared context, mutual connection, or a relevant observation about their role. "I saw your post on outbound attribution" works. "I help companies like yours" does not.
- State why connecting makes sense (1 sentence)
Frame the relationship, not the pitch: "I work with revenue teams on similar problems" or "We have mutual connections in the [industry] space." If you cannot complete this sentence without pitching a product, your note is a sales note, not a connection request.
- No CTA in the connection request
The only goal of the request is the accepted connection. The DM sequence handles the next step after acceptance. A meeting request or link in the note signals a sales agenda before any rapport exists and consistently lowers acceptance.
"Hi [First Name], I'd love to connect and share ideas" is recognizable as automation to most senior buyers and performs below a blank invite. If your note is not specific to the recipient or their situation, send blank.
Connection Request Examples
5 connection request examples by ICP scenario
Each example below follows the 3-part structure, stays under 300 characters, and is specific enough to avoid reading as a template while remaining replicable across a filtered segment.
| Scenario | Example note (under 300 chars) | What makes it work |
|---|---|---|
| Cold outreach to Head of Sales at a Series B company | "Saw you're scaling the sales team at [Company] after the Series B. I work with outbound teams at similar stages. Would love to connect." | References company stage, not the product. States relevant context. No ask. |
| Post-content engagement (they commented on a relevant post) | "Your comment on [Author]'s post about pipeline attribution resonated. We work on similar problems. Happy to connect." | References a specific shared interaction. No pitch. Keeps the relationship framing. |
| Job change trigger (they just started a new role) | "Noticed you just joined [Company] as VP Sales. Congrats. I work with revenue leaders navigating new team buildouts. Would be good to connect." | Names the trigger event specifically. Frames the connection around a relevant challenge for this role transition. |
| Recruiter reaching out to a passive candidate | "Your background in enterprise sales engineering aligns well with a role I'm working on. Happy to share details if you're open to a conversation." | States a specific skill match. Keeps the ask optional. Does not name the company or salary upfront. |
| Founder doing manual outreach to a target account | "Love what [Company] is doing in the data quality space. I'm building something adjacent. Would value your perspective if you're open to connecting." | References something specific about their company. Positions the connection as a conversation, not a pitch. |
Before sending at volume, read the note as if you received it cold. If the first reaction is "this could have been sent to anyone," rewrite it or send blank.
Volume and Pacing
100 invites/week: how to pace inside LinkedIn's limit safely
LinkedIn's weekly invite limit is approximately 100 connection requests per account. The threshold varies by account age, SSI score, and activity history, but 100/week is the widely observed safe ceiling for most accounts.
Distribute sends across the week rather than hitting the quota in one or two days. Expandi, Dripify, and Waalaxy all enforce daily action caps and randomize sending intervals to mimic human activity patterns.
New or low-SSI accounts should ramp from 5-10 requests/week, increasing gradually over 4-6 weeks before reaching full volume. The LinkedIn Account Warm-Up SOP covers the full ramp process.
Recommended Tools
Expandi, Dripify, Waalaxy: 3 tools for safe connection automation
Cloud-based tools are the correct choice for any volume above 30 requests per week. Browser extensions run from the local machine and are more detectable than cloud tools with dedicated residential IPs.
Common Questions
6 questions on limits, acceptance rates, and automation
Include a note when you can make it specific: a trigger event, a piece of their content, a mutual connection, or a relevant observation about their role. Send blank when the only alternative is a generic template. A specific note outperforms blank. A generic note underperforms blank.
The widely observed safe ceiling is approximately 100 requests per week per account. New accounts should start at 5-10 per week and ramp gradually over 4-6 weeks before approaching the full weekly quota.
A cold campaign with a specific note typically achieves 25-40% acceptance. Trigger-based or warm outreach reaches 40-60%. Rates below 15% signal a targeting problem or a note that reads as templated.
Yes, with cloud-based tools like Expandi or Dripify that enforce daily action caps and randomize sending intervals. Stay inside the 100/week limit, warm up new accounts, and enable reply detection so the sequence pauses when a prospect responds.
Wait 24-48 hours, then open with a relevant resource or a specific question. No pitch in the first message. The DM Sequence Framework covers the full post-acceptance outreach structure.
Waalaxy is browser-based, which carries higher detection risk than cloud tools with dedicated IPs. It enforces monthly invite limits by plan (300-800/mo) and suits teams starting out. For higher volume or lower risk tolerance, use Expandi or Dripify instead.
Framework clear. Now build the sequence that follows the acceptance.
The DM Sequence Framework covers what to send in the 24-72 hours after a connection is accepted, including the first message structure, follow-up spacing, and when to move to email.