---
name: no-show-recovery
description: Builds follow-up for event and webinar registrants who didn't attend. Splits no-shows by engagement and value (target account, open opportunity, customer, opened reminders, past attendee, cancelled ahead), writes recovery emails with the replay, a recap or a meeting offer, re-invites dinner and field event no-shows, and sets send timing. Use after a webinar, virtual event, conference, field event, roadshow or executive dinner when the user has a registrant list with attendance status and asks about no-shows.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: leads-and-follow-up
  source: https://eventmarketingsoftware.com/skills/no-show-recovery
---

# No-show recovery

People who registered and didn't come are already warm. Most teams send them one generic "sorry we missed you" with a replay link. This skill segments no-shows by how engaged and valuable they are, writes a short recovery sequence per segment, and hands target accounts to sales with a personal note.

Campaign member status values (No Show, Cancelled, Attended On-Demand) and flags follow [references/shared-terms.md](references/shared-terms.md). For people who did attend, use event-follow-up-sequences or webinar-attendee-scoring.

## Intake

1. Read `event-context.md` (or `event-program-context.md`) if present: company, sender names, tone, target account list, CRM, next events.
2. Ask for anything missing, in one message:
   - Registrant list with attendance status (registration platform export, webinar report or CRM campaign members). Engagement columns help: reminder opens or clicks, registration date, past attendance, registration questions.
   - Event type, name, date and what happened (key takeaways, or the recording and slides).
   - The recovery asset: replay link, recap, slides, or the next date for in-person formats. Use placeholders if links aren't ready.
   - Target account list and customer list, or a CRM connector to check them.
   - Sender for the sales-led segment.

## Connectors (optional)

- **HubSpot or Salesforce connector**: read campaign members with status No Show and Cancelled, account owner, customer status and open opportunities. Create tasks, lists or drafts only after the approval gate.
- **Google Sheets connector**: read the list and write segments to new tabs.
- **Otherwise**: work from the uploaded or pasted list and return CSVs plus Markdown copy.

## Method

### 1. Confirm who's really a no-show
- No-show = registered, didn't attend live, didn't watch on demand. If the export has replay views, those people are Attended On-Demand, not no-shows.
- Separate `Cancelled` (told you they couldn't come) from silent no-shows.
- Remove internal staff, speakers, sponsors and competitors, and say how many.
- Check that attendance data is complete. If check-in data is missing for a whole session or day, stop and ask; don't treat everyone as a no-show.

### 2. Segment
Assign each no-show to one segment, first match wins:

| Segment | Rule | Sender | Goal |
|---|---|---|---|
| S1 Sales priority | Target account, open opportunity, or senior title (VP and up) at an ICP account | Account owner | Personal note with recap and a meeting or private walkthrough offer |
| S2 Customers | Existing customer | Account manager or CSM | Replay plus what it means for them |
| S3 Engaged | Opened or clicked a reminder, registered in the last 7 days, answered a registration question, or attended a past event | Event marketer | Replay or recap, then a next step |
| S4 Low engagement | Everyone else | Event marketer | One replay or recap email, then nurture if consent allows |
| S5 Cancelled ahead | Told you they couldn't make it | Event marketer or host | Thanks for letting us know, recap, invite to the next one |

The user's rules override these. For in-person formats (dinner, field event, roadshow), S1 and S3 get a re-invite to the next date in the same city when there is one.

### 3. Write the messages
Use [references/recovery-playbook.md](references/recovery-playbook.md) for timing and format specifics and [references/email-examples.md](references/email-examples.md) for examples. Rules:
- Email 1 within 24 hours of the event (48 at most): no guilt, no "we missed you!" theatrics, the replay or recap up front.
- A recap is 3 bullets of real takeaways, written from the user's notes or transcript. Never invent what speakers said.
- One ask per email. Subject lines under 7 words.
- S1 notes come from the owner's own mailbox, under 100 words, referencing why this topic matters to their account if the user gave that context.
- Use placeholders `{{replay_link}}`, `{{slides_link}}`, `{{next_event_link}}`, `{{booking_link}}`.

### 4. Timing

| Touch | Webinar or virtual | Conference | Dinner, field event, roadshow |
|---|---|---|---|
| 1 | Replay and recap, within 24 hours | Recap and session recordings, within 48 hours | Personal note from the host, within 48 hours |
| 2 | One takeaway plus CTA, day 3 or 4 | Most-watched session plus CTA, day 5 | Re-invite to the next date, 2 to 3 weeks before it |
| 3 | Meeting or next event, day 7 to 10 (S1 to S3 only) | Meeting offer, day 10 (S1 only) | Reminder of the next date (S1, S3) |

### 5. Exit rules
- Anyone who watches the replay becomes Attended On-Demand: stop the no-show sequence and hand them to webinar-attendee-scoring or event-follow-up-sequences.
- Anyone who replies, books or unsubscribes leaves the sequence.

## Output

**1. Segment table**

| Segment | People | Sender | Touches | First send | Notes |
|---|---|---|---|---|---|

Plus totals: registrants, attended live, attended on demand, cancelled, no-shows, excluded. Show the live attendance rate and say what it's based on.

**2. Email copy per segment** with subject lines and send days, in this structure:

```
## S1 Sales priority (sender: account owner)
### Email 1, send within 24 hours
## S2 Customers
...
```

**3. Segment file** (CSV): `email`, `first_name`, `last_name`, `company`, `title`, `segment`, `segment_reason`, `sender`, `owner`, `email_1_date`, `email_2_date`, `email_3_date`, `campaign_member_status`, `consent_note`.

**4. Sales task list** for S1: owner, person, account, reason, suggested note, due date.

A worked example, built from `assets/sample-registrants.csv`, is in [references/examples.md](references/examples.md). Benchmarks for context (dated and sourced) are in [references/benchmarks.md](references/benchmarks.md).

## Validation checklist

- [ ] Registrants = attended live + attended on demand + cancelled + no-shows + excluded. Show the arithmetic.
- [ ] Every no-show is in exactly one segment with a reason.
- [ ] No replay viewer is in the no-show file.
- [ ] Recap bullets come from the user's material; nothing invented.
- [ ] S1 notes have an owner and a due date.
- [ ] EU/UK no-shows without opt-in get only the replay or recap they registered for, not the marketing touches.

## Approval gates

- Draft only. Never send, enroll or post.
- With a connector, preview any tasks, list changes, status updates or drafts (who, what, when) and get an explicit yes first.

## Privacy and consent

Registrant data is personal data; keep it in the user's tools. Sending someone the recording or recap of an event they registered for is usually seen as part of what they asked for, but later marketing emails need consent or another lawful basis, especially for EU and UK contacts. Flag them and let the user's privacy lead decide.

## Pushback

- "Just send everyone the replay": fine as a baseline; show that pulling out S1 and S5 takes minutes and S1 is where meetings come from.
- "Say seats are limited for the next one": only if true.

## Related skills

crm-event-import (No Show and Attended On-Demand statuses), webinar-attendee-scoring (for people who watched), event-follow-up-sequences (for attendees).
