The planning essentials
A controlled lead flow explains how a visitor moves from the first conversation to the right specialist and what a host may record along the way. Define qualifying questions, clear stopping points, approved fields, the relevant lawful basis, ownership of follow-up and a close that does not promise more than the sales organisation can deliver. Adapt the process to the exhibitor's actual data setup.
Define what a handoff means for this exhibitor
At a trade show, ‘pass the lead on’ can describe several outcomes. Some visitors need an available specialist now. Others may request an approved follow-up route after the show. Another person may only want public material. Define the possible closes so hosts do not have to invent the moment when a useful conversation becomes a data-capture exercise.
Use the visitor's expressed need and observable question rather than a hidden judgement about the person. A host can identify the subject, confirm it and offer an approved next step. Qualification, advice and commercial commitment stay with the exhibitor team. This boundary makes the role easier to train across shifts, languages and a mixed international audience.
Draw a flow that includes respectful stopping points
A good lead flow makes it easy to close when the visitor does not want further contact. The host opens, clarifies interest, selects an approved route and confirms the next step. If there is no relevant fit, the exchange can end politely without capture. A process with only a forward sales path encourages staff to collect details without a clear need.
Provide a fallback for an occupied specialist or unavailable tool. It might be a public contact route or approved material. The host should not create a temporary list on a private device or personal notes. If the authorised process is unavailable, the booth should be able to pause capture while continuing to welcome and help visitors appropriately.
Give each role one bounded decision
The host or brand ambassador owns first contact and the agreed transition language. The specialist owns substantive answers and commercial assessment. The exhibitor's responsible data function owns purpose, fields, information and access. The booth lead owns live staffing and operational changes. Without these boundaries, the host becomes salesperson, lawyer and system administrator without the authority or context for any of them.
Create a small role card for live use. Show who accepts each subject, how availability is indicated and whom staff contact when uncertain. Avoid listing the exhibitor's entire organisation. Hosts need a functional path from a visitor's real question to a person who can take responsibility on the stand or through the approved follow-up process.
Limit capture to the defined purpose
The EU General Data Protection Regulation sets out principles including lawfulness, transparency and data minimisation. A generic booth template cannot decide the exhibitor's lawful basis. The exhibitor must define purpose and processing, while the operational flow helps staff use only the fields and information that the authorised process contains for that specific purpose.
Remove speculative free-text fields that have no fixed need or responsible recipient. Free text invites subjective descriptions of visitors and makes the next action harder to interpret. Use controlled categories requested by the receiving team and a field for the visitor's expressed request. Do not capture information about another person merely because the visitor mentions them during conversation.
Lead flow from first contact to close
The exhibitor must validate purpose, information, system and responsibilities before using the flow.
- Open the conversation
- Use an approved question that helps the visitor without pushing towards capture.
- Clarify the need
- Match the expressed subject to a specialist, follow-up route, material or close.
- Inform at capture
- Use the exhibitor's approved solution, fields and information for the stated purpose.
- Hand to an owner
- Assign the next action to a named function without making an unauthorised promise.
- Confirm and close
- Tell the visitor what will actually happen, or finish without capture.
Make information understandable at the moment of capture
The exhibitor should provide the information relevant to the chosen processing through its approved solution and in language the intended audience can understand. Hosts need to know where that information is, but they should not improvise a legal explanation. Route questions about processing or rights to the contact the exhibitor has designated for them.
Distinguish a visitor voluntarily sharing a business card, using a badge scan and requesting a specific follow-up. The physical actions may feel similar, yet the purpose and information may differ. The brief should state the approved path for each tool. Access to a data point does not by itself tell booth staff that it may be used for every later activity.
Build an accountable handoff into sales
A handoff finishes only when the receiving function can see the next action and its owner. If a specialist joins on the booth, the host provides a short neutral introduction and steps back. If follow-up happens later, the approved system should carry the subject, requested contact path and person or queue responsible for receiving the action.
Do not promise a response time, meeting or solution unless the exhibitor has explicitly authorised it and can deliver it. Hosts can state what will actually happen: the request is recorded in the approved channel, or the specialist is joining now. This sets an accurate expectation and lets the team assess completed handovers rather than vague promises.
Decision summary: design a bounded lead flow
Use this summary to agree where the host's task ends and sales ownership begins. Responsible functions should approve the flow, information and capture process. Confirm the final choice in the shared live brief before the team follows it.
- Criterion: Define the specific interest or request that triggers a handoff to the sales function.
- Choice and stopping: Make it easy for visitors to understand capture, decline it or end the conversation.
- Receipt: Name the function receiving the lead and how a failed transfer becomes visible for action.
Planning questions
What information should the host capture?
Capture only fields with a defined purpose in the approved process. Explain the capture at the contact point and route questions about basis or retention to the data owner.
What if a visitor wants a conversation but no registration?
Design a respectful stopping option. The host can close without capture or point to public material when the exhibitor has approved that route.
How should we test the lead flow before the show?
Rehearse varied conversations, including uncertain interest, an unavailable salesperson and declined capture. Note missing ownership or wording, then ask the responsible functions to decide the correction.
Sources
- EUR-Lex: Regulation (EU) 2016/679
The limited references to lawfulness, transparency and data minimisation principles and the need for a lawful basis.
This is operational planning guidance, not legal advice. The exhibitor is responsible for defining purpose, lawful basis, information, access, retention and follow-up for the actual lead process.