How to give exhibitors a lead capture process they can actually use

Your exhibitors have the app. Their staff have the instructions. Then the doors open, someone can't log in, another person saves a contact without a note, and the sales manager back at the office can't find the export. You offered lead capture, but the people doing the work still have to figure out the process themselves.

A usable process starts with the conversation and finishes when the right person receives an understandable follow-up task. Work through that whole journey before opening. Keep the information you ask staff to record small, let them practice with their own accounts, and make someone responsible for the records after the stand closes.

This exhibitor lead capture guide is for organizers running paid exhibitions and conference shows. It assumes you've already chosen how exhibitors will collect contacts. The work now is getting that arrangement used properly, including by the temporary representative who missed the briefing and the sales colleague who never attended the event.

Agree what exhibitors should be able to do

Start with an ordinary stand conversation. An attendee stops to discuss a product, asks for information and agrees how the exhibitor should send it. What does the representative need to record, and what should their colleague understand later? Write that result down before you write instructions about buttons.

For example, imagine a fictional paid foodservice exhibition. A commercial refrigeration supplier is demonstrating a cabinet. A restaurant operator asks whether it will fit a kitchen refurbishment and requests the installation requirements by email. The representative needs a suitable contact address, the cabinet discussed and the request. Recording a purchasing budget would add work without necessarily helping fulfill that request.

The exhibitor can have its own sales qualification process. Your official capture service needs to support a dependable basic exchange. Explain what staff can record, who can see it, how the exhibitor receives it and where help comes from. Set those expectations using the configuration you actually provide, including any license or account restrictions.

Keep the operational promise consistent with the commercial offer. If your exhibitor prospectus says contact capture is included, a representative shouldn't discover an unmentioned charge for the access needed to use it. Resolve package questions before training. Otherwise your support team will spend opening morning explaining a disagreement that started when the stand was sold.

There's a useful distinction between making the service available and making an exhibitor ready. An invitation email proves very little. A representative who can access the correct stand account, save a test conversation and retrieve the result has shown that the essential steps work. That's a much better preparation target for your team.

Put responsibility with people who will do the work

Ask each exhibitor to nominate the person managing its capture process. This might be the stand manager, an events marketer or a sales operations colleague. They need authority to confirm staff, agree the information collected and arrange delivery to the sales team. The person who signed the booking may have none of those responsibilities.

Then identify who will receive the records after the event. In our refrigeration example, the stand manager can organize the representatives, while a sales coordinator distributes requests to the right product specialists. Introduce that coordinator before the event. They should inspect a sample record while there's still time to change how staff collect information.

The organizer also needs one named person responsible for delivering the official service. That person manages the supplier relationship and unresolved issues. Floor staff can answer common questions, but they shouldn't have to negotiate with registration, the application provider and an exhibitor's sales department to work out who owns a problem.

Write down the practical boundaries. Your team can help an exhibitor regain authorized access and understand the supplied export. The exhibitor decides which employee contacts a prospect and whether that contact is appropriate. If an independent sales system rejects a file, agree who investigates its import rules. Clear responsibility prevents a routine technical question becoming everyone's problem and nobody's task.

Connect these contacts to your exhibitor onboarding checklist. You don't need another welcome sequence asking the same company who it is. Add the capture owner, actual users and receiving colleague to the preparation you already manage, then send the relevant instructions directly to those people.

Make account activation a completed task

An account invitation can reach the wrong inbox, expire or be blocked by an exhibitor's email settings. Ask users to activate access before they travel. Tell them how to recognize the legitimate invitation and where to ask for another one. Don't expect a busy representative to investigate an unfamiliar message while setting up a stand.

Use the access each person will actually have during the exhibition. An administrator demonstrating everything through their own account doesn't prove the representative can do the same. Check that the correct event and exhibitor appear, that required functions are available and that any device restrictions are understood. A successful login to an empty account still leaves work unresolved.

Have the exhibitor confirm its attending staff rather than forwarding a password around a company. When the service supports individual accounts, use them. It becomes easier to remove access when a representative changes and to identify who recorded a conversation. Where the service uses another arrangement, explain its limits and agree how the exhibitor will control access.

The US Federal Trade Commission's guide to protecting personal information recommends limiting access to people with a legitimate business need. Apply that to the lead list as well as the app. Someone hired to demonstrate a product may need to save a request without needing a download of every contact the exhibitor collected.

Keep activation status specific. You might know an invitation was sent, accepted or tested. Don't compress all those states into ready. If someone hasn't completed the test, contact the exhibitor owner with the outstanding action. This lets you direct support toward real access problems instead of sending repeated reminders to everyone.

Include shift changes in the account plan. The people demonstrating equipment in the morning may leave before the afternoon team arrives. Ask the exhibitor owner how a replacement representative gets access and where they find the current instructions. If adding someone needs supplier approval, disclose the cutoff and route for a late change. Don't leave a departing employee's account as the only practical way for someone else to work.

Decide the smallest useful conversation record

The record should explain who the attendee is, how to contact them for the agreed purpose and what happens next. The exact fields depend on the exhibition and the exhibitor's business. Start with the information required for an ordinary request, then consider which other questions genuinely change the response.

For the refrigeration supplier, the representative might select the cabinet range, record that the attendee requested installation requirements and note the contact address the attendee wants used. A sales colleague can act on that. A mandatory field asking for estimated annual spend may be hard to answer and irrelevant to sending the document.

Keep the attendee's request separate from the representative's judgment. "Asked for installation requirements" describes what happened. "Ready to buy" is an assessment needing evidence. If exhibitors use interest ratings, ask them to define those ratings and retain the underlying notes. Otherwise their sales team will receive confident labels that mean different things to different staff.

The UK Information Commissioner's Office explains data minimisation as keeping personal data adequate, relevant and limited to the purpose. That principle supports a useful form rather than an empty one. Collect enough to fulfill the request, but challenge fields added merely because the database can hold them.

Make the required fields possible to complete honestly. A representative may not know a visitor's purchasing timetable, and the visitor may not want to discuss it. Allow an appropriate unknown answer or leave the question optional where suitable. Forcing a selection encourages staff to invent certainty, which makes the export less trustworthy.

Free text deserves guidance too. Ask for a short explanation of the business request and avoid unrelated personal observations. A note about a kitchen's installation constraints can help the next conversation. A comment about the attendee's appearance cannot. Show one useful sample so representatives understand the level of detail you expect.

Let the conversation sound like a conversation

Don't train staff to interrupt every visitor with a form. Start by understanding why the person stopped. Once there's a reason to continue, the representative can explain what information they need and what they will do with it. The attendee should recognize the request they're agreeing to receive afterward.

In the example, the representative could say, "I can send the installation requirements for this cabinet. Which email should we use?" They can confirm the product while entering the note. That's a natural continuation of the discussion. Asking every visitor to complete a qualification interview before answering a simple question is harder to justify.

Explain what happens when someone doesn't want to share details. Staff should be able to provide whatever publicly available information the exhibitor has chosen to offer without treating refusal as a fault. A visitor might prefer to read the specifications online and contact the company later. Record only what the situation and your agreed policy support.

Avoid a script that promises more than staff can deliver. If a specialist must assess installation suitability, the representative shouldn't assure the attendee that a cabinet will fit. Record the question and route it for review. Useful capture preserves uncertainty so the colleague following up knows what still needs an answer.

The interesting part is how much better the note gets when staff understand the next person's job. They stop writing "send info" and start naming the information requested. You don't need a long script to achieve that. Let representatives read a vague record and try to respond, then compare it with a record containing the actual request.

An exhibitor running a prize draw alongside product demonstrations needs particular care. The visitor entering the draw may have no product request at all. Keep the purpose of that entry understandable and avoid making the sales team infer buying interest from it. If the same person later asks about refrigeration, record that conversation separately enough for the receiving colleague to see what happened. The prize draw's terms and any marketing choices still need their own approved handling.

Test the form with the people using it

Run the process on the devices exhibitors intend to bring. A form that looks comfortable on a laptop can be awkward on a phone held beside a demonstration. Check that staff can read labels, correct an address and save a note without losing what they already entered. Use an ordinary user account throughout.

W3C's form labeling guidance explains the need for labels that identify controls, including for people using assistive technology. Ask your supplier about the actual form, including required fields and instructions. A placeholder that disappears when someone starts typing isn't a dependable substitute for a proper label.

Try errors deliberately. Enter an invalid email format, leave a required answer blank and return to an unfinished record. The user should understand what needs attention and how to correct it. A general failure message gives your floor team little to work with, especially when the representative cannot tell whether anything was saved.

Include an alternative for a person who cannot use the proposed interaction. They may be unable to scan, unable to use a shared device or simply carrying something in both hands. Agree a supported way for staff to help record the request. Don't let an accessibility problem turn into pressure to use a particular phone or camera.

Pay attention to the confirmation after saving. Staff need to distinguish a completed record from an unfinished form or information waiting to upload. Have them show you how they know. If the answer depends on a subtle icon nobody noticed during practice, improve the explanation before you rely on it at the show.

Ask a representative who wasn't involved in setup to try the instructions. Let them find the correct event, start a record and locate the saved result while you watch. Resist explaining the missing step immediately. Write down where they stopped, then change the instruction or ask the supplier to resolve the difficulty. A colleague who already knows the application will unconsciously fill gaps that a temporary member of the stand team cannot.

Rehearse a complete request before opening

A dry run is most useful when it includes someone at the receiving end. Give a representative the fictional refrigeration conversation and ask them to record it without coaching. Then ask the receiving colleague what they would send and who should handle the installation question. Compare that answer with what the attendee requested.

Use invented contact details clearly marked as test data. You don't need real attendee records to find a missing note field or a confusing export. Agree how test records will be removed or excluded from reporting. Otherwise your training exercise can appear in exhibitor totals and give someone an unnecessary follow-up task.

Let the test continue beyond saving. Have the receiving colleague open the record through the route they will use after the event, whether that's an authorized account, an export or a supported connection. Check that the request, product and assigned person survive. A neat app screen doesn't help if the file drops the only useful note.

Next, change something ordinary. The attendee wants a different contact address from the one initially displayed. Another representative has a later conversation with the same person. A staff member edits a note. Find out whether those actions preserve the information the exhibitor needs, and explain the behavior in the training.

Finish the rehearsal with an actual response drafted to the test contact. Does it mention the cabinet discussed and supply the requested requirements? If the colleague has to call the stand to reconstruct the conversation, change the record or instructions. The dry run has found a problem while you can still do something about it.

For the refrigeration example, a suitable test response might introduce the sales coordinator, identify the cabinet demonstrated and attach or link the installation requirements. It would say that the installation specialist will review the kitchen question if that's what was agreed. It wouldn't announce an installation date or describe the attendee as a committed buyer. Read that response against the saved note. The comparison exposes assumptions much more clearly than checking whether every field contains text.

Prepare for the failures your staff can recognize

Choose a fallback with your supplier before the exhibition. If connectivity fails, representatives need to know which actions still work and what the screen will show. Some tools can retain records for later upload; others cannot. Teach the verified behavior of your setup rather than relying on the word offline in a sales description.

Ask staff to demonstrate reconnecting and confirming that waiting records have arrived. Don't tell them to sign out, reinstall the app or clear local storage unless the supplier has confirmed that doing so is safe for unsent information. A well-intended troubleshooting step can make recovery harder if the device holds the only copy.

A paper fallback needs an owner too. Decide what staff may write, where they keep it, who enters it into the approved system and how the original is handled afterward. Avoid loose sheets left beside a public demonstration. Collecting fewer fields makes the fallback easier to use and reduces what can be exposed if someone misplaces it.

Explain what to do when staff can't find a saved contact. They should check the correct account and any waiting upload status before repeatedly creating a new record. Give your help team the details needed to investigate without asking exhibitors to post personal contact information in a public group chat.

For a lost phone or suspected unauthorized access, the representative needs a different reporting route from an ordinary forgotten password. Tell them whom to contact immediately and who can remove access. The organizer's service owner should know how to reach the supplier during opening hours, including when the regular account manager isn't available.

Give floor support a way to close problems

Your help team needs the same working setup and instructions as exhibitors. Give staff a test account or another supplier-approved demonstration route so they can reproduce common issues. They shouldn't borrow a real exhibitor login and inspect its contacts merely to understand where a button appears.

Record the exhibitor, affected user, device, issue and time, along with whoever is investigating. Keep attendee information out of the issue log unless it's necessary and the log is appropriate for it. An error screenshot may contain more personal information than the help desk needs, so ask staff to check before sharing.

Separate an explanation from a repair. A missing field might be outside the event's sharing arrangement, while a record stuck waiting to upload may need technical attention. Your support instructions should help staff recognize those situations and route them correctly. Telling every exhibitor to restart the app doesn't answer either question.

Close a ticket only when the exhibitor confirms the relevant action works or the team has clearly explained an actual limitation. A supplier saying fixed isn't enough if the representative is still unable to save. This is ordinary event operations applied to a service that exhibitors depend on during commercial conversations.

If several stands report the same fault, tell the service owner and send one clear notice to affected users. Explain what they can do now and when the next information will arrive. Avoid repeated speculative fixes from different team members. Exhibitors need a dependable answer while their representatives continue speaking with visitors.

Brief replacement staff during the event too. A stand manager may swap someone in after lunch who has never seen the original email. Keep the immediate instruction short and accessible through an approved location. Show that person how to confirm a record was saved and how to get help. Ask them to complete a test before they take over capture. The organizer can provide the material, but the exhibitor owner needs to make that staff handover happen.

Confirm the records reached the sales team

Don't wait until exhibitors have packed up to test delivery. Ask each capture owner to review a small sample during the show, using its permitted access. Can the receiving colleague find the requested action and identify the representative who spoke to the attendee? This catches problems while memories are fresh and staff are available.

An export deserves a real inspection. Check what happens to accents, line breaks, empty values and conversation notes when the receiving system opens the file. Confirm that a field such as requested contact date remains understandable. If a connected import is part of the offer, test the imported result rather than assuming an accepted file means correct delivery.

Keep contact details and conversations distinct when resolving duplicates. The refrigeration attendee may ask one representative about a cabinet and another about service cover for existing equipment. Combining the contact can be useful, but losing either request creates a problem. Agree how the exhibitor will preserve both discussions before someone starts tidying the data.

Assign a receiving owner for requests that cannot be distributed automatically. The export may contain a product interest but no employee name, or the intended colleague may be away. Someone needs to review those records and decide where they go. An unassigned request can remain untouched even when every technical transfer worked.

Tell exhibitors when access ends and what happens to stored information under the agreed arrangement. Remind the responsible contact while there's time to retrieve the permitted records. Closing the show, downloading a file and ending supplier storage are different events. Each needs the right action from the person who controls it.

Set expectations for response timing with the exhibitor before the show. Some requests can be answered while the exhibition is running; others need a specialist back at the office. The representative should communicate the timing the business can actually meet and record any specific agreement. A visitor expecting installation information tomorrow will judge a response differently from someone told the specialist returns next week. The organizer shouldn't promise a universal response deadline on every exhibitor's behalf.

When the receiving colleague finds a problem, agree how it returns to the person who can resolve it. An unreadable product note might go back to the representative. A missing field across the entire export needs the service owner. Keep those corrections with the request so staff don't each make a different guess. Once the issue is resolved, confirm the usable record reached the receiving colleague before considering the request ready for action.

Before staff leave the venue, have the exhibitor owner check any device that might still hold unsent records. A representative can reasonably assume closing the stand ends their task, especially if they are hired only for the day. Explain that they must confirm delivery before returning equipment or removing access. Where personal devices are permitted, agree how the supplier handles locally held information afterward. This should follow the approved retention and security arrangement, with a named person available to answer questions rather than improvised instructions at the loading entrance.

Keep requests and marketing choices understandable

A request for installation requirements tells the exhibitor something useful about the next response. It doesn't automatically settle every question about adding that person to a marketing audience. Record the request and any separate marketing choice according to the arrangement your privacy reviewer has approved, then preserve that distinction when the information moves.

For UK activity, the ICO's business-to-business marketing guidance distinguishes corporate subscribers from sole traders and certain partnerships. Named business contacts can still involve personal data obligations. Make sure whoever designs the follow-up understands the recipient and channel rather than assuming a company email address resolves everything.

For US commercial email, the FTC's CAN-SPAM compliance guide makes clear that business-to-business messages are covered too. Have the exhibitor apply the requirements relevant to the message it actually sends. A sales colleague shouldn't classify an email as purely transactional just because its recipient visited the stand.

Operationally, the organizer needs the form, attendee explanation, exhibitor instructions and delivered record to agree. If the form records one choice but the export replaces it with a general subscribed label, investigate before sending. Technical convenience is a poor reason to discard the distinction a person was asked to make.

Give staff a contact for privacy questions they cannot answer. They can explain the approved process and help someone find the relevant information. They shouldn't invent a legal assurance during a busy stand conversation. A correction, objection or deletion request also needs a route to the party responsible for handling it.

Explain the process to attendees where it happens, in words that match the actual arrangement. A short notice beside the collection point can identify the exhibitor receiving information and direct people to the full explanation. Staff still need to answer the immediate question about what follows. Check the wording on the device as well as printed material, because an old form description can contradict an otherwise correct briefing.

Review whether exhibitors could actually use it

After the event, ask about the process separately from the exhibitor's sales result. Could staff activate access, record requests and receive usable information? Where did they need help? A successful contract doesn't prove the service was easy to use, and a disappointing sales outcome doesn't establish that capture failed.

Look at unresolved support issues and a small set of permitted, appropriately handled examples with the exhibitor. Find the reason a record became unusable. Was the address wrong, the note missing, the assignment unclear or the export incomplete? Each points to a different correction. Another training email won't repair a field that never reaches the receiving system.

Avoid measuring staff only by the number of contacts saved. That can encourage scanning people who never requested follow-up while giving careful conversations too little recognition. If you report capture totals, explain what they count. Keep saved contacts, requests assigned and completed responses separate so exhibitors can understand their own results.

Start the next edition by correcting the recurring problem your review found. Simplify an unnecessary question, change an access instruction or test a repaired export with the receiving colleague. Then ask a representative to complete the whole refrigeration conversation again. When the colleague can understand the request and act without calling the stand, you've got a process worth asking exhibitors to use.