AI-generated event follow-up (L3)

Trade show scans → enrich → personalize → sequence within 24h. The window matters.

WORKFLOW1Import and Enrich Lead Sc…nsManual2Generate Personalized Ope…ers via LLMManual3Push Contextual Data to S…quencerManual4Execute 5-Touch High-Inte…sity SequenceManual5Track ROI and Pipeline At…ributionManual
5 steps, in order, with the tool that owns each one.
Adoption ladderSix levels from Starter to Rebuilt. This item sits at level 3.L1 StarterOne tool, no workflow changeL2 AssistedAI drafts, humans approveL3 IntegratedWired into CRM and SlackL4 OrchestratedMulti-step, owned, measuredL5 AutonomousAgent runs, human auditsL6 RebuiltThe process itself changes
This playbook belongs at L3 Integrated. Running it above your level is how pilots stall.
Measures of successevent-sourced pipeline; lead-to-meeting ratePROVE IT WORKEDevent-sourced pipelinelead-to-meeting rate

The steps

  1. 01

    Import and Enrich Lead Scans

    The Marketing Event Manager and Ops Lead must establish a data bridge between the physical lead scanner (e.g., Cvent, Swapcard, or Stova) and the enrichment layer. Within 4 hours of the event closing, export the lead CSV. • Go to your Event Management platform's 'Leads' or 'Reports' tab. • Ensure you export 'Notes' or 'Conversation' fields,this is where your SDRs wrote down booth context. • Create a new Workspace in Clay (clay.com) and import this CSV. • Map the 'Email' column and 'Company' column precisely. • Add an enrichment column for 'Find LinkedIn Profile' to ensure you are targeting the person, not just the generic email. • Use the 'Enrich Company' action to pull the latest firmographics (headcount, industry, recent news) which will be used for AI context. The goal is to have a clean, enriched table ready for the LLM by the end of the show day. PITFALL: Forgetting the Notes field. Without notes, the AI can't bridge the gap between 'Generic Attendee' and 'Potential Buyer.' DONE: A Clay table with 100% of scanned leads, their LinkedIn URLs, and firmographic data attached. TIME: 1 Hour.

  2. 02

    Generate Personalized Openers via LLM

    The RevOps Specialist will now configure the 'AI Agent' or 'HTTP Request' column in Clay to synthesize the event context. Use the GPT-4o model. • In Clay, add a new column: 'AI' -> 'Write Personalized Text.' • Input the following prompt: 'Given the attendee name {{Name}} from {{Company}} and the booth notes "{{Notes}}", write a 1-sentence opening for an email. Mention we met at [Event Name] and specifically reference the conversation about {{Notes}}. Keep it casual and professional. If notes are empty, mention their recent company news about {{Latest_News}}.' • Set the 'Creativity' (Temperature) to 0.5 to balance novelty with professional tone. • Run a sample of 5 rows to ensure the output doesn't sound 'bot-like.' This step transforms a cold lead into a 'warm' follow-up by proving you listened at the booth. PITFALL: Over-automating empty notes. If a note says 'Interested,' the AI might write a weird sentence. Add a conditional 'If/Else' formula in Clay to use a generic 'Great meeting you at the booth' if the notes contain fewer than 3 words. DONE: A completed column in Clay titled 'Opening_Line' for every lead. TIME: 1.5 Hours.

  3. 03

    Push Contextual Data to Sequencer

    The SDR Manager or Marketing Lead must sync the enriched leads to the sales engagement platform (Salesloft, Outreach, or Apollo). • In Clay, use the 'Export to Sequel' or native integration button. • Map the 'Opening_Line' column from Clay to a 'Custom Field 1' or 'Personalization_Block' attribute in your CRM/Sequencer. • Map the 'Event_Name' to a custom field so you can track attribution. • Set the 'Lead Source' to 'Trade Show - [Name of Event].' • Ensure leads are assigned to the correct owners based on territory or show attendance. The handoff must happen within 12 hours of the event to ensure the message hits the inbox while the lead is still traveling or catching up on work. PITFALL: Mapping data to the wrong fields, causing the AI opener to be overwritten by a generic template. Triple-check your field mapping settings in your Zapier or Clay integration. DONE: Lead records created in the sequencer with their custom AI snippets populated. TIME: 45 Minutes.

  4. 04

    Execute 5-Touch High-Intensity Sequence

    The Copywriter or SDR Lead must build a 5-step 'Event Recovery' sequence. This is shorter than a standard cold sequence because the interest is time-sensitive. • Step 1: Manual Email (Day 1). Use the dynamic tag {{Custom_Field_1}} (your AI opener) as the first line. Ask for a 10-minute recap call. • Step 2: LinkedIn Connection Request (Day 2). Use a simple: 'Great meeting at [Show Name], {{First_Name}}! Just sent an email, let's connect here.' • Step 3: Automated Email (Day 4). Mention a specific whitepaper or case study related to the event's theme. • Step 4: Soft Bump (Day 7). 'Hey {{First_Name}}, wanted to make sure our booth conversation didn't get buried in the post-show inbox chaos.' • Step 5: Final Break-up (Day 10). 'Assuming priorities shifted after the show. I'll reach out in 6 months.' PITFALL: Making the sequence too long. Post-event fatigue is real; if they don't reply in 5 touches, they aren't ready. DONE: A live sequence ready to be toggled 'On' for the imported leads. TIME: 2 Hours.

  5. 05

    Track ROI and Pipeline Attribution

    The RevOps Lead or Marketing Analyst must set up the tracking dashboard to justify the event's $10k+ sponsorship cost. • In your CRM (Salesforce/HubSpot), create a Campaign with the 'Event' type. • Use a 'Lead Source' report to filter for leads added during the show dates. • Create a 'Pipeline by Event Source' chart showing 'Opportunity Stage' for all leads in the sequence. • Calculate 'Cost Per Meeting' by dividing the total show cost (booth + travel + swag) by the number of meetings booked from the sequence. • Review these metrics 30 days after the event. If the lead-to-meeting rate is below 5%, refine the AI prompt or the SDR booth note requirements. PITFALL: Failing to tag leads to the Campaign immediately. If they aren't tagged, you lose the ability to prove that a $50k deal originated at a specific booth. DONE: A dashboard showing: Total Scans, Meetings Booked, Pipeline Generated, and ROI per Event. TIME: 1 Hour.

Next playbooks

Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.

Share this playbook

Posting to Instagram or TikTok? Copy the link, it carries the title, summary and share image.

Arrives weekly by email. Free. Unsubscribe anytime. By subscribing you agree to our Privacy policy and Terms. We never sell or share the list.