Events Outreach by Anthony

User wants clear recommendations; lead with the call the assistant would make.

Assistant uses a dedicated Gmail outreach inbox for sales outreach (separate from the user's personal inbox).

Preferred prospecting model: assistant uses Apollo for lists/enrichment and email outreach; an executive assistant runs LinkedIn / Sales Nav from lookalike packs; the user focuses on calls.

Booking CTAs should say the 15-min call is with the Events team (not the sales lead by name).

Gmail API sends do not auto-append the Gmail Settings signature; include the team signature HTML in the email body on every send and draft.

Outreach signature for API sends is text/HTML only — no CID or hotlinked logo, because Gmail API shows inline images as attachments and they distort. Full logo signature belongs in Gmail Settings for manual UI compose only.

For email replies from the outreach inbox: always draft and show the user for review before sending — never send a reply without explicit approval.

CC the sales lead and events owner on all outbound outreach emails and replies.

Warm outreach tone (locked): no venue or location names past or present; offer is simply a private event experience; no guest counts; light past-event nod only when the user verified the correct person/event; CTA remains a 15-min call with the Events team.

ICP for event bookings: client-entertainment / brand partnerships, brand-activation agencies, experiential/event planners, Office Managers / People Ops, and CPG for custom or mobile activations; call-first playbook with a short calendar CTA, history-led emails, and phone follow-ups on warm tier-1.

Weekly call-first cadence: Mon–Tue send personalized emails to tier-1 warm accounts; Wed–Thu call and follow opens; Fri book holds; park most one-off social hosts.

Pipeline mix: warm re-engage past event contacts each week, plus net-new lookalikes found on LinkedIn then enriched and emailed; ask for referrals on every booked call.

Before drafting warm outreach, verify the correct past event per contact with the user; do not mass-create drafts with unmatched event hooks.

Wave cadence pattern: early-week warm send wave, mid-week second warm wave, following week remaining warm plus first cold lookalike batch once enrichment credits are approved.

Uses Apollo.io for prospect lists and enrichment alongside Gmail for outreach drafts and sends.

Monday morning: confirm with the user, then send the approved warm outreach drafts from the dedicated inbox.

Mid-week morning: draft the next warm outreach wave for user approval before staging Gmail drafts.