# LinkedIn connection requests after an event or webinar
> Learn how to write LinkedIn connection notes after an event. Get templates for attendees, speakers, and hosts to move from a session to a real conversation.
- HTML: https://getkinlead.com/connection-request-after-event-or-webinar
- Markdown: https://getkinlead.com/connection-request-after-event-or-webinar.md

**Short answer:** To send a LinkedIn connection request after an event, reference a specific moment from the session to prove you were actually there. Generic notes get ignored. Your goal is to move from a shared experience to a 1:1 conversation without pitching your product in the first message.

## The rule for post-event notes

Most post-event requests say the same thing. Great session, thanks for sharing, would love to connect. The person reading it has no way to tell whether you watched for ten minutes or copied the event hashtag, so most of these requests sit unanswered.

A note that works does one job: it proves you were in the room. Name the talk, the panel answer, the slide, the number the speaker quoted, or the argument someone made in the chat. One specific detail beats three lines of praise.

Keep the request about the conversation. The invite opens the door, and the message after they accept is where the real exchange starts. A pitch inside the note reads like a mail merge and gets treated like one.

**Generic and ignorable**

- Great webinar today. Would love to connect and share synergies.
- Thanks for the event. I'm looking to expand my network in this space.
- Hi, I saw you attended [event]. I help companies like yours cut costs by 30%.

**Specific and human**

- Your answer about sales playbooks during the Q&A stuck with me. I'm rewriting ours this week. Let's connect.
- The point about pricing pressure in the panel matched what I'm seeing with mid-market buyers. I'd like to follow your work.
- You asked the question about attribution in the chat. I've been chewing on the same problem. Happy to compare notes.

## Templates for attendees

Other attendees are the easiest group to reach and the easiest to ignore. They are in the same information-gathering mode you are, and most of them are not being pitched by anyone else that day.

If you saw their name in the chat, a breakout room or a poll, use that. It is the closest thing to a shared moment you will get with a stranger.

| | Scenario | Template |
| --- | --- | --- |
| Saw them in the chat | I saw your comment about [topic] in the chat. The part about [reason] is what I keep running into. Let's connect. |
| Shared a breakout room | We were in the same breakout room on [topic]. You made a point about [detail] that I want to steal for my team. Let's connect. |
| Asked a question in the Q&A | You asked about [topic] in the Q&A. I've been stuck on the same thing. Happy to compare notes. |
| General attendee, no interaction | I was in [event name] today and I'm connecting with a few people who sat through the [topic] track. What did you make of it? |

## Templates for speakers and hosts

Speakers get more praise than they can read. A note that says great talk lands in the same pile as the other fifty. A note that says what you are doing differently because of minute 22 gets a reply.

Hosts and moderators are worth connecting with too. They usually know the speaker, the sponsor and half the room, and they remember who asked a useful question.

| | Scenario | Template |
| --- | --- | --- |
| Specific insight | Your point about [topic] changed how I'm thinking about [process]. I'm trying it with my team this week. Let's connect. |
| Asked a question | I asked about [topic] during the session. Your answer about [detail] was the clearest part of the hour. Let's connect. |
| Host or moderator | You kept that panel on track when it could have gone sideways. I'd like to follow what you run next. |
| Podcast or recorded session | I listened to your episode on [podcast] while walking the dog. The bit about [detail] made me rethink [process]. Let's connect. |

## What to send after they accept

The acceptance is not the win. The win is a reply that turns into a conversation. Most people ruin it by sending a calendar link in the first message.

Wait a day, then pick up the thread from the session. Ask what they are doing about the problem the speaker described. If they answer with a real constraint, offer something small and specific.

1. **Wait a day.** Send the first message the day after they accept. Same-day follow-ups read like a sequence, not a conversation.
2. **Ask about the problem.** Reference the session and ask what they are doing about the problem the speaker described. One question, not three.
3. **Offer one small thing.** If they name a constraint, send a template, a checklist or a short write-up that addresses it. No deck, no pricing page.
4. **Let them suggest the call.** When they ask how you solved it for someone else, offer a short call. If they don't ask, keep the thread going with another useful answer.

- **you:** Thanks for connecting. Are you planning to try the ramp framework from the session, or does it feel too heavy for your team right now?
- **them:** I want to, but we're still tracking onboarding in spreadsheets, so a migration feels like a lot.
- **you:** That's the usual blocker. I have a one-page version that works without moving anything. Want me to send it?
- **them:** Yeah, that would help.

## Timing, and what to do when nobody accepts

Send the request within a day or two. Event memory fades fast, and the note only works if the detail is still fresh for both of you. A request sent three weeks later needs a different opener, because the session is no longer the shared context.

If a request sits pending, do not send another. Withdraw it after a couple of weeks and try a different angle later, or engage with their posts first so your name is familiar before the next invite.

> One request per person per event. If the first one sits unanswered, withdraw it after a couple of weeks and warm the contact up by commenting on their posts before you try again.

## Keep notes while you watch so the message writes itself

The reason most post-event notes sound generic is that people write them from memory two days later. Take notes during the session and the message takes a minute.

Keep one line per person: their name, where you saw them, and the exact thing they said or the speaker said that you can quote. That is enough to write a note that could not have been sent to anyone else.

```
Event:
Date:
Person and role:
Where I saw them (chat, breakout, Q&A, poll):
One thing they said or asked:
One thing the speaker said that connects:
Follow-up idea:
```

## Doing this with Kinlead

If you can't attend every event in your space, the [Steal Customers](/features/steal-customers) agent watches competitor company pages and optional founder or employee profiles, reads the comments on their recent posts, and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what the person commented, which is the same detail you would have written down during a session.

Kinlead scores each lead from 0 to 100 against the customer profile you describe and drops the ones below the fit line. Connection notes can be written by AI under 200 characters and open with why that person became a lead. Outreach runs from your own LinkedIn account through Unipile at one action every 5 minutes, inside the daily limits and send window you set.

## Related

- [LinkedIn connection request templates](https://getkinlead.com/linkedin-connection-request-message-templates.md)
- [Steal Customers](https://getkinlead.com/features/steal-customers.md)
- [LinkedIn follow-up templates](https://getkinlead.com/linkedin-follow-up-no-reply-templates.md)

## Common questions

**Should I pitch my product in the connection request?**

No. Pitching in the request feels like spam and lowers your acceptance rate. Focus on the shared event experience first, then have the real conversation after they accept.

**How soon after the event should I send the invite?**

Send it within 24 to 48 hours. Any later and the specific details of the session will be forgotten by both of you.

**What if the speaker doesn't accept my request?**

Some speakers get a high volume of requests. If they don't accept, engage with their next post with a thoughtful comment before requesting again.

**Can I connect with someone I only saw in the chat?**

Yes, if you can quote what they said. A comment in the chat is a real interaction, and referencing it is more specific than most notes the speaker or attendee will receive that day.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
