Trade show meeting bookings: organize times, owners, and commitments

Separate interest in a meeting from a confirmed booking

A trade show meeting is confirmed when the visitor and the assigned colleague agree on its purpose, time, location or joining method, and contact route. Keep tentative requests separate from accepted appointments.

A visitor saying we should talk later is a useful signal, but it is not an appointment. Staff need to know whether the person requested a booth conversation, accepted a specific time, or simply wanted someone to contact them after the show. Treating all three as booked meetings creates confusion at the booth and produces calendar invitations that the visitor does not recognize. Record the stage of the agreement in ordinary words.

Use a small shared process alongside your team's calendar. The lead record should explain why the meeting exists and who owns it; the calendar should carry the accepted time and joining details. Neither replaces the other. A time slot without the question leaves the host unprepared. A detailed note without a confirmed slot leaves the visitor unsure when or where to arrive.

Choose the meeting purpose before offering a slot

Ask what the visitor needs from the conversation. A brief product question, a technical assessment, and a discussion involving another stakeholder need different hosts and preparation. Confirm the question in one sentence before reaching for the calendar. That sentence also gives the visitor an easy way to correct your understanding. If the requested information can be sent directly, offer that option rather than booking a meeting by default.

For a technical discussion, capture the condition that needs checking and the information the specialist will require. For a buying conversation, record what the visitor actually wants to compare. Do not invent a budget, approval role, or purchase date simply to make the booking look complete. An appointment can have a clear purpose while several commercial details remain unknown.

Offer only time your team can genuinely cover

Before opening, identify which colleagues can host each kind of meeting and which periods must remain free for booth coverage. Reserve time between appointments for notes, overruns, and movement across the venue. Use your own rehearsal to decide the spacing rather than assuming every consultation lasts the same number of minutes. A schedule that fills every available minute leaves no room to serve visitors who arrive without an appointment.

One person should check availability before confirming a slot. Staff can collect preferences, but two people should not independently promise the same host at the same time. Use a shared calendar or another clearly agreed scheduling record. If availability cannot be checked immediately, say that the time is a request pending confirmation and tell the visitor who will confirm it.

Confirm the practical details in one message

A usable confirmation contains the purpose, date, time, time zone where relevant, expected duration, host, location or joining method, and a way to report a change. At a large venue, booth number alone may not identify the meeting point. Describe whether the visitor should go to the reception counter, a consultation table, or a separate meeting room. For a remote follow-up, check the link before sending it.

Ask the visitor to confirm the proposed arrangement. Silence should remain a pending response rather than being converted into a confirmed booking.

A confirmation message you can adapt

Example wording: Thank you for visiting us at [event]. We agreed to discuss [question] with [host] on [date] at [time and time zone]. Please meet us at [location or joining method]. We have set aside [duration]. If your plans change, reply to this message and we will check another time. Please confirm that these details work for you. Adjust the wording to match what was actually agreed, and do not send a confirmed-style message while the host is still unavailable.

For a tentative request, use different wording: I have noted your preference for [time]. [Owner] will check the host's availability and confirm by [time]. Please treat the slot as provisional until you receive that confirmation. The distinction is especially useful when staff are collecting requests during a rush and the person managing the calendar is handling another appointment.

Give the host a short preparation note

The person who collected the booking may not host it. Send the host the visitor's name and company, the original question, what has already been shown or sent, and any unresolved detail that affects preparation. Include whether other colleagues will attend. Keep speculation separate from confirmed information. If the visitor's role is unknown, the host should learn that before the meeting rather than receiving an invented decision-maker label.

A fictional handoff might say: [Visitor] asked about fitting the review workflow into two regional teams. Saw the short demo; has not received the technical overview. Wants to understand ownership and handoff. [Host] will discuss the workflow at [time]. Integration conditions remain to confirm. This note helps the host begin with the visitor's actual question instead of restarting the entire booth introduction.

Handle changes without leaving two active promises

When either side requests a change, check a replacement time before announcing it as accepted. Update the shared calendar and the lead note together. Mark the earlier arrangement as superseded so another staff member does not guide the visitor to the old appointment. If the host changes, introduce the replacement and make sure the new person has the same preparation context.

Do not try to recover an overrun by silently shortening the next person's meeting. Explain the delay and offer the visitor a choice: wait for an agreed period, speak to another appropriate colleague, or schedule a new time. Keep the original request visible so a change of format does not accidentally remove the question the visitor came to discuss.

Coordinate appointments and walk-in visitors

A booked visitor should be easy to recognize without forcing every walk-in to go through a complicated booking process. Give staff a simple reception question and a way to check the host. Avoid reading personal details aloud across the queue. A separate meeting point can help appointments start while other staff continue QR registration, short explanations, or business card capture.

During a rush, explain the available paths: a quick answer now, a longer consultation when a host is free, or an agreed follow-up after the event. Do not use the booking list as a measure of every visitor's value. Someone without an appointment may have an important question, while a booked meeting may turn out to have no further action. The process should preserve access and context rather than assign importance by arrival format.

Keep the agreement in BoothCatch and the time in your calendar

Capture the visitor through the appropriate intake route, then record the meeting purpose, agreed arrangement, and remaining questions in the note. Assign one owner for confirmation and put the next confirmation or preparation task in the next action. Use the follow-up status for the work completed so far. A request waiting for a time is still unfinished work, even if a draft invitation exists.

Use your team's calendar to arrange and send the appointment. BoothCatch provides the lead context and responsibility record for this workflow. At closeout, review records with open meeting requests and check that each has a named person responsible for the next message. If exporting to CSV, remember that the event export includes all leads; select the relevant meeting records in your working file after export.

Check the booking before calling it complete

A calendar entry is a starting point for verification, not proof that both sides share the same agreement. Review one booking from the visitor's perspective and another from the host's perspective. Each should be able to identify the purpose, arrival or joining method, and change route without asking the booth team for clarification. Correct pending arrangements before publishing them as confirmed meetings in a results report.

• The visitor accepted the proposed time and purpose.
• The host is available and has accepted responsibility.
• The time zone and location are unambiguous.
• The host has the original question and relevant context.
• Changes update both the calendar and the lead note.
• An unresolved request has a next action and owner.

Frequently asked questions