AI SDR templates for following up after events
Learn how to write LinkedIn follow-up messages after networking events with AI SDR templates, a clear sales playbook and a sequence that sounds human.
Get startedShort answer
To follow up after a networking event on LinkedIn, reference a specific topic you discussed, a session you both attended or a comment you heard at the booth. Then write from a sales playbook that names the event, the shared problem and the outcome you want, so the message connects the conversation to your offer without sounding like a blast.
The mistake in most event follow-ups
Most people send the same message to everyone they met at a conference. They mention the event, say it was great to meet, then ask for a call. The prospect cannot tell if the sender remembers them or copied the note from a template. That is the moment the follow-up dies.
A follow-up after an event is a memory test. You have to prove you were in the same conversation. Being in the same building is not enough. The first two lines should name the session, the booth argument or the problem they described. If the person cannot place you, the rest of the message does not matter.
You do not need a long recap. One specific detail is enough. The detail also gives the AI something real to work with when you write at scale. Without it, the AI fills the gap with phrases like great to meet you and looking forward to staying in touch.
Generic follow-up
- It was great meeting you at the conference. I'd love to connect and tell you about our platform.
- Enjoyed the event last week. Let's jump on a call to see how we can work together.
Specific follow-up
- I enjoyed our chat about hybrid work at the Marketing Summit. Your point about team burnout stayed with me.
- That debate over AI pricing at the booth was the best part of my day. I thought more about your seat-based model point.
If the prospect cannot place the conversation within two sentences, they will read the next line as a pitch and archive it.
Build a sales playbook before you prompt the AI
An AI will write exactly what you ask for. If you ask for a follow-up, you get a polite paragraph with no memory hook and no reason to reply. The fix is a sales playbook, which is your own script for how the conversation should go.
A useful playbook for event follow-up has five parts: the event, the memory hook, the shared problem, the outcome you want and the tone. You can keep it in a doc or paste it into the campaign. The AI needs the same context a new SDR would need on their first day.
If the playbook is vague, the AI fills the gaps with marketing language. Review two sample notes before you load a list. Edit the playbook until the notes sound like something you would send to a person you met.
- 1
Name the event and the room
Write down the event name, the session or booth where you met and anything the audience was talking about that day. SaaS Summit, pricing panel, everyone arguing about seat-based contracts is enough.
- 2
Write the memory hook
Add one line about the comment, question or story you remember. Do not invent it. If you only remember the topic, say that and keep the message honest.
- 3
Name the shared problem
State the problem in the prospect's words, such as forecasting renewals without a CRM or hiring a first SDR without a playbook. This keeps the message on their work, not your product.
- 4
Set the goal and tone
Choose one outcome: a 15-minute call, permission to send a resource or a simple reply. Then choose a tone, like peer to peer, direct or formal. Do not ask for a meeting and a download in the same note.
Paste this job
You are writing a LinkedIn follow-up for [name] after [event]. We met at [session or booth]. I remember [specific detail]. Their likely problem is [problem]. Write a connection note under 200 characters that opens with the specific detail, names the problem in their words and ends with one small question. Tone: [peer, direct, warm]. Do not use the words solution, platform or synergy. Do not ask for a call in the first note.
Templates for different event scenarios
Your message should change with the length and depth of the conversation. A 30-second booth chat and a 20-minute coffee talk are not the same lead. The template should match what you actually have.
Use the table as a starting point, then replace the brackets with a real detail. If you cannot fill a bracket, send a shorter note and treat it as a list touch. Do not borrow intimacy you did not earn.
If you promised a resource in the conversation, send it in the first message. Do not make people ask for it twice. If you promised an intro, make the intro before you pitch.
Do not use the deep conversation template for a badge scan. It reads as fake familiarity. Match the template to the memory you actually have. A short honest note beats a long invented one.
Short booth chat
- Scenario
- A comment or question
- What you have
- Caught your question about [topic] at the [event] booth. I have a thought on that. Want me to send it over?
Shared keynote
- Scenario
- A session you both saw
- What you have
- That session on [topic] at [event] changed my mind about [idea]. Are you planning to try [specific tactic] on your team?
Deep conversation
- Scenario
- A problem they described
- What you have
- You described [problem] over coffee at [event]. I found a short example of how a team like yours handled it. Should I send the link?
Dinner or happy hour
- Scenario
- A personal detail and a work topic
- What you have
- Good to meet you at the [event] dinner. You mentioned [personal detail] and [work problem]. I have one idea on the work side. Open to a quick note?
Run the follow-up like a short sequence
One message is rarely enough. People return from an event to a full inbox, a backlog of Slack threads and a week of catch-up meetings. Your first note can get buried even when the person meant to reply.
Keep the sequence short and make each message do a different job. The first note earns the connection. The second gives something useful. The third asks for a small next step. The fourth closes the loop so you are not left guessing.
The gap between messages matters. Wait a few days after the connection note, then send the resource. If they reply, answer like a person. If they do not, send one nudge, then stop. A daily reminder reads as noise, and it will get you ignored.
Example
- You
Hi Sarah, I enjoyed our chat about Q4 planning at the SaaS Summit. Your take on budget cuts was sharp. I'd like to stay in touch.
- Prospect
Thanks, it was a busy event. Happy to connect.
- You
Glad we connected. I mentioned a short example of how a team handled Q4 budget cuts during our talk. Here it is: [link]. Hope it helps with your planning.
- You
Sarah, since you are working through those cuts, would it make sense to spend 15 minutes on how Acme automated the review? I have a few slots open Thursday.
The second message should give something away before the third message asks for time.
Handle the awkward event follow-ups
Not every conversation ends with a clear problem and a warm goodbye. Sometimes you remember the face but not the name of the session. Sometimes the person was polite and vanished. Handle those cases directly instead of pretending you have a deep relationship.
When you cannot remember the person, ask a question that gives them an easy out. I remember we spoke about hiring, was that for your team or a client? is better than pretending you remember their name.
A clean exit is better than a forced sequence. If someone says they are not interested, thank them and remove them. Your next event follow-up will land better when your list is not full of people who asked you to stop.
- You barely remember them: name the event and the general topic. Ask one question about what they took away. Do not fake a detail.
- They said not now: ask when to check back and put the date in your notes. A short note in six weeks beats five messages this week.
- They referred you to a colleague: ask for a warm intro and mention the original conversation. Do not pitch the colleague from scratch.
- They only scanned your badge: send one short note with the resource you promised. If they do not reply, let it go.
Doing this with Kinlead
If your event list is a CSV of LinkedIn profile URLs, import it into a lead group in Kinlead. You can point a campaign at that group and set the goal, tone and sales playbook for the event.
Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead. Messages and follow-ups are written from the campaign goal, tone and your playbook. Queued messages can be read and edited on the Actions page before they send, and any campaign can be paused.
Kinlead sends from your own LinkedIn account through Unipile and never stores your LinkedIn password. Each account 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. Replies from every campaign land in one inbox, classified by intent, with interested replies first, and you get an email when someone replies. You can choose hand-off at the first reply, AI replies until real interest, or AI replies until a meeting is booked with your scheduling link. Read AI LinkedIn outreach for the campaign setup.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? AI SDR templates for following up after events.md