LinkedIn message templates for sales conversations, follow-ups and replies

Choose a LinkedIn sales message from the relationship you actually have: an invitation after a real interaction, a first message to an accepted connection, a useful follow-up or a reply to an explicit question. Changing the person's name does not fix a message written for the wrong state.

The examples below are original, hypothetical drafts. Bracketed fields are instructions to replace with verified details, not text to send. They are not tested results or promises of replies. If you cannot truthfully fill a field, remove the claim or choose another message.

This page covers the sales conversation from initial context to a reply or stop. Use the separate recruiting templates for candidate conversations, and the after-acceptance guide for greetings and first exchanges.

Match the message to an available channel

LinkedIn says connections can message each other directly. Following someone does not create that relationship. A pending invitation is also different from an accepted connection.

Its invitation guidance describes a short note explaining who you are and why you want to connect. Account allowances and note lengths apply; check the composer and current help rather than treating a template as permission to exceed them. LinkedIn also advises connecting with people you know and trust.

If you lack a direct-message route, do not paste a sales sequence into repeated invitations. Consider whether following the person's work or contributing something relevant to the public discussion is the appropriate next action. InMail has a separate channel decision.

Invitations after a real interaction

Use these only when the exchange happened. Mentioning a large conference you both attended does not establish that you met.

After a conversation at an event

Hi [first name], we spoke at [event] about [specific topic]. I'd like to stay in touch here. I'll send the [resource] I mentioned once we're connected.

Only promise a resource you possess and can share. If you already have a suitable channel for sending it, you do not need to make connection acceptance a condition.

After a substantive public exchange

Hi [first name], we exchanged comments on [person's] post about [topic]. Your question about [detail] is relevant to my work on [area]. Open to staying connected?

Check the attribution and exact topic. Avoid “we both know” unless the relationship is real and relevant. A mutual name visible on LinkedIn is not an endorsed introduction.

First messages to an accepted connection

Acceptance opens the channel. It does not establish purchase intent. Fulfill the invitation's promise before introducing a new request.

Deliver a resource you offered

Thanks for connecting, [first name]. Here is the [resource] I mentioned: [link]. The section on [detail] addresses the question we discussed. No need to book anything to use it.

Use that last sentence only if access really has no booking requirement. Disclose a signup requirement instead of hiding it behind “free resource.”

Ask one relevant discovery question

Hi [first name], your post described [specific process problem]. I work on [relevant area]. Is [narrow issue] something your team is handling now, or was the post about an earlier project?

This draft leaves room for your inference to be wrong. Do not substitute a generic title-based assumption such as “as a founder, you must be struggling with sales.” The free first-message builder drafts from the situation and facts you enter, with editable output and a copy control. It does not verify those facts or send to LinkedIn.

Follow up only when you can add something

Do not choose a calendar gap and assume it supplies a reason to write. Read the thread, confirm the person has not replied and decide whether another message is useful. Silence is not an agreement to a meeting.

Add a relevant detail

One detail to add to the [resource] I sent: [specific finding or limitation]. It matters when [condition]. If that is not the situation you meant, I can leave it there.

Ask whether to close the conversation

I'll close the loop on [topic], [first name]. If it becomes relevant later, you can reply here. I won't keep following up on this thread.

Honor the statement. Do not put a further “last message” behind it. Avoid guilt, artificial urgency and unsupported claims about how much money the recipient is losing. The follow-up guide covers timing and reply-aware sequencing in more depth.

The free follow-up builder uses the response state you select and fixed rules. An unanswered message sent today or an agreed future contact date produces Wait; choosing a decline produces Stop. It does not interpret the pasted conversation or verify your facts.

Respond to the words they sent

A reply changes the task from scheduled outreach to conversation. A polite acknowledgment, a question and a decline need different responses.

They ask for details

Yes. For [their stated use case], the relevant part is [specific capability]. It does [verified behavior], and it does not cover [material limit]. Would a short written example help, or do you already have enough to assess it?

They suggest a later date

Understood. Would you like me to check back in [period they named], or would you prefer to restart the conversation yourself?

Record the answer rather than converting “later” into your own recurring reminder sequence.

They agree to a next step

Confirming [agreed date] at [time and timezone] for [agreed action]. I'll provide [promised item] beforehand. Please reply here if I've recorded anything incorrectly.

Use this only after agreement on the action and timing. A tentative “maybe next month” is not a booking. If they instead identify another owner, use the referral-request guide without assuming that person has endorsed an introduction.

They decline or ask you to stop

Understood, [first name]. I'll stop contacting you about [topic]. Thanks for letting me know.

Remove them from the relevant follow-up process and preserve the instruction where the team can act on it. Do not argue with an opt-out or ask someone to justify it.

Put conditions around the templates

Before sending, verify the profile, relationship state, source detail, link and any promise. Remove unfilled placeholders. Check for an existing conversation or another teammate already handling it. If a message contains a customer result, quote or benchmark, you need actual evidence and permission to use it; none is supplied by these drafts.

In OutreachGenie, Send message and Message sequence use first-degree connections. Message sequence groups an initial message and timed follow-ups and stops that prospect's sequence on a tracked or detected reply. A standalone Check reply is not a manual approval gate; it does not by itself create a replied/no-reply branch. Review the sequence plan and supported settings before launch.

LinkedIn's prohibition on third-party scraping and automation still applies. Good wording, low volume and browser execution do not remove restriction risk. Use the templates to make a truthful, appropriate exchange easier to write, and let the recipient's actual response determine the next step.