---
name: pre-show-meeting-outreach
description: Plans and writes pre-event meeting booking outreach for trade shows and conferences, whether exhibiting or attending without a booth. Produces an outreach timeline from about 6 weeks out to show week, tiered email and LinkedIn sequences for target accounts, warm prospects and customers, AE and exec personal notes, SDR talk tracks, meeting logistics and a confirmation flow. Use for booking meetings at events, pre-show outreach, conference meeting requests or show-week calendar planning.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: trade-shows-and-field
  source: https://eventmarketingsoftware.com/skills/pre-show-meeting-outreach
---

# Pre-show meeting outreach

Plan and write the outreach that fills reps' calendars before a show: a dated timeline, sequences by account tier and
channel, personal notes from AEs and execs, SDR call scripts, and the confirmation and reminder flow once meetings are
booked. Everything is a draft until the user approves it.

## Intake

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

1. Event name, dates, city, and whether you have a booth, a meeting room, a suite, or no booth at all.
2. The target list, ideally tiered (Tier 1, 2, 3) with owner and CRM status. If it isn't tiered, offer to run the
   event-target-accounts method first or tier it quickly by relationship (open opp, target account, customer, other).
3. Meeting goal (number of meetings) and who's attending: reps, SEs, execs, with the days and hours each is free.
4. The reason to meet: something specific to this show (a launch, a demo, a customer story, a benchmark, an exec
   roundtable, a dinner). If there's nothing, help them pick one before writing copy.
5. Sending setup: who sends (marketing, SDRs, AEs), which tools (your CRM, your sales engagement tool, plain email),
   and any brand or legal rules for outbound email.

Before writing, clean the list: normalize tier labels ("tier 1" = "Tier 1"), merge duplicate accounts so one owner
coordinates all contacts at the account, and route contacts with no email to the owner or LinkedIn instead of
dropping them. Report how many rows changed.

## Connectors (optional)

- **CRM connector:** read the target list, owners and last activity; after approval, create draft tasks or update
  campaign member status. Never send from the CRM without a yes.
- **Google Sheets connector:** read the target list or rep availability; write the meeting tracker to a new tab.
- **Slack connector:** post the rep briefing or daily meeting count to a channel, only after a preview and a yes.
- **No connector:** work from pasted text or CSV/XLSX; return Markdown copy and a CSV tracker.

## Method

```
- [ ] 1. Confirm the reason to meet and the meeting format
- [ ] 2. Set capacity and targets per rep
- [ ] 3. Build the dated timeline
- [ ] 4. Write sequences by tier and channel
- [ ] 5. Write AE and exec personal notes
- [ ] 6. Write SDR talk tracks
- [ ] 7. Set up the tracker and confirmation flow
- [ ] 8. Validate and get approval
```

### 1. Reason to meet and format
A meeting request works when it gives the buyer a reason that only exists at this show. Write one line for the
reason and one for the format: length (15, 20 or 30 minutes), place (booth meeting area, hotel lobby, a reserved room,
coffee nearby), and who they'll meet. Attending without a booth? Use a nearby reserved space or a named cafe, and say
so; never imply a booth you don't have.

### 2. Capacity
Meetings per rep per day is usually limited by show hours, travel between halls and other duties. Ask the user; if
they don't know, plan 5 to 7 per rep per day and label it an assumption. Total capacity = reps x meetings per day x
days. Set the target below capacity to leave room for walk-ups and reschedules.

### 3. Timeline
Default (adjust to the date the user starts; if the show is under 3 weeks away, compress and say what's dropped):

| When | What |
|---|---|
| 6 weeks out | Final tiered list; reps confirm their Tier 1 accounts; set up tracker and calendar booking links |
| 5 weeks out | Exec and AE personal notes to Tier 1; customer invites from CSMs |
| 4 weeks out | Email step 1 to Tier 2; LinkedIn connection notes |
| 3 weeks out | Email step 2 to Tier 1 and 2; SDR calls to engaged non-responders |
| 2 weeks out | Email step 3 (short, last call); Tier 3 booth invite |
| 1 week out | Confirm every booked meeting with location and a calendar invite |
| 24 to 48 hours out | Reminder with exact meeting spot and the rep's mobile number if the rep agrees |
| Show days | Daily morning reshuffle of no-shows and new requests |

### 4. Sequences
Write 3 steps per tier, each under 120 words, plain text, one ask. Rules:
- Subject lines under 50 characters, naming the show; no clickbait or fake "Re:".
- Step 1: reason to meet, format, two specific time options or a booking link.
- Step 2: a different angle (customer story, what they'll see in 15 minutes), new short ask.
- Step 3: two lines, easy out ("If the show's packed, happy to catch up after.").
- Tier 1: personalize the first line to the account (open opp stage, last conversation, their talk at the show).
- Customers: lead with value for them (roadmap preview, user group, thank-you coffee), not a pitch.
- LinkedIn: connection note under 300 characters; no pitch in the note itself.

Patterns and examples by tier: [references/email-examples.md](references/email-examples.md).

### 5. Personal notes
Short notes (under 80 words) the AE or exec sends from their own inbox. Write in first person, conversational, with
the same reason to meet. Leave clear `[brackets]` where the sender should add something only they know.

### 6. SDR talk tracks
For each tier: opener (under 20 seconds), reason to meet, two time options, three common objections ("not going",
"too busy at the show", "send me info") with replies, and how to log the result.

### 7. Tracker and confirmations
Tracker columns:

`account, tier, contact_name, title, owner, outreach_channel, last_touch_date, status, meeting_date, meeting_time,
location, attendees_internal, prep_notes, confirmed`

Status values follow the campaign member statuses in your CRM. If the user has none, suggest:
Targeted, Invited, Responded, Meeting Booked, Meeting Held, No Show, Declined. Keep these labels identical across all
show campaigns so reporting works. Write the confirmation (1 week out) and reminder (24 to 48 hours out) templates
with date, time with time zone, exact spot, who they're meeting, and how to reschedule.

### 8. Validate
- Every date in the timeline falls before the show and on a weekday; flag any that don't.
- Each sequence step has one ask and is under the word limit.
- Meeting target is at or below capacity; double-booked slots are flagged.
- No claims about the show (hall numbers, session times) that the user didn't provide.

## Output

1. **Plan summary:** goal, capacity, reason to meet, format, timeline table with real dates.
2. **Copy pack:** headings `Tier 1`, `Tier 2`, `Tier 3`, `Customers`, each with Email 1 to 3 and the LinkedIn note;
   then `Personal notes (AE)`, `Personal notes (Exec)`, `SDR talk tracks`, `Confirmation`, `Reminder`.
3. **Tracker:** CSV with the columns above, prefilled from the target list with `status = Targeted`.
4. **Show-week calendar (when meetings are booked):** table per rep with date, time, account, contact, location.

## Approval gates

- Default to drafts. Never send email, schedule sequences, post to Slack, or update CRM records without showing the
  exact content and recipients and getting a clear yes.
- For bulk sends, show the count by tier and three rendered samples with merge fields filled before asking.

## Privacy and consent

- Personal 1:1 outreach from a rep is different from bulk marketing email. For bulk sends, respect unsubscribes and
  the user's email rules.
- Flag EU and UK contacts who haven't opted in to marketing (`consent_check = needed`) and suggest a rep sends a
  personal note instead of adding them to a bulk sequence. Follow the user's legal guidance.
- Include the sender's real name and company. Don't scrape or guess emails.

## Related skills

event-target-accounts (builds the tiered list), booth-staffing-schedule (schedules reps around booked meetings),
exec-dinner-planner (for Tier 1 accounts that merit a dinner seat).

Sample input: `assets/sample-target-list.csv`.
