IceWarp Booth Buddy

Learn

Working With Visitors

Capture the Lead. Own the Promise.

ALL TEAM

Capture Meaningful Interactions

A great conversation without a contact is a lost conversation.

Capture every meaningful interaction where the visitor shows real interest, asks a useful question, joins a demo, requests material, or needs a next step.

ENGAGE → DISCOVER → CAPTURE → CHOOSE / ROUTE → DEFINE NEXT STEP

Capture Meaningful Interactions

Remember

A scan records a contact. It does not record the promise.

What to Capture

Where possible, capture:

  • Name
  • Company
  • Contact details
  • Relevant interest
  • Use case
  • Useful context
  • Promised action
  • Owner
  • Next step

Keep it short, but make it useful. The next person should understand why this contact matters.

Use the Approved Capture Method

Lead capture changes by event. Confirm the method during the pre-event briefing.

Possible methods include:

  • Event lead-scanning app
  • Badge scanner
  • QR or vCard exchange
  • Business card
  • Landing page
  • Booking link
  • Agreed fallback process

Warning

Do not invent your own privacy process. Use the lead-capture and privacy procedure approved for the event.

Know the Fallback Before You Need It

If the main capture method fails, use the agreed fallback.

Before the doors open, confirm:

  • What is the main method?
  • Who can use it?
  • What is the fallback?
  • What data may we collect?
  • Where does the information go after capture?

If no fallback is clear, confirm with the team before collecting data another way.

If you cannot use the capture device, photograph the badge. Add a written note of the promise, the owner, and the next step. The photo records the contact. It does not record the promise.

Keep the Chain Visible

Person → Name → Company → Conversation → Promise → Owner → Deadline / Next Step

If one part is missing, the chain is weak. Add the missing context as soon as you can.

Remember

Never lose the chain. A contact is useful only when the next person understands the conversation.

Who Captures What

RoleNormal responsibility
SALESEngage, qualify, scan or capture visitors they speak with, and add useful context.
BOOTH OPERATIONSSupport capture when Sales is busy. Capture listeners and passive participants when they become meaningful contacts.
PRESALESUsually receive visitors who are already captured. If you promise anything, keep your own follow-up record too.
ALL TEAMIf you are free and see a meaningful contact not captured, help protect the chain.

Primary ownership creates clarity. It does not mean “not my job”.

Capture During Busy Moments

Rush Mode

When the booth is crowded, do not stop good conversations just to manage scanning.

Use the team:

  • Sales keeps talking.
  • Another team member captures nearby listeners.
  • Presales receives qualified visitors.
  • Everyone keeps an eye on missing contacts.

Useful phrase:

“Can I scan your badge so we can send you the right material after the event?”

Presales: Do Not Rely Only on the Front Line

PRESALES

Ideally, visitors come to you already captured. Still, if you have a deeper technical conversation or promise a follow-up, keep your own note.

Record enough to find the person later:

  • Name
  • Company
  • Question or use case
  • What you promised
  • Who else is involved
  • Expected timing

A lead scan may exist somewhere else. Your promise still belongs in your own follow-up list.

Own Every Promise You Make

Lead capture does not replace personal responsibility.

If you promise an answer, document, demo, booking link, technical check, or internal escalation, record it immediately.

Capture:

  • Who the person is
  • Company
  • Exact question or use case
  • What you promised
  • Who else is involved internally
  • When an answer is expected
  • Who owns the next step

The next step may belong to you, Sales, Support, Development, or another expert. Confirm that before you move on.

Close the Loop

A promise is complete only when the next step is clear or done.

DO → HAND OFF → CONFIRM → MARK COMPLETE

  • Perform the promised action.
  • Reference the actual booth conversation.
  • Hand off with full context if someone else must answer.
  • Confirm who owns the next step.
  • Mark the promise complete in your own follow-up list.

Hand Off With Context

Handover

Use a short, complete handover when another person must continue the conversation.

Template:

“This is [name] from [company]. They asked about [use case]. We discussed [context]. I promised [action] by [time]. [Owner] owns the next step.”

Do not hand over only a name. The conversation is the value.

Use Personal Contact Options Carefully

Pro Tip

A personal QR code, vCard, business card, or booking link can help visitors reach you after the event.

Use it as a helper, not as a replacement for lead capture. The team still needs the contact, context, promise, owner, and next step.

Common Scenarios

Visitor Asks for a Demo Immediately

Situation: A visitor walks up and says, “Can you show me the product?”

What to do:

  • Pause before opening the full demo.
  • Ask 2–3 discovery questions.
  • Show the parts that match their interest.

Useful questions:

  • “What are you using today?”
  • “What would you like to improve?”
  • “Are you more interested in email, collaboration, security or deployment?”

Lesson: Demo what matters. A short relevant demo is better than a full product tour.

Visitor Asks for a Demo Immediately

You Do Not Know the Answer

Situation: A visitor asks a technical or product question and you are not sure.

What to do:

  • Say you want to verify it.
  • Capture the exact question.
  • Capture who asked it.
  • Assign or escalate it to the right person.
  • Set a clear next step.

What to say:

“I don’t want to guess. I’ll verify this and get back to you.”

Lesson: Don’t guess. A clear follow-up is stronger than a wrong answer.

Brochure Holder Is Almost Empty

Situation: You notice the brochure holder is nearly empty, but Booth Operations is speaking with someone.

What to do:

  • Refill it if you are free.
  • Keep the booth looking ready.
  • Tell Booth Operations later if stock is running low.

Lesson: Know your role, but protect the booth as a team.

You Promised a Deployment Diagram

Situation: During a conversation, you promised to send a deployment diagram after the event.

What to do:

  • Write it down immediately.
  • Capture the visitor’s name and company.
  • Capture exactly what you promised.
  • Add the next step and owner.

Remember

If you promised it, you own it.

Lesson: Do not rely on memory. The next conversation will arrive faster than you think.

Several People Are Waiting

Situation: You are already speaking with someone and more visitors arrive.

What to do:

  • Make eye contact.
  • Acknowledge them.
  • Give a short signal that you will help them soon.
  • Ask a free colleague to step in if possible.

What to say:

“Hi, welcome. I’ll be with you in a moment.”

Remember

Nobody becomes invisible.

Lesson: You do not need to stop every conversation. You do need to make people feel seen.

Quiet Period Starts

Situation: Booth traffic slows down. Nobody has approached for a while.

What to do:

FOLLOW UP → NETWORK / EXPLORE → RESET

  • Reset the booth.
  • Restock visible materials.
  • Check your notes and promised follow-ups.
  • Agree who stays at the booth.
  • Use rotations for breaks, networking or exploring the exhibition.

Side Quest

Visit relevant exhibitors, observe competitors and learn what visitors are seeing elsewhere.

Lesson: Quiet time is useful time. Reset first, explore second.

Another Colleague Can Help Better

Situation: A visitor needs something another colleague can handle better.

What to do:

  • Do not just point across the booth.
  • Bring the colleague in.
  • Give context before you leave the conversation.

Handover

“This is Anna from a 2,000-user company. They use Exchange today and want to understand deployment options and migration.”

Lesson: A warm handover keeps the chain intact.

Visitor Speaks a Language You Cannot Support Well

Situation: A visitor wants to speak in a language you cannot support well.

What to do:

  • Use available team language coverage.
  • Use simple shared language if possible.
  • Use appropriate translation support if needed.
  • Invite the visitor back when a suitable colleague is available.
  • Check the event briefing before you promise a specific person or time.
  • Capture contact information so the opportunity is not lost.

What to say:

“We can try in English now, or I can connect you with a colleague who can support this better.”

Lesson: Language should not break the chain. Keep the visitor connected to the next useful step.