# LinkedIn connection requests after a local meetup
> Scripts and a short sequence for turning a conversation at a local business meetup into a LinkedIn connection while the person still remembers who you are.
- HTML: https://getkinlead.com/connection-request-templates-for-industry-events
- Markdown: https://getkinlead.com/connection-request-templates-for-industry-events.md

**Short answer:** Send the request the same day and put one specific detail from the conversation in the note. That detail tells them which person you were, and the request exists to get you recognized, not to sell.

## What a request after a meetup has to do

A connection request after a local meetup has one job: confirm which person you were. The person you met spoke to a room of strangers and probably came home with a handful of cards. If your note could have been sent by anyone in that room, it does nothing.

The detail does the work. A compliment is pleasant and forgettable. Something they said that only someone in the room could know is harder to drop: the second location they're opening, the hiring problem they described, the supplier that keeps missing deliveries. One line of that beats three lines of flattery.

Keep the note to two short lines and leave selling out of it. A request that pitches your service reads like every other salesperson who worked the room, and it throws away the one advantage you have, which is that you already spoke in person.

**Could have been sent by anyone**

- Hi, it was great meeting you at the event. Let's connect!
- Hi, I'm a marketing consultant and I think I could help your business grow. Would love to chat.

**Could only have come from you**

- Hi Priya, I was the one asking about the delivery vans at the Riverside meetup. Good luck with the second location. Let's connect.
- Hi Tom, we talked about the taproom licence at the chamber event. Curious how that goes. Sending a request.

## Write the detail down before you leave

The note you send is only as good as what you remember, and by the time you're home the specifics have blurred into a general impression of someone nice. Fix that at the event. Keep one note per person on your phone, or write on the back of their card if they gave you one.

You need three things for each person, and none of them take more than a few seconds to write down.

- Their name and where you met them, including the room or the stand if the event ran across a big venue.
- The one thing they said they're working on, in their words rather than yours.
- Anything you offered, a guide, an introduction, a name, so you don't forget it or promise it twice.

> A photo of the card plus those three lines is enough to write a note two hours later that reads like you were paying attention, because you were.

## Match the template to the conversation you had

A five minute chat by the coffee table and a forty minute conversation about hiring need different notes. Using a deep-dive line on someone you barely met reads as invented familiarity, and they will notice.

Pick the row that fits, then replace the brackets. Delete anything you can't honestly claim.

| | The conversation | What to write |
| --- | --- | --- |
| A long talk | Hi [Name], I'm still thinking about what you said about [topic] at [event]. Sending a request so we can keep the thread going. |
| A short chat | Hi [Name], we spoke briefly at [event] about [topic]. It would be good to connect. |
| They asked a question you couldn't answer | Hi [Name], I said I'd find out about [question] at [event]. I have the answer. Let's connect and I'll send it over. |
| You were introduced by someone | Hi [Name], [mutual contact] pointed you out at [event]. Good to meet you properly. Let's connect. |
| They mentioned a problem you know | Hi [Name], you mentioned [problem] at [event]. I went through something similar at Acme last year. Let's connect. |
| Cards swapped, nothing much said | Hi [Name], we swapped cards at [event] but didn't get past hello. What did you make of the panel? |

> If you genuinely can't remember a detail, say that in plain words. 'I lost track of the details but I remember the bit about the vans' beats a note that fakes specificity.

## Send it before you go to bed

The memory fades on their side, not yours. Send the request the same evening, or on the train home while you still remember what they said. A request that lands next week relies on them remembering a face from a crowded room.

Work through the list in one sitting. Ten minutes of typing beats a week of meaning to do it.

1. **Pull up your notes.** Open the phone note you made at the event and pick the people you actually want to stay in touch with. Skip anyone you have no detail for.
2. **Find the profile.** Search the name on LinkedIn and add the town or the company if the name is common. If you can't find them, open the event page and look through the people who posted or commented.
3. **Use the note field.** Add the note rather than sending a blank request, which throws away the only context you have. If your account isn't offering the note option, send the request anyway and put the detail in your first message after they accept.
4. **Fill in the template.** Two lines. Who you are and where you met, then the detail. No links, no attachments, no calendar invite.
5. **Send and log it.** Note the date and the detail you used. You'll want both when you decide whether to follow up.

```
Hi [first name], I was the one asking about [thing] at [event] on [day].
[One line about what they said they're working on].
Let's connect.

Before you send, check:
- Is there a detail only we two would know?
- Is it under two lines?
- Have you removed every word that sounds like a pitch?
```

## What to say when they accept

An accepted request is not a conversation. The next message decides whether it becomes one. Pick up the thread they gave you at the event and leave the pitch out of it for now.

If they mentioned a problem, offer the thing that helps with it and nothing else. A guide, an introduction, the name of a supplier. That offer is what turns a connection into a conversation you can build on later.

- **you:** Hi Priya, I was the one asking about the delivery vans at the Riverside meetup. Good luck with the second location. Let's connect.
- **them:** Ah yes, thanks for the request. The van question was a good one. We're still deciding.
- **you:** What swung it for you in the end? We went through the same thing at Acme last year and ended up leasing rather than buying.
- **them:** Leasing looks cheaper up front but the mileage cap worries me.
- **you:** Fair. I have a one page comparison a supplier sent me at the time. Happy to pass it on if it's useful.
- **them:** That would actually help, please send it over.

## When the request sits there

Some requests will sit unanswered. People accept in batches, often weeks later, and some never will. Leave a pending request alone for a couple of weeks, then withdraw the ones that clearly aren't moving. A long list of old pending requests makes your own list harder to read and tells you nothing.

If they accepted and then went quiet, one follow up in the same thread is fine. Make it useful rather than a nudge. Two follow ups starts to feel like pressure and rarely produces a reply.

The same applies when a good conversation leads to no reply at all. You can try once more later with a different detail, but if that one sits too, let it go. Keep the person on a list for the next event they might attend and pick it up there.

> The note's job is recognition. The pitch, the meeting and the proposal all come after they've replied to something you sent.

## Doing this with Kinlead

If you come back from a bigger event with a list of profile URLs, [import them as a CSV](/ai-sdr-csv-import-workflow) into a lead group in Kinlead and run the follow up from your own LinkedIn account. You set the campaign goal and tone, and Kinlead writes the messages and follow ups, including a connection note under 200 characters that opens with why that person became a lead.

For event follow up, set the campaign to hand the conversation to you at the first reply. You already know what you talked about, so the notification matters more than a drafted answer. Replies from every campaign land in one inbox sorted by intent, with interested ones first, and you get an email when someone replies.

- Import leads from a CSV of LinkedIn profile URLs and keep them in a lead group.
- Set daily invite and message limits and a send window per account.
- Read and edit queued messages on the Actions page before they send.

> Sending runs inside the limits and send window you set, in the lead's time zone, so a list from a Thursday event doesn't all go out at once.

## Related

- [See how Kinlead works](https://getkinlead.com/demo.md)
- [Connection note examples](https://getkinlead.com/ai-sdr-connection-note-examples.md)
- [CSV import workflow](https://getkinlead.com/ai-sdr-csv-import-workflow.md)
- [LinkedIn account safety](https://getkinlead.com/features/linkedin-account-safety.md)

## Common questions

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

The same day if you can, and the next morning at the latest. After that you're asking them to remember a face rather than a conversation.

**Should I mention my job title in the note?**

No. It's on your profile already. The note has room for the thing you talked about, and that's what makes them accept.

**What if I can't find their profile?**

Search the name with the town or company added. If that fails, open the event page on LinkedIn and look through the people who posted or commented, then match the face.

**Is it worth connecting with someone I only said hello to?**

Only if you have one real detail. Saying hello by the door is not a reason to connect. Wait until you have something to say.

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