A LinkedIn thank you message should hand the other person something, not just thank them for the click.

What a LinkedIn thank you message is

A LinkedIn thank you message is a short note you send after someone does something for you on the platform: accepts your invitation, meets you, introduces you to a contact, refers you, writes you a recommendation or endorses a skill.

It is the smallest unit of LinkedIn networking, and the one most people get wrong in the same way. They treat the note as the courtesy and stop there, so the reader receives a line of politeness and nothing else.

This page treats the note as a message with a job. Every version below names the exact act being thanked and hands the reader something: an answer, a resource, a summary, an introduction, or a public credit they can use.

Why a bare thank you wastes the moment

Acceptance is rare attention. For a few seconds, a person who did not know you has chosen to look at your name and decide it is acceptable in their network. That is the one moment when a message from you is expected rather than tolerated.

A note that reads "Thanks for connecting, great to be in your network" spends that attention and returns nothing. The reader has no question to answer, no fact to react to and no reason to open the thread again.

Professional gratitude is cheap to express and easy to discount, which is exactly why the message needs something else in it. The thanks costs you one clause; the rest of the note is what the reader actually weighs.

The second row is the more common failure. A thank you that turns into a pitch in the same message is the fastest way to sound salesy, because the gratitude is visibly instrumental.

What to hand over instead of thanks alone

Before writing, answer one question: what does the reader get? If the answer is nothing, keep the note to two lines and expect nothing back. These are the things that actually qualify.

Notice what is missing: a calendar link, a deck, a demo, a discount and a newsletter signup. Those are asks dressed as gifts, and readers separate the two instantly.

Templates, examples and what personalized actually means

Every template on this page is scaffolding, not a script. A template holds the shape of the message: the reason, the gift, the question. What makes it work is the personalized detail you drop into the placeholders before sending.

The examples below show the difference between a placeholder filled with a profile field and one filled with something you had to go and find.

• Personalized means unreusable. If the sentence would fit the next person on your list, it is not personalization, it is formatting.
• One specific detail beats three general ones. A single accurate reference carries the whole message and keeps it short.
• Professional does not mean formal. Plain sentences read as professional; company boilerplate and a signature block read as a mailing.
• Gratitude is the frame, not the content. Expressing gratitude takes one clause; the rest of the message has to earn the open on its own.
• Keep sending by hand. The moment templates go into a sending tool with merge tags, the personalized detail is the first thing dropped.

The four parts of a message that gets answered

The order matters. Reason first, because that is what the notification preview shows. The gift second, the question third, and no signature block with a phone number, a title and a tagline on a platform that already displays all three.

When to send each kind of thank you

Past about a week, the note needs an apology for the delay, which makes it longer and more awkward than it deserves to be. If you are that late, skip the thanks and send the useful thing on its own.

The thank you for connecting message, and five versions of it

This is the situation people search for most: the invitation is accepted, the thread is empty, and the next move belongs to you. The rule from how to connect on LinkedIn applies here too. Acceptance is agreement to be reachable, not agreement to a conversation.

Every thank you for connecting message below was written for this page. Replace the placeholders with facts you can point to, and delete any line you cannot make specific. These are examples of the shape, not sentences to send unchanged.

1. You sent a cold invitation with a reason

Hi {{firstName}},

Thanks for accepting. I asked because {{reason}}, and I did not want to leave it at a click.

Here is the thing I mentioned: {{link}}. It is the part most {{role}} teams say they had not thought about, and it is useful on its own.

If it is not relevant, no reply needed at all.

{{senderName}}

2. You met at an event

Hi {{firstName}},

Thanks for connecting after {{eventName}}. Your point about {{topic}} is the thing I kept repeating to people afterwards.

I went looking for what you described and found {{resource}}: {{link}}

Did {{openQuestion}} ever get resolved on your side?

{{senderName}}

3. A mutual connection is the reason

Hi {{firstName}},

Thanks for connecting. {{mutualName}} and I worked on {{context}}, and your name came up when we talked about {{topic}}.

No agenda here. If {{topic}} is live for you this quarter, {{resource}} is what we ended up using: {{link}}

{{senderName}}

4. You have been reading their posts

Hi {{firstName}},

Thanks for connecting. I have been reading your posts on {{topic}} for a while, and the one about {{specificPost}} changed how we handle {{process}} here.

One thing we found that you did not mention: {{observation}}.

Curious whether you have seen the same.

{{senderName}}

5. They invited you, and you have no reason yet

Hi {{firstName}},

Thanks for the invitation, accepted. I do not know your work yet, so a plain question: what are you spending most of {{period}} on?

I write about {{yourTopic}}, so if anything there is useful to you, say the word and I will send the version worth reading.

{{senderName}}

Thank you message after a meeting or call

After a meeting, the thank you is the smallest part of the message. What the other person needs is the record: what was agreed, who owns it, and when it happens. The gratitude belongs in a clause, not a paragraph.

Hi {{firstName}},

Thanks for the time today. Three things I took away: {{point1}}, {{point2}}, and that {{constraint}} is the real limit.

I said I would send {{promisedThing}}, so here it is: {{link}}

You were going to check {{theirAction}} with {{colleagueName}}. I will follow up on {{date}} unless I hear earlier.

{{senderName}}

If the meeting was a sales conversation, this note is the first step of the sequence rather than a separate courtesy. Our sales follow-up email templates cover what comes after it, including the point at which you stop.

Thanking someone for an introduction

An introduction spends someone else's credibility on you. Two notes are owed: one to the person who made it, and one to the person you were introduced to. Most people send the first and forget the report that closes it.

Hi {{introducerName}},

Thank you for the introduction to {{contactName}}. I know that costs you something, and I will not waste it.

I have written to them separately so this thread can stop here. I will tell you what comes of it either way, by {{date}}.

If there is anyone you are trying to reach in {{yourArea}}, tell me and I will look.

{{senderName}}

Thanking someone for a referral

A referral is an introduction with a recommendation attached. The person who made it has told someone else that you are worth their time, so the thank you should name what they said yes to and where it now stands.

Hi {{firstName}},

Thank you for putting my name forward for {{roleOrProject}} at {{companyName}}.

Where it stands: {{status}}. I will tell you the outcome when I have it, good or bad, so you are not left guessing what happened to your recommendation.

In return, I can {{specificOffer}}. Say the word and it is done.

{{senderName}}

Thanking someone for a LinkedIn recommendation

A recommendation is the most expensive thing anyone gives you on LinkedIn, because it is written by hand and signed with their name. LinkedIn Help notes that you can include a personalized message when you request one, and that there is no limit on how many you can receive.

That last detail matters for the thank you. Because there is no cap, an immediate recommendation written back can look like a trade. Answer the substance first, and write theirs later, when you have something real to say.

Hi {{firstName}},

Your recommendation is up on my profile, and thank you. The line about {{quotedLine}} is the one I would not have written about myself, and it is the part people have mentioned.

You remembered {{specificProject}} better than I did.

When you want one from me, ask. I would rather write it about something specific than hand back a favor.

{{senderName}}

Thanking someone for a skill endorsement

An endorsement costs one click. LinkedIn Help states that skills can be validated by 1st-degree connections, that you do not need to request an endorsement to receive one, and that endorsements contribute to the strength of your profile and to being discovered for opportunities.

So the thank you should be proportionate: one or two lines, no obligation created, and no automatic endorsement back. Endorsing a skill you have not seen the person use is the reason the feature is discounted by most readers. Our guide to LinkedIn skills covers which ones are worth listing.

Hi {{firstName}},

Thanks for the endorsement on {{skillName}}. Coming from someone who does it for a living, that one counts.

I have not endorsed anything back, on purpose: I would rather do it for {{theirSkill}} after {{sharedWork}}, where I actually watched you do it.

{{senderName}}

Thanking an interviewer on LinkedIn

LinkedIn is the second channel here, not the first. Send the real thank you by email, where a recruiting team can file it, and use LinkedIn only if that is where the conversation already lives or you have no address.

Hi {{firstName}},

Thank you for the time today on {{roleTitle}}. The part about {{challenge}} is the reason this role is interesting to me rather than just available.

One thing I did not explain well: {{clarification}}.

Happy to wait for your process. Thanks again for a straight conversation.

{{senderName}}

How to reply to a thank you for connecting message

The other side of this page: someone thanks you, and now you decide whether to spend a reply. Three cases cover almost everything you will receive.

• A real note with a real reason. Answer within a day, add one line of substance, and ask something you genuinely want to know.
• A bare thank you. Answer with a question if the person looks worth knowing, and ignore it otherwise. Neither choice is rude.
• An obvious automation. No reply is needed. If it keeps arriving on a schedule, the report and disconnect options are there for a reason.

Hi {{firstName}},

Good to be connected. Since you work on {{theirArea}}: how are you handling {{specificProblem}} at the moment?

Asking because we are mid-decision on it here, and I would rather hear from someone doing it than read another vendor page.

{{senderName}}

What LinkedIn's own rules allow

Before any of this scales, check what the platform actually permits. These points come from LinkedIn Help and the LinkedIn User Agreement, not from outreach vendors.

If you are weighing a paid seat to reach people outside your network, what is InMail on LinkedIn explains what the credits buy and what they do not.

Automated thank you messages, and why they read as spam

Every outreach tool offers an automatic message on acceptance, because it is the easiest feature to build. Two separate problems come with switching it on.

The rule problem

The LinkedIn User Agreement prohibits using bots or other unauthorized automated methods to access the services, add or download contacts, send or redirect messages, or otherwise drive inauthentic engagement. It separately prohibits software, scripts, browser plugins and add-ons used to scrape or copy the services.

LinkedIn Help is explicit about the consequence: members using prohibited tools risk having their accounts restricted or shut down, and those tools may stop working without notice. Our pages on LinkedIn automation and a restricted LinkedIn account cover what recovery looks like.

The reading problem

Even if nothing is enforced, the message fails on its own terms. Recipients who work in sales or recruiting see several of these a week and recognize the shape immediately.

• The interval is identical. It arrives minutes after acceptance, every time, which no human sender manages.
• The specifics are profile fields. First name, company and title are the only personal details, because those are the merge tags available.
• The compliment is unfalsifiable. "Impressive background" and "great to see your work" fit anyone with a profile.
• The link is the point. A resource appears in message one, before a single question has been asked.
• The follow-up ignores the reply. The second message arrives on schedule even when the first was answered, which is the clearest tell of all.

Once a reader classifies your note as automated, they stop reading the category, not just your message. That cost lands on everyone who writes these by hand afterwards.

How to write a LinkedIn thank you message

1. Name the exact thing you are thanking them for

   Write the specific act: the invitation you sent and why, the meeting last Tuesday, the introduction to a named person, the skill they endorsed.

2. Decide what you are giving before you write a line

   A resource, an answer, a useful observation, an introduction of your own, or a public thank you. If you have nothing, keep the note to two lines and send nothing else.

3. Write two to four short sentences

   Open with the reason, give the thing, then stop. No company boilerplate, no attached deck, no calendar link in the first message.

4. Ask one question they can answer in a line

   Make it easy and optional. A question that needs a meeting to answer is a pitch, and the reader will read it that way.

5. Send it by hand within a day or two

   Type it in the thread yourself. Automated thank you messages breach the LinkedIn User Agreement and read as spam even when they do not.

6. Log the reply, and stop if there is none

   One note, one polite follow-up later if it fits, then leave the connection alone. Silence after a thank you is an answer.

Which message fits which situation

If the goal behind all this is pipeline rather than a network, the note is one step inside a wider process, which LinkedIn prospecting covers end to end.

What to track, and what not to

Mistakes that make a thank you worse than silence

• Thanking and pitching in the same message, so the gratitude is visibly a setup.
• Sending the identical note to everyone, which is the spam pattern whether a tool or a person types it.
• Attaching a calendar link to a first message, before anyone has agreed there is something to discuss.
• Claiming a shared event, group or conversation that did not happen, which is checkable in one reply.
• Writing five paragraphs of appreciation, which reads as a request for something in return.
• Promising to report back on an introduction or referral and then going quiet.
• Endorsing a skill back automatically, which devalues both endorsements at once.
• Following up three times on a note the reader never asked for. Our outreach tips cover the pacing.

The message to copy

The version below is the default for the most common case: your invitation was accepted, you had a real reason for sending it, and you have one thing worth handing over. It was written for this page.

Hi {{firstName}},

Thanks for connecting. I sent the invitation because of {{reason}}, and I did not want to leave it at a click.

{{usefulThing}} is the piece most {{role}} teams tell me they have not seen, so it is yours whether or not we ever speak: {{link}}

One question, if you have a minute: {{question}}

{{senderName}}

Frequently asked questions