Trade Show Lead Follow-Up: A Practical Plan and Email Templates

Agree what counts as a useful lead before the show

Set a few practical categories before staff start scanning. A quotation request, a technical evaluation, a potential distributor and someone collecting general information should not receive the same response. Ask the people who will follow up what they need to know. Keep the form short enough to use during a conversation.

Informa’s exhibitor guidance describes qualification fields alongside scans and distinguishes different interaction types in exports. The lesson is to check what your event’s tools actually retain. Confirm that notes, qualification answers and the staff member who met the visitor will reach the team doing the follow-up, rather than assuming a headline lead count contains them.

• Company, contact and the person’s role in the discussion.
• Product, application or problem discussed.
• Relevant timing and any specifications voluntarily provided.
• The item promised and the next action agreed.
• Preferred contact method, permission or preferences recorded in the event process.
• Named follow-up owner and a due date.

Capture the context while you still remember it

At the end of a conversation, confirm the next action aloud: for example, sending a specification sheet or arranging a technical call. Record the relevant product or project, not a long account of everything said. A short, accurate note is more useful than a rating of hot with no explanation.

Review the day’s records before leaving the venue. Merge duplicate contacts carefully without deleting distinct requests, assign an owner and check the export. Keep access limited to the colleagues who need the information. Use the event’s instructions and your organisation’s data-handling process; a badge scan should not be treated as permission for every unrelated campaign.

Use a schedule based on the promised next step

The following is a suggested operating plan, not a claim that one timing produces a particular conversion rate. Handle an urgent request by the time agreed with the visitor. For other relevant conversations, aim to organise the records on the same day and send a useful personal response within the next one or two working days.

During the first week, check whether the promised material arrived and whether a meeting or technical answer is still needed. In the second week, make one relevant follow-up if there has been no response. Stop or change the approach when someone declines, asks you to wait or gives another preference. Do not keep sending an automated sequence simply because a contact was scanned.

• Show day: record context, next action and owner.
• Next one or two working days: send what was promised or give a clear delivery date.
• First week: resolve questions and confirm any agreed meeting.
• Second week: make a brief, relevant check-in where appropriate.
• Later review: record the outcome, next date or reason to close the enquiry.

Template 1: deliver what you promised

Subject: [Product or project] — following our conversation at [event]

Hi [Name], thank you for discussing [specific requirement] with us at [event]. As promised, here is [the relevant document, answer or link]. You mentioned [one useful detail from the conversation]. Would [proposed next step] help you assess whether this is suitable? If useful, I can arrange [a short call or demonstration] with [relevant colleague]. Best, [Name].

Replace every bracket and check that the message matches the conversation. Send the relevant material rather than attaching an entire catalogue by default. If an answer is not ready, explain what you are checking and when you expect to respond.

Templates 2 and 3: qualify a quotation, or close the loop

Quotation clarification — Subject: Details for your [project] quotation. Hi [Name], we discussed [requirement] at [event]. To prepare a useful proposal, could you confirm [two or three missing details]? We have already noted [known information], so there is no need to repeat that. Once confirmed, we will outline the scope and expected proposal date. Best, [Name].

Final check-in — Subject: Is [requirement] still on your plan? Hi [Name], I’m following up on [specific topic] from [event]. Is this still something you would like to explore, or would another time be better? If it is no longer relevant, let me know and I will close this enquiry. Best, [Name].

Use the clarification message only when the missing information affects the proposal. Use the check-in after a reasonable interval for the actual buying process. Neither template should imply that the visitor requested a quotation if the conversation was only a general introduction.

Report progress without treating every scan as a sale

Track captured contacts, qualified enquiries, completed follow-ups, meetings held, proposals issued and outcomes as separate stages. Decide what qualifies for each stage and use the same definition across the team. Keep customers already in discussion before the show identifiable so a later deal is not automatically counted as newly created by the event.

For a simple illustration, if a team captures 80 contacts and records 20 as qualified enquiries, its contact-to-qualified rate is 25%. If 12 of those 20 receive the agreed follow-up, follow-up completion is 60%. Those two measures reveal different things. They do not establish revenue, profitability or causation. Review open actions as well as totals, and give every unresolved enquiry a next date or a clear closure reason.

Put your plan into action