·6 min readtrade showpre-show meetingslead generationoutreach

The Trade Show Starts Before the Doors Open — Booking Meetings in Advance

Leaving your best leads to walk-by traffic is leaving them to luck. A D-30 outreach timeline, meeting-slot logistics, no-show handling, and how pre-booked meetings feed into on-site records.


Teams that do well at trade shows walk in on opening morning with a meeting schedule already filled. The difference between a team that leaves booth traffic to chance and one that invited the companies it wants to meet shows up clearly in the lead list on closing day. This guide covers a pre-show meeting strategy starting a month out (D-30): who to contact, when and how, and how to handle the meetings you land on a busy show floor.

Why a booked meeting beats walk-by traffic

Visitors you meet by chance are plentiful but uncontrollable. Pre-booked meetings are the opposite.

  • Pre-qualified: someone who accepted your invitation has already shown interest. You start the conversation halfway through qualification.
  • Prepared: you can research the company and bring tailored material. The depth is different from an improvised aisle conversation.
  • Time under control: deep conversations can be scheduled into quiet hours, untouched by peak-time crowding.

This isn't an argument to ignore walk-by traffic. The stable structure is a floor of booked meetings with on-site leads layered on top.

Who to contact — building the invitation list

Around D-30, build the list of companies you want to meet. Four sources:

Source What it gives you
Current pipeline Prospects in the region or industry — "shall we meet at the show?" is a natural re-engagement pretext
Past event leads Warm leads from last year or the last show — a chance to raise the temperature again
Organizer materials Exhibitor directory and pre-registered visitor information, within what the organizer provides
Wish-list accounts Companies you've wanted to reach — a trade show is one of the few occasions when cold outreach gets warmer response rates

Prioritize over volume. Split the list into ten must-meets and thirty nice-to-meets, and spend your personalized effort on the must-meets.

When and how — the D-30 timeline

  • D-30 to D-21: first touch. "We're exhibiting at ___ — could we have 15 minutes at our booth?" Booth location, one new thing you'll be showing, and the meeting ask, kept short. No reply yet is normal.
  • D-14: second touch, with something new — a photo of the product you'll show, an on-site event. A reminder needs fresh content or it reads as spam.
  • D-7: reconfirm time and booth location with confirmed contacts; a final offer to the undecided.
  • D-1: a one-line reminder for confirmed meetings, and put every meeting on the staff rotation plan.

The writing principles — short, about them, one clear next step — are the same as in our follow-up email guide; only the direction changes, from after the show to before it.

Running meeting slots without the floor collapsing

Booking meetings is easier than honoring them.

  • Generous slots: 15–20 minutes each, with a 10-minute buffer between — show-floor travel always runs late.
  • Avoid the peaks: keep crowded windows for walk-by response; place meetings in the early morning or the afternoon lull.
  • Named owners: assign a specific person to each meeting on the rotation plan. "Whoever's free" means no one prepares.
  • Expect no-shows: some fraction won't come. Convert the slot to floor time on the day, and follow up after the show with "sorry we missed each other — here's what we'd prepared."

Record booked meetings like any other lead

The trap with pre-booked meetings is skipping the record "because we know them." The opposite is true: a prepared meeting produces the most concrete content, so log temperature, discussion points, and next actions in the same system as walk-up leads — otherwise your best conversations miss the post-show priority list. What the first day after closing should look like is in the first 24 hours guide.

From invitation to record in one flow — TagBooth

Leads from booked meetings and leads from chance encounters have to end up in one list. With TagBooth, one tap opens a 30-second logging screen with temperature, rating, and interest chips, and business cards are captured from a single photo by AI. You can even send invited contacts your visitor page — company introduction and brochures — as a link before the show.

When the event ends, a report with daily and hourly charts and the temperature distribution builds itself, letting you compare how booked meetings performed against walk-up leads. Try the logging screen and visitor page in the demo without signing up; the full flow is in how it works.

A company introduction and brochure page shown on a visitor's phone

FAQ

How many companies should we reach out to?

It depends on team size, but 20–30 personalized first touches per staff member is a realistic ceiling. Beyond that the messages become copy-paste and response rates drop. Go deep on the priority ten, broad on the rest.

How do we invite a company where we have no contact?

Use the company's public channels — website contact form, LinkedIn — with a specific ask: "we're exhibiting at ___ and would like 15 minutes with the relevant team." The concrete occasion makes this warmer than ordinary cold outreach. If the organizer runs a matchmaking program, start there.

What's the right balance between meetings and floor coverage?

Keep half the booth staff on floor coverage at all times, even in meeting-heavy hours — passers-by don't wait. The trick is to cluster meeting slots into the quiet windows rather than spreading them across the day.

What do we do about no-shows?

A certain rate of no-shows is inevitable. On the day, convert the slot into floor time; within two days after the show, send "it seems our schedules slipped — here's the material we'd prepared." A no-show still accepted your invitation once — keep them on the follow-up list.

Start capturing booth conversations with a single tag

From event setup to performance reports, see it yourself in the demo.

Try the demo →