Follow up on trade show leads with AI

Trade show lead follow-up is where most event budgets quietly die. You come home with a few hundred badge scans, a handful of conversations you actually remember, and a marketing-built email that thanks everyone for "stopping by." Here is a four-step AI workflow for the rep who owns that list: sort the scans by what happened at the booth, write follow-ups from your own notes, and plan touches two and three. The prompts are ready to copy into ChatGPT, Claude, Gemini or Copilot.

Why most trade show follow-up fails

A badge scan tells you who walked past, not who had a problem or who wanted a free pen. When every scan gets the same email, the buyer who spent twenty minutes at your booth reads a note that proves you forgot them.

AI helps here by doing the sorting you never have time for, and by turning a half-sentence of booth notes into an email that proves you were listening.

Step 1: Capture three lines per conversation at the booth

For every conversation longer than two minutes, note three things before the next person walks up:

  • What they asked about, in their words if you can.
  • What is happening on their side: a project, a renewal, a new hire, a complaint about their current tool.
  • What you agreed: a demo, a case study, an intro to a colleague, or nothing.

"Asked about SSO. Replacing current vendor next quarter. Wants a demo with IT lead" is worth more than any enrichment data you can buy later.

Step 2: Sort the scan list into tiers with AI

Export the scans with your notes column and paste the rows into a chat, or paste them in batches if the list is long. Before you do, check your company's AI policy: badge data is personal data, and what you can paste into which tool is not your call alone. Then run this:

You are helping me triage leads from [EVENT NAME]. Below are badge scans with my booth notes. Sort every row into one of four tiers:

Tier 1 - Real conversation with a stated need or an agreed next step.
Tier 2 - Real conversation, interest but no need or next step stated.
Tier 3 - Scanned with no notes, but title and company fit my ICP: [DESCRIBE ICP].
Tier 4 - No notes and no ICP fit.

Rules:
- Use only what is in the notes and the row. Do not guess at needs.
- If a note is ambiguous, put the row in the lower tier and say why.
- For every Tier 1 row, restate the need and the agreed next step in one line each.

Return a table: name, company, title, tier, one-line reason.

[PASTE ROWS]

Check Tiers 1 and 2 against your own memory. The model is sorting text; you were in the room.

Step 3: Write the follow-up from the notes, not the template

Tier 1 gets a personal email, one at a time. Run this prompt per contact:

Write a follow-up email to [NAME], [TITLE] at [COMPANY], who I spoke with at [EVENT NAME].

My booth notes: [PASTE THE THREE LINES]
What I can offer next: [DEMO / CASE STUDY / INTRO / RESOURCE]

Requirements:
- Open with the specific thing they told me, not with "great to meet you."
- One short paragraph connecting their situation to the next step.
- Propose one concrete next step with two time options.
- Under 110 words. Plain text. No exclamation marks.
- Do not invent details that are not in my notes. If the notes are thin, keep the email shorter instead of padding it.

Then give me one alternative subject line that references the conversation.

Tier 2 gets the same prompt with a lighter ask: a useful resource and a question, not a meeting. Tier 3 gets a short, honest note with one reason you fit their role. Tier 4 goes to marketing's nurture track.

Step 4: Plan touches two and three before you send touch one

Event follow-up usually stops after one email because the second never gets written. Draft it now, while the context is in the chat:

Using the email above and my booth notes, write two more touches for [NAME]:
Touch 2 (sent if no reply after 4 business days): add one new piece of value tied to what they said at the booth. Under 80 words.
Touch 3 (sent a week later): a short, low-pressure note that makes it easy to say "not now." Under 60 words.
Neither touch may repeat the first email's wording.

If you want a stronger structure for those later touches, the follow-up email prompts and the three-touch sequence for people who open but do not reply both slot in here.

Common mistakes

  • Sending one email to the whole list. It is efficient for you and invisible to the buyer who actually cared.
  • Letting AI fill gaps in your notes. A model asked to personalize with no notes will invent a conversation. The "do not invent" line in each prompt is there for a reason.
  • Waiting for marketing's list to clean up. Your Tier 1 contacts need you, not enrichment.
  • Asking Tier 2 for a meeting. Interest is not a need. Earn the next conversation with something useful first.
  • Skipping the CRM. Log the tier and the notes on each record so the next rep, or next year's event, starts ahead.

The logic behind responding to inbound leads fast applies here too, except a booth conversation gives you better material than any form fill. For the wider event play, see the conference and event follow-up use case.

Frequently asked questions

How soon should I follow up after a trade show?

Send Tier 1 follow-ups in the first few business days, while the buyer still remembers the conversation. Specificity matters more than speed, but it fades with time on both sides.

What should a trade show follow-up email say?

Name what the buyer told you at the booth, connect it to one next step, and offer two times. With no notes, keep it short and honest rather than pretending you remember them.

Can AI write trade show follow-up emails that do not sound generic?

Yes, if you give it your booth notes and tell it not to invent details. Generic output comes from generic input; three lines of notes is usually enough.

Keep the prompts for next event season

The Events, Field Marketing & Community prompts include tested versions of this play, including "Segment Event Attendees and Generate Follow-Up Plays" and "Build a post-conference follow-up that converts leads," so you are not rebuilding the workflow before every show.