Eventica
← All articles

Meetings

Bilateral meetings: why most of them never happen

The report says fourteen meetings were confirmed. The exhibitor remembers six. The difference is not bad luck. It is a series of small failures that can be fixed.

A meeting area with numbered tables beside an exhibition hall, only one of them in use

On paper, the exhibitor had a very good event. Fourteen meetings requested, fourteen accepted, a neat schedule across two days. The organiser’s report said so too.

On the day, six of those meetings took place.

One contact waited at table 12 while the exhibitor waited at table 21. One was stuck in a panel that ran twenty minutes over. One had accepted three weeks earlier and simply forgot. One never realised the meeting had been confirmed at all. Two people turned up at the right table at the right time and did not recognise each other.

None of this is dramatic. That is the problem. Each failure is small enough to shrug off, and together they quietly halve the value of the most commercially important part of many events.

Confirmed is not the same as happened

Most matchmaking systems count what is easy to count: requests sent, requests accepted, slots filled. Very few count whether two people actually sat down together.

That is a measurement problem before it is anything else. If the number in the final report is “meetings confirmed”, everyone involved is optimising for confirmations. Exhibitors send more requests, attendees accept to be polite and the dashboard looks healthy right up to the moment the exhibitor tries to remember who they spoke to.

Start by counting the meetings that happened. A simple check-in at the table, or both people marking the meeting as held in the app, is enough. The first time you see the real number, it will probably be uncomfortable. It will also tell you exactly where to look.

An attendee alone at a meeting table with two coffees, checking his watch

The meeting was booked weeks ago

A meeting accepted three weeks before an event was accepted by a slightly different person. Their priorities were different, their calendar was emptier and the event felt far away.

By the day itself, that meeting is competing with a keynote, a colleague who wants lunch and an inbox that did not stop for the conference. Without a reminder it does not stand much chance.

Reminders work, but only the right ones. A message the evening before with the full day’s meetings. Another shortly before each meeting, with the place, the time and a photo of the person. Not a stream of notifications that people learn to swipe away by the second morning.

Nobody could find the table

“Meeting area B, table 14” is clear to the person who drew the floor plan. It is less clear to someone who has just come out of a session on another floor, in a venue they have never visited.

An attendee holding her phone and looking around a crowded exhibition hall

Meeting areas should be easy to find and hard to miss: visible from the main circulation routes, signposted from the session rooms, with large table numbers that can be read from a distance. If tables are moved or renumbered during setup, the app has to know before the doors open.

A person at the entrance of the meeting area helps more than any signage. They can point people to the right table, notice when someone has been waiting alone for ten minutes and send a message on their behalf.

The programme ate the slot

Sessions overrun. It is one of the few certainties in the events industry. A meeting scheduled for five minutes after a popular panel ends is a meeting that starts fifteen minutes late, if it starts at all.

There are two practical answers. The first is to design meeting blocks around the programme rather than on top of it, so that the main sessions and the busiest meeting slots do not compete. The second is to make small changes easy. If someone is running late, they should be able to push the meeting by fifteen minutes with one tap and have the other person told immediately.

One side never really agreed

Some meetings were never going to happen. They were accepted because declining felt rude, or because the request was too vague to judge.

“I would like to connect” tells the recipient nothing. A request that says who the person is, what they are working on and why this conversation might be useful gives the other side something to decide on. It also produces better meetings, because both people arrive knowing why they are there.

Declining should be just as easy and just as respectable. A polite “not this time” is far better than an acceptance that turns into an empty chair.

Cancelling is harder than not turning up

This one is almost always overlooked. If cancelling a meeting means finding it in the app, opening it, writing an apology and confirming, many people will simply not show up instead. It is less effort and nobody sees it happen.

Make cancelling a single action. Tell the other person straight away, so they are not left waiting. Free the slot so it can be used for something else. A cancelled meeting is a small disappointment. A meeting nobody cancelled is half an hour of someone’s event spent looking at the door.

What organisers can actually change

None of this requires a new kind of technology. It requires paying attention to the parts of the meeting that happen outside the booking screen:

  • Count the meetings that took place, not just the ones that were confirmed.
  • Protect meeting time from the most popular sessions, and plan for overruns.
  • Make the meeting area obvious, with large table numbers and a person in charge.
  • Send fewer, better reminders, with the place, the time and a photo.
  • Ask for a reason with every request, and make declining easy.
  • Make rescheduling and cancelling take one tap, and notify the other side instantly.
  • Help with the follow-up, so the contact and a short note survive the trip home.

The number that matters

Exhibitors and sponsors do not remember how many meetings were confirmed. They remember who they spoke to and what came of it. When they decide whether to come back next year, that is the number they use, even if nobody wrote it down.

An event that turns six real meetings into ten has done more for its exhibitors than one that turns fourteen confirmations into thirty. The difference is rarely the matchmaking algorithm. It is the reminders, the tables, the timing and the courtesy of a clear cancellation.

More from the blog

All articles
A long queue of attendees waiting at a registration desk in a conference venue

Event apps

A serious event needs its own app

A conference can put artificial intelligence on its main stage and still make attendees search their inboxes for a PDF agenda.

Ana Petrović · 4 min read

Attendees checking their phones in a conference hall under signs in Arabic and English

Multilingual events

Building an event app for Arabic and English at once

Translating the strings is the easy part. A bilingual event app has to work in two directions, two scripts and two sets of expectations, on the same day.

Eventica Team · 5 min read

See it running

A demo on a live system, not a slide deck. Tell us about the event and we will show you the backoffice, the site and the apps as they actually work.