# Connection requests for people who attended your webinar
> Stop sending generic thank you notes to webinar attendees. Use Q&A answers and poll data to write LinkedIn requests that actually get accepted.
- HTML: https://getkinlead.com/connection-requests-for-webinar-attendees
- Markdown: https://getkinlead.com/connection-requests-for-webinar-attendees.md

**Short answer:** The best LinkedIn connection requests for webinar attendees skip the generic thank you note. Reference a specific question they asked during Q&A, a poll answer they gave, or a moment they engaged with the content, so the note proves you were paying attention to them and not to the attendee list.

## Why generic requests fail

Most people send a request that says thanks for attending. The attendee reads it, recognises the template, and moves on. It gives them no reason to accept other than politeness, and politeness is a weak reason to open your network to a stranger.

A webinar already put you in front of them for an hour. That is more context than most cold outreach ever gets. Spending it on a thank you note is the actual mistake, not the send itself.

The fix is to reference something only that person would recognise. A question they typed into the Q&A box, an answer they gave in a poll, a comment in the chat. That turns a broadcast into a one to one conversation, and it tells them you were paying attention rather than exporting a list.

**Generic**

- Thanks for joining my webinar on B2B sales. Let's connect!
- Great to have you at the session today. I'd love to add you to my network.

**Specific**

- I noticed you asked about handling price objections during the Q&A. I have a follow up resource on that if you're interested. Let's connect.
- Your point in the chat about API latency was spot on. I'm curious how you're solving that at Acme. Let's connect.

## Mining your webinar data for hooks

You can't write a specific note without specific data. Most webinar platforms give you a transcript, a chat log, a Q&A export and poll results. Pull all four before you write anything.

The attendee list is the least useful file you have. It tells you who showed up. The Q&A export tells you what they were worried about at 11am on a Tuesday, which is what you actually want.

Build a sheet with one row per person and columns for the question they asked, the poll answer they gave, and the company they work at. If a row is empty on all three, they go in a separate pile and get a different message. Don't invent a hook to fill the gap.

1. **Export the data.** Download the full attendee list, the Q&A transcript, the chat log and the poll results into one spreadsheet.
2. **Mark the engaged.** Highlight every person who asked a question, answered a poll or commented in the chat. These are your first wave.
3. **Name the topic.** Write the specific subject they cared about next to their name, such as lead scoring, API integrations or pricing.
4. **Split the list.** Put people with a real hook in one group. Everyone else goes in a second group that gets a different, softer message.

## Templates for different attendee types

Different attendees carry different intent. Someone who asked three questions is further along than someone who watched quietly and left before the end. The note should match the signal you actually have, not the signal you wish you had.

Below are three common types and the hook that fits each. Swap the brackets for real details before sending. A template with the brackets still in it is worse than no note at all.

| | Attendee type | The hook | Template |
| --- | --- | --- | --- |
| The questioner | Their specific Q&A question | Hi [Name], your question about [topic] during the webinar stuck with me. I have a short write up on that if you want it. Let's connect. |
| The poll voter | Their poll answer | Hi [Name], you voted that [pain point] is your biggest hurdle in the poll. I'm talking to a few people in the same spot this month. Let's connect. |
| The quiet attendee | The segment they stayed for | Hi [Name], thanks for joining the [topic] session. Curious whether the part on [specific section] matches how you handle it at [company]. |

## The timing of the request

Send too early and you land while they're still closing tabs. Send too late and the session has faded into the pile of things they meant to follow up on.

The practical window is the day after. They've had the recording email, they've skimmed it or saved it, and the session is still recent enough to remember. Same day feels rushed because you're competing with the live session itself.

One rule matters more than the exact hour: don't send the invite before the recording email goes out. If your note references a session they haven't been reminded of yet, it reads as random rather than attentive.

- **you:** Hi Sarah, your question about scaling SDR teams during the Q&A was the one I kept thinking about after we wrapped. I found a write up on that exact transition. Let's connect.
- **them:** Thanks for the webinar. I'd like to see that write up.
- **you:** Here it is. It covers how Northwind went from 2 to 10 reps in six months and what broke first. Happy to talk through the messy parts if that's useful.
- **them:** Useful, thanks. The part about ramp time is what we're stuck on.

> Send the request the day after the session, once the recording email has landed. Same day feels rushed, and a week later you're a stranger again.

## When there's no question to reference

Most attendees never type anything. On a session with a few hundred people, the chat and Q&A might cover twenty of them. The rest need a different approach, and pretending otherwise produces notes that sound invented.

For quiet attendees, use the segment they stayed for. Most platforms show join and leave times. If someone dropped off before your demo section, don't reference the demo. Reference the part they actually sat through.

If you have nothing at all, send a blank request or wait until they engage with something else you publish. A blank request from a name they recognise from a webinar does better than a fabricated compliment they can tell you didn't mean.

- A question typed into the Q&A box
- A poll answer that names a specific problem
- A chat comment with an opinion in it, not just a greeting
- A resource they asked for in the chat
- A follow up question they asked after the session ended

## What to do when they accept

Acceptance is not the finish line. The note got you in the door, and the conversation has to continue from the same thread or it dies in a week.

Send one message within a day of acceptance that delivers whatever you promised in the note. If you said you'd send a resource, send it. If you asked a question, don't repeat it word for word.

Keep the first message short and end with something easy to answer. A question with a yes or no answer gets a reply. A paragraph about your product gets ignored, and it wastes the goodwill the note earned you.

```
Hi [Name], here's the [resource] I mentioned. Given what you asked about [topic], I'd start with the section on [specific part]. Want me to send the follow up piece, or would a 15 minute call be easier?
```

## Doing this with Kinlead

If the attendee list is large, writing notes by hand stops being realistic around the second hundred. [Kinlead](/features/ai-linkedin-outreach) can send the invitations and handle the first replies at a human pace.

Import your attendee list as a CSV of LinkedIn profile URLs into a lead group, then point a campaign at that group. Connection notes are AI written, under 200 characters, and open with why that person became a lead.

Kinlead connects through Unipile and sends at most one action every 5 minutes per LinkedIn account, inside daily limits and a send window you set in the lead's time zone. Replies from every campaign land in one inbox, and you choose whether the AI answers, books a meeting with your link, or hands the conversation to you at the first reply.

1. **Import attendees.** Load the CSV of LinkedIn profile URLs into a lead group so every campaign can point at it.
2. **Set the strategy.** Create a campaign with the goal and tone for the follow up, and add your own sales playbook if you have one.
3. **Review the queue.** Read and edit queued messages on the Actions page before they send, and pause the campaign if the wording drifts.
4. **Handle replies.** Work from the unified inbox, where interested replies are sorted to the top and you get an email when someone responds.

## Related

- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Webinar recruitment templates](https://getkinlead.com/ai-sdr-templates-for-webinar-recruitment.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**Should I send the request without a note?**

For webinar attendees, a note proves you are the person they just spent an hour watching. Without it you're another profile in their queue. If you have no specific hook, a blank request still beats a note that sounds copied.

**What if they don't accept the request but replied in the chat?**

If they were active in the chat and ignore the invite, follow up by email if you have their address. Mention the specific chat comment so they can place you. Don't send a second invite.

**How many attendees can I add per day?**

LinkedIn does not publish exact limits. Set a daily limit you can sustain in your settings, watch your pending invitation pool so it doesn't grow beyond what you can manage, and withdraw stale invites rather than stacking more on top.

**What if the webinar had no Q&A and no chat?**

Use the segment they stayed for and the company they work at. If neither gives you anything specific, send a blank request and save the personalised note for the first message after they accept.

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