---
name: booth-staff-briefing
description: Creates booth staff briefing documents and training for trade shows and conferences. Covers show goals and targets, booth roles, opening lines, qualifying questions agreed with sales (BANT, CHAMP or custom), demo flow, competitor talk tracks, lead capture and scanner note rules, what to say about pricing, staff schedule, dress code and logistics, plus a pocket cheat sheet and a huddle message. Use for booth training, staff briefing, pre-show huddle or booth cheat sheets.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: trade-shows-and-field
  source: https://eventmarketingsoftware.com/skills/booth-staff-briefing
---

# Booth staff briefing

Write the briefing that gets a booth team aligned: why we're here, who we want to talk to, what to ask, how to record
it so sales will use it, and where everyone needs to be. The qualifying questions you set here become the lead
capture fields that post-show lead scoring uses for lead tier A/B/C, so they matter more than anything else in it.

## Intake

If the user has an `event-context.md` file, read it first. Then ask for anything missing in ONE message:

1. Show name, dates, hall and booth number, booth size and layout (demo stations, meeting area, theater).
2. Goals: qualified leads, meetings held, demos, pipeline, or something else, with numbers if they have them.
3. ICP and the 2 or 3 personas you want at the booth.
4. Qualification: the framework sales uses (BANT, CHAMP, MEDDICC-lite or custom) and what makes a lead "sales ready".
5. Product messaging: the one-line pitch, what's being demoed or launched, top competitors you'll be asked about.
6. Lead capture: the scanner or lead app, the qualifier fields or notes it supports, and the follow-up owner.
7. Staff list with roles, and the schedule if one exists (booth-staffing-schedule can build it).
8. Logistics: badge pickup, dress code, booth hours, setup and teardown, where to store bags, emergency contact.

If goals or qualification criteria are missing, propose defaults and label them "proposed, confirm with sales".

## Connectors (optional)

- **Google Sheets connector:** read the staff list, schedule or Tier 1 account list; never edit the source sheet.
- **Slack connector:** post the huddle message to the event channel after showing it and getting a yes.
- **No connector:** work from pasted text or files; return a Markdown document the user can paste into a doc.

## Method

```
- [ ] 1. Set goals and per-person targets
- [ ] 2. Assign booth roles
- [ ] 3. Write openers and the 30-second pitch
- [ ] 4. Agree qualifying questions and map them to scanner fields
- [ ] 5. Write demo flow, competitor and pricing lines
- [ ] 6. Set lead capture rules
- [ ] 7. Add schedule and logistics
- [ ] 8. Build the cheat sheet and huddle message
- [ ] 9. Validate
```

### 1. Goals
Turn the show goal into numbers per person per shift so staff know what good looks like. Example: 120 qualified leads
over 3 days with 8 staff on 4 shifts a day is about 1.25 per staff shift. Show the math. Separate "qualified leads"
from "scans".

### 2. Roles
Typical roles: greeter or qualifier, demo lead, sales or AE (meetings), exec (Tier 1 accounts), booth captain (runs
the shift, keeps the floor clear, handles issues). Each role gets a one-line job and a hand-off rule (who passes to
whom and how).

### 3. Openers and pitch
Write 4 or 5 open questions that aren't "Can I help you?", one 30-second pitch, and two polite exits ("I don't want to
keep you from the show. Can I scan your badge so [rep] can send you [thing]?").

### 4. Qualifying questions
Pick 3 to 5 questions, written with sales, that answer: do they fit, do they have the problem, what's the timing,
what's their role in the decision, what's the next step. Frameworks are a starting point, not a script; don't make
budget the opening question. See [references/qualifying-questions.md](references/qualifying-questions.md) for
question banks and how to map answers to scanner fields.

Map each question to a field the lead app supports (picklist where possible, free text only where needed). Use the
same field values that post-show scoring will use, so leads land as lead tier A, B or C without guesswork:
- **A:** fits ICP, has the problem, timing within the user's sales window, agreed next step.
- **B:** fits and has interest, but timing or next step is unclear.
- **C:** low fit or just browsing.

### 5. Demo, competitors, pricing
- Demo flow: 3 steps, under 5 minutes, ending in a next step.
- Competitor lines: one neutral, factual sentence each, no trash talk. If unsure, "Happy to have [rep] send a
  side-by-side."
- Pricing: say exactly what staff can share (ranges, "starts at", or nothing) and the hand-off line.

### 6. Lead capture rules
- Scan every real conversation; never scan badges just to pad numbers.
- Fill the qualifier fields before the next conversation; a scan with no notes is a C at best.
- Note the next step in plain words ("demo with ops team week of the 20th").
- Ask before adding anyone to a newsletter. For EU and UK visitors, record consent explicitly in the app if it has a
  consent field, or note "no marketing consent".
- Follow-up owner and timing: hot leads to the rep within 24 hours; everything else per the follow-up plan.

### 7. Schedule and logistics
Include the shift schedule (or "see schedule"), booth rules (no eating in the booth, phones away, no sitting unless in
a meeting), dress code, badge pickup, contacts, and where the meeting area, storage and nearest exits are.

### 8. Cheat sheet and huddle
Cheat sheet: fits on one phone screen or a folded card. Huddle message: under 150 words, Slack-ready, with today's
goal, one reminder, and the schedule link.

### 9. Validate
- Every qualifying question maps to a scanner field and to lead tier A/B/C rules.
- Per-person targets add up to the show goal.
- No pricing, roadmap or customer names that the user didn't approve for public use.
- Names in the schedule match the staff list.

## Output

1. **Briefing document** with these headings in this order: `Show at a glance`, `Goals and targets`, `Who we want to
   meet`, `Roles`, `Openers and pitch`, `Qualifying questions`, `Demo flow`, `Competitors and pricing`,
   `Lead capture rules`, `Schedule`, `Logistics and booth rules`, `Contacts`.
2. **Pocket cheat sheet:** opener, 3 qualifying questions, 30-second pitch, exit line, lead tier A/B/C rule.
3. **Huddle message** (Slack-ready).
4. **Qualifier field map:** question, scanner field, allowed values, how it feeds lead tier.

Template and a filled example: [references/briefing-template.md](references/briefing-template.md).

## Approval gates

- Show the huddle message and channel before posting to Slack; post only after a yes.
- Mark anything you inferred (goals, pricing guidance, competitor lines) as "confirm before sharing".

## Privacy

- Don't put attendee personal data in the briefing. Tier 1 account names are fine for internal use; contact names only
  if the user provides them and wants them shared with booth staff.

## Related skills

booth-staffing-schedule (shift grid), event-target-accounts (Tier 1 accounts to watch for), pre-show-meeting-outreach
(booked meetings), and the lead scoring and follow-up skills that use the lead tier A/B/C fields set here.
