Chapter 07 of 12
Audience comms: notifying clients and prospects, filling calendars
How the world hears INTO will be somewhere — and how that becomes booked meetings. All outbound copy: Copywriter drafts, Editor pass, Class B human gate before send; brand forbidden patterns apply.
Doctrine: meetings before you fly
The pre-show motion determines whether an event produces pipeline — not the booth, not the sponsorship tier. Senior-buyer calendars lock 4–6 weeks out; teams starting outreach inside 4 weeks (as 55% do) get "I'm booked solid" (memo-03, Vendelux 2026). So the comms plan opens at T-6w or the event isn't ready to be attended. Planning rates (vendor-published, directional): a disciplined multichannel program books meetings with 10–15% of contacted ICP prospects; 100–150 researched contacts per event → 10–20 booked conversations — enough to fill two exec calendars for a two-day conference before doors open.
Segments and their asks (never cross the streams)
The cardinal error is one message to everyone. Four relationships, four asks:
| Segment | The ask | Sender + channel | Notes |
|---|---|---|---|
| Existing clients attending or nearby | "We'll be there — dinner seat / 1:1 with <exec>" + hospitality | Their exec contact, personal email + calendar hold | Relationship maintenance and expansion. Never a marketing blast; never prospect-grade messaging |
| Open opportunities | "<Exec> will be at X — 30 minutes to work the open questions in person" | Exec-to-exec email; deal owner backs it with a call | In-person time is a deal accelerant; this segment gets weekly persistence until booked |
| Named target accounts (cold/warm ICP) | Value-led meeting ask — a benchmark, a teardown, a relevant case pattern; "coffee near the hall Tue/Wed?" | Comms owner drafts, sent from the exec; email + LinkedIn | The event is the trigger, not the pitch. Never "visit our booth" |
| Lapsed contacts | "It's been a while — we'll both be at X"; softest ask (drop by the drinks) | Whoever owned the relationship | Reactivation costs one email; write it |
VIP invitees for owned dinners/workshops are a fifth stream with their own ladder — chapter 12.
The sequence spine (per segment, slots in the pack)
- T-6w — Touch 1: we'll be at X, here's why it matters to you. (6 weeks ideal; 4 is the minimum viable start.)
- T-3–4w — Touch 2: value add — a data point, a case pattern, a relevant article. This lands in the window when attendees plan their conference schedule.
- T-2–3w — Touch 3: the meeting ask, with two specific time options drawn from the reserved exec calendar blocks.
- T-5–7d — Touch 4: brief, polite last call to non-responders.
- T-3d: logistics note to everyone booked (where, when, mobile numbers).
Channel mix: email carries the spine; LinkedIn carries touches 2 and 4 (as a fellow attendee, not a vendor); a call from the deal owner backs the ask on open opps; physical/hand-written notes reserved for VIP dinner invites (they earn their cost only there — memo-03 direct-mail data).
What good looks like (calibration, sources in research-foundations)
- Event-triggered outreach reliably runs 2–3× cold-email baselines; signal-referencing emails see 5–18% replies vs the ~3.4% cold average. Bars for our tracking: <2–3% positive reply = list or message problem; 4–6% = healthy; 8%+ = the personalization is working.
- Subject lines: value/outcome-led beats logistics-led ("The 15-minute AI-readiness benchmark" > "Meet INTO at X"); under 60 characters; from a named human. For 1:1 exec notes, plain and specific wins: "Coffee at <event> Tuesday?"
- Every touch carries exactly one CTA, and the booking link resolves to reserved exec calendar blocks — the comms owner reserves those blocks (slots × length, lunches protected) before touch 1 goes out.
Mechanics that keep it honest
- List building is selection work (chapter 01): sponsor list entitlements (ask for timing before signing — many top-tier events share nothing), LinkedIn event RSVPs and "heading to X" posts, speaker/exhibitor rosters, client and community intel. Respect platform rules and privacy law — no scraped-list purchases; event lists arrive under GDPR-shaped terms and get used within them.
- CRM hygiene from touch 1: every contacted person is tagged with the
event_idcampaign at first touch — attribution at T+90 is built now, not reconstructed later. - Tracking table in the pack reviewed weekly at T-4w/T-2w/T-0: sent, replies, meetings booked vs the P2 target. Under 50% of meeting quota at T-3w triggers the downgrade gate (chapter 03).
- The broadcast layer (newsletter block, company LinkedIn post at T-2w) exists to make the outbound touches feel ambient, not to book meetings; it never replaces the 1:1 spine. SMM owns it per chapter 08.
Voice
Elliot posture (senior operator, calm confidence), neuromarketing sequencing for long-cycle B2B (reference/ files named in the brief), CEF terminology for Consulting. No hype words, no client names, nothing that reads like a booth flyer. The test for every touch: would the recipient forward this to a colleague as useful even if they never meet us?