## TL;DR
The agent never learns about the no-show because nothing tells it: Calendly knows, the sequence does not. Subscribe to Calendly's webhook events for cancellations and no-shows, and on each event pause the lead's standard follow-up track and enroll them in a dedicated no-show rebooking track with a fresh booking link.

## The query

```text
calendly 'invitee no-show detected'  -  agent kept the sequence running instead of triggering the no-show follow-up
```

## Steps

### 1. Subscribe to Calendly cancellation and no-show webhooks
In the Calendly integration settings, create a webhook subscription for invitee cancellation events (and no-show detection where available), pointed at the agent's event endpoint. Verify the subscription with a test event.

Expected: test events arrive at the agent's endpoint and are logged.

### 2. Map the event to the lead and their active sequence
On each event, match the invitee email to the CRM contact and find their active sequence enrollment. Log the no-show on the contact timeline so the AE sees it too.

Expected: the event resolves to exactly one contact and one active enrollment.

### 3. Pause the standard track and enroll the no-show track
Pause the lead's normal follow-up sequence and enroll them in a no-show track: a short, empathetic rebooking sequence with a fresh scheduling link, not the standard nurture content. Cap it at two or three touches.

Expected: the lead leaves the standard track and enters the no-show track within minutes of the event.

### 4. Add a polling fallback for missed webhooks
Webhooks occasionally fail silently. Add a nightly job that asks Calendly for recent events and reconciles any no-show the webhook missed, so no lead sits in the wrong track for more than a day.

Expected: the reconciliation job finds zero unhandled no-shows on a clean run.

## Use this when

- Calendly reports a no-show but the agent's sequence keeps running unchanged
- Reps complain that no-show leads never get rebooking outreach
- The agent has no webhook subscription for scheduling events

## Not for this skill when

- The booking page itself errors (that is a Calendly configuration problem)
- Calendly API calls fail with invalid_grant (that is OAuth, not event handling)
- The problem is leads booking but never showing with no event recorded anywhere

## Variant phrasings

### calendly no show not triggering follow up
Short form. The webhook-to-track wiring is the fix.

### agent ignores calendly no-shows keeps emailing
Symptom phrasing. Same pause-and-reenroll handling.

### calendly invitee no-show detected but sequence continues
Explicit form of the same gap. Identical steps.

## Why it happens
Scheduling state lives in Calendly and sequence state lives in the outreach tool, and nothing connects them unless someone builds the bridge. The agent only knows what its own tools report, so a no-show recorded in Calendly is invisible to it. The standard track then keeps sending as if the meeting happened, which reads to the lead as if nobody noticed they missed it.

## Edge cases

- A lead who cancels and rebooks themselves should leave the no-show track. Handle the new-booking event as an exit condition.
- Duplicate webhook deliveries happen. Make the enrollment idempotent on the event ID so a redelivered event does not double-enroll.
- If the no-show track's booking link expires or the rep's calendar disconnects, the track silently fails. Monitor booking-link validity.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_pB1qZKM8TbbHzYBp4fAYMw