InMail is a paid LinkedIn message type that lets a sender reach any member directly without an existing connection, drawn from a monthly credit allotment tied to a Sales Navigator or Premium subscription.
A normal LinkedIn message only works between two members who are already connected. InMail exists to get around that gate: it lets a sender reach someone they aren't connected to, at the cost of one credit from a monthly allotment attached to their subscription. It shows up in the recipient's LinkedIn inbox alongside their regular messages, not as a separate category they have to go looking for.
Because it lives inside LinkedIn's own messaging product, InMail behaves like a LinkedIn message rather than an email. It's read on the platform, often on the mobile app, next to a recipient's other notifications. That changes what works: a long, formatted pitch built for an email client tends to read poorly here, and the sender's profile, headline, and mutual connections are visible right alongside the message in a way they aren't in an inbox.
Because each send costs a credit, teams generally treat InMail as a lower-volume, higher-intent tactic rather than something run at cold-email scale. It gets reserved for specific, high-value targets where a personalized message justifies the cost, rather than sent as a first-touch to an entire list.
InMail is usually one channel in a multi-channel sequence rather than the whole play: a connection request or a piece of content engagement first, an InMail or cold email as the direct ask, sometimes a call layered in. Sending it cold with no prior context tends to perform the same way a cold email with no personalization does.
InMail gets treated as a direct substitute for cold email with the same volume and cadence expectations. It isn't built for that. The credit limit caps how many a single account can send in a month, and the messaging format rewards something shorter and more personal than a cold-email template pasted in as-is.
Tell us how your motion runs today. We'll show you what we'd engineer.
Contact us