An after-event cold email is a message sent within five working days of a conference, webinar or trade show to someone who attended, using the event as shared context rather than claiming a conversation that did not happen. It is the highest-replying template in the set, 8 to 18% positive replies reported on verified lists, and the one with the dirtiest raw list: attendee exports and badge scans mix personal addresses, typos and role mailboxes, and need verifying before the window closes.
| List | Where it comes from | Typical problems | What to do before sending |
|---|---|---|---|
| Badge scans | Your own stand or scanner app | Typos at the scanner, personal addresses, duplicates | Verify, dedupe, flag personal domains |
| Attendee export | The organiser, if the terms allow | Registered but did not attend; stale by the event date | Verify; segment by session attended if the data exists |
| Speaker and sponsor lists | Public agenda | Senior people, assistant-managed inboxes | Find the direct address; expect catch-all domains |
| Webinar registrants | Your own platform | Freemail-heavy; 17.6% invalid on freemail in 2026 corpus data | Verify; send only to attendees, not all registrants |
"Great to meet you at the show" to someone you never met is the most common cold email lie, and it ends the relationship before it starts. The template uses the event as context you both have: the keynote, the theme, the hall, the session they attended. It never claims a conversation.
The context does real work. The reader was thinking about the event's topic for a day or two, and the email arrives while that thought is still warm. Reference something specific, a talk, a stat the keynote used, a question from the Q&A, and connect it to what you do.
The five-day window is not a rule of thumb; it is how long the shared context lasts. By day ten the event is a memory and the email is an ordinary cold send.
Subject: {event_name}: {session_or_theme}
Hi {first_name},
We were both at {event_name} last week. {speaker}'s point about {specific_point} stuck with me, mainly because it is the problem {sender_company} works on.
For {customer_type}, we {outcome}. {similar_company}, who were also there, {result}.
If {specific_point} is on your list this quarter, 15 minutes would tell us if it is worth a longer conversation.
{sender_name}
{sender_title}, {sender_company}
If this is not relevant, reply "no" and I will not write again.
{session_or_theme} A session title or the event theme, in the organiser's words{speaker} A speaker whose point you reference{specific_point} The point, in one phrase; it must be realSubject: Following up from the {sender_company} stand
{first_name},
Thanks for stopping by the stand at {event_name}. You scanned in during the {time_slot}, so you may have spoken to {colleague} rather than me.
The short version of what we do: {outcome} for {customer_type}. If it was {specific_interest} that caught your eye, I can send the relevant two-pager, or we can talk for 15 minutes.
Which is easier?
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{time_slot} Morning, afternoon, or the session name{colleague} Whoever staffed the stand then{specific_interest} What the stand was showingSubject: Your question in the {webinar_name} Q&A
Hi {first_name},
You asked about {question_topic} during the {webinar_name} Q&A. We ran out of time, so here is the fuller answer in two lines: {two_line_answer}.
If you want it applied to {company}'s own setup, I can do that on a call or send a short write-up. Your call.
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{question_topic} What they asked, in their words{two_line_answer} The answer, actually in two linesThe window is five days and the list is dirty. Run bulk verification on day one: badge-scan typos become invalid, personal addresses get flagged, duplicates go.
Webinar lists run freemail-heavy, and freemail on B2B lists ran 17.6% invalid in 2026. Send to work addresses from the cold domain; treat personal addresses as consumer contacts with consent rules.
It is the one line that converts an interested reader into a complainer. Shared context only. Keep complaints under 0.3%.
Attendee exports usually come with usage conditions. Read them; a single complaint to the organiser can cost next year's stand.
| Metric | Healthy range (industry) | If missed |
|---|---|---|
| Positive replies | 8 to 18% per 100 delivered | Sent after day five, or the context was generic |
| Bounce rate | Under 2%; under 1% verified | Badge-scan typos; verify on day one |
| Meetings | 3 to 7% of delivered | Ask was a call only; offer the two-pager as the easier option |
| Complaints | Under 0.3% | A claimed conversation, or registrants who did not attend |
Subject: SaaStock: the "22% decay" point Hi Martin, We were both at SaaStock last week. Nadia's point in the outbound session about B2B addresses decaying fast, with only 19.2% of addresses still valid 90 days after verification in the BounceZero decay study stuck with me, mainly because it is the problem we work on. For outbound teams, we re-verify the base on a 90-day cycle so sequences never run on last quarter's addresses. Bramble, who were two rows ahead of you in that session, cut bounces from 7% to under 1% on the first pass. If list decay is on your list this quarter, 15 minutes would tell us if it applies. Jess Carr BounceZero If this is not relevant, reply "no" and I will not write again.
"Great to meet you" to a stranger ends the relationship. Shared context only.
Registrants who did not attend have no shared context and complain. Attendees in your profile only.
Verify on day one. The window is five working days.
Personal addresses are consumer contacts with consent rules, and 17.6% of them are invalid.
The full set
Day 3 of the thread
When a colleague at the stand made the connection
How specific the event reference should be
Freemail and business invalid rates
Event prospecting among the other methods
Within five working days, ideally two to three. The shared context fades fast; by day ten the event is a memory and the email reads as an ordinary cold send. Verify the list on day one so nothing waits on cleanup.
No. It is the most common lie in cold email and it ends the relationship. Use context you both have: a session, a speaker's point, the theme. Variant A handles the case where a colleague, not you, spoke to them.
Only attendees in your profile, and only at work addresses. Registrants who did not show, personal addresses and contacts outside the profile raise complaints and lower replies. Segment by session if the organiser data allows.
Badge scanners mistype, people register with personal or throwaway addresses, and the list is weeks old by the event. Verification on day one turns typos into invalid, flags freemail, and removes duplicates before the first send.
The highest in the set: teams report 8 to 18% positive replies on verified lists sent inside the five-day window, with meetings at 3 to 7%. The rate halves if the send slips past a week.
Typos, personal addresses and duplicates out; confirmed-valid work addresses in; sent inside the window. 100 free checks a month, unknowns refunded.
Ayoub built BounceZero's 5-stage validation pipeline, its dedicated BGP-announced IP infrastructure, and the Patroni HA PostgreSQL cluster behind every verification. Previously built high-volume email delivery infrastructure. Trained at 1337 Benguerir (École 42 network, 2019). Open-source: bgp_analyzer.
Templates by trigger and stage, each with the deliverability rules that apply
A technology change cold email template for tech-stack triggers
A competitor user cold email template
A first follow-up email template for when a cold email gets no response
A second follow-up email template for cold sequences
A third follow-up email template for cold sequences
A break-up email template for cold sequences
Continue through related topics