How to help exhibitors distinguish useful leads from badge scans

Your exhibitor comes away from the show with a long list of scanned badges. They're pleased with the activity, their sales manager asks which people actually want a conversation, and suddenly that impressive total becomes difficult to explain. Some visitors asked for a demonstration. Some wanted a brochure. Others entered a prize draw and barely looked at the product. Those interactions might all deserve a record, but they don't deserve the same follow-up.

Exhibitor lead qualification means deciding whether a contact fits the exhibitor's business, what need the conversation established and which next action the person actually requested. As the organizer, you can help exhibitors agree those decisions before the event and record enough evidence to make them afterwards. You can provide the conditions for useful conversations. The exhibitor still decides whether a contact deserves sales attention, and a badge scan alone cannot answer that question.

This matters commercially because exhibitors are paying for access to a relevant audience. When they can explain what that access produced, they have something useful to take into their next budget discussion. When your report celebrates scans while their sales team finds little worth pursuing, you end up arguing about whether the event worked. Agreeing what counts beforehand gives both sides a fairer conversation.

Agree what a useful contact means for this exhibitor

Start with the person who will receive the contacts after the event. Often that's a sales manager who won't spend much time on the stand. Ask them to describe a conversation they would want their team to continue. Push past "decision-makers" and "high-quality leads". Which organizations can they serve? What problem would make their offer relevant? What would they need to know before putting an engineer, adviser or account manager on a call?

Imagine an exhibitor selling temperature-monitoring equipment to food manufacturers. A maintenance supervisor investigating inconsistent readings may be more useful than a managing director browsing without a project. The supervisor might understand the installation requirements, influence the shortlist and introduce purchasing later. Qualification needs to capture that contribution rather than treat seniority as a shortcut for interest. A job title tells you something about someone's role. It doesn't explain what they came to discuss.

Ask the exhibitor what would make a conversation unsuitable as well. Perhaps they cannot install outside a particular region, their product doesn't meet a required specification, or the visitor needs a service they don't provide. Those are practical reasons to change the next action. They are different from not knowing the budget yet. An unknown answer should stay unknown until someone establishes it; quietly translating every blank into a negative makes your records look more definite than the conversation was.

Salesforce's guide to creating a lead qualification model separates interest from suitability and recommends involving sales when setting criteria. That's a useful distinction for an exhibition, even if an exhibitor never uses a scoring system. Someone can show enthusiasm for a product their organization cannot use. Another visitor can fit the customer profile perfectly while wanting nothing more than a general introduction. Record those differences so the next person can respond sensibly.

Put the agreed definition into the exhibitor briefing. Our exhibitor onboarding checklist covers the wider preparation, but this conversation needs the exhibitor's commercial input. You can offer a common structure across the show. You shouldn't promise that every exhibitor will share the same definition of a worthwhile enquiry.

Record fit, need, request and next action

A useful record should allow a colleague to understand why contact would be appropriate without asking the stand representative to reconstruct the conversation. Keep the structure simple enough to use while visitors are waiting. Record whether the organization fits, what problem the visitor described, what they asked to receive and who should do it. Those answers give the exhibitor a starting point for deciding priority. They also make it harder for an enthusiastic representative to disguise an ordinary exchange as a ready-to-buy enquiry.

For fit, ask about the conditions that genuinely determine whether the exhibitor can help. The equipment supplier might need to know the manufacturing process and where the site is located. Another exhibitor could need to know whether a visitor operates a venue, advises venue owners or sells to them. Let the exhibitor choose the necessary questions. A universal form that demands company size from everyone can collect information that has no bearing on the product discussed.

For need, record the visitor's explanation in concrete words. "Interested in monitoring" could mean almost anything. "Existing sensors lose accuracy during washdown; wants to understand suitable replacements" gives a technical colleague a reason to reply. Staff don't need to transcribe a conversation. They need to preserve the part that changes the response. If no problem was established, say that. A visitor can ask for information without having an active project, and the record should allow that answer.

For request, distinguish what the visitor asked for from what the representative hopes will happen. Asking for a specification sheet is not agreeing to a sales meeting. Agreeing to a demonstration is not accepting a quotation. Record the actual request and confirm the destination for the response. If the visitor says they will return with a colleague, keep that as the agreed action rather than inventing an outbound call to make the record look more complete.

Then give the next action an owner and a realistic date. "Follow up" leaves too much for someone else to decide. "Applications engineer to send washdown suitability information after the show" explains the task and the person needed. The exhibitor can agree a more precise deadline with the visitor when appropriate. You don't need to impose the same deadline on every interaction. A technical answer that needs checking and an already-booked meeting require different preparation.

Ask questions that continue the conversation

Qualification should sound like someone trying to understand a visitor, because that's what it is. Staff can begin with "What brought you over?" and follow the answer. If a visitor mentions replacing equipment, ask what the current equipment isn't doing. If they mention opening another site, ask what they need to work out before choosing suppliers. These questions establish relevance without turning the stand into a registration desk where everyone must complete the same interview.

There is a temptation to collect every possible sales detail while you have the person in front of you. Resist it. Visitors may be researching several options, attending a session shortly or looking for a colleague. Asking about purchasing approval before establishing the problem can make an otherwise helpful exchange feel premature. Let the exhibitor decide what must be known now and what belongs in the next conversation. The aim is enough information to take the right action, not an exhaustive account of their business.

Consider what happens when the answer is "I'm looking on behalf of our production team". A weak process asks whether the person controls the budget and marks them down when they don't. A better conversation asks what their production colleagues need to compare and whether there is something useful to send back. They may be the person gathering the information that shapes a shortlist. Record that role accurately without upgrading it to purchasing authority or dismissing it as irrelevant.

Offer attendees a comfortable way to decline. "Would you like the technical information, or are you just having a look today?" makes both answers possible. Staff should accept the second answer without treating it as a failure. You still want visitors to explore the exhibition. If every stop creates an unwanted sales conversation, the event becomes less useful for the people whose attendance makes it valuable to exhibitors in the first place.

Treat buying role and timing as information

A short-term purchasing deadline can help an exhibitor prioritize work, but it doesn't prove that the visitor is suitable or that a purchase will happen. Ask what is driving the timing. A maintenance shutdown, contract renewal or new site opening gives the sales team context. "Soon" leaves them guessing. If the visitor doesn't know, record that uncertainty. Don't force a specific month into the form simply because the reporting system requires an answer.

Budget needs similar care. An approved budget, an early estimate and permission to investigate options are different situations. Someone researching an unfamiliar solution may need technical information before they can build a budget at all. The exhibitor can decide whether that makes the enquiry suitable for immediate sales work or a later conversation. Your role is to make room for an honest answer, rather than encourage staff to tick "budget confirmed" whenever a visitor says their organization spends money on equipment.

Buying responsibility can also be shared. An engineer may assess performance, procurement may negotiate terms and a director may authorize spending. Recording the person as "not the decision-maker" throws away what they can actually contribute. Record the role they describe and any agreed introduction. Don't demand colleagues' personal details to make the record look complete. The next conversation can establish who else needs to participate, with the visitor helping arrange it where appropriate.

For organizers, this is why a show-wide promise of "qualified buyers" deserves scrutiny. You can describe attendance criteria and explain how you verify them. You can support conversations between relevant businesses. You cannot assume that every attendee with a purchasing-related job has a current project for every exhibitor. Make that distinction when selling space. Our exhibitor prospectus guide helps you state the audience and the service you can support without turning an attractive prospect into a guaranteed commercial result.

Give staff a shared way to decide priority

Once the exhibitor knows what it needs to record, agree how its team will use the information. A practical approach is to distinguish requests ready for a sales conversation, relevant contacts needing information and interactions with no agreed commercial next step. These descriptions can work without a numerical score. The important part is that the team can explain which evidence puts a record into each group and what happens afterwards.

A request ready for a sales conversation might require a suitable organization, a specific problem and an agreed discussion about how the exhibitor could help. The exhibitor may add other conditions where they matter. A visitor requesting general information can remain a useful contact without meeting those conditions. Someone entering a prize draw should be recorded according to that activity, without being promoted into either group just because their badge was scanned at the stand.

Avoid categories that pretend to be objective while relying entirely on staff enthusiasm. "Hot" means different things to different representatives. If an exhibitor keeps that label, ask what observable evidence justifies it. A friendly conversation, an impressive employer and a long stay at the stand don't automatically add up to an active purchasing enquiry. An explanatory note allows the sales team to review the decision; a label by itself asks them to trust an impression.

Take a visitor who asks for a demonstration but won't describe their organization. Staff can record the request and the missing information together. The exhibitor might need to clarify suitability before arranging a specialist demonstration, or it might offer an open session available to anyone. Either response can be reasonable. What matters is that the record doesn't pretend the missing answer was established. The next colleague should see what needs checking rather than discover it after making a promise the team cannot keep.

The reverse situation deserves equal care. A visitor from a suitable organization describes a real problem but declines contact because they are gathering information privately. That is a relevant conversation with no agreed outbound action. Staff can offer material the visitor can take away and leave the record accurate. Respecting that choice protects the relationship and keeps the exhibitor's priority list useful for the people expecting a response.

Before opening, walk through a few fictional conversations with the stand team. Use one clear request, one relevant but early enquiry and one ambiguous exchange. Let staff decide the next action, then discuss where their answers differ. You may discover that the form makes an honest response difficult or that sales and marketing expect different things. Fixing that disagreement before visitors arrive is more useful than finding it in the final report.

A fictional example of scans and useful requests

Here's an original worked example using entirely fictional figures. It describes an equipment exhibitor at a paid industry exhibition, not a Loopyah customer result or an industry benchmark. The exhibitor agrees its qualification rules before the event and records enough information to review every interaction. The numbers show how those rules change the meaning of a scan total. They are not suggested targets for your event or evidence that this process will produce comparable results.

The exhibitor records 160 scan entries. After identifying repeat scans of the same people, it has 120 distinct contacts. It reviews those contacts against its agreed rules and assigns each person to one mutually exclusive group according to their recorded conversation. Twenty-four have a suitable organization, an identified need and an agreed sales discussion. Thirty-six fit the business and request information but have no agreed sales discussion. The remaining 60 have no agreed commercial next step under those rules.

The chart accounts for all 120 distinct contacts, with each person counted once. Of those contacts, 24 divided by 120, or 20%, have an agreed sales discussion. Another 36 divided by 120, or 30%, requested information. The remaining 60 divided by 120, or 50%, have no commercial next step recorded. Source: this article's original fictional worked example. These are classifications of event conversations, not sales conversion rates, and none of the groups tells you how many purchases will follow.

Notice what disappears when the report says "160 leads". Repeat scanning inflates the number of people, and the single label hides different requests. Yet saying "only 24 useful contacts" would also distort the evidence. The information requests may deserve a thoughtful response, while some visitors without a commercial next step may have valued the demonstration. The exhibitor needs to understand those outcomes separately rather than force every interaction into a single favourable total.

Suppose the sales manager later decides that two of the 24 discussions need more technical information before a sales meeting makes sense. Preserve the original classification and record the review decision. That correction helps the team learn what evidence was missing. It shouldn't silently rewrite what staff recorded during the show or turn an early assessment into proof that the organizer delivered fewer people. State when each count was taken and whose decision it represents.

Match the response to the recorded request

After the show, the first message should make sense to the person receiving it. If they asked about washdown suitability, send the relevant answer or explain when the engineer will reply. Refer to the actual discussion so they can recognize why you're writing. A generic pitch for every product wastes the detail the stand team collected and can make a perfectly reasonable exchange feel like a mailing-list acquisition exercise.

The exhibitor should name who handles technical requests, sales discussions, existing customers and messages that need clarification. You can help by asking for those owners during preparation and making sure the information can reach them. But don't assign the organizer responsibility for an exhibitor's internal sales work. The commercial agreement needs to describe what your event provides, including any support for recording and transferring requests, and what the exhibitor must manage afterwards.

A visitor can have several legitimate reasons to speak to the same business. They might request a new product demonstration and report a problem with equipment they already own. Keep both requests visible and send each to the appropriate team. Marking the entire contact as an existing customer may hide the new enquiry. Marking everything as a sales opportunity may leave a service complaint unanswered. The useful unit of work is the request, even when you also report distinct people.

Don't assume silence tells you the original classification was wrong. A relevant visitor can be busy, their project can pause or the message can arrive at an inconvenient time. Equally, a courteous reply doesn't establish a purchasing opportunity. Ask the exhibitor to distinguish whether it delivered the requested response, whether the visitor engaged further and whether its sales team accepted a commercial opportunity. Those are separate observations with different meanings for the next event.

Keep contact permission separate from commercial interest

A person can be a strong commercial fit and still decline marketing. Another can agree to receive a newsletter without having any current need for the exhibitor's offer. Record the intended contact and handle the applicable privacy and marketing requirements separately from qualification. A high priority label cannot create permission, and entering the exhibition doesn't tell you which individual exhibitors an attendee wants to hear from.

For UK activity, the ICO's business-to-business marketing guidance explains that rules depend on the contact method and the type of subscriber. Corporate bodies and sole traders can be treated differently, and UK data protection requirements still apply when business contact information identifies an individual. The guidance is under review following legislation, so check the current requirements for your intended activity. Avoid either blanket claim that every business email needs consent or that business contacts can always be marketed to freely.

For US commercial email, the FTC's CAN-SPAM compliance guide explains requirements including accurate sender information, non-deceptive subject lines and a working way to opt out. The rules cover business-to-business commercial email too. That doesn't settle requirements in other jurisdictions or make every use of an event contact appropriate. The exhibitor needs a compliant plan for the actual messages it intends to send, with relevant advice where its circumstances require it.

Collect only information needed for the task. The ICO's data minimisation guidance explains the principle of keeping personal data adequate, relevant and limited to what is necessary. A note about a production problem can help answer an enquiry. Speculation about a visitor's personality, finances or private circumstances usually has no place in the record. Ask staff to write factual notes that the visitor could read without discovering an invented account of what they meant.

Our guide to permission for sharing attendee details with sponsors covers the organizer's wider planning. Keep the attendee-facing explanation aligned with what happens on the stand and afterwards. If a visitor asks for a document, staff should know how to fulfil that request without automatically enrolling them into every campaign the exhibitor runs.

Review quality while the event is still open

Give the exhibitor a chance to inspect a small set of its own records during the show. Ask whether another colleague could understand each request, identify the right response and see why the priority was chosen. This review can reveal missing context while the representative still remembers the conversation. It also allows the team to change a confusing question before using it for the rest of the event.

Look at differences between representatives with curiosity. One might record more requests because they ask a useful closing question. Another might have spent the morning supporting existing customers rather than finding new buyers. A scan leaderboard conceals those differences and encourages people to collect more scans. If you want useful conversations, reward accurate records and fulfilled requests. Don't make staff choose between treating visitors properly and hitting an arbitrary activity target.

When an exhibitor says the audience is wrong, ask which mismatch it is seeing. Visitors outside the service area, organizations too small for the offer and relevant businesses without active projects suggest different responses. Some findings may justify changing the event's audience messaging. Others may require the exhibitor to explain its offer more clearly or adjust its expectations. You need concrete examples before deciding which party should change something.

Decide what you can promise exhibitors

Be specific about the service in the stand offer. You might provide preparation guidance, a briefing for stand managers and a common way to record requests, depending on your actual arrangements. Each commitment needs an owner and a cost in your event budget. Helping exhibitors qualify conversations can improve the usefulness of what you deliver, but it also takes staff time. Don't sell detailed support across the whole exhibition if your team can only provide it to a small group.

It helps to distinguish access from outcomes in the agreement. An exhibitor can buy an exhibition space, agreed promotion or participation in a scheduled activity. Those deliverables can be checked. Whether a visitor has the right problem, chooses to continue a conversation or eventually buys depends on circumstances beyond your control. If you include an audience commitment, define what you will verify and how you will deal with a shortfall. A vague promise of quality leaves everyone arguing from different expectations afterwards.

During busy periods, the form must still allow staff to tell the truth. A representative who only had time to send a brochure shouldn't be required to invent a project stage before saving the request. Provide an honest incomplete state and let the exhibitor decide how to review it. Otherwise the pressure to finish the form produces answers that look complete in a report but fail as soon as someone tries to use them. Review whether required questions actually prevent useful records from being saved.

You also need a response when the exhibitor changes its criteria halfway through the event. Perhaps it learns that a different product is attracting interest or that its original service area was too narrow. Record the change and when it took effect. Apply the revised criteria consistently to records that can support them, and leave anything else unclassified until reviewed. Comparing results under different definitions without explanation can make an improvement look real when the team has simply started counting a different kind of conversation.

Ask for feedback you can actually use

Agree a review date with the exhibitor before everyone leaves. Ask how many contacts it reviewed, which requests it completed and which records its sales team accepted for further discussion. Give it a way to explain rejected classifications, including unsuitable organizations, insufficient context and requests that belonged with another department. Those reasons help you distinguish an audience problem from a recording problem or an internal handover that never happened.

Make participation and missing information visible when you combine feedback across exhibitors. AAPOR's survey research best practices support being clear about how you collected responses and who answered. If only some exhibitors return your questionnaire, report results for those respondents. Don't present their assessment as the view of every exhibitor. Keep the question wording consistent enough to compare results, while allowing comments that explain why a simple rating may conceal an important problem.

If an exhibitor volunteers the value of opportunities it associates with the show, ask what that value represents. A possible order estimated by a salesperson is different from an accepted quotation or collected payment. The contact may also have existed before the exhibition. Record whether the event introduced the business, helped an existing discussion or simply happened before the opportunity was recorded. You can acknowledge the event's contribution without claiming that every associated opportunity originated there or will turn into revenue.

Commercial comparisons need care too. An exhibitor selling long-term equipment contracts may review progress over a different period from one selling a simple service. Comparing their immediate sales totals can conceal those differences. Agree a suitable review point with each business and describe the observation period in the results. When an exhibitor hasn't reviewed its contacts yet, report that status. Missing feedback does not establish that the contacts were poor, and an unreviewed list should never quietly become a count of rejected leads.

Use aggregate results for the organizer's review wherever possible. You generally need to understand the kinds of conversations and the reasons they did or didn't progress, rather than receive every attendee's personal sales record. Agree any more detailed exchange separately. The sponsorship report guide explains how to connect delivery, evidence and commercial outcomes without claiming that every recorded interaction produced revenue.

Take one exhibitor through this process before building a show-wide reporting promise. Ask its sales manager to define a useful conversation, test the questions with its stand team and inspect the resulting records together. Then decide which parts you can support consistently for the next event. You'll have a specific service to explain, realistic responsibilities to agree and a clearer answer when someone asks what their badge scans were actually worth.