LinkedIn Message After Meeting at an Event: Templates
Most event follow-ups fail before the recipient even opens them. The person gets back from the conference, sees fifteen connection requests from the same two days, and approves them all without reading a word. Your message, whenever it arrives, is competing with that fog.
The one thing that cuts through: a concrete, specific reference to the actual moment you shared. Not "great connecting at SaaStr." Something like "your point about churn attribution during the panel on Tuesday." That single line proves you were paying attention, and that proof is what earns a reply.
These templates are built for founders, AEs, and anyone doing genuine business development who meets real prospects in person and wants to continue the relationship on LinkedIn. Each one includes a connection-request note (under 300 characters) plus a short follow-up message for after they accept.
The Templates
Template 1: After a Quick Chat in the Hallway or at a Booth
Connection request note (under 300 characters):
Hi {first_name}, we had a quick chat near the {company} booth at {event_name} on {day}. You mentioned {specific_topic}. Would love to stay connected here.
Follow-up after acceptance:
{first_name}, glad we connected. The point you made about {specific_topic} stuck with me. I'm working through something similar at {my_company} and would value a 20-minute call if you're open to it. No agenda beyond the conversation.
Hallway conversations are easy to forget on both sides. Mirroring their own words back ("the point you made about...") is a memory trigger, not flattery. Use this when you had a genuine but brief exchange and want to build on it.
Template 2: After Attending Someone's Talk or Presentation
Connection request note:
Hi {first_name}, I attended your talk on {talk_topic} at {event_name}. Your take on {specific_point} changed how I'm thinking about {relevant_area}. Would be glad to connect.
Follow-up:
{first_name}, I've been thinking about what you said regarding {specific_point}. We're running into the same issue at {my_company} and solving it differently. Happy to share our approach if it's useful, no strings.
Speakers get a flood of generic "loved your talk" messages. Naming the specific point you disagreed with, found surprising, or are applying yourself shows you actually processed it. Send within 12-24 hours while the talk is still on their mind too.
Template 3: After a Longer Conversation at Dinner or a Side Event
Connection request note:
{first_name}, the dinner conversation at {event_name} was genuinely one of the better ones I had all week. Wanted to stay in touch properly. Let's connect here.
Follow-up:
{first_name}, picking up from Thursday dinner: you raised the question about {topic_discussed}. I've been sitting with it and think {brief_observation_or_question}. Worth a proper call?
A longer in-person conversation earns a warmer, more direct message. You do not need to rebuild the context, they remember you. Skip the preamble and get to the substance. This works especially well for relationship-first sales or partnership conversations.
Template 4: After Exchanging Cards (or Details) and Explicitly Agreeing to Talk
Connection request note:
{first_name}, good to meet you at {event_name}. You said to follow up about {topic}. Connecting here first, I'll send the {resource_or_intro} in a message.
Follow-up:
{first_name}, as promised: {resource_link_or_brief_description}. Still happy to do that call you mentioned. What does your calendar look like next week?
When someone explicitly asked you to follow up, your job is simple: do it, and do it on time. The worst thing you can do here is be vague. Deliver the thing you said you would, then make the ask. No warmup needed.
Template 5: After Meeting a Potential Partner or Collaborator (Not a Direct Sale)
Connection request note:
{first_name}, the conversation at {event_name} about {shared_interest_or_problem} made me think we might be useful to each other. Would like to stay connected.
Follow-up:
{first_name}, I've been looking at what {company} is doing in {space} and I think there could be a genuine overlap with what we're building at {my_company}. Would a 30-minute intro call make sense? Happy to share what I've been thinking ahead of time if useful.
Partnership outreach after an event needs to be honest about intent early. "We might be useful to each other" sets an equal tone and avoids the awkward reveal later. Good for founders doing BD, not just sales.
Template 6: When You Only Have Their Name (Minimal Context)
Connection request note:
{first_name}, we briefly crossed paths at {event_name}. I work on {my_focus_area} and noticed you do too. Worth staying connected in case our paths cross again.
Follow-up:
{first_name}, I realise our conversation was brief. I'm {role} at {my_company}, focused on {focus_area}. If {relevant_challenge} ever comes up for you, happy to be a useful contact.
This is the most honest template in the set, use it when you genuinely only caught someone's name on a badge or had a 90-second exchange. It does not pretend the relationship is deeper than it is. That honesty lands better than fabricated warmth.
Scenario-to-Template Mapping
| Situation | Template | Primary Goal |
|---|---|---|
| Quick hallway or booth chat | Template 1 | Continue the conversation |
| Attended their talk or panel | Template 2 | Establish credibility, open dialogue |
| Dinner or extended side event | Template 3 | Move to a direct follow-up call |
| Explicit agreement to connect | Template 4 | Deliver on the promise, book a call |
| Potential partner, no clear sale | Template 5 | Mutual exploration, no pressure |
| Minimal shared context | Template 6 | Honest low-key connection |
What Actually Works (and What Kills the Reply)
Do:
- Send within 48 hours, ideally the same evening
- Name one specific thing: a word they used, a question they asked, a slide they showed
- Keep the connection note under 200 characters if you can; the 300-character limit is a ceiling, not a target
- Match warmth to the actual depth of the conversation
- Have one clear, low-friction next step in the follow-up message
Do not:
- Open with "I hope this message finds you well" or any equivalent. It signals copy-paste
- Pitch in the connection request note. The note is for recognition, not selling
- Wait a week and then pretend you just "came across their profile"
- Reference the event without referencing anything specific about your interaction
- Send a wall of text explaining your company before you have asked a single question
- Follow up again the same day they accepted. Give it 24-48 hours
The mistake we keep seeing in outbound sequences built through Ampliflow is teams sending event-triggered messages with zero personalisation, just a merge tag for the event name. A single custom field for the specific detail they remember makes a visible difference in reply rates. It takes ten seconds per contact to add. Do it.
Using These Templates at Scale
If you are running event follow-up across a full sales team or doing it repeatedly across multiple events per quarter, manually sending and tracking each conversation becomes a real bottleneck fast.
Ampliflow's visual drag-and-drop workflow builder lets you set up a post-event sequence with conditional logic: connect, wait, check if accepted, send the follow-up if yes, route to a different path if no. The cloud execution via the Unipile API means the sequence runs without a browser extension or your laptop open overnight. Built-in randomised timing jitter means messages do not send in robotic batches. Real-time account safety scoring flags anything that looks off before LinkedIn does.
For a solo founder sending 20-30 post-event messages a month, doing it manually is fine. Once you are at 100+ contacts per event, a tool starts paying for itself. Ampliflow's founding price is $19/month (first 100 founding members only; public launch price is $39/month Starter). If price is the primary filter, Linked Helper at $15/month or Octopus CRM at $9.99/month are genuinely cheaper; they run locally via browser extension rather than cloud, which is a real architectural difference if you care about account safety, but they are cheaper.
For context on the alternatives, see Dripify Alternative: Cloud LinkedIn Automation From $19/mo or the pricing page.
Connecting Templates Into a Sequence
A single follow-up message rarely closes anything. Most real relationships built from events take two or three touches. A simple structure that works:
- Connection request note (one of the templates above)
- 24-48 hours after acceptance: the follow-up message
- 5-7 days later if no reply: a short, low-pressure check-in
For the third touch, see LinkedIn follow-up message after no response templates. That page has templates specifically for the "went quiet after showing interest" situation, which event contacts hit regularly.
If you are thinking about the connection request note itself in more depth, the connection request with or without a note templates page covers when to skip the note entirely and when it hurts more than it helps.
Variables Reference
Every template above uses merge tags. Here is what each one expects:
| Variable | What to fill in |
|---|---|
{first_name} |
Their first name |
{company} |
Their employer or company name |
{event_name} |
The event name (e.g., "SaaStr Annual 2026") |
{day} |
Day of the week or date you met |
{specific_topic} |
The actual thing you discussed |
{talk_topic} |
Title or subject of the talk |
{specific_point} |
One argument or claim from their presentation |
{topic_discussed} |
Subject of the extended conversation |
{resource_or_intro} |
What you promised to send |
{my_company} |
Your company name |
{my_focus_area} |
Your role or domain |
{focus_area} |
Shared professional area |
{relevant_challenge} |
Problem your work addresses |
{space} |
Industry or product category |
Fill these in before sending. Sending with an unfilled {variable} tag is one of the fastest ways to kill trust in a message. Ampliflow's A/B testing and funnel analytics make it straightforward to test variations on the personalisation fields and see which approach moves people further down the sequence.