LinkedIn connection request templates for networking events
Use these short templates to follow up with people you met at conferences and webinars. Reference one specific detail so the note reads like a real follow up.
Get startedShort answer
Send your connection request within a couple of days and mention one specific thing from the conversation. Keep the note short, under 200 characters, so it reads like a follow up rather than a pitch.
The 48 hour rule
The window after an event is short. After two days, the details of a conversation fade and you become another profile in someone's notifications. Send the request while the event is still part of their week.
LinkedIn does not publish exact invite limits, so ignore anyone who gives you a daily number. The safer rule is to send only to people you can write a specific note to. If you cannot remember one detail about the person, wait until you have a reason to connect.
The note is not the place to explain your whole job. It is a bridge back to the conversation. One detail, one sentence, one reason to accept.
- 1
Write down the detail
Right after the chat, note one thing the person said, a problem they mentioned or a question they asked. Put it in your notes app before you leave the room.
- 2
Use the event name
Name the conference, meetup or webinar exactly as it appeared. That removes the guesswork about which event you both attended.
- 3
Send while it is fresh
Submit the request within two days. The note can be one sentence when the memory is still clear.
Templates for in person events
The request moves an existing conversation onto LinkedIn. Use the same tone you used at the event. Formal language makes you sound like a stranger, which is the opposite of what you want.
Keep the note to one or two sentences. A long note reads like a pitch. A note that could have been sent to anyone reads like a bot. The middle ground is a single detail that proves you were listening.
Do not ask for a meeting in the connection note. That comes later, after they accept and reply. The request has one job: get the conversation back into a place where you can both continue it.
Talked about a problem
- Situation
- Hi [Name], good to meet you at [Event]. I kept thinking about what you said about [Problem]. I would like to stay connected and hear how it goes.
Met during a break
- Situation
- Hi [Name], we spoke during the break at [Event] about [Topic]. I enjoyed the conversation. Let's connect here.
Swapped cards
- Situation
- Hi [Name], we met at [Event] and swapped cards. I'm following up here so we have an easier way to stay in touch.
Saw their session
- Situation
- Hi [Name], I was in your session at [Event] on [Topic]. Your point about [Detail] stuck with me. I would like to connect.
Templates for webinars and virtual events
Virtual events leave fewer physical memories, so use the digital trail. A comment in the chat, a question to the speaker or a poll answer gives you something concrete to mention.
If you did not speak to the person, do not pretend you did. Say you were in the same session and name the part that caught your attention. That is enough of a reason to connect.
If the webinar had a Q&A, use the question they asked or the answer they gave. Those details are public to everyone in the session, so they feel natural to reference.
Too vague
- Hi, I saw you were at the webinar and wanted to connect.
- We both attended the same virtual event today. Let's network.
Specific and human
- Hi [Name], your question about [Topic] in the [Webinar] chat was the one I wanted to ask too. I would like to connect and hear what you thought of the answer.
- Hi [Name], I was in the [Webinar] session on [Topic] today. Your comment about [Detail] matched something I'm working through. Let's connect.
When you didn't actually speak to them
Sometimes you see a name in the attendee list or on a session panel and there was no conversation. Do not invent one. A small, honest note works better than a fake memory.
Use the shared event as context and point to one public detail: a comment, a question, a slide or a point from their profile. The note should show why you picked them out of the crowd.
Attendee lists are not permission to send the same note to everyone. If you cannot name a detail, skip the person. A smaller list with real reasons beats a big list with generic notes.
Paste this job
Hi [Name], I was in the [Session] at [Event] today. Your point about [Detail] was the part I wrote down. I work on [Your Area] and would like to follow what you do. Let's connect.
Avoiding the bot feel
People recognize a template fast. A cleverer template does not fix a generic note. Use a specific detail and a normal tone. Write the note the way you would text a colleague after the event.
Skip words you would not say out loud. 'Synergy', 'opportunity' and 'value add' make the note sound like a brochure. Use contractions. Read it once and cut anything that sounds like a press release.
Read the note out loud before you send it. If you stumble, cut a word. If it sounds like something you would say to a person standing next to you, it is ready.
Example
- You
Hi Sarah, good to meet you at the Northwind FinTech Summit. I kept thinking about the reporting issue you mentioned in the tax session. Did you find a workaround? Let's connect.
- Prospect
Hey, yes. I found a tool that handles most of it. Happy to connect and share what I learned.
One rule: if the note could be sent to ten other people without changing a word, it is not ready. Add one detail that only fits that person.
What to send after they accept
An accepted request opens a conversation. Continue the one you started at the event. A pitch in the first message wastes the context you just built.
Send a short message within a day or two, while the event is still fresh. Pick one direction: ask about the thing they mentioned, share a resource that connects to their point, or suggest a short call if they raised a problem you can help with. Do not do all three in one message.
If they do not reply, leave it. One follow-up a week later is fine if you have something new to add. A third message with no new reason is noise. When they ask to move to email, use this guide so the switch does not feel abrupt.
- Ask about the detail: 'You mentioned [Problem] at [Event]. Did [Solution] work out?'
- Send one useful link: 'You asked about [Topic]. This write-up covers the part we discussed.'
- Offer a next step: 'If it helps, I can walk you through how we handled [Problem] on a 15 minute call.'
Doing this with Kinlead
If you leave an event with a list of profile URLs, Kinlead can run the follow up without you pasting notes one by one. Import the CSV, put the leads in a lead group and point a campaign at that group.
Kinlead sends from your own LinkedIn account through Unipile. It sends at most one action every 5 minutes, inside the daily invite and message limits you set and inside a send window in the lead's time zone. Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead.
Replies from every campaign land in one inbox, classified by intent, with interested replies first. You get an email when someone replies. You can also read and edit queued campaign messages on the Actions page before they send.
- 1
Import the attendee list
Export the profile URLs you collected and import them as a CSV. Leads go into a lead group you can reuse.
- 2
Write the note rule
Set the campaign goal and tone so the AI note opens with the reason the person became a lead. Keep it under 200 characters.
- 3
Choose a send window
Use business hours or extended hours in the lead's time zone. The campaign will not send outside the window you pick.
- 4
Watch replies in one inbox
Replies from every campaign land in the unified inbox, sorted by intent. You get an email when someone replies.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? LinkedIn connection request templates for networking events.md