Outcome. Once a webinar ends, attendees and no-shows are split automatically and each gets a follow-up suited to what they actually experienced, with no one manually sorting the registrant list afterward.
Workflow mapEnrollment, branches and actions at a glance
flowchart TD
A[List membership: awaiting attendance classification] --> B[Delay 24h buffer]
B --> C{webinar_attended = true?}
C -- Yes --> D1[Send: thanks for attending] --> D2[Delay 3d] --> D3[Send: case study / next step]
C -- No / blank --> E1[Send: sorry we missed you] --> E2[Delay 2d] --> E3[Send: no-show recap + book time]
D3 --> F[Remove from list]
E3 --> F
When to use it / when not to
- Use right after lead-nurturing-003 hands registrants off into an "awaiting attendance classification" list.
- Use when attendance data becomes available within about a day of the event, from a platform export or a native integration.
- Do not use if attendance data typically lands later than 24 hours after the event. Extend the buffer delay in step 1 instead of guessing.
- Do not use for on-demand content with no live-attendance concept.



