There is no shortage of trade show follow-up templates on the internet. Most of them are interchangeable, and the reason is not that the writers are lazy. It is that a template can only be as specific as the information it has to work with, and most templates are written to work for a reader who captured nothing.
So the honest version of this article is not a list of templates. It is a demonstration that the same skeleton produces four completely different emails depending on what you wrote down at the booth, followed by the skeletons themselves.
An email is only as specific as your capture
Every follow-up email does three jobs in sequence: remind them who you are, prove you were listening, and make one clear ask. The first and third are easy. The second is where emails succeed or fail, and it is entirely determined by what you captured while the person was standing in front of you.
This is the whole argument. If your follow-ups read generic, the fix is upstream of the writing, and no amount of template shopping will help. We went through why the context disappears in why event leads go cold.
The same email at four levels of context
Here is one lead, written four ways. The person is an operations lead at a logistics company. What changes between versions is only what was captured.
Level 0: name and company
Hi Anita, it was great meeting you at the expo last week. Karo helps teams capture event leads without manual data entry. Would you be open to a quick call this week to see if it is a fit?
Nothing here could not have been sent to two hundred other people. There is no evidence a conversation occurred. The ask is vague and it asks her to do the work of remembering why she might care. This is the email most event leads receive, and its reply rate reflects that.
Level 1: plus what they asked about
Hi Anita, good to meet you at the expo. You mentioned your team loses cards between the booth and the office, and that follow-ups often go out a week late. That is the specific thing we fix. Worth a short call?
One captured sentence and the email is now unmistakably about her. Note that it is shorter, not longer. Specificity replaces padding rather than adding to it.
Level 2: plus the timeline
Hi Anita, good to meet you at the expo. You mentioned cards going missing between the booth and the office, and that you are reviewing tooling before the January show season. I can send a short comparison for that review, or walk through it on a call if that is easier. Which suits?
The timeline changes the ask. Rather than requesting a generic call, the email offers to serve a decision she has already told you she is making. It also gives her two ways to say yes, which reliably outperforms one.
Level 3: plus the second stakeholder
Hi Anita, good to meet you at the expo. You mentioned cards going missing between the booth and the office, and that you are reviewing tooling before the January season with Ravi signing off. I have put together a one-page summary aimed at that decision, covering cost per event and what your team would actually do differently. Happy to send it over for both of you, or run through it on a call before you take it to him. Which is more useful?
This one is longer, and it earns the length. It names the decision, the decision maker and the format, and it positions the sender as making her internal case easier rather than asking for her time.
Subject lines
Subject lines for event follow-up have one job: make it obvious this is not cold outreach. The reader is deciding in about a second whether they have ever heard of you.
What works is naming the event or naming the specific thing discussed. What fails is anything that could plausibly have been sent by a stranger.
- Works: “Following up from the expo, the card capture question”
- Works: “Your January review, one page as promised”
- Weak: “Great meeting you!” Could be anyone, says nothing.
- Weak: “Quick question” Reads as cold outreach, because it almost always is.
- Avoid: Anything with false urgency. “Last chance” two days after a handshake destroys the relationship you just built.
Keep it under about eight words, because most of your leads will open on a phone, and put the distinguishing detail at the front rather than the end where it truncates.
What each touch in the sequence contains
The sequence itself is covered in the 48-hour playbook. What matters here is that the three messages have different content, because reusing the first email slightly reworded is why sequences stop working after touch one.
The second touch is where most sequences die. “Just checking in” and “bumping this to the top of your inbox” both ask the recipient to do the work of remembering and deciding, while offering nothing in return. Send the pricing they asked about, a relevant comparison, an answer to the question they raised at the stand. If you have nothing to add, that is information about the lead rather than a reason to write anyway.
The third touch should be genuinely easy to say no to. Something close to: “I will stop here, but if the January review moves forward, happy to help.” That gets more replies than a fourth chase, and the replies it gets are honest.
What never to do
Do not attach the deck to the first email. A cold attachment is friction and frequently a spam signal. Offer it and let them ask, which also tells you something about interest.
Do not pretend to remember more than you do. If your note says “interested” and nothing else, do not invent a conversation about their warehousing operation. A wrong specific is far more damaging than an honest general, because it proves you were not listening while claiming that you were.
Do not send from a no-reply or a shared marketing address. The person met a human. The email should come from that human, with their phone number in the signature.
Do not merge everyone into one campaign on day one. Event leads are not a list, and treating them as one wastes the single advantage you have over cold outreach, which is that you actually met.
The skeletons worth reusing
Here is what to reuse: the structure, not the words. Every good event follow-up has the same four parts in the same order.
- Where we met, in five words. “Good to meet you at the expo.” Not two sentences about how much you enjoyed the show.
- The thing they said. One clause, in their language rather than yours. This is the part that comes from your capture and the part that cannot be templated.
- One line on why that connects to you. Not your positioning statement. The specific link between their problem and what you do.
- One ask, with two ways to say yes. A call or a document. A Tuesday or a Thursday. Two options convert better than an open question.
Total length for touch one: three to six sentences. If it is longer, the extra is almost always about you rather than about them.
The reason this skeleton survives contact with reality is that only part two changes per lead, and part two is a single clause lifted from what you captured. Filling in one clause for forty leads is a twenty-minute job. Writing forty bespoke emails is not, which is why nobody does it and why most event follow-up is generic.
Personalising forty emails in half an hour
The objection to everything above is time. Forty leads, four minutes each, and the afternoon is gone. In practice it takes far less, provided you do it in the right order.
Export the leads to a spreadsheet with the captured context as a column, which is what the CSV export is for. Sort by that column rather than alphabetically. Leads with rich context cluster together, and so do the level-0 ones, which means you are not switching modes on every row.
Then work in three passes. First pass: the ten with the most context get individually written, because they are worth the four minutes. Second pass: the middle group get the skeleton with one clause swapped, which takes under a minute each once you are in rhythm. Third pass: the level-0 leads get the honest short version, which is quick precisely because there is nothing to personalise.
Half an hour, and the ten that mattered got real emails. The mistake is starting at row one and working down, because you spend your freshest attention on whoever happens to be alphabetically first. Tagging by event, covered in the event capture guide, is what makes the sort possible in the first place.
The short version
Your follow-up can only be as specific as your capture, so the writing problem is usually a capture problem. Reuse the four-part skeleton rather than the words: where we met, the thing they said, why it connects, one ask with two ways to say yes. Put the distinguishing detail in the subject line and in the first two lines. Make touch two a contribution rather than a nudge, and make touch three easy to decline.
If the reason your emails start at level 0 is that nothing survives your events except names and companies, that is fixable at the booth rather than at the keyboard. The WhatsApp capture flow attaches a transcribed voice note to the contact, and 20 free scans is enough to test it on one event and compare what you have to write from afterwards.