Blog

    LinkedIn InMail vs Connection Request: Which Should You Use?

    FollowArc6 min read
    LinkedIn outreachInMailconnection requests

    Quick answer: A connection request asks someone to join your network, and once they accept you can message them freely. An InMail is a message sent directly to someone you are not connected to, usually using a limited allowance that comes with certain paid plans. For most outreach, start with connection requests because they are the default, low-friction path. Use InMail for the people who matter most or who are unlikely to accept an invitation.

    The two tools in plain terms

    Connection request. You send an invitation, optionally with a short note. If the person accepts, you become a first-degree connection and can send normal messages. Nothing is delivered to their inbox until they accept, other than the invitation itself.

    InMail. You send a message to someone outside your network without needing them to accept first. It lands in their inbox with a subject line and a body. How many InMails you can send, and whether you can send any, depends on the LinkedIn plan you hold. Check LinkedIn's current plan details for the specifics, because they change.

    There is also a free route some people overlook: certain members allow anyone to message them without a connection. Whether that applies depends on their settings, so you only find out when you look at the profile.

    Side-by-side comparison

    QuestionConnection requestInMail
    Who can receive itAlmost anyoneAlmost anyone, subject to your plan and their settings
    Do they need to accept firstYes, before you can messageNo, it is delivered directly
    What it costs youCounts toward your invitation limitsUses a limited allowance from a paid plan
    Message lengthA short optional noteA subject line and a longer body
    What it feels like to the readerA small ask: add meA cold message from a stranger
    After a positive responseYou are connected and can keep talkingYou can reply, but you are not connected
    Main riskLow acceptance if the request looks irrelevantWasting a scarce allowance on the wrong person

    The key trade-off is permission versus reach. A connection request asks for a tiny bit of permission and builds a lasting link. An InMail skips the permission step but spends something scarce and arrives as an obvious cold message.

    When a connection request is the better choice

    • You are reaching many people. Connection requests scale in a way a limited InMail allowance does not, though they are still capped. See the weekly invite limit explained and how many requests per day are reasonable.
    • The relationship is the point. Being connected gives you ongoing access: you can follow up, see their posts, and stay visible.
    • Your offer needs a warm-up. A request, a few days, then a short message is a gentler path than a pitch.
    • You can write a reason to connect. Shared context, a mutual interest, or a specific compliment makes acceptance more likely. The connection note generator can help you draft one.

    When InMail is the better choice

    • The person is high value and your list is short. If you are targeting a handful of senior people, spending allowance on each is reasonable.
    • They rarely accept invitations. Some people have thousands of pending requests and never look at them. A direct message to the inbox may be seen sooner.
    • You need to say something that does not fit in a short note. A clear, specific message with a reason you are writing can be too long for an invitation note.
    • Your connection requests are already pending or ignored. Rather than sending another invitation, a single well-aimed message can be a different attempt.

    When neither is the answer

    If your message could be sent to anyone, neither channel will rescue it. Both fail when the target is wrong or the message is generic. Before choosing a channel, decide who you are writing to, using an ideal customer profile, and what you are offering them.

    A practical way to combine them

    You do not have to pick one. A simple pattern:

    1. Default to a connection request with a short, specific note or no note at all.
    2. If accepted, send a short first message a few days later that references why you connected.
    3. If the request sits unaccepted for a few weeks, withdraw it to keep your pending list tidy.
    4. For a small set of priority people, consider an InMail instead of, or after, the request.
    5. Add email as a third channel where you have a legitimate way to reach someone. See LinkedIn vs email outreach.

    Keep the sequence short. Building one end to end is covered in how to build a LinkedIn outreach sequence.

    How to decide with your own numbers

    There is no universal winner, and any article that claims one is guessing. Run a small comparison on your own audience:

    • Split a similar list into two groups.
    • Send one group a connection request and the other an InMail with the same core message.
    • Track replies and booked conversations, not just opens or acceptances.
    • Account for cost: an InMail spends a limited allowance, so a reply from an InMail is worth more only if you would otherwise not have reached that person.

    Keep the test small and the groups comparable. If the numbers are too small to tell the groups apart, treat the result as inconclusive rather than picking a winner. For the full set of numbers worth tracking, read the LinkedIn outreach metrics that matter.

    Mistakes to avoid

    • Pitching in the connection note. A sales pitch in the invitation tends to read as spam. Save the offer for after they accept.
    • Treating InMail as free. The allowance is limited, so using it on a poorly matched person is a real cost.
    • Ignoring pending invites. A large pile of unanswered requests is a bad signal for your account.
    • Sending the same text to everyone. Even a short personal line beats a template. See cold message examples that get replies.

    Where FollowArc fits

    FollowArc's agent, Sophia, runs LinkedIn connection requests and follow-ups across a sequence, and can combine them with email, while safeguards such as per-account pacing and a killswitch keep the volume in check. Those safeguards reduce risk but cannot remove it, since LinkedIn sets the rules. You can read more on the LinkedIn outreach automation page or try FollowArc free for 7 days.

    Keep reading

    Follow FollowArc on LinkedInPractical outreach tips, no fluff.
    Share this:LinkedInXEmail

    Get new guides and tools by email

    When we publish a new outreach guide, template or free tool, we will send it to you. No spam, and you can unsubscribe any time.

    We will email you about new guides and tools. Unsubscribe any time.

    See FollowArc run your outreach

    An autonomous AI sales agent for LinkedIn + email — you stay in control.

    Start your 7-day free trial

    7-day free trial. Add a card to start, $0 today, cancel before day 7 and pay nothing.