LinkedIn InMail credits: how they actually work
LinkedIn InMail credits are a paid currency that lets you message people you are not connected to, with a partial refund if they respond. Used well, they are a precision tool for high-value targets, but for most outbound, connection-based outreach beats LinkedIn InMail credits on cost and volume.
We see founders burn hundreds of dollars on InMail in a single quarter then quietly switch back to connection requests. That is usually not because InMail is “bad”, it is because they never learned how the credits, refunds, and limits really work.
What LinkedIn InMail credits actually are
An InMail credit is one paid message you can send to a LinkedIn member outside your 1st-degree network: no intro, no email address required. Credits sit in a shared pool attached to your premium or sales plan, and each InMail you send consumes exactly one credit.
Key points from running our own outbound:
- Credits are scarce, especially on non-sales plans.
- They are not tied to a specific recipient until you hit Send.
- If several team members share one Sales Navigator contract, they share the same credit pool.
Compared to regular LinkedIn messages, InMail has two unique traits:
- You can reach people without connecting first.
- Subject lines and templates look slightly different in the inbox, so your message feels closer to email than chat.
That second part sounds like a small UI detail, but in practice we see recipients treat InMail as “sales outreach” by default and regular messages as “networking”. It affects reply tone and expectations.
If you are still new to outbound on LinkedIn, it is usually smarter to first master acceptance rates and reply rates via connection-led flows. Our benchmarks for what “good” looks like are here: LinkedIn acceptance rate: what "good" really looks like and LinkedIn reply rate: realistic benchmarks and fixes.
How InMail credits work across plan types
LinkedIn does not expose one single, simple table inside the app, but the pattern across plans is very consistent: higher-priced sales and recruiting products include larger InMail bundles because that is the core of how power users work.
Here is the rough shape:
| Plan type | Typical InMail role | Who it actually suits |
|---|---|---|
| Premium Career / Basic | Occasional reach-out to hiring managers | Individual job seekers |
| Premium Business | Light prospecting and vendor outreach | Solo founders and consultants |
| Sales Navigator Core | Primary 1-to-1 outbound channel | SDRs, AEs, solo sales-led founders |
| Recruiter plans | High-volume candidate pipelines | Internal recruiters and agencies |
A few practical details from our own use and clients we talk to:
- Credits renew on a monthly cycle aligned to your billing.
- Some plans let unused credits roll over for a few cycles up to a cap, after which you start losing the oldest credits first.
- If you run out, you either wait for renewal or pay for add-on credits, which gets expensive fast.
For teams doing systematic outbound, we treat InMail as a special budget line, not the default channel. At Ampliflow, we run the bulk of our founder outreach through connection-based flows and keep InMail for very narrow slices, for example 10 to 20 “must reach” people for a beta cohort.
If your main tooling is Sales Navigator plus a cloud automation platform like Ampliflow, your real throughput comes from connection requests and follow-ups, not from InMail volume.
Refund-on-reply mechanics: when you actually get credits back
The most misunderstood part of LinkedIn InMail credits is the refund logic. Many people assume every “seen” or “clicked” InMail earns a refund, then get a shock when their pool does not refill.
The real rules are stricter:
- You earn a credit back only if the recipient replies within a defined time window.
- Any reply counts, even “No thanks”, as long as it is a direct response to that InMail.
- You do not get credits back if they simply accept a connection, react with an emoji, or message you separately without replying in-thread.
Two subtle gotchas we keep running into:
- People forget that refunds are not instant. Credits can take some time to show back up, which makes day-to-day tracking messy.
- If an account is restricted or closed after you send, you usually do not see an automatic credit return.
What this means in practice:
- You should treat every InMail send as money spent, and the refund as a bonus.
- Campaigns that drive polite “No, not now” replies are financially better than ones that get ghosted.
When we coach founders, we push them to write short, clear InMail copy that invites a binary answer. Two or three lines with one sharp question like “Is outbound on LinkedIn a priority for you this quarter or not really yet?” beats long essays. You either get a route-forward or you recover the credit.
InMail vs connection-request economics for outbound
This is the real decision: pay-per-send with InMail, or spend your finite connection slots and use follow-ups that cost you time but not hard cash.
From running our own outbound and helping early Ampliflow beta users wire up campaigns, we see these patterns:
Cost and volume
- InMail: Each message consumes paid credits, so your volume is hard-capped by your plan. If a credit works out to several dollars, you can easily spend hundreds across a small campaign.
- Connection flows: Connection requests have no direct monetary cost, but you are limited by daily and weekly caps. You pay with time and system complexity instead of per-message fees.
On our founder accounts, we cap connection sends far under the public limits described in LinkedIn connection limits 2026: safe daily & weekly caps. That keeps account health high and avoids sudden restrictions.
Reply behavior
- InMail: Recipients expect a pitch, so reply intent is colder. However, if they reply at all, they are at least acknowledging your topic.
- Connection-first: People are more open to a soft intro, especially if you personalise the note and build a short follow-up sequence.
Multi-touch sequences
- InMail is mostly single-shot with maybe one or two follow-ups before it feels pushy.
- Connection-based outreach can support structured multi-step flows: connect, value drop, question, case study, soft CTA.
This is exactly what Ampliflow is built for: visual workflows where you string together visits, follows, connection requests, messages, and If-Else branches tied to replies. Because we run through the Unipile API in the cloud, the laptop can stay closed while the workflow executes with human-like jitter and real-time safety scoring.
Our own rule of thumb:
- Use InMail for ultra-targeted, high-value people you might not get another shot at, for example, 5 to 10 VPs in a niche account list.
- Use connection requests for everything else, then nurture those connections properly.
If you try to brute force top-of-funnel entirely through InMail, your cost per meeting balloons fast. Even at Ampliflow’s planned Starter price of $39/mo, a single month of heavy InMail sends can outstrip your automation stack budget.
Where LinkedIn InMail credits fit in a modern outreach stack
InMail is one channel among many. If you stack it with cloud automation, email, and some content, you get a flexible system that does not depend on one brittle tactic.
Here is how we position it in our own stack:
- Core: connection-based LinkedIn workflows running in Ampliflow, backed by Sales Navigator searches and auto-pause on reply.
- Precision: a small weekly quota of InMails for “harder to reach” people, often senior titles who keep tight control on their network graph.
- Support: occasional manual InMail from founders when you genuinely have a tailored reason to reach someone.
Because Ampliflow is pre-launch, we are using our own outreach to recruit founding members who lock $19/mo for life (first 100 only). Competing tools like Dripify at 79 dollars a month or Expandi at 99 dollars a month are excellent for teams that want mature playbooks and do not mind browser extensions or more aggressive volume. A few cheaper desktop-first tools such as Linked Helper or Dux-Soup can make sense if budget is the only constraint and you are comfortable managing account safety yourself.
We take a different bet: lower volume, higher quality, everything cloud-side via API with safety controls baked in. Randomised timing, anomaly detection, and hard caps based on your warm-up stage, which we have written about here: LinkedIn account warm-up: safe ramp-up that actually works.
If you already use a legacy tool and are comparing architecture and pricing, we wrote a practical breakdown here: Dripify Alternative: Cloud LinkedIn Automation From $19/mo. Our public Pricing page covers how the founding price lock works and how it will compare to the $39/mo Starter and $79/mo Pro tiers at launch.
Used like this, LinkedIn InMail credits stop being a vague “extra feature” and become exactly what they should be: a small, intentional part of a larger outbound system, not the engine that has to carry your entire funnel.