How to Reduce No-Shows at Event Meetings

Event meetings go missing differently

The general advice on no-shows still applies at events: a clear purpose, a meeting the attendee chose, and an easy way to reschedule. Our guide to reducing no-shows for B2B meetings covers those foundations.

But a meeting at a trade show or conference is not an ordinary call moved to a different venue. The attendee is in an unfamiliar building, their day is full of sessions and other meetings, their phone is their only calendar, and they are walking between halls with a badge and a coffee. A video call that someone misses can be rebooked for tomorrow. A meeting at an event that someone misses is usually gone — the show closes and everyone goes home.

That changes where the effort should go. At an event, the risk sits less in whether the attendee remembers the meeting and more in whether they can physically get to it at the right moment.

Where event no-shows come from

It is worth sorting missed event meetings by cause before changing anything, because each cause has a different fix.

The meeting booked too early and never revisited. It was agreed six weeks before the show, the attendee's plans shifted, and nobody checked. Fix: reconfirmation in the week before the event.

The attendee who cannot find the room. Hall numbers, meeting-suite names, and booth references that make sense to the organiser and to nobody else. Fix: directions written for someone who has never been in the building.

The overrun. A keynote ran late, the previous meeting ran long, or the walk between halls took fifteen minutes rather than five. Fix: buffers and realistic travel time between meetings.

The better offer. Something more attractive appeared on the show floor — a customer, a competitor's party, a session they had not noticed. Fix: a meeting with a clear reason to attend, and a confirmation close enough to the day that it still feels like a commitment.

The attendee who is not at the event at all. Travel was cancelled, the colleague came instead, or they are only attending one of the three days. Fix: ask which days they are on site before offering times.

Reconfirm before the show

Pre-booked meetings are the most valuable meetings at an event, and booking them weeks ahead is the right approach. The cost of booking early is that the booking goes stale.

Plan one reconfirmation, sent roughly a week before the event, that asks for a reply rather than just informing:

• The meeting's purpose in one line, specific to this attendee.
• The day, time, and time zone of the event venue — attendees travelling in often still have their calendar set to home time, which causes the familiar time-zone errors.
• Who from your side will be there.
• A simple question: "Is this still good for you?", with a one-click way to move or cancel.

The replies are useful in both directions. A confirmation is a strong signal. A reschedule is recoverable while there is still time to fill the gap. Silence is the case to act on — a second, personal message from the person they will actually be meeting often gets a reply where the automated one did not.

Make the meeting point impossible to miss

Most event venues are confusing, and meeting rooms are usually the hardest thing in them to find. Directions that feel obvious to the team who set up the space are rarely obvious to a visitor.

For every meeting, the confirmation and reminders should say:

• The exact meeting point, in words a first-time visitor would recognise: "Meeting Room 4, first floor above Hall B, next to the escalators" rather than "MR4".
• Where to go if they cannot find it — the booth number, or a named person with a mobile number who answers messages during the show.
• How long to allow to get there, especially if the room is in a different hall or a separate building from the sessions.

If you have several rooms or a mix of rooms and booth space, plan the meeting space so each attendee has one simple meeting point rather than a different one per meeting.

Time reminders to the show day

A reminder the day before a normal meeting lands in someone's inbox at their desk. A reminder the day before a show meeting may land in the middle of a flight or at an evening event, and be forgotten by morning.

Reminders at events work better when they fit the rhythm of a show day:

1. The evening before, a short summary: time, meeting point, and who they are meeting.
2. The morning of, before sessions start, when attendees are planning their day and checking their phones.
3. Shortly before the meeting, a brief message with directions — sent from a named person rather than a no-reply address, so a reply like "running ten minutes late" reaches someone who can act on it.

Keep every message readable on a phone with one hand. The meeting point and time belong in the first line, not below a logo and a paragraph of introduction.

Build slack into the schedule

Many event no-shows are not decisions at all. The attendee meant to come and simply could not get there on time.

A few scheduling rules reduce this:

• Leave buffers between meetings so an overrun does not cascade through the rest of the day. The buffer matters for your team as much as for the attendee.
• Avoid slots that clash with the event's own agenda — the minutes straight after a keynote, the opening of the exhibition hall, and lunch are when people are most likely to be delayed.
• Account for travel between locations. If a meeting is in a hotel across the road from the venue, the slot needs to include the walk.
• Hold a little capacity back for meetings that need to move, rather than filling every slot on the first day of booking. The meeting capacity calculator shows how many meetings fit once buffers are counted.

These rules are easier to enforce when they are part of the booking itself rather than something each person remembers to check. Most scheduling conflicts come from changes, not original bookings, and events generate a lot of changes.

When someone does not arrive

At an event, waiting passively costs more than it would on a call. After five minutes, message the attendee directly — a short, friendly note asking whether they are on their way or would prefer another time. Offer a specific alternative slot if you have one, or a different day of the event.

If the meeting cannot happen at the event, offer a call in the week after rather than letting the conversation lapse. The attendee agreed to meet for a reason, and that reason usually survives the show. The post-event follow-up plan covers what to do in those first two weeks.

Then record the no-show, with the cause if you know it: booked too early, could not find the room, overrun, or not attending. Across a whole event, those records show whether the problem was the schedule, the directions, or the booking process — and what to change before the next one. They also belong in any honest measure of the event's return, because a booked meeting that did not happen is not a meeting.

An event no-show checklist

• Do you ask which days the attendee is on site before offering times?
• Is every pre-booked meeting reconfirmed in the week before the event?
• Are times shown in the venue's time zone, and labelled as such?
• Does every message describe the meeting point in words a first-time visitor would understand?
• Is there a named contact with a mobile number for attendees who are lost or late?
• Are reminders sent the evening before, the morning of, and shortly before the meeting?
• Are there buffers between meetings, and are slots next to keynotes avoided?
• Does someone follow up within five minutes when an attendee has not arrived?
• Are no-shows recorded with a cause?

CallShark is being built to run event meetings this way — rooms reserved alongside people and times, reminders sent in the venue's time zone, and outcomes, including no-shows, recorded against each meeting. The product is temporarily down.