You've found the recruiter and the hiring manager at the company you've been watching. Their profile is open in front of you, and you're hovering between two buttons: Connect and Message. This is the moment where most job searches quietly lose steam, not because the wrong choice is catastrophic, but because the decision gives people something to debate instead of something to write.
The direct answer to the LinkedIn InMail vs. connection request question: connection requests win in most situations. The reason why matters more than the conclusion, because understanding it changes what you actually put in the message.
A note capped at 300 characters is a structural constraint that becomes an advantage when you treat it correctly. You cannot fit your work history into 300 characters, which means you end up with something leaner by necessity: one observation about them, one signal about yourself, one reason to respond. When those three things are genuinely specific, the note reads like a message from someone who actually did their homework rather than someone running a search.
Recruiters see a lot of InMail, and most of it sounds identical. "I came across your profile and was immediately impressed by your background" lands in the same mental category as the fourteen other messages that opened exactly that way this week. A connection note with real specificity inside it cuts through more than it rationally should, simply because the bar for InMail has fallen low enough that basic preparation stands out.
Once someone accepts a connection, messages don't require credits and the interaction isn't a single transaction you have to win on the first send. Response rates for conversations that begin with an accepted connection tend to run higher, not because the channel is inherently better but because clearing that first filter already told you something: they were interested enough to say yes.
InMail exists because sometimes there is no other direct line. If the person you need to reach has no mutual connections with you and your network has no foothold at that company, a connection request might sit unread for two weeks while the opportunity closes. InMail reaches a dedicated folder and signals real intent, since it costs something to send.
LinkedIn's refund policy returns the credit if you don't receive a response within 90 days, so the economic cost is mostly your time. That shifts the math for situations where the target matters and timing is short: you need a direct line now rather than a connection that clears when they happen to log in.
The scenario where InMail wins is specific: you have no path in, timing matters, and you've written something that isn't templated. Sending InMail that opens with a generic compliment hands the channel's one structural advantage right back.
The format question is downstream of a harder one: do you know what you're offering clearly enough to say it in two sentences? Most outreach fails not because of the delivery format but because the message gives the reader no particular reason to respond.
The people who get responses are usually the ones who understood their track record well enough to know which problems they solve, what outcomes they've produced, and why that's relevant to this specific person at this specific company. Writing the note becomes easier once that thinking is done. The character limit stops feeling like a problem and starts functioning as a structure you can actually use, because you already know what matters enough to know what to leave out. That clarity rarely comes from drafting the message; it comes from doing the thinking before you ever open LinkedIn.
Prism Tree generates both a tight connection note and a full recruiter message from your Career Brain and the specific role you're targeting, so you arrive at the conversation with something worth sending. Start at app.prismtree.ai.