LinkedIn InMail vs Connection Request: Which to Use
Connection requests should do the heavy lifting in your LinkedIn outreach. They cost nothing, and an accepted request opens a channel you can message as often as your cadence needs. InMail is the specialist tool: worth a credit for a short list of prospects who matter a lot and won't accept your invite. That's the whole answer to LinkedIn InMail vs connection request. The rest of this post covers the mechanics behind it and how to set the split for your plan.
What you're actually choosing between
A connection request is an invitation, with or without a short note, that lands in the recipient's "My Network" tab. If they accept, you become first-degree connections and can message them like anyone else in your network. If they ignore it, it sits pending. It can't be resent until you withdraw it, and LinkedIn makes you wait before inviting that person again.
An InMail is a direct message to someone you're not connected to. It needs a paid LinkedIn subscription such as Premium or Sales Navigator, and each send uses a credit from a monthly allowance. Two exceptions change the maths. Messages to members with open profiles don't use a credit. And when a recipient replies within LinkedIn's response window, the credit comes back.
These aren't interchangeable. One builds a relationship you keep. The other buys a single shot at someone's attention.
LinkedIn InMail vs connection request: cost, deliverability, scale
| Connection request | InMail | |
|---|---|---|
| Direct cost | Free on any account | One credit per send (returned on reply) |
| What you need | Any LinkedIn account | Premium or Sales Navigator for credits |
| Where it lands | Invitations tab | Recipient's message inbox |
| Follow-ups | Unlimited once accepted | Each new thread costs another credit |
| Volume ceiling | Daily and weekly invite limits | Your monthly credit allowance |
| Main risk | Pending invites piling up, "I don't know this person" flags | Burning credits on people who never reply |
| Best for | Ongoing outbound at volume | A short list of high-value or hard-to-reach prospects |
The row most people underweight is "Follow-ups." Building a connection means you pay nothing for the second, third and fourth touch. With InMail you get one thread per credit, so a multi-step sequence costs more as it grows.
Cost: credits versus your daily budget
InMail's price is mostly hidden inside a subscription. If you already pay for Sales Navigator, the credits feel free until you run out partway through the month. Then you're stuck until the allowance refills. The refund on reply is a real feature, but it pushes you toward careful targeting. A lazy InMail blast spends credits you never get back. A tight list of people who have a reason to answer costs close to nothing.
Connection requests cost no money. They cost something different: capacity. You get a fixed number of invites per day and per week, and every one you spend on a poor-fit prospect is gone. Spending that capacity well comes down to list quality, which is why we'd put more effort into filtering than into copy. Our Sales Navigator search tricks cover how to cut a list down before it reaches your invite queue.
So the cost question isn't "free versus paid." It's which resource you're short on: credits or invite slots.
Deliverability: where each message lands
An InMail arrives in the inbox, so it's more visible than an invitation. That's its real advantage. The catch is that people know what InMail is. Recipients can switch off InMail they don't want, and a pitch from a stranger reads as a pitch no matter how it's written. Spam reports on InMail count against you.
A connection request is quieter. It sits in the invitations tab, and many people accept without reading the note. Once accepted, your follow-up lands in the main inbox as a message from a connection. A message from a connection reads very differently from a message from a stranger who paid to get in.
The deliverability risk with connection requests is account-level, not message-level. A pile of pending invites that nobody accepts, plus recipients marking you as someone they don't know, are the signals that lead to invitation restrictions. That's why profile quality matters before you send anything. A stranger checks your headline before accepting, and optimizing your profile for outbound affects acceptance more than any note template does.
Scalability: which one grows with you
Connection requests grow with the number of LinkedIn accounts you run, not with spend. One account sending 25 invites a day, five days a week, is a steady and predictable pipeline input. Add a second teammate's account and you double it at no extra LinkedIn cost.
InMail grows with subscription spend. More volume means more seats or a higher tier, and every seat comes with its own monthly credit ceiling. For a recruiter or an enterprise seller working a few hundred named accounts, that's fine. For a founder trying to reach a whole category of buyers, it gets expensive and tops out fast.
There's also a compounding effect. Every accepted connection stays in your network. They see your posts, which is why pairing content with outbound works: the people you connected with last quarter are this quarter's warm audience. An InMail thread that went nowhere leaves nothing behind.
The mix we'd actually run
We'll take a side: default to connection requests and treat InMail as an exception you have to justify. Here's how that plays out by situation.
You're on a free or basic LinkedIn account. Connection requests are your only cold channel apart from open profiles. Don't buy Premium just for InMail. Spend that money on list quality and a better cadence first.
You have Sales Navigator. Run connection requests as the main sequence. Use InMail in two places. First, for open profiles, since those sends are free. Second, as a fallback step for high-value prospects who haven't accepted after a reasonable wait. A branch like "if not accepted after X days, and the account is on the target list, send InMail" captures most of the value without spending credits on everyone.
You're hiring. Recruiting is where InMail holds up best, because candidates expect it and a role offer is a reason to reply. Even there, connecting first and messaging after builds a talent network you can come back to. The recruiter playbook walks through that structure.
You're selling high-ACV into a small account list. InMail earns a bigger share here. When there are only 40 people in the world you need to reach, a returned-on-reply credit is cheap.
For almost everyone else, the right ratio is mostly connection requests with a small InMail tail. The cadence design guide covers how to space the steps after acceptance.
Where automation fits, and where it doesn't
Automation helps most on the connection-request side, because that's where the work is repetitive: sending invites, waiting for acceptance, then running follow-ups on a schedule. Ampliflow handles that in a visual drag-and-drop workflow builder with If/Else branches and delays. "Accepted? Send message one. Not accepted after a week? Branch somewhere else" is a few blocks on a canvas.
Limits are where architecture matters. Every paid Ampliflow plan caps connection requests at 25 per LinkedIn account per day. Follow-up messages are capped at 25 a day on Standard, 50 on Pro and 80 on Team. Profile views are 50, 80 and 100. Sends happen only during your configured working hours with randomised timing jitter, so the pattern doesn't look like a script firing every 90 seconds. A real-time safety score with anomaly detection flags trouble before LinkedIn does, and auto-pause on reply stops a sequence the moment someone answers.
Campaigns run in the cloud through the Unipile API. You connect your account once with the Chrome extension, and after that nothing depends on your laptop being open.
On price: Standard is $19/mo for founding members (regular $39), Pro is $39/mo (regular $59), and Team is $99/mo. Founding prices are locked for life for the first 100 paying customers. Every plan has a 7-day free trial, and full details are on the pricing page. Some tools are cheaper. Linked Helper starts at $15/mo and Dux-Soup at $14.99/mo, and if budget is your only constraint, they're legitimate options. Check how and where they run before you trust them with your account. At the other end, Expandi and Salesflow start at $99/mo and Zopto at $197/mo, so cloud-based safety doesn't have to cost that much.
Once replies come in, the job moves from sending to converting. Our meeting-booking playbook picks up from there.