How to message prospects after a shared event
Turn a shared conference into a meeting with specific LinkedIn messages, follow-up timing and a way to find attendees who never spoke to you.
Get startedShort answer
Message prospects after a shared event by quoting something specific they said or wrote, then continue that thread instead of introducing your company. The event gets you a reply; the follow-up earns the meeting.
Find the people who were actually in the room
Your best prospects are rarely the people you shook hands with. They are the ones who posted about the keynote, asked a question in the panel, or left a comment on the organizer's recap. Those people left a public trail, and that trail is what makes a first message read like a reply instead of a cold pitch.
Start with the event hashtag. Search it on LinkedIn, switch to Posts, and read what people actually wrote. You want two things from each post: a person whose job matches your buyer, and a sentence you can quote back to them later. Save the profile and the sentence together, because the sentence is the whole reason the message will work.
If the organizer ran a formal LinkedIn Event, the attendee list is there too. It is a blunt instrument, since it mixes speakers, sponsors and press in with buyers, so filter it by title and company before you spend time on it.
- 1
Search the hashtag and read the posts
Type the official hashtag into LinkedIn search and filter to Posts. Skip the organizer's own marketing and read what attendees wrote. Save anyone whose title matches your buyer.
- 2
Open the event page and check attendees
If the organizer created a LinkedIn Event, the attendee list is visible to people who joined. Filter by current company to line it up with the accounts you already want.
- 3
Read the comments on the recap post
The recap collects everyone who cared enough to respond. Commenters are warmer than silent attendees because you can quote what they said.
- 4
Check the speakers and their threads
A speaker's comment section fills up with people disagreeing about the talk. Those disagreements are the best openings you will get all week.
Write a first message that proves you were there
A connection note has a hard character limit, which is a useful constraint. You get roughly two sentences. Spend both on the event and on them. Name the session or the comment, say what you thought about it, then ask to connect.
The common failure is describing your own company. Nobody accepts a request because you work at Acme or because you help companies like theirs grow. They accept because you noticed something they said and had a reaction to it.
Generic
- Hi Sarah, great meeting you at the FinTech Summit. I'd love to connect and stay in touch.
- Hello, I saw you attended SaaS North. I work with companies like yours on growth. Let's connect.
Specific
- Hi Sarah, your question about API rate limits at the open banking panel stuck with me. We hit the same wall last year. Happy to compare notes.
- You wrote that the pricing workshop was the only useful hour of the day. I had the same reaction. Worth comparing what you'd have changed?
Paste this job
{{First name}}, you asked {{the question or point they made}} at {{session name}}. {{One line on why it landed with you}}. Worth connecting?What to send when they accept
Acceptance is not permission to pitch. It is permission to keep talking. Send the second message the same day if you can, while the event is still in their head and the session is still something they remember sitting through.
Give them something before you ask for anything. A short note on how you handled the problem they raised, a line about what you took from the same talk, or the answer the speaker dodged. Keep it to something you would send a colleague who missed the session.
Example
- You
Thanks for connecting, Sarah. You asked about rate limits at the panel and the speaker dodged it. Short version of what worked for us: we capped requests per key and published the limits in the docs. The support tickets about it dropped off.
- Prospect
That's useful. We're still arguing about whether to publish ours.
- You
Publishing was the easy part. Deciding what to do when someone blows through the cap was the argument. Are you free Thursday for 15 minutes to compare notes?
- Prospect
Thursday afternoon works.
Follow up once, then leave it
Most replies arrive after the second message. Plan for two touches and stop. A third message to someone who has ignored two is a bad use of your week and a good way to get muted.
Keep a simple note of who you messaged and when. When the next event comes around, that list is worth more than a fresh hashtag search, because those people already know who you are and did not reply for a reason that had nothing to do with you.
Same day
- When
- The specific follow-up on what they said, with something useful attached
- What you send
- Whether they want the conversation
Day four or five
- When
- One line on a different angle from the event, with no apology for following up
- What you send
- Whether the topic was the hook or the person
Two weeks
- When
- Nothing. Move them to a list you check before the next event
- What you send
- Whether the timing was wrong
One follow-up is persistence. Three is a reason to mute you.
Ask for the meeting so it is easy to answer
Vague asks get vague answers. "Would love to chat sometime" hands the work to them. Name a day, name a length, name what you will cover.
Repeat their problem back. If they mentioned a migration landing in Q3, say so. A question built from their own words can be answered with yes, no, or a different date, and all three are useful.
Hold the calendar link until they agree. Dropping a booking page into the first ask turns a conversation into a transaction. Offer the day, then send the link once they say yes. If they ask about price before you get there, answer with a range and what changes it rather than a single number, and read how to handle a prospect asking for a price estimate before you reply.
Paste this job
You mentioned {{their problem}} lands in {{timeframe}}. I spent last quarter on the same thing. Worth 15 minutes on {{day}} to compare how we sequenced it?Doing this with Kinlead
If the event produced more names than you can work by hand, Kinlead can carry the list. The Steal Customers agent watches a company page 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 they commented, so the opening line is already half written.
Those leads land in a lead group, and any campaign can point at that group. Connection notes are written by AI under 200 characters and open with why that person became a lead. Messages and follow-ups come from the campaign goal, tone and your own sales playbook. You can read and edit queued messages on the Actions page before they send.
Kinlead sends from your own LinkedIn account through Unipile and keeps to one action every 5 minutes inside the daily limits and send window you set. For event follow-up, set the campaign to hand the conversation to you at the first reply, so the thread stays yours once someone answers.
What to do when the thread goes quiet
Silence after a good exchange usually means the week got away from them, not that they lost interest. Send one short message that adds something new: a recording of the session they missed, a correction to something the speaker said, or a two-line summary of how a peer solved the problem.
If that gets nothing, close the loop yourself. "I'll leave this here, we can pick it up after {{next event}}." It costs nothing, it keeps the door open, and it stops you from spending another hour on a thread that has already answered your question.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to message prospects after a shared event.md