---
name: meeting-no-show-recovery
description: Finds meetings that happened with no follow-up logged (likely no-shows or dropped threads) and drafts a recovery email with a reschedule offer plus a follow-up task for each. Use when the user asks to "recover no-shows", "who ghosted my meetings", "draft reschedule emails", "clean up missed meetings", or runs a recurring no-show sweep.
license: MIT
compatibility: Requires a connected CRM (and calendar where available). Read-only — drafts recovery, no writes.
metadata:
  author: Builder.org
  version: 2.0.0
  persona: Strategic Steve, Operator Owen
  rave: R4 A4 V3 E3
  category: crm
---

# Meeting No-Show Recovery

## What it does

Catches meetings that came and went with nothing logged after them, the quiet no-shows and dropped threads, and drafts a graceful recovery email for each so they get rebooked instead of forgotten. A missed meeting recovered inside a week usually reschedules; one discovered a month later is a cold start.

## When to use

- "Recover no-shows", "who ghosted my meetings", "draft reschedule emails", "clean up missed meetings".
- As a recurring weekly sweep.
- Not for meetings that happened and need a summary or follow-up email; that is `meeting-follow-up-coach`. This skill is for the ones where nobody showed or nobody followed through.

## Inputs

None required. Optional: lookback window (default: meetings between 24 hours and 14 days old). Works with any CRM your assistant can read (HubSpot, Salesforce, or similar); it only needs meetings and engagements.

## The bar

- Tone is the product. Every draft assumes a busy calendar, never a snub. Zero guilt, zero "I waited on the call for 15 minutes".
- Every draft contains a reason to re-engage, not just a reschedule link. "Why meet" has to survive the miss.
- Drafts are under 75 words. A no-show recovery is a light tap, not a case for the meeting's importance.
- A meeting already handled (any later touch exists) never appears. False positives teach the user to ignore the list.

## Workflow

1. **Find candidates.** Meetings older than 24 hours with no call log, note, email, or task recorded after them. The 24-hour floor exists because same-day follow-ups are often just not logged yet; the 14-day ceiling because past two weeks this stops being recovery and starts being re-outreach.
2. **Confirm the gap.** Check for any later engagement with the contact on any channel and skip handled ones silently.
3. **Classify the miss** where the data allows: they no-showed, we no-showed, or it happened but nobody followed up. The draft differs: an apology belongs only in the middle case.
4. **Draft the recovery per contact.** Warm, short, easy yes: one line of context, one line of why meeting is still worth it (tied to whatever prompted the original booking), one reschedule offer with two concrete windows or a link placeholder.
5. **Attach a task suggestion** per row: a follow-up reminder 3 business days out if no reply.
6. **Output the list**, most recent misses first, since fresh ones recover best.

## Output

```
## No-show recovery · [date]
1. **[Name, Company]** · meeting [date] · [they missed / we missed / no follow-up]
   Subject: [subject line]
   [Body under 75 words with a reason to re-engage and two time offers]
   Task: [follow-up reminder + date]
2. ...
```

## Worked example

```
Fictional example. Never reuse these names or numbers in real output.

## No-show recovery · March 3
1. **Tomas Herrera, Fieldstone Payroll** · meeting Feb 27 · they missed
   Subject: we'll try that again
   Tomas, Thursday clearly got away from one of us, and my money is on your calendar being the busier one. Still keen to show you the credentialing flow we discussed, since your compliance launch makes the timing good. Does Tuesday at 10 or Wednesday at 2 work? If it's easier, grab any slot here: [link].
   Task: remind me Friday, March 6 if no reply.

2. **Dana Okafor, Brightpath Staffing** · meeting Feb 24 · happened, no follow-up
   Subject: the two things I owed you
   Dana, good conversation last Monday, and I owe you the onboarding checklist and the reference contact. Both attached. If it's useful, I'd take 20 minutes next week to walk through the checklist against your process. Tuesday or Thursday afternoon?
   Task: remind me Thursday, March 5 if no reply.
```

## Never

- Never guilt the contact, mention waiting, or ask what happened. The reason for the miss does not matter; the rebook does.
- Never send-style a recovery with no substance beyond "reschedule?". The why-meet line is mandatory.
- Never surface a meeting that has any later touch on any channel.
- Never write the email, create the task, or edit the meeting record. The rep sends; the skill drafts.

## Recovery

- Cannot tell who missed whom: write the neutral version ("Thursday got away from us") which reads correctly in every case.
- No context on why the meeting was booked: pull the reason from the deal stage or the original invite title; if truly nothing, keep the why-meet line generic to their company and flag it for the rep to sharpen.
- The same contact missed twice: one draft, not two, acknowledging nothing, offering the lightest possible ask (15 minutes, or an async alternative like a two-minute video).
- Calendar data unavailable: work from the CRM's meeting engagements alone and say the sweep only sees logged meetings.