IceWarp Booth Buddy

Learn

Know Your Role

Know Your Role. Protect the Booth as a Team.

Before each event, assign a person to each of the four primary roles:

  1. Sales
  2. Booth Operations / Sales Operations
  3. Presales / Technical
  4. Booth Lead

The playbook names the role. It does not name the person. The person in each role can change from venue to venue.

At smaller events, one person may cover more than one role. That is fine. The responsibilities still need to be clear.

Know Your Role. Protect the Booth as a Team.

Golden Rule

Primary Role Is Not a Wall

Know your main job. Help the booth when you see something that needs action.

RolePrimary job
SalesStart the conversation and qualify the visitor
Booth OperationsKeep the booth ready, flowing and captured
PresalesTurn real interest into technical understanding
Booth LeadKeep ownership clear and the team coordinated

SALES — Own the Front of the Conversation

Mission

Make the booth approachable

Sales is usually the first active contact. You notice interest, start discovery, qualify enough and move the visitor toward the right next step.

Your core actions:

  • Be visible near the front
  • Notice interested visitors
  • Start conversations
  • Ask short discovery questions
  • Understand why they stopped
  • Identify the visitor context
  • Qualify before using Presales time
  • Capture meaningful contacts
  • Route visitors correctly
  • Create warm handovers
  • Own commercial next steps unless reassigned

Remember

Presales is not the default destination for every visitor. Qualify first.

Understand the Visitor Before You Route Them

You are not interrogating the visitor. You are learning enough to choose the right path.

WHO

  • Name
  • Company
  • Role
  • Country or region, where useful

WHAT

  • What caught their attention?
  • What are they interested in?

WHY

  • What problem are they solving?
  • What change are they exploring?

HOW BIG

Where relevant:

  • Number of users
  • Current environment
  • Deployment type
  • Geography
  • Scope

WHAT NEXT

Choose the useful next step:

  • Answer
  • Product information
  • Demo
  • Technical discussion
  • Meeting
  • PoC
  • Commercial follow-up

Choose the Right Visitor Path

Visitor contextWhat to do
Prospective customerDiscover, qualify, capture, route
Existing customerUnderstand current situation and next need
Partner or potential partnerCapture context and route commercially
Press or mediaCapture and route to the right owner
CompetitorStay professional and avoid sensitive detail
Job seekerRoute only if there is an agreed path
VendorKeep it short unless relevant
Casual visitorBe polite, qualify lightly
Giveaway hunterKeep the booth moving

Trap

The Full Product Monologue

Do not start by explaining every IceWarp module. Ask what brought them to the booth first.

SALES — Avoid These Booth Habits

  • Starting with a long product speech
  • Sending every curious visitor to Presales
  • Using Presales as the first contact by default
  • Handing over without context
  • Assuming a badge scan is enough
  • Ignoring waiting visitors because you are busy

Golden Rule

Nobody Becomes Invisible

If another visitor appears while you are busy, acknowledge them. A look, a smile or “I’ll be with you in a moment” is enough.

Handover

Context Travels With the Visitor

Do not hand over a person with:

“This is our technical guy.”

That makes the visitor restart the conversation.

A good handover gives your colleague the useful context in one short summary.

Warm handover flow:

DISCOVER → CAPTURE → CHOOSE / ROUTE → DEFINE NEXT STEP

A good handover includes:

  • Who the visitor is
  • Company or context
  • Current system, where relevant
  • Problem or requirement
  • What was already discussed
  • What they want next

Example

“This is Anna from a 2,000-user manufacturing company. They run Microsoft 365 today, are exploring on-premises collaboration for a regulated environment, and want to understand migration and mobile access.”

Remember

A warm handover saves time and shows the visitor we listened.

BOOTH OPERATIONS — Keep the Booth Ready to Perform

Mission

Make the booth feel effortless

Visitors should not see the backstage work. Booth Operations keeps the booth ready, clean, stocked, practical and flowing.

Your core actions:

  • Understand the event lead-capture process
  • Keep lead capture available
  • Watch for visitors not yet engaged or captured
  • Support handovers during busy periods
  • Help maintain visitor flow
  • Coordinate practical booth operations
  • Watch demo stations and visible equipment
  • Watch power, chargers and cables
  • Coordinate breaks so key roles stay covered
  • Know event logistics and escalation contacts

Lead capture can change by event. Know the agreed method before doors open: badge scanner, QR code, event app, manual process or another approved tool.

Keep the Booth Full, Clean, Ready, Intentional and Calm

Full

Refill materials and giveaways before displays look empty.

Clean

Remove unnecessary:

  • Cups
  • Food
  • Packaging
  • Rubbish
  • Abandoned papers
  • Personal items

Ready

Demo stations should be:

  • Powered on
  • Logged in where appropriate
  • Prepared
  • Immediately usable

Intentional

Printed materials, gifts, merchandise and equipment should look deliberately placed.

Calm

Visitors should not see internal scrambling.

Refill Before It Looks Empty

Booth Operations monitors:

  • Brochures
  • Flyers
  • Business cards, where used
  • QR materials
  • Gifts
  • Branded merchandise
  • Promotional items

Do not wait until something is completely gone. Refill early so the booth looks cared for.

Golden Rule

If You See It, Own It

Operations is the primary owner. But if you are free and see a problem, fix it.

Examples:

  • Empty brochure holder
  • Messy merchandise
  • Rubbish
  • Abandoned cup
  • Demo screen in the wrong state
  • Visible cable problem

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

PRESALES — Turn Interest Into Understanding

Mission

Connect the need to the right IceWarp story

Presales should ideally receive visitors who have already been:

  • Engaged
  • Captured
  • Lightly qualified

You then connect the visitor’s need to the relevant IceWarp workflow, product capability, deployment model, architecture or technical discussion.

Your core actions:

  • Understand the use case before the demo
  • Show the relevant IceWarp workflow
  • Run short, prepared demonstrations
  • Answer technical questions within your knowledge
  • Discuss deployment scenarios where relevant
  • Discuss migration where relevant
  • Discuss security where relevant
  • Escalate questions you cannot answer reliably
  • Record technical promises yourself
  • Support technical qualification during rush periods

PRESALES — Spend Technical Depth Where It Creates Value

Presales is a scarce booth resource. Do not spend the whole event standing in the aisle collecting every lead.

During busy periods, Presales can help with:

  • Engaging visitors
  • Qualifying interest
  • Routing people
  • Keeping conversations moving

When the pressure passes, return to the primary Presales role.

Rush Mode

Shorten the interaction, not the quality.

ENGAGE → QUALIFY → CAPTURE → CHOOSE / ROUTE

Demo What Matters

Understand what the visitor needs before you start showing the product.

Good demo rhythm:

DISCOVER → DEMO OR DISCUSS → DEFINE NEXT STEP

Show what matters to this visitor. Do not give the same full product tour to everyone.

Trap

Debugging in Public

Do not debug the demo environment in front of visitors. If something does not work, move to a prepared path, capture the question or escalate.

Warning

Do not knowingly demonstrate something that is not ready or not working.

When You Do Not Know the Answer

Golden Rule

Don’t Guess. Escalate.

If you cannot answer reliably, say so and keep control of the next step.

Use this flow:

CAPTURE → ESCALATE WHERE NECESSARY → DEFINE NEXT STEP → FOLLOW UP

Example

“I do not want to guess. I’ll capture the question and get the right answer back to you.”

If You Promise It, You Own It

If Presales promises a technical answer, document, diagram or follow-up, Presales records it personally.

Do not assume Sales will remember a technical promise you made.

Capture:

  • Who asked
  • Company
  • Question or promise
  • Agreed next step
  • Owner
  • Timing, if agreed

Golden Rule

If You Promise It, You Own It

A lead record is not enough if it does not say what you promised.

BOOTH LEAD — Keep Ownership Clear

Booth Lead is a primary role. Assign a person to it for each event. That person can change from venue to venue.

Use this role to keep the booth working as one team.

Booth Lead actions:

  • Confirm who covers each primary role
  • Make combined roles explicit at smaller events
  • Check that Sales, Operations and Presales understand their responsibilities
  • Keep event-specific details visible to the team
  • Help prevent role gaps during busy periods
  • Reinforce that primary role is not a wall

Before doors open, confirm:

  • Who starts visitor conversations
  • Who owns lead capture
  • Who runs demos
  • Who handles technical escalation
  • Who watches booth readiness
  • Who coordinates breaks
  • What event-specific tools or processes apply

Warm Handover Checklist

Use this before you pass a visitor to another colleague.

  • Visitor name captured
  • Company understood
  • Role or context clear
  • Interest or problem known
  • Current system noted, if relevant
  • Useful next step clear
  • Receiving colleague briefed
  • Ownership confirmed

Good handover

“This is Martin from a regional partner. They are interested in IceWarp for customers who want an alternative to Microsoft 365. We discussed hosting options, and he would like to understand deployment and migration.”

Weak handover

“Can you talk to him?”

Never Lose the Chain

Every meaningful visitor should stay connected from first contact to a clear next step.

The chain is:

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

If the visitor is meaningful, do not let the context disappear between people.

Remember

A badge scan records a contact. It does not automatically record the conversation.

Booth Lead

BOOTH LEAD

Mission

See the Whole System

Booth Lead is a defined role. A person is assigned to it for each event, and that person can change from venue to venue.

Your job is to notice what others cannot see while they are inside conversations.

You are not necessarily the busiest person at the booth. You are the person who watches the full flow: visitors, team roles, demos, breaks, escalations, booth readiness and follow-up ownership.

MISSION — See the Whole System

Remember

Nobody becomes invisible. Never lose the chain.

Start the Day with a Clear Briefing

Run a short briefing before the booth opens.

Confirm:

  • Roles for the day
  • Scheduled meetings
  • Language coverage
  • Break coverage
  • Demo readiness
  • Lead capture method
  • Escalation path
  • Follow-up ownership

Keep it practical. The team should know who does what, who is available, and what to do when traffic increases.

Lead capture tools, meeting schedules and language coverage can change by event. Confirm the current event setup before doors open.

Keep Roles Clear, Not Rigid

Role clarity prevents confusion. It should not create silos.

Check that the team knows:

  • Who opens conversations
  • Who qualifies visitors
  • Who captures contacts
  • Who handles deeper product or technical questions
  • Who manages booth operations
  • Who owns each follow-up

If roles conflict during the day, decide quickly and keep the booth moving.

Remember

Know your role. Protect the booth as a team.

Watch the Visitor Flow

Keep asking yourself the same questions during the day.

  • Is anyone waiting without being acknowledged?
  • Are meaningful contacts being captured?
  • Is useful context being recorded?
  • Is Presales being used where technical depth creates value?
  • Does the booth still look full, clean and ready?
  • Are breaks creating gaps?
  • Does every promise have an owner?

If the answer is no, act. Rebalance people, capture missing context, or assign ownership before the chain breaks.

Rush Mode

Rebalance Fast

When the booth gets busy, your job is to protect flow without losing quality.

Do this:

  • Acknowledge waiting visitors
  • Move available people forward
  • Keep capture alive
  • Route technical depth to Presales
  • Let active conversations continue
  • Capture passive listeners where useful
  • Protect handovers
  • Pause non-essential tasks

Presales is not the default destination for every visitor. But if Sales is overloaded and a relevant visitor needs product depth, use Presales where it creates value.

Own or Route Escalations

You do not need to answer every question yourself. You need to make sure it goes somewhere useful.

Use this route:

Commercial issue → Sales
Technical depth → Presales
Booth setup issue → Booth Operations
Unclear or serious issue → CAPTURE → DEFINE NEXT STEP → FOLLOW UP

If nobody clearly owns the issue, you own the routing until someone does.

Protect Demo Quality

Keep the demo on the agreed path.

Make sure demo stations are ready, the environment looks usable, and the team is not improvising with something untested. If someone wants to show something outside the agreed demo flow, pause and confirm it works first.

Trap

Avoidable Improvisation

A confident demo is not a live experiment. If it is not ready, do not let the booth discover that in front of a visitor.

Keep Breaks from Creating Gaps

Breaks are normal. Gaps are not.

Before someone leaves the booth, confirm:

  • Who covers their role
  • Whether any meeting is coming
  • Whether language coverage changes
  • Whether a demo or conversation is waiting
  • Whether the booth still looks covered

Quiet moments are the best time to rotate breaks.

Side Quest

Use Quiet Time Well

Quiet period?

FOLLOW UP → NETWORK / EXPLORE → RESET

Team members may use quiet time to visit other booths, observe competitors or join event networking. They should only leave after coverage is confirmed.

End the Day with No Loose Ends

Run a short end-of-day review.

Check:

  • Captured contacts are complete
  • Useful context is recorded
  • Follow-ups have owners
  • Escalations are routed
  • Demo or booth issues are noted
  • Tomorrow’s role changes are clear

Do not end the day with “someone will handle it.” Name the owner.