Connection request templates for SDRs that get replies

SDRs do not lose replies because they lack hustle, they lose them because their connection notes read like cold email subject lines stuffed into 280 characters.

These connection request templates for SDRs are built for short, specific outreach where the only goal is: get accepted and start a real thread. Everything else can wait for the follow-up. We use variations of these in our own outbound and plug them into Ampliflow’s workflows so timing, delays, and safety are handled by the system.

The one principle that makes these land: one idea per message. One trigger, one question, one tiny ask. No bullet points, no mini-pitch.

How to use these connection request templates for SDRs

These templates are for SDRs who are:

• Prospecting on LinkedIn as a main channel, not an afterthought
• Working named accounts or clear ICP lists from LinkedIn search or Sales Navigator
• Planning to send a short follow-up after the connect, not cram everything into the note

We typically drop these into sequences using Ampliflow: a visual drag-and-drop workflow builder with If/Else logic and delays, plus reply detection, so cloud execution runs via the Unipile API (no browser extension; laptop can be closed). Tools like Dripify Alternative: Cloud LinkedIn Automation From $19/mo or Expandi Alternative: Cloud Outreach From $19/mo | Ampliflow compete here on feature sets too, and some have been around longer. Where we lean hard is architecture and account safety: human-like daily limits with timing jitter, auto-pause on reply, and anomaly detection baked in.

Before you copy-paste:

• Keep every connection note under 260 characters to give yourself buffer
• Personalize at least one variable beyond {first_name}
• Avoid pitching discounts, trials, or booking links in the note itself

Now into the actual templates.

Template 1: SDR to VP/Head of Sales - “peer process” angle

1. VP of Sales: short process curiosity hook

"Hey {first_name}, saw you run sales at {company}. I\u2019m talking with a few {industry} teams about how they handle outbound on LinkedIn. Curious if your SDRs do structured sequences here or mostly ad hoc?"

When to use it:
Use this for VP/Head of Sales or CRO personas when your product touches outbound, tooling, or SDR productivity.

Why it works:
This opens as peer-to-peer research, not a pitch. It anchors the topic (LinkedIn outbound) and asks a simple either-or question, which makes replying much easier than a vague "thoughts?".

Variables to customize:

• {first_name}
• {company}
• {industry} (e.g. B2B SaaS, manufacturing, logistics)

Template 2: SDR to Founder/CEO - “seen your post” angle

2. Founder: reference a real signal, no flattery

"Hey {first_name}, your post on {topic_or_post_hook} hit home. I work with founders juggling founder-led sales plus an SDR or two, and I\u2019m mapping how they split prospecting. Open to a quick compare-notes connection?"

When to use it:
Best for founders or CEOs who are active on LinkedIn and post about sales, go-to-market, or hiring SDRs. Works especially well when you actually read and reference a specific post.

Why it works:
It shows you are not scraping a list blindly. The "compare-notes" phrasing feels lighter than "jump on a call" and fits naturally inside a connection request.

Variables to customize:

• {first_name}
• {topic_or_post_hook} like "ramping reps in Q3" or "your SDR comp structure thread"

If you focus mostly on founders, you might also skim the patterns in our LinkedIn Connection Request Template For Founders to mix in more angles.

Template 3: SDR to RevOps / Sales Ops - “tooling sanity check”

3. RevOps: stack sanity check without naming your product

"Hi {first_name}, I\u2019m mapping how RevOps teams at {segment} companies wire up LinkedIn, CRM, and sequencing tools. You look like the right person at {company}. Any chance you\u2019re open to a quick compare-stacks chat here?"

When to use it:
Use with RevOps, Sales Ops, or Sales Enablement leads who likely own the tooling stack and process design.

Why it works:
Ops people respond to system talk. This message frames the conversation as a peer stack review, not "let me pitch you my product", which lowers defenses and starts from curiosity.

Variables to customize:

• {first_name}
• {segment} such as "mid-market SaaS" or "agency"
• {company}

Template 4: SDR to ICP after content engagement - “liked your comment”

4. After they like or comment: light-touch bridge

"Hey {first_name}, saw your comment on {thread_owner}\u2019s post about {topic}. I help {persona} teams with that exact bit of the puzzle and would love to compare what\u2019s working for you vs what I\u2019m seeing elsewhere."

When to use it:
Right after the prospect comments on a relevant thread or interacts with content about your problem space. This can be triggered automatically if your workflow tool surfaces engagements.

Why it works:
Timing plus context. You are piggybacking on something they literally just engaged with, so the topic is fresh and the connection feels natural instead of random.

Variables to customize:

• {first_name}
• {thread_owner} such as "Jason" or "your VP"
• {topic} like "outbound reply rates" or "SDR ramp"
• {persona} for clarity, like "sales" or "RevOps"

Template 5: SDR to cold prospect - “no context, still human”

5. Pure cold: honest, short, and specific

"Hi {first_name}, cold note from an SDR here. I work with {persona_plural} at {segment} companies on {1-short-problem}. Wanted to connect here first and see if this is even on your radar before I make assumptions."

When to use it:
Use this when there is no content hook, no mutual connections, and no warm intro. This is your baseline for a cold but still human note.

Why it works:
You are transparent about being an SDR and avoid pretending there is a fake "reason" for the outreach. The "see if this is even on your radar" line gives them an easy opt out without feeling ambushed.

Variables to customize:

• {first_name}
• {persona_plural} such as "sales leaders" or "RevOps teams"
• {segment} like "Series B SaaS" or "outsourced SDR"
• {1-short-problem} like "keeping LinkedIn accounts safe at higher send volumes"

Template 6: SDR to existing tool user - “replacement or complement”

6. Prospect using a competitor: acknowledge what they already have

"Hey {first_name}, noticed {company} is already using {tool} for LinkedIn. I work with teams that either outgrow it or run a second path for safer outbound. Mind if I connect and share 1-2 patterns I\u2019m seeing?"

When to use it:
Ideal when you know or strongly suspect which tool they use, from job posts, signatures, or tech tags on websites.

Why it works:
You do not trash the existing tool or pretend they are doing nothing. You acknowledge their current setup and position yourself as bringing patterns from the field, not just a competitive pitch.

Variables to customize:

• {first_name}
• {company}
• {tool} such as "Dripify", "Dux-Soup", or "Expandi"

If a prospect already runs something like Dripify at 79 dollars a month or Expandi at 99 dollars a month and only cares about price, you might not win that deal immediately. On the other hand, if they keep getting restricted or juggling browser extensions, a cloud tool with real-time account safety scoring, human-like rate limits, and no need to keep a laptop open is usually an easy wedge.

Template 7: SDR to ABM target - “account-specific wedge”

7. Named account: show you did homework

"Hi {first_name}, I was looking at {company}\u2019s push into {new_motion_or_market} and how that affects outbound. I talk with a few {similar_companies} working through the same shift, and thought it\u2019d be smart to connect here."

When to use it:
Use this for ABM lists, strategic accounts, or tier 1 companies where you are willing to spend real research time before reaching out.

Why it works:
It references a visible strategic move instead of generic personalization. That tends to resonate more with senior stakeholders and makes your outreach feel like part of a thoughtful account plan, not a mass blast.

Variables to customize:

• {first_name}
• {company}
• {new_motion_or_market} like "mid-market expansion", "US launch", or "partner motion"
• {similar_companies} such as "PLG SaaS teams" or "consultancies"

Quick scenario-to-template map for SDRs

Use this table to pick the right template for your situation.

We typically drop different templates into separate branches in Ampliflow’s drag-and-drop builder and run A/B tests on acceptance and reply rates. The visual If/Else logic and funnel analytics make it easy to redirect prospects who accept but do not reply into a softer follow-up path.

How SDRs should customize and send these safely

Templates are a starting line, not the whole race. In our own testing, the biggest gains did not come from inventing a new magic sentence but from:

• Trimming bloaty phrases, keeping notes concise
• Being ruthless about one clear idea per message
• Matching the follow-up message to the angle used in the connection request

For daily volume, here is what we personally do on production accounts:

• Mature, warmed-up account: around 50-70 total outreach actions per day, of which 30-50 are connection requests and the rest are DMs and follow-ups
• New or previously restricted account: closer to 20-30 total actions while we watch how LinkedIn reacts

Hard truth: raw send count is not the bottleneck for most SDR teams. Random timing, identical messages, and ignoring account health are what get you throttled.

Tools like Ampliflow, Dux-Soup, and Dripify all try to help on the workflow side, but their architectures differ:

• Browser-extension tools such as Dux-Soup or Linked Helper are cheaper on paper, sometimes under 20 dollars a month, but require a running browser and can be fragile if you log in from multiple devices.
• Cloud tools such as Expandi, HeyReach, or Salesflow handle execution server-side, often at 79 to well over 150 dollars a month, and bundle in more safety logic.

Ampliflow sits in the second camp: pure cloud execution via the Unipile API (no browser extension; laptop can be closed), human-like daily rate limits with randomised timing jitter, auto-pause on reply, unified smart inbox, account safety scoring, and anomaly detection. Founding members lock 19 dollars a month for life (first 100 only) ahead of public launch pricing at 39 dollars Starter and 79 dollars Pro. Cancel anytime; 30-day refund once paid plans start. Details are on the Pricing page, and you can Join the waitlist if you want early access. Keep in mind the beta is paid; it is not a trial.

We are in pre-launch while running our own outbound on the same infrastructure, so we bias conservative on safety. If we would not run a pattern on our own accounts, we do not build it into the product.

Do and don’t list for SDR LinkedIn connection requests

Here is the grounded, slightly unglamorous version of what actually works.

Do:

• Keep notes under 260 characters, bluntly short, and focused on one idea
• Reference a real trigger: a post, hiring plan, tech stack, or company move
• Be explicit if you are an SDR, it reduces the “who are you pretending to be” friction
• Ask a small, clear question that can be answered in a sentence
• Personalize beyond the name: industry, motion, or specific problem
• Space your sends across the workday and respect human patterns

Don’t:

• Dump your full pitch, feature list, or calendar link into the connection note
• Fake familiarity with “saw you checked out our site” if you did not, prospects feel that
• Over-automate to the point every message is identical for thousands of people
• Brag about reply rates or mention discounts in the first touch
• Argue in DMs if someone says “not a priority”, that is how you get screenshotted
• Ignore warnings from your tooling about anomaly detection or safety scores

If you keep the messages human and the sending pattern sane, you usually avoid the harshest restrictions. We have seen spikes of identical connection requests sent back to back for hours be the common cause of trouble, far more than total volume alone.

These connection request templates for SDRs are what we actually use and tweak week to week. Start with them, change 10-20 words for your persona and language, and let your workflow tool handle the boring parts: delays, If/Else branches on reply versus no reply, and A/B tests.