# LinkedIn InMail vs. Connection Requests: Which One Should You Use URL: https://warmerly.com/blog/linkedin-inmail-vs-connection-request Published: 2026-07-03 Reading time: 8 minutes Tags: LinkedIn outreach, InMail, Sales Navigator > InMail vs connection request on LinkedIn compared on cost, reach, and reply rates, with a decision framework by account type, degree of connection, and role. You've got a prospect in front of you and two ways to reach them: send a connection request with a note, or spend an InMail credit. Most people pick based on habit, not math — SDRs default to connection requests because they're free, recruiters default to InMail because that's what the seat came with. Neither instinct is wrong, but neither is a strategy either. This piece breaks down what actually differs between the two — cost per send, who can even see your message, and how reply rates move depending on degree of connection — then gives you a decision framework you can apply scenario by scenario instead of defaulting to whatever your LinkedIn tier happens to include. ## The core mechanical difference: InMail bypasses the connection requirement, connection requests don't A connection request note caps out at 300 characters and only reaches people you're not yet connected to — it sits in their invitation queue until they accept or ignore it, and you can't send a real message until they accept. InMail, by contrast, lands directly in the recipient's inbox even if you're a 3rd-degree connection with no mutual connections, and it supports up to 2,000 characters including a subject line. That's the whole trade: InMail buys you inbox access without needing a relationship first, at the cost of looking exactly like what it is — a paid, unsolicited message from a stranger. A connection request buys you nothing until accepted, but once accepted you're inside the recipient's network permanently, with unlimited free messaging and visibility into their future posts. One is a transaction, the other is an investment with a vesting period. ## Cost per send: free vs. roughly $8-10 per credit, depending on plan Connection requests are free on every LinkedIn tier, capped only by the platform's weekly invite limits — currently around 100-200 per week for standard accounts before you risk restriction, detailed on the limits guide at /linkedin-outreach/limits. InMail is metered: Sales Navigator Core includes 50 InMail credits a month, Advanced includes 50 as well but with better targeting filters, and Recruiter Lite/Corporate seats typically get 30-150 depending on the contract. Unused credits roll over for a maximum of 90 days, then they're gone. Do the arithmetic on a $99.99/month Sales Navigator Core seat with 50 InMail credits and you're at roughly $2 per credit if you use every one — but most reps use 15-20, which pushes real cost per send closer to $5-6.50. Buy à la carte credits instead (available in some regions) and you're paying closer to $10 each. Either way, InMail has a hard unit cost that connection requests never will, which matters when you're outreaching at volume rather than sending a handful of high-intent messages a week. ## Reply rates move with degree of connection, not with which button you clicked Industry benchmarking on cold outreach commonly puts average InMail response rates around 10-25%, but that range collapses hard once you segment by relevance and personalization — generic InMail to a cold VP sits closer to 3-5%, while a highly targeted InMail referencing a specific trigger event can clear 30%. Connection request acceptance rates run higher on average, commonly cited around 30-50% for well-targeted, personalized requests, but acceptance isn't reply — it's just the front door opening. What happens after acceptance is where connection requests actually win: message reply rates to 1st-degree connections you personally invited routinely beat cold InMail by 2-3x. The reason isn't the format, it's the signal each format sends. A connection request implicitly asks the recipient to vet you — they check your profile, your mutual connections, your headline — before they even see your pitch. InMail skips that vetting step entirely and puts your pitch first, which is exactly why it performs worse per-send on cold, unqualified lists and better on lists where you've already done the qualification work yourself. Full breakdowns of response benchmarks by channel and message type are on /linkedin-outreach/response-rates. > **InMail buys access, not warmth** — InMail doesn't buy you a warmer reply — it buys you the ability to skip asking permission. If your message wouldn't earn a connection accept on its own merits, spending a credit to force it into someone's inbox anyway just gets you a faster no. ## When InMail is the right call InMail earns its cost in three specific situations: the prospect is 2nd or 3rd-degree with no mutual connections and time-sensitive context (a funding round, a job change, a product launch) makes waiting for a connection accept a real cost; you're recruiting for a role where candidates expect direct, professional outreach and treat InMail as a legitimate first contact rather than spam; or you've already built enough account-level context (from Sales Navigator lead lists, recent activity, or a warm signal like a shared group) that the message can be genuinely specific rather than templated. - Recruiter filling a niche technical or executive role where candidates are used to being InMailed directly - SDR working a named-account list with a live trigger event (funding, leadership change, tech stack signal) that justifies urgency - Enterprise seller reaching a 3rd-degree buying-committee member who'll never show up in a mutual-connection path - Anyone re-engaging a prospect whose connection request they already sent and got ignored, where InMail is the deliberate escalation In every one of these, the InMail is doing a job a connection request structurally can't — reaching someone with no network path to you, on a timeline that can't wait for an accept. If your list doesn't have that constraint, you're paying $5-10 a message to solve a problem you don't have. ## When a connection request wins, even if you have InMail credits sitting unused For most SDR and founder-led outreach, the connection request is the better default, not the fallback. It's free, and because it's a native platform action rather than a paid override, it's less likely to trip LinkedIn's spam and rate-limit detection than a wave of unsolicited InMail. It also compounds: every accepted connection becomes a channel you can message for free indefinitely, not just for this one campaign. Templates that get accepted without looking like a pitch are covered in detail on the templates guide at /linkedin-outreach/templates and the connection-requests guide at /linkedin-outreach/connection-requests. The math changes when you're working high volume against a broad ICP rather than a short, hand-picked list. A free-account or Premium user with no InMail credits and 150 weekly connection requests available has more effective reach per week than a Sales Navigator seat burning through 50 InMail credits a month, especially against 2nd-degree prospects who share mutual connections — acceptance rates jump noticeably when even one mutual connection shows on the profile. If your list skews 2nd-degree, save the credits and send the request. ### Sales Navigator user vs. free account On a free or Premium account with no InMail credits, the decision is made for you — connection requests are your primary lever, and you supplement with open profile messages or group messaging where available. Sales Navigator users have a real choice, and the right call is to reserve InMail for 2nd/3rd-degree targets with no mutual path and use connection requests everywhere a mutual connection or shared group already exists, since that overlap is what drives acceptance regardless of which tier sent it. ### Recruiter vs. SDR Recruiters see structurally different InMail performance than sales reps because candidates expect to be InMailed — it's a known, accepted channel in that context, which is why Recruiter seats come with more credits by default. SDRs pitching a product face the opposite expectation: an unsolicited sales pitch via paid InMail reads as more transactional than the same pitch arriving after a mutual, accepted connection, so SDRs should lean connection-request-first and reserve InMail for named-account, high-value targets only. ## Running both channels without burning your account Mixing InMail and connection requests on the same list isn't just fine, it's usually correct — but sequencing matters more than most people realize. Send the connection request first with a short, non-pitchy note; if it sits unanswered for 5-7 days, that's a legitimate trigger to escalate to InMail for a high-value target rather than sending both simultaneously, which reads as pushy and can trigger LinkedIn's spam detection on the account. Sequencing rules and safe daily/weekly volumes across both channels are laid out on /linkedin-outreach/automation and /linkedin-outreach/strategy. This is also where LinkedIn account health becomes a real constraint independent of which message type you're sending — an account that isn't warmed up, or one that's brand new and immediately hitting daily connection and InMail caps, gets rate-limited or flagged regardless of how good your copy is, a failure mode covered in /blog/warming-up-a-linkedin-account-before-outreach and /blog/linkedin-account-restricted-recovery. ## Where Warmerly fits into this Once you've settled on the mix — connection-request-first with InMail reserved for named accounts, say — the operational problem is just keeping both channels running on schedule without tripping LinkedIn's limits or letting your email side go stale in parallel. That's the part Warmerly handles day to day: it warms up the LinkedIn account itself, sequences connection requests and follow-ups alongside email touches in the same multichannel flow, and tracks reply rates per channel so you can see whether InMail is actually earning its cost on your list instead of guessing. ## The takeaway Treat InMail and connection requests as tools for different reach problems, not competing versions of the same message. Connection requests are free, compound into a lasting network, and outperform on lists where a mutual connection or shared context already exists. InMail costs real money per send but is the only channel that reaches 2nd/3rd-degree prospects instantly without waiting on an accept — spend it there, on targets and timelines that actually need it, and skip it everywhere else. --- Source: https://warmerly.com/blog/linkedin-inmail-vs-connection-request Full content index: https://warmerly.com/llms-full.txt Site index: https://warmerly.com/llms.txt