To qualify a visitor at a trade show, establish why they are there, what they need, whether your offer fits and what next step they actually want. Use a respectful conversation and a short, agreed record. A badge scan, job title or giveaway entry does not establish a sales opportunity on its own.
Qualification helps the team direct its time and expertise. A visitor may be a buyer, user, adviser, distributor, student, journalist or existing customer. Different roles can be relevant to different event objectives; do not treat a person without immediate purchasing authority as automatically unimportant.
Define what it means to qualify a visitor at a trade show
Before the event, agree the purpose of participation and the criteria for each type of useful conversation. The AUMA briefing guidance offers a reference for connecting objectives, resources and responsibilities. A technical product launch may need application feedback; a distributor search may need territory, capabilities and partnership discussions.
Define a qualified opportunity in your own process. For example, your team might require a relevant application, a plausible fit, a stated project and an agreed follow-up. Those are possible criteria to adapt, not an industry benchmark. Avoid recording a guess about budget or buying authority as something the visitor confirmed.
Use questions that match the conversation
| Purpose | Possible question | Record carefully |
|---|---|---|
| Understand the visit | What are you looking into at the event? | The visitor’s stated interest, rather than an assumed need. |
| Explore the application | Where would you use this, and what matters in that situation? | Relevant constraints and questions that require specialist input. |
| Check the current approach | How do you handle that task now? | The described process and any problem the visitor wants to address. |
| Understand timing | Is there a project or decision schedule you can share? | Confirmed timing, or that no timing was provided. |
| Understand involvement | Who else would need to review the information? | The visitor’s role and agreed route for involving colleagues. |
| Agree a useful next step | Would a sample, technical answer or meeting help? | The requested action, owner and agreed delivery timing. |
These questions are prompts, not a script to complete regardless of context. Listen, explain why you need information and let the visitor decline. Do not make a short exploratory visit feel like an interrogation. Ask about commercial constraints when relevant, without demanding confidential details to receive basic information.
Route visitors to the right activity or colleague
A welcoming team member can identify the topic and introduce the appropriate specialist. Explain the handover so the visitor does not need to repeat everything. If the specialist is occupied, offer an actual available time or an agreed route for a later answer.
Demonstrations and trials can reveal useful questions, but participation does not prove buying intent. Check the application and limitations before suggesting a fit. If the product is unsuitable, say so and avoid promising a capability that has not been confirmed.
Plan staffing from the tasks, meeting schedule, activity duration and space. Include breaks and overlapping responsibilities. There is no universal staffing ratio or conversation length that establishes quality. The stand activity and staff guide covers practical operating checks.
Create a short, useful contact record
Use the approved system to record what the next person needs to fulfil the request. Separate observed facts from staff interpretation, and avoid unnecessary personal details. A practical record may include:
- The visitor’s relevant organisation and role, where provided.
- The stated application, question or project.
- The product or demonstration discussed and any limitations explained.
- The requested material, technical answer or meeting.
- The assigned colleague and agreed follow-up timing.
- The approved contact route and relevant information about purpose and permissions.
Test the form, access permissions, duplicate handling and offline procedure before opening. Do not collect fields simply because the scanner supports them. Confirm spelling and the requested response when appropriate, and keep records secure through the organisation’s approved process.
The responsible team should determine the applicable lawful basis, notices, retention and marketing requirements. A badge scan, prize entry or request for a technical sheet is not automatic permission for every later campaign. The EDPB guidance on lawful processing provides an initial reference; the actual process needs assessment in context.
Prioritise follow-up without inventing certainty
Use categories with definitions the team understands. “Technical answer requested,” “meeting agreed,” “early research” and “existing customer issue” can be more useful operational labels than an unexplained hot, warm or cold rating. If you use a score, document its criteria and keep the underlying facts visible.
Deliver the promised response within the agreed timing. A technical request may need expert review; an urgent customer problem may need immediate routing. There is no single follow-up deadline appropriate to every interaction. Track unanswered requests and reassign them when the original owner is unavailable.
Measure conversation quality separately from footfall
Count visits, conversations, completed records, agreed actions, attended follow-up meetings and later opportunities separately. Define how repeat visits and duplicate contacts are handled. A scan count cannot stand in for qualified opportunities or attributable revenue.
Review which questions helped clarify needs and where staff struggled to record or fulfil requests. Compare against your own objectives and documented past results, allowing for differences in event, audience, location and offer. Avoid promising a percentage increase or using unsourced industry benchmarks as evidence of success.
If calculating cost per qualified opportunity, state the included event costs and the qualification definition. If calculating ROI, define the attributable financial return, time period and total investment. Do not substitute pipeline value or badge scans for realised profit without explaining the measure.
Frequently asked questions
Must every visitor have purchasing authority?
No. Users, technical advisers and other stakeholders may be relevant to your objectives. Establish their role and the appropriate next step without assuming that title alone establishes influence or intent.
How long should qualification take?
Long enough to understand the relevant need and agree a useful next step, within the visitor’s available time. Plan capacity around the actual activity and conversation rather than a universal time target.
Does an appointment guarantee a qualified lead?
No. An appointment indicates planned contact. Confirm the purpose, fit and agreed action through the conversation, and record attendance separately from opportunity qualification.
When briefing Adam Expo Stand, explain the visitor activities, demonstration requirements, meeting capacity and staff roles. These requirements help inform the layout and service scope alongside the actual event rules.