Meeting Booking

A trade show appointment scheduler that starts before the show and finishes after the meeting.

Invite target contacts to your booth before the event, book meetings on the spot while you are still talking to the visitor, and record the outcome of each one afterwards. Meeting records and outcomes sync to HubSpot or Salesforce. Works the same whether your team calls it a trade show, a conference, or just "the event."

TL;DR: BoothMaven covers meetings from two directions. Before the show, select contacts from your list, choose the event and booth, and send a booth-visit invitation with Yes I'll visit, Maybe and Can't make it responses. During the show, book a meeting from the visitor's contact record with a date, time, duration, type and location. Afterwards, record the outcome as Done, Rescheduled, Cancelled or No Show, with optional notes and a voice recording. Both routes produce the same meeting record, and both sync to the CRM.

Invite before · book on the spot · record after RSVP tracking with reminders HubSpot & Salesforce meeting sync
Meetings & RSVPs Live
Meetings RSVPs
25 RSVPs · NextGen Tech Conference
Daichi Yang · Société Générale Accepted
Booth West Hall – 302 · Responded 09:30 AM
Sophie Jensen · Cognizant Maybe
Booth D-455 · Responded 09:31 AM
James Wu · Rockwell Automation Awaiting
No response yet · 73 hrs · Reminder available
Yumi Weber · Cisco Declined
Booth West Hall – 302 · Responded 09:24 AM
Remind anyone still awaiting a response. Mark as visited when an accepted contact reaches the booth.
RSVPs panel · accepted · maybe · awaiting · declined
What it does

Most meetings at a show are discussed and then never booked.

A conversation ends with "let's set something up," and the follow-up email goes out a week later, if it goes out at all. BoothMaven covers both ends of that problem. Before the show, exhibitor meeting software invites the contacts you want to see and tells you who is planning to come. During the show, you book the meeting while the visitor is still standing at the booth. After the meeting, you record what happened, so the CRM shows a meeting that took place rather than a lead that went quiet.

Two ways in, one meeting record out. An invitation that gets a Yes, and a booking made on the spot, both lead to the same place.

The two flows are not separate tools bolted together. A booth-visit invitation answered before the show tells you who is coming, and a meeting booked at the booth produces the meeting itself against the contact, tied to the event and the booth, with a status that can be updated afterwards. That matters because it means the team does not have to reconcile two lists, and the outcome sync carries to the CRM either way.

Where meeting booking falls apart

The conversation ends and nothing gets booked.

"Let's set something up" is not a meeting. By the time the follow-up email goes out, the visitor has been to thirty other booths and the context is gone.

No idea who is actually coming.

Pre-show outreach goes out and responses scatter across inboxes. Nobody knows how many target contacts are planning to visit, so the booth cannot be staffed or prepared around it.

Generic scheduling tools lose the event context.

A booking link that works for any meeting in the calendar does not record which show the meeting belongs to, which booth it happened at, or what the outcome was.

The CRM never learns the meeting happened.

The meeting sits in a personal calendar. The contact record in HubSpot or Salesforce shows a lead that was scanned and then went nowhere.

Where BoothMaven fits

Booked before the visitor walks away.

The rep books the meeting from the contact record with a date, time, duration, type and location, so the commitment is made during the conversation.

You know who is coming before doors open.

Booth invitations carry Yes, Maybe and Can't make it responses. Accepted, declined and awaiting-response contacts are all visible in one RSVPs list.

Every meeting carries its event and booth.

The meeting record holds the event, the booth, the host and the participants, so the meeting is attributable to the show that produced it.

Outcomes reach the CRM.

Marking a meeting Done, Rescheduled, Cancelled or No Show syncs to HubSpot or Salesforce as activity on the contact, with notes and voice recordings attached.

Know who is coming before the doors open.

Select the contacts, choose the event and booth, and send a booth-visit invitation with Yes, Maybe and Can't make it responses. Responses arrive back in the RSVPs list, and a reminder can go to anyone still awaiting a reply.

Booth meeting software for the conversation itself.

The rep books during the conversation, not after. Duration, type and location all sit on the record, so a fifteen-minute stand meeting and a scheduled demo room session are distinguishable.

The outcome is the point.

A meeting that happened and a meeting that did not are different facts. Recording Done, No Show or Rescheduled is what turns a booked slot into something the CRM can act on. See CRM sync for how the write works.

What a meeting carries

The fields that make a meeting reportable.

A meeting record is more than a name and a time. These are the fields captured on each booking, and each one answers a question the team asks after the show.

Date and time

When the meeting is scheduled for. On a show day this usually means the next slot, or a specific hour the visitor has free.

Date · Time

Duration

How long the meeting is expected to run. A 15-minute stand conversation and a 30-minute demo room session are different commitments.

Minutes

Type and location

Whether the meeting is in-person or virtual, and where it takes place — the booth itself, a demo room, or a hotel lounge.

In-person · Virtual

Host and participants

Which rep is hosting, and who is attending from the visitor's side, with their role and company recorded.

Host · Attendees

Agenda

A short note on what the meeting is for, so whoever picks up the meeting — or the CRM record — knows the purpose without asking.

Free text

Booking information

Who booked the meeting, when, by which method, and its current status. Useful when several reps are booking into the same event.

Booked by · Method · Status

Outcome

What happened afterwards: Done, Rescheduled, Cancelled or No Show. This is the field the CRM sync acts on.

Done · No Show · Rescheduled

Notes and voice recording

Optional meeting notes typed at the outcome screen, plus the option to record a voice note so the context is captured while it is fresh.

Text · Voice

Every field exists to answer a question after the show. Date and time answers whether the meeting was on day one or day three. Type answers whether it was a stand conversation or a proper demo. Booking method answers whether it came from an invitation or a rep. Outcome answers whether it happened at all. Without these, a meeting count is just a number. Meeting records and their outcomes sync to HubSpot and Salesforce as activity.

The three capabilities

Invite. Book. Record.

Three parts to the flow: inviting the contacts you want to see before the show, booking the meeting during the conversation, and recording what happened afterwards.

Invite · before the show

Select the contacts, choose the event and booth, and send a booth-visit invitation.

This is a booth-visit invitation, not a meeting slot. The team picks the contacts to invite from the contact list — with anyone previously invited for the same event already flagged, so the same person does not get two invitations. Then they choose which event and which booth the invitation refers to, add an optional personalised line, and preview the email before sending. The invitation carries three response buttons — Yes I'll visit, Maybe and Can't make it — and the responses land in the RSVPs list, which is where the accepted, maybe, declined and awaiting statuses live. Anyone who has not replied can be sent a reminder, and when an accepted contact arrives at the stand, the rep marks them as visited.

  • Contact selection from your list, with already-invited contacts flagged
  • Event and booth selection, with date, venue and booth number on the invitation
  • Optional personalisation line before the send
  • Yes I'll visit, Maybe and Can't make it responses
  • RSVPs list with Accepted, Maybe, Declined and Awaiting reply filters
  • Reminder to anyone still awaiting a response
  • Mark as visited when an accepted contact reaches the booth
  • The response link can be copied into any email tool, and Zapier connects BoothMaven to the rest of your stack
Book · on the spot

Book the meeting from the contact record, while you are still talking to the visitor.

A trade show meeting scheduler built for the conversation at the stand, not the email after it. The rep opens the visitor's contact record, taps Book Meeting, and sets the date, time, duration, type and location. The meeting then appears in the Meetings tab with a status of Upcoming, and the full record — Meeting Details, Host and Participants, Agenda and Booking Information — is available from the mobile app. Meeting type distinguishes an in-person stand conversation from a virtual meeting, and location captures whether it happened at the booth itself or somewhere else at the venue. A commitment made in the moment is worth more than one made by email a week later.

  • Booked from the contact record during the conversation
  • Date, time, duration, type and location on every booking
  • In-person or virtual meeting type
  • Host and participants recorded, with role and company
  • Optional agenda so the purpose travels with the meeting
  • Booking information — who booked, when, and by which method
  • Meeting status of Upcoming until the outcome is recorded
Record · the outcome

Mark what happened — Done, Rescheduled, Cancelled or No Show — and it reaches the CRM.

A booking is a prediction. The outcome is the fact. After the meeting, the rep opens Update Status from the Meeting Detail screen and picks one of four outcomes: Done, Rescheduled, Cancelled or No Show. The screen also takes optional meeting notes and, on the full version, a voice recording, so the substance of the conversation is captured while it is still fresh. The outcome then updates the meeting record and syncs to HubSpot or Salesforce as activity on the contact. A No Show is not a dead end — it is a fact worth recording, because a contact who accepted a meeting and did not appear is a different follow-up case from one who was never invited.

  • Four outcomes: Done, Rescheduled, Cancelled, No Show
  • Optional outcome detail and meeting notes at the same screen
  • Voice recording option so context is captured in the moment
  • Status updates the meeting record immediately
  • Meeting outcome syncs to HubSpot or Salesforce as activity
  • Meetings list filterable by Scheduled, Rescheduled, Done and Cancelled
Why it compounds

A meeting booked is a meeting the CRM can see. Across shows, the pattern builds.

One meeting is a conversation. A record of meetings across several events, with their types and outcomes, tells you which shows produce real conversations and which produce noise.

Accepted invitations tell you how to staff the booth. If nine of twenty-five invited contacts accept and twelve are still awaiting a reply, the booth team knows how the day is likely to run before the doors open — and can send a reminder to the twelve while there is still time.

The outcome separates the meetings that happened from the ones that were hoped for. A meeting list full of Upcoming statuses is a plan. A list with Done and No Show statuses is a record. Only the record can be reported on, and only the record can be synced onward to the CRM as something that actually took place.

Booking method and meeting type accumulate into a picture. Over several events, the split between invitation-driven meetings and rep-booked ones shows which channel produces conversations that actually happen, and whether the fifteen-minute stand meeting or the thirty-minute demo room session converts better.

For the outreach that fills the invitation list, see event-based outreach. For how meetings sit inside the wider field programme, see field marketing.

Three
stages in one flow — invite before, book on the spot, record the outcome after
Four
outcomes on every meeting — Done, Rescheduled, Cancelled, No Show
Five
RSVP states tracked — Accepted, Maybe, Declined, Awaiting reply, Visited
Synced
to HubSpot and Salesforce as activity on the contact record, with Zapier for everything else
Meeting booking · FAQs

Trade show meeting booking, answered.

The questions exhibiting teams ask about inviting contacts, booking at the booth, and recording what happened.

Booking meetings at an event

What is on-spot meeting booking at a trade show?

On-spot meeting booking is scheduling a follow-up meeting with a visitor during the conversation at the booth, rather than after the show. The rep opens the meeting form from the visitor's contact record, sets the date, time, duration, type and location, and saves. The meeting is committed before the visitor has walked away from the stand, rather than depending on an email that may or may not get a reply.

How does a pre-event booth invitation work for exhibitors?

The exhibitor selects a set of contacts to invite, chooses the event and the booth the invitation refers to, and sends a booth-visit invitation email containing a Yes I'll visit, Maybe and Can't make it response. Responses appear in the RSVPs list, where the team can see who accepted, who declined, and who has not yet replied, and can send a reminder to anyone still awaiting response. The RSVPs list is where the accepted, maybe, declined and awaiting statuses live. When a contact who accepted arrives at the booth, the rep marks them as visited.

How do you book meetings at a trade show?

Two things happen at different times. Before the show, invite target contacts with a booth-visit invitation so you know who is planning to come. During the show, book the meeting itself from the visitor's contact record while you are still talking to them. The invitation is a booth visit, not a meeting slot; the meeting is booked in person at the event, and is recorded against the contact and the event.

Is this a Calendly replacement for trade shows?

No, and it is not trying to be. Calendly is a general-purpose scheduling tool that gives a contact a link to pick a slot in your calendar. Calendly for trade shows is a narrower job: booking a meeting with a specific visitor you are standing in front of, recording which event and booth the meeting belongs to, and capturing the outcome so the CRM reflects what happened. Both can coexist, and the choice usually comes down to whether the meeting needs to carry event context.

What happens after a meeting is booked?

The meeting appears in the Meetings tab with a status of Upcoming. After the meeting takes place, the rep updates the outcome from the Meeting Detail screen, choosing Done, Rescheduled, Cancelled or No Show, optionally adding notes and a voice recording. The meeting record and its outcome sync to HubSpot and Salesforce as activity on the contact.

Does this work for conferences and other event types, not just trade shows?

Yes. Meeting booking and booth invitations work the same way regardless of what the event is called. A conference meeting scheduler works the same way a trade show one does: choose the event, choose the booth, invite the contacts, and record the outcome of each meeting afterwards.

Ready when you are

Invite before. Book on the spot. Record what happened.

Booth invitations with RSVP tracking before the show, meeting booking from the contact record during it, and outcomes that sync to HubSpot or Salesforce afterwards.

Booth invitations · RSVP tracking · On-spot booking · Outcome recording · HubSpot & Salesforce sync