Get the kit
Guide · Templates · LinkedIn

Every LinkedIn cold message template here is grouped by the situation you are writing in, with placeholders and a note on when it backfires.

A LinkedIn cold message template is a shape, not a finished message: a reason line about the reader, one line of relevance, one ask, and placeholders where the specifics go.

This page holds 16 of them, grouped by the situation you are writing in, from a connection note to the last message in a thread. Each one names its placeholders and the moment it backfires, inside the limits LinkedIn sets.

Last checked Sep 23, 202615 min read16 messages written for this page

What a LinkedIn cold message template is

A LinkedIn cold message template is a reusable structure for writing to someone who has never spoken to you: an opening line about the reader, one line that explains why you are writing, one ask, and placeholders where the specifics go.

It is a shape, not a finished message. The template decides the order of the ideas and the size of the ask. You still have to supply the reason, and the reason is the only part the reader cares about.

LinkedIn is not email with a different logo. The reader can see your photo, your headline and your last post before deciding whether to open the message, and there is no unsubscribe link between you. That changes what a template can get away with.

Sellers use the word template for two different things: a finished message they paste and send, and a structure they fill in. Only the second kind survives contact with a real prospect. The first kind is the one your industry has already read twice this quarter.

This page is the message library for cold outreach on LinkedIn. The surrounding method, building the lists, running the search and setting the cadence, sits on our LinkedIn prospecting guide.

LinkedIn cold outreach compared with cold email

Cold outreach on LinkedIn and cold email are not the same job with a different address bar. A template that earns replies in a sales inbox usually fails in LinkedIn messaging, because the reader can see exactly who is writing before deciding to open it.

What changesCold emailLinkedIn message
What the reader sees firstA name, a subject line and a signatureYour photo, headline, company and recent activity
Length that fitsAround 120 words200 characters in a note, four short lines in a message
The exitAn unsubscribe link, required by lawNo unsubscribe, so the copy has to offer one
Cost of a careless sendDomain and sending reputationInvitation restrictions on your own account
Follow-upA few messages in the same threadTwo, and none at all on an unanswered InMail
Who you can reachAnyone whose business address you can verifyLimited by degree, shared groups and credits

Most sales teams end up keeping two libraries of templates for that reason: one for the inbox, one for LinkedIn messaging. This page is the LinkedIn one. How the two channels are timed against each other belongs in your sales outreach plan.

The limits LinkedIn sets on each message type

Every template below has to fit inside a box LinkedIn defines. The box is different for each route, and picking the wrong route is a more common failure than picking the wrong words.

RouteWho it reachesWhat LinkedIn Help states
Connection request noteAnyone with a visible Connect buttonEach note can be up to 200 characters. LinkedIn Help says free accounts can add a note to a small number of requests per month
Message to a 1st-degree connectionPeople who accepted youOrdinary messaging, no credit and no separate allowance
InMailMembers you are not connected toPremium feature. Optional subject up to 200 characters, body up to 1,900 characters (LinkedIn's general FAQ says 2,000; write to the lower figure). Credits expire after 90 days and come back when the recipient accepts, declines or replies
InMail in Sales NavigatorLeads you have unlocked50 credits a month, accumulating to 150, with a credit returned when the lead accepts, declines or replies within 90 days
Message requestCoworkers and fellow group members you are not connected toThe recipient accepts or privately declines, the sender is not told about a decline, and attachments cannot be sent

Two rules shape the whole library. LinkedIn states that InMail is designed for initial outreach only and that you cannot send a follow-up InMail unless the recipient accepts and responds. Its Professional Community Policies say not to use the invitation feature to send promotional messages to people you do not know.

One number LinkedIn does not agree with itself on

The Help page on personalizing invitations gives free accounts three notes a month at 200 characters. A second Help page says basic accounts get five, and that Premium members send unlimited notes at 300 characters. Check your own account before you plan a week of sends.

LinkedIn also caps invitations without publishing the weekly number. Its Help pages say a restriction usually lasts a week, that withdrawing pending invitations will not remove it, and that after a withdrawal you cannot invite the same person again for up to three weeks. Our LinkedIn connection limit entry covers that in detail.

The four parts of a LinkedIn cold message

Strip any message that earns a reply and the same four parts are there, in the same order.

  • The reason line. What you saw, and why it made you write today. A post, a job posting, a role change, a group, a mutual contact.
  • The relevance line. One sentence connecting that observation to a problem people in their seat actually have. Not your product, the problem.
  • The ask. One question, answerable in a line, that a busy stranger can say yes or no to without a calendar.
  • The exit. A short signature, and a way to say no that costs them nothing. On LinkedIn there is no unsubscribe, so you supply one.

The reason line is the only part a template cannot write for you. Everything else can be structured in advance, which is what the blocks below do.

How long a LinkedIn cold message should be

Length is set by the route, not by taste. A connection note has 200 characters, which is about 35 words, so it holds one observation and one plain sentence about why you want to connect. Nothing else fits.

A first message after acceptance should still read in one screen on a phone, which in practice means four short lines. An InMail body can run to 1,900 characters (LinkedIn's general FAQ says 2,000), and using all of them is the fastest way to look like a mail merge with a bigger budget.

LinkedIn's own guidance for writing InMail messages is short: be brief and to the point, mention the profile content that prompted you to write, and give the reader a reason to reply by asking for advice, opinions or referrals.

No benchmarks here

Outreach vendors publish acceptance rates and reply rates for LinkedIn messages, measured on their own users and their own markets. None of those figures are quoted on this page. Compare your own variants on your own list instead, over enough sends to mean something.

The one ask, and why a second question kills the first

Two questions in a cold message do not double your chances. They make the reader choose which one to answer, and choosing is work, so the message gets left for later and later never comes.

The ask should also match how far you have earned the right to ask. A stranger who has read one message from you owes you nothing, so a 30 minute call is a large request and permission to send something is a small one.

AskCosts the readerRight when
Permission to send one resourceA one-word replyFirst touch, no prior relationship
A diagnostic questionA sentence, if they careThe problem is obvious from their role or their posting
Pointing you to the right personA nameYou wrote to someone senior to the owner of the problem
A short callCalendar timeThey replied, engaged with your content, or the trigger is strong
A demo or a trialReal evaluation effortThey asked what it looks like

LinkedIn prospecting messages examples, grouped by situation

The 16 blocks below are LinkedIn prospecting messages examples written for this page, not collected from anyone's campaigns. They are grouped by the situation you are writing in, because the situation decides the route, the length and the size of the ask. Between them they cover most of what a sales team writes into.

Each block gives you a label, the placeholders to replace, and a note on when that template backfires. Read the backfire note first. It is usually the reason a message that works for one seller reads as spam from another.

  • Replace every placeholder. A stray set of braces in a sent LinkedIn message is the clearest proof of automation there is.
  • Rewrite the first line in your own words. It is the only part that shows a person, not a tool, chose to write to this reader.
  • Keep the route. A note written for 200 characters does not become an InMail by adding paragraphs to it.

Connection request notes that get accepted

The note has one job: earn the connection. It does not sell, it does not link, and it does not ask for time. LinkedIn treats invitations that sit unanswered or get marked as spam as a reason to restrict an account, so a note that overreaches costs more than a lost prospect.

1. After something they published

Note 01, their post
Hi {{firstName}}, your post on {{topic}} said the part most {{role}} posts skip. I work on {{area}} and would like to keep reading what you write.
Backfires when

You did not actually read the post. Naming something you skimmed invites a reply that asks what you thought of it, and there is no recovering from the answer. Quote a specific line or pick another reason.

2. Through a mutual connection

Note 02, mutual contact
Hi {{firstName}}, {{mutualName}} and I worked together on {{project}}, and your name came up when we talked about {{topic}}. Glad to connect.
Backfires when

The mutual contact barely remembers you, or would not vouch for you if asked. The reader can message them in one tap. Ask the mutual contact first, or leave the name out.

3. After an event or a shared group

Note 03, event or group
Hi {{firstName}}, we were both at {{eventName}}. Your question about {{topic}} was the one I left thinking about too. Connecting so I can follow what you publish.
Backfires when

The event was months ago, or you are working from an attendee export rather than a memory. A shared room is a weak reason that goes stale fast. Send it the same week or not at all.

4. A peer with no trigger at all

Note 04, no trigger
Hi {{firstName}}, I run {{area}} at {{companyName}} and read most of what {{role}}s in {{industry}} publish about {{topic}}. Connecting for that reason only.
Backfires when

You send it to a budget owner instead of a peer. Between equals, curiosity is a complete reason. Sent up the org chart with nothing behind it, it reads as a list import.

The message after a connection is accepted

This is where most LinkedIn outreach dies. The note earned the connection on a promise of no pitch, and the message that arrives an hour later pitches. The reader does not withdraw the connection, they just stop reading anything you send.

The fix is to continue the reason you gave, offer exactly one thing, and ask one question that lets them end it politely.

5. Continue the reason from the note

Message 05, continue the reason
Thanks for connecting, {{firstName}}.

The {{topic}} point you made lines up with what {{role}} teams keep telling us. We wrote our version down as {{resource}}.

Want it, or is that already handled on your side?

{{senderName}}
Backfires when

The resource is a landing page behind a form. You promised a document and delivered a lead capture, which is the moment the reader decides what every later message from you will be.

6. Offer one thing, no call attached

Message 06, one offer
Hi {{firstName}}, thanks for the connection.

I put together {{resource}} for {{role}}s dealing with {{problem}}. It takes about {{minutes}} minutes to read and there is no call attached to it.

Say the word and I will paste it here.

{{senderName}}
Backfires when

You promise no call and open the next message with a calendar link. If the resource is genuinely the offer, the follow-up has to behave like it was.

7. The diagnostic question

Message 07, diagnostic
Hi {{firstName}}, quick question rather than a pitch.

When {{role}} teams at {{industry}} companies handle {{process}}, it usually breaks at {{stage}}.

Is that where it breaks for you, or somewhere else entirely?

{{senderName}}
Backfires when

The premise is wrong for their company. A confident diagnosis of a problem they do not have proves you know the segment and not the reader. Check the size, the stack and the market first.

LinkedIn messages by trigger

A trigger is a dated event that gives you a reason to write today rather than last month or next year. It also sets the window. Our trigger marketing entry covers how the signals are built; these are the messages that sit on top of them.

8. A new role or a job change

Message 08, new role
Congratulations on the move to {{companyName}}, {{firstName}}.

New owners of {{area}} usually spend the first weeks deciding what to keep. We wrote down the {{problem}} questions the last few {{role}}s asked us.

Useful, or too early?

{{senderName}}
Backfires when

The move is old news. A note about a first few weeks sent in month nine tells the reader exactly how the list was built. Check the start date on the profile before you write.

9. An open job posting

Message 09, hiring signal
Hi {{firstName}}, I saw {{companyName}} is hiring a {{jobTitle}}.

That role usually gets opened when {{problem}} has outgrown the current setup. We work on that part with {{role}} teams.

Worth a short exchange here, or is the hire the whole plan?

{{senderName}}
Backfires when

You imply the hire is a mistake, or that your product replaces the person they are recruiting. The reader wrote that job description. Position alongside the hire, never instead of it.

10. Funding, expansion or a new market

Message 10, expansion
Hi {{firstName}}, {{companyName}} announcing {{event}} is the reason I am writing.

Teams going through that usually hit {{problem}} a quarter or two later, because {{reason}}.

Happy to send what we have seen work, no call needed. Want it?

{{senderName}}
Backfires when

Congratulations is the whole message. Every vendor with a news alert sent the same note that week, so the opening line has to be followed immediately by something only you would say.

11. A change in their stack

Message 11, tech change
Hi {{firstName}}, I noticed {{companyName}} started using {{tool}}.

The part teams usually rebuild around it is {{process}}, and it tends to surface about {{timeframe}} in.

Do you want the checklist we use for that, or are you past it already?

{{senderName}}
Backfires when

Your source for the tool is a guess from a job posting or a badge on a website. A wrong specific ends the conversation faster than a missing one, and it names the data vendor you used.

12. They engaged with your content

Message 12, after engagement
Hi {{firstName}}, you commented on my post about {{topic}}, so I owe you a proper answer.

Short version: {{answer}}. The longer version is in {{resource}}, which I can paste here.

What made the topic land for you?

{{senderName}}
Backfires when

The engagement was a reaction on a post from four months ago. A like is a very small signal with a short window, and treating it as intent is how a good content account gets a reputation for pouncing.

Messages to people outside your network

When the Connect button is missing, the invitation is pending, or the reader is out of network, two routes remain. Both are covered by LinkedIn's rules rather than by your preference, and both are described on our what is InMail on LinkedIn page.

A message request reaches coworkers and fellow group members you are not connected to. The recipient accepts or privately declines, and LinkedIn does not tell you which happened. Read receipts appear only after they accept, so silence is genuinely silent.

13. InMail with the reason in the subject

Message 13, InMail
Subject: your {{topic}} post, and one question

Hi {{firstName}},

You wrote that {{observation}}. We hear the same thing from {{role}}s at {{industry}} companies, usually because {{reason}}.

I can send the one page we use for it. Want it, or is this the wrong week?

{{senderName}}
Backfires when

You spend a credit on someone whose Connect button was right there. LinkedIn returns the credit only if the recipient accepts, declines or replies, and it allows no follow-up InMail until they do. Invite first, spend second.

14. A message request through a shared group

Message 14, message request
Hi {{firstName}}, we are both in {{groupName}}.

Your point in the {{threadTopic}} thread is the one I keep arguing internally. We ended up building {{approach}} around it.

Would the write-up be useful, or is that a solved problem for you?

{{senderName}}
Backfires when

You joined the group that morning to unlock the route. Members can see when you joined and what you have posted, and a group used only as a door is obvious from the profile.

Follow-up on LinkedIn, and when to stop

Follow-up on LinkedIn behaves differently from email. The messages stack in one thread the reader can scroll, so a third nudge with nothing new in it is visibly a third nudge. InMail has no follow-up at all until the recipient responds.

Two follow-ups after the first message is enough for most sellers, spaced across business days rather than hours. The pacing belongs in your sales cadence, not in the template.

15. One follow-up with something new in it

Message 15, follow-up
Hi {{firstName}}, adding one thing rather than repeating myself.

{{newFact}}, which is the part {{role}} teams usually find out the hard way.

Still happy to send {{resource}}. A "no thanks" is a completely fine answer.

{{senderName}}
Backfires when

The new thing is a reminder that you wrote before. Bumping the thread with "just following up" adds a message and no reason, and it is the line readers use to decide you are working a list.

16. The last message in the thread

Message 16, closing the file
Hi {{firstName}}, I will leave this here.

If {{problem}} becomes a priority at {{companyName}}, my messages stay open and you can reply to this one.

If someone else owns it, a name is all I need and I will stop writing to you.

{{senderName}}
Backfires when

It is not actually the last message. A closing note followed by another sequence two weeks later teaches the reader that nothing you write is true, which is a worse outcome than no reply.

What gets ignored, and why

Messages are not usually rejected. They are skipped in a list of notifications, which means the decision happens in the preview line, before any of your copy is read.

What the reader seesWhat they concludeWhat to do instead
A blank invitation from a strangerList importUse the note, even at 200 characters
An opening line that fits any readerMail mergePut something only true of them in sentence one
A pitch straight after a no-pitch noteThe note was a trickContinue the reason you actually gave
A wall of text in the previewWorkFour short lines, one ask
A calendar link in a first messagePresumptionAsk permission to send one thing
A wrong company factBad data, bad vendorVerify the specific or drop the sentence
Three messages with no new informationAutomationStop after two follow-ups

Most of these are tone problems rather than copy problems, and tone is what our salesy entry is about. A template cannot fix a message that is asking for too much too early.

The placeholders, and how to fill them

Every block above uses double-brace placeholders so the unfilled ones are impossible to miss. They fall into three groups, and they are not equally safe.

Safe to merge{{firstName}}, {{companyName}}, {{role}}

Fields you can pull from the profile with low risk. Check the spelling of the first name and whether the person uses a shortened version in their headline.

Verify one by one{{topic}}, {{observation}}, {{tool}}, {{event}}

Anything you claim to have seen. If you cannot point at the post, the posting or the announcement, delete the sentence rather than guessing at it.

Written once, reused{{problem}}, {{resource}}, {{approach}}

Your own material. Write these for each segment, not each prospect, and keep the wording consistent across the team so replies are answered the same way.

Never mergedThe first sentence

The reason line is a research output, not a field. It is the difference between a message written for one reader and a message sent to a list of them.

Use your ideal customer profile to decide which segments get their own set of the reusable placeholders. Two or three sets, one per industry you sell into, is usually enough to start.

One placeholder deserves its own rule. Fill the first name slot with the name the person uses in their headline and signs their own posts with, not the name in the profile URL and not a full legal name they never use. A wrong name costs more than a missing sentence.

Which template fits which situation

SituationRouteBlocksWindow
They published something you readConnection note01, then 05Days, while the post is live in their feed
You share a real mutual contactConnection note02Open, as long as the contact would vouch
Same event or groupNote or message request03, 14The same week for events
No trigger, peer levelConnection note04Open
They changed jobsNote, then message08The first months in the seat
They are hiring for the problemNote, then message09While the posting is open
Funding or expansion newsNote, then message10Weeks, not quarters
They engaged with your contentMessage12Days
No Connect button, no shared groupInMail13Whenever the reason is real
First message went unansweredMessage15, then 16Across business days

What to check before you write

The research is the template. Everything below takes a couple of minutes per prospect, and it decides whether the message reads as work or as a send.

  • The name they use. Take the first name from the headline and the way they sign their own posts, not from the profile URL. A shortened name typed in full is a small, loud tell.
  • The role, and how long in it. Time in seat sets both the trigger and the window, and it tells you whether this person owns the problem or inherited it from someone who left.
  • The company. Size, industry, market and what the company page has published recently. A message aimed at the wrong size of company is wrong before the first line.
  • Their last few posts and comments. This is where reason lines come from. It is also where you find out they already sell something adjacent to yours.
  • What they say about being contacted. Some profiles state it plainly in the About section, and ignoring that line is the one mistake no template survives.
  • Whether a colleague already wrote. Two sellers from one company in one week reads as a campaign, whatever each message says.

Cap the time you spend. If a prospect needs 20 minutes of research to produce one specific sentence, the list is wrong rather than the message, and the fix is upstream in how the leads were built.

How to turn a LinkedIn cold message template into a sent message

  1. Check the account before the person

    Confirm the company matches who you sell to and could actually buy. A perfect trigger at a company that will never be a customer wastes a send and part of your invitation allowance.

  2. Pick the route, then the block

    Look at the profile: connected, out of network, shared group, Connect button missing. The route decides the length and whether a credit is involved, so choose it before you choose the words.

  3. Date the trigger

    Find when the post, the posting, the role change or the announcement happened, and compare it with the window in the table above. If the window has closed, pick a different reason to write.

  4. Write the first line yourself

    Say what you saw and why it made you write today, in one plain sentence. Every other line can come from the template, but this one cannot be merged from a field.

  5. Fill or delete every placeholder

    Replace each one with something you verified. If a slot cannot be filled with a true specific, remove the sentence around it rather than softening it into something vague.

  6. Cut to one ask, proofread, send, log it

    Delete the second question, read it once on a phone screen, send, and record which block went out so you can tell later which situations your replies come from.

You have 60 minutes, then it is permanent

LinkedIn Help says a sent message can be edited or deleted within 60 minutes, that an edit carries an Edited label, and that deleting removes it for everyone in the conversation. After that hour, see whether you can unsend a LinkedIn message.

Where these messages sit in a sequence

No single template is a campaign. The library works as a route through a small number of steps, with an exit at every one of them.

Note200 characters, no pitch
Accepted1st degree, free to message
First messagecontinue the reason
One follow-upsomething new
Close the fileor ask for a name
Blocks 01 to 04WaitBlocks 05 to 12Block 15Block 16

If the invitation is never accepted, the branch is block 13 or 14, not a second invitation. LinkedIn does not let you resend to the same person for up to three weeks after a withdrawal, and repeated pending invitations are one of the stated reasons accounts get restricted.

Anything that sends these for you is covered by LinkedIn's rules on LinkedIn automation, and an account that messages faster than a person could is the account that gets limited.

How a sales team should run a message library

A set of LinkedIn templates goes stale the moment every seller keeps a private copy of it. Cold outreach that keeps working is shared, named and reviewed, which is a process problem rather than a copywriting one.

  • Give every block a name and a number. "Note 03" is something a sales team can talk about in a pipeline review. "The one I use for events" is not.
  • Keep one owner for the library. One person edits the templates, everyone else proposes changes. Otherwise the same message drifts into six versions with no record of which one earned the replies.
  • Suppress by company, not by person. Two sellers messaging two people at one company in one week reads as a campaign. Check the account before the send, not after the complaint.
  • Log which block went out. Put it on the lead record with the trigger and the date. Without that, nobody can say which situations produce replies and which just produce activity.
  • Review by industry, not in general. A block that is dead in one market is often fine in another, so look at the results segment by segment before rewriting anything.
  • Rewrite the reason lines, keep the shape. When a block stops working, the wording is usually tired and the structure is not. Change one element at a time.

A shared library also makes the messaging consistent when leads answer. Two sellers using the same specific words for the same problem sound like a company; two sellers improvising sound like two strangers.

Mistakes that ruin a good template

  • Sending the same block to everyone in a company on the same afternoon.
  • Breaking the promise in the note with the first message after acceptance.
  • Spending an InMail credit on someone whose Connect button was visible.
  • Treating a reaction on an old post as buying intent.
  • Writing 1,900 characters because InMail allows 1,900 characters.
  • Leaving a placeholder in the sent message, or merging a fact you never verified.
  • Asking for a call in the first message to a stranger who has read nothing of yours.
  • Following up a closing message with a new sequence two weeks later.
  • Copying a template word for word, so your market reads it twice in a month.

What to track, by block and by situation

Track the library the way you would track subject lines: per block, per segment, on your own sends. Reply quality matters more than reply count, because a message that pulls polite brush-offs is still failing.

SignalWhat it tells you
Acceptance of invitations by noteWhether the reason line earns the connection
Replies to the first message after acceptanceWhether you kept the promise the note made
Replies that are questions, not brush-offsWhether the ask is the right size
InMail credits returnedWhether the paid route is earning its cost
Pending invitations and warningsThe account's standing with LinkedIn
CompareOne block against one block, on the same segment

Profile quality sits underneath all of it, because the reader checks it before replying. Our LinkedIn profile guide covers the part of the message you are not writing.

The skeleton every block here uses

If you only keep one thing from this page, keep the order. Reason, relevance, one ask, an easy exit. The template below is that order with nothing else in it.

The skeleton every block on this page uses
Hi {{firstName}},

{{observation}}. That is why I am writing today.

{{role}} teams in {{industry}} usually hit {{problem}} at that point, because {{reason}}.

{{ask}} A "no thanks" is a fine answer.

{{senderName}}
Backfires when

You keep the skeleton and merge the observation from a field. That first line is the only part proving a person chose this reader, so a generic opener turns the whole message into automation with better grammar.

Frequently asked questions

What is a LinkedIn cold message template?

A LinkedIn cold message template is a reusable structure for writing to someone who has not spoken to you: a reason line about the reader, one line of relevance, one ask, and placeholders for the specifics. It fixes the order of the ideas, not the content.

How long should a LinkedIn cold message be?

A connection note is capped at 200 characters by LinkedIn, which is roughly 35 words. A first message after acceptance should fit one phone screen, about four short lines.

An InMail body can run to 1,900 characters, or 2,000 in LinkedIn's general FAQ, but using all of them reads as a mail merge.

What do you say in a LinkedIn message after a connection is accepted?

Continue the reason your note gave, offer exactly one thing, and ask one question they can answer in a line. The fastest way to lose the connection is to promise no pitch in the note and then pitch an hour later.

What are the best LinkedIn prospecting messages examples to start with?

Start with the situations you can verify: something they published, a real mutual contact, a shared event or group, a role change, an open job posting or engagement with your content. The situation decides the route, the length and the size of the ask.

Can you message someone on LinkedIn if you are not connected?

Yes, through two routes. A message request reaches coworkers and fellow group members you are not connected to, and the recipient can accept or privately decline without you being told. InMail reaches anyone, needs a Premium subscription and spends a credit.

How many characters is a LinkedIn connection request note?

LinkedIn Help states each personalized note can be up to 200 characters. A separate Help page says Premium members can send unlimited notes with a 300 character limit. The Help pages also differ on how many notes a free account gets each month.

What should the ask in a LinkedIn cold message be?

One ask, answerable in a line. Permission to send a resource works on a first touch, a diagnostic question works when the problem is obvious from their role, and a call should be earned by a real trigger or by prior engagement with your content.

How many follow-ups should a LinkedIn message get?

Two after the first message is enough for most sellers, spaced across business days. Each one has to add something new. InMail is different: LinkedIn says it is initial outreach only and blocks a follow-up InMail until the recipient accepts and responds.

Why do my LinkedIn messages get ignored?

Usually the preview line. A blank invitation, an opening that fits any reader, a wall of text, a calendar link in a first message or a wrong company fact all get skipped in the notification list before your copy is read.

Is it better to send a connection request or an InMail?

Send the invitation first. It is free, a 1st-degree connection can be messaged without credits, and an InMail credit only comes back if the recipient accepts, declines or replies. Use InMail when the Connect button is missing or the invitation went unanswered.

Do LinkedIn cold message templates get accounts restricted?

The templates do not, the sending pattern does. LinkedIn restricts accounts that send many invitations quickly or leave many pending, and its policies forbid using the invitation feature to send promotional messages to people you do not know.

Can I edit or delete a LinkedIn message after sending it?

LinkedIn Help says you can edit or delete a sent message within 60 minutes. An edited message carries an Edited label, and deleting removes it for everyone in the conversation. After that hour, the message stays where it is.

Should I copy these LinkedIn templates word for word?

No. Copy the order of the ideas, then rewrite the reason line, the relevance line and the ask in your own words. A template your whole market received unchanged is one your prospects have already skipped twice.

Do read receipts tell me if my cold message was seen?

Not reliably. LinkedIn states read receipts do not appear to senders of InMail messages, and for message requests they appear only after the recipient accepts. The setting is also reciprocal, so a reader who turns it off is invisible to you.

Sources and reading
  1. LinkedIn Help, Personalize invitations to connect, for the 200 character note and the monthly allowance on free accounts, checked Sep 23, 2026.
  2. LinkedIn Help, Differences between InMail Messages and personalized invitations, for the second, higher note allowance and the 300 character Premium note, checked Sep 23, 2026.
  3. LinkedIn Help, InMail Messages FAQ, for the 200 character subject, the 2,000 character body, the 90 day credit expiry and credits returned on a response, checked Sep 23, 2026.
  4. Sales Navigator Help, Send an InMail message in Sales Navigator, for the 200 character subject, the 1,900 character body and the 150 character signature, checked Oct 1, 2026.
  5. LinkedIn Help, Unable to follow-up with InMail Messages, for InMail being initial outreach only and no follow-up until the recipient responds, checked Sep 23, 2026.
  6. LinkedIn Help, InMail message credits and renewal process, for credits returned when an InMail is accepted, declined or answered within 90 days, checked Oct 1, 2026.
  7. LinkedIn Help, Writing InMail Messages, Best Practices, for brevity, naming the profile content that prompted you, and giving a reason to reply, checked Sep 23, 2026.
  8. LinkedIn Help, Send, receive, and manage message requests, for coworkers and group members, the private decline, no notification to the sender and no attachments, checked Sep 23, 2026.
  9. LinkedIn Help, Invitation limit reached, for the one week restriction and withdrawals not removing it, checked Sep 23, 2026.
  10. LinkedIn Help, Types of restrictions for sending invitations, for the causes, the one month wait and the three week block on resending, checked Sep 23, 2026.
  11. LinkedIn Help, Delivery and typing indicators, for read receipts not appearing to InMail senders and only after a message request is accepted, checked Sep 23, 2026.
  12. LinkedIn Help, Edit or delete a sent message within a conversation, for the 60 minute window, the Edited label and removal for all participants, checked Sep 23, 2026.
  13. LinkedIn Sales Navigator Help, Understand InMail credits in Sales Navigator, for 50 credits a month, the 150 ceiling and the refund on a response within 90 days, checked Sep 23, 2026.
  14. LinkedIn, Professional Community Policies, for the rule against using the invitation feature to send promotional messages to people you do not know, checked Sep 23, 2026.
  15. Jeluvi entries this guide builds on: LinkedIn prospecting, how to connect on LinkedIn, what is InMail on LinkedIn, LinkedIn connection limit, sales cadence.
  16. All 16 messages and the skeleton were written for this page. No acceptance rates, reply rates, customer names or vendor benchmarks are quoted.
Take the sequence with you

The 10-day cadence, five templates, one email.

Five touches across email, LinkedIn and phone, five templates with placeholders marked, and the first-30-days checklist. One email.

Build a LinkedIn or outreach tool? Jeluvi is read by the people who use them. See how partners appear on Jeluvi.