How Long Should a LinkedIn Message Be? Lengths by Stage

Most LinkedIn messages lose the reader before the second sentence. So here is the direct answer to how long should a LinkedIn message be: keep connection notes under 300 characters (LinkedIn caps them there anyway), first messages between 40 and 80 words, and every follow-up shorter than the one before it. If your cold message needs scrolling on a phone, it is too long.

The rest of this post is the reasoning, because the numbers only hold up if you understand why they work.

How long should a LinkedIn message be at each stage?

Length is not one setting. It changes with how much the other person already knows about you. A stranger owes you nothing, so the first contact has to cost them almost no attention. Once they have replied, the rules loosen, and you can match whatever length they send back.

Our position is blunt: in cold outreach, short wins, and the burden of proof sits on every extra sentence. Most messages that fail did not need more explaining. They needed a reason to care, stated early, and a question that was easy to answer.

Quick-reference table by message type and funnel stage

If you only remember one row, make it the third column of the first message. Forty to eighty words fits three or four short sentences, and that is enough to be specific without becoming a pitch deck.

The mobile preview does the first round of reading

A large share of LinkedIn reading happens on a phone, inside a notification or a cramped inbox list. In both places the prospect sees your name, your photo, and the opening fragment of your message. That fragment decides whether they tap.

This is why "Hope you're having a great week!" is so expensive. It burns the only text that is guaranteed to be seen on words that carry zero information. Open with the reason instead: the post they wrote, the hire they just made, the tool they mentioned. The preview should make the rest of the message feel relevant before it is opened.

Once opened, a message that fits on one phone screen gets read in full. One that requires scrolling gets skimmed, and skimming means your ask, usually sitting at the bottom, never lands. Your profile carries part of the load here. A clear headline lets the message stay short, since the reader can check who you are in one tap. We cover that side in Optimizing Your Profile for Outbound.

Reply effort: long messages ask for long answers

People mirror. A four-line message can be answered in four words. A six-paragraph message seems to deserve a considered reply, and "considered reply" is exactly the task that gets postponed until it is forgotten.

Before hitting send, picture the prospect's easiest possible answer. If it is "Yes, Thursday works" or "Not a priority this quarter", you have written a message that is cheap to respond to. If the honest answer requires them to explain their stack, their team structure, and their budget, you have handed them homework.

Even a "no" is useful. It closes the loop, it stops your sequence, and it tells you something about your targeting. Long messages suppress those quick no's along with the yeses.

One message, one ask

The most common reason a message runs long is that it is trying to do three jobs: introduce, educate, and book a call. Each job adds a paragraph, and each paragraph adds a decision for the reader.

Pick one ask per message. Good asks are small and answerable:

• "Is onboarding still handled by your CS team, or did you move it to product?"
• "Worth a 15-minute look, or not relevant right now?"
• "Want me to send the template?"

Two asks in one message create a choice the reader has to resolve before replying, and an unresolved choice usually means no reply. If you have a second question, it belongs in the follow-up. That is what follow-ups are for. For how to space those messages across days and channels, see Designing an Outreach Cadence That Gets Replies.

What fits in a connection note

Three hundred characters is roughly two sentences. That is the right amount, because a connection note has one job: get the request accepted. Selling before acceptance reads as a bait-and-switch, and prospects have learned to spot it.

A note that works:

Hi Priya, your post on moving onboarding in-house at a 20-person team was the clearest take I've read on it. I work on the same problem and would like to follow your writing.

That comes in well under the cap. It is specific, it is true, and it asks for nothing beyond the connection.

A note that does not work: anything that starts with your company name, includes a calendar link, or could be pasted to a thousand people unchanged. If you cannot find a specific reason, send the request blank. A blank request is neutral. A generic one tells the recipient a template is coming.

First messages and follow-ups, written short

Here is a first message in about 55 words:

Thanks for connecting, Priya. Since you moved onboarding in-house, I'm curious how you're handling accounts that stall after week one. We built a checklist for exactly that gap, used by teams around your size. Is that a problem you're actively working on, or already solved?

One reason, one piece of context, one question. Nothing to scroll.

The first follow-up should add something new rather than repeat the pitch:

Here's the checklist I mentioned, no call needed. If stalled accounts aren't a priority right now, just say so and I'll stop nudging.

The final nudge gets even shorter: "Should I close the loop on this one?" It gives permission to decline, and that often draws the reply the longer messages could not.

When a longer message is the right call

Short is the default for cold contact, not a law. Write longer when:

• They asked a detailed question. Answer it properly. Clipping a real answer to hit a word count is worse than a long reply.
• You are confirming specifics. Agendas, pricing details, or next steps after a call can run longer because the reader is already invested.
• The conversation is warm. Once someone is replying in full paragraphs, matching them shows you are paying attention.

The rule underneath all of this: length should track the reader's investment, never yours. For what happens once a thread turns into a booked call, How to Book Meetings from LinkedIn picks up from there.

Keeping messages short when outreach is automated

Automation tends to make messages longer. Templates accumulate merge fields, people add "just in case" sentences, and a sequence written once gets sent hundreds of times without anyone rereading it on a phone.

A few habits help, and this is where Ampliflow's features apply:

• Test length directly. Ampliflow's A/B testing lets you run a 45-word first message against a 90-word version on the same audience and compare replies in funnel analytics, instead of guessing.
• Stop sequences on reply. Auto-pause on reply means a short scripted follow-up never lands after a prospect has already written back. Nothing undoes a warm reply faster than a canned "just bumping this".
• Respect volume ceilings. Ampliflow caps each LinkedIn account at 25 connection requests a day on every paid plan, and messages at 25 on Standard, 50 on Pro, and 80 on Team, sent with randomised timing only during your working hours. Fewer, tighter messages fit those limits better than long ones sent in bulk.

Honest note on cost: if you only need basic sequences, Linked Helper at $15/mo and Dux-Soup at $14.99/mo are cheaper than our Standard plan at $19/mo for founding members. What you get with Ampliflow is campaigns running in the cloud via the Unipile API with the laptop closed, If/Else workflow logic, and real-time account safety scoring. Plans and the 7-day free trial are on the Pricing page.

Whatever tool you use, reread every template on your phone before it goes live. If it scrolls, cut it.