Scheduling Ops

Booking Reminder Flow with No-Show Recovery

Timed reminders before a booked call and an automatic recovery path when someone no-shows, so the calendar stays full without the team chasing confirmations by hand.

Start a ProjectAll Case Studies
4 to 7 days
build time
4
outcomes
5
stack tools
6
build steps

Built with real HMX tool paths

CCal.com Webhooks
MMake
TTwilio SMS
RResend
GGoHighLevel
CCal.com Webhooks
MMake
TTwilio SMS
RResend
GGoHighLevel

Outcome signals

These are the real outcome statements attached to this HMX case study.

Fewer
no-shows from consistent timed reminders
Auto-rebook
no-shows get a recovery path instead of vanishing
Capped
attempts stop and hand to a human, no endless nudging
In-sync
CRM always reflects true attendance status

Case architecture

Booking Reminder Flow with No-Show Architecture

6 nodes
on Cal
Schedule 24h and 1h email +
Cal
Make
Exception Path
Booked Handoff
  1. 01on Cal

    Timed reminders before a booked call and an automatic recovery path when someone no-shows, so the calendar stays full without the team chasing conf...

  2. 02Schedule 24h and 1h email +

    Schedule 24h and 1h email + SMS reminders with quiet-hours and reply-stop conditions

  3. 03Cal

    Cal.com Webhooks carries Booking Reminder Flow with No-Show through validated triggers, branches, writebacks, and exception paths.

  4. 04Make

    After the slot, read booking status to detect attended vs no-show

  5. 05Exception Path

    When automation confidence is low, route the record to a manual owner with the source, stage, and last action attached.

  6. 06Booked Handoff

    Fewer no-shows from consistent timed reminders; Auto-rebook no-shows get a recovery path instead of vanishing; Capped attempts stop and hand to a h...

Problem

The operating gap

Booked calls slip because reminders are inconsistent and no-shows just disappear. Nobody reliably follows up to rebook, owners waste slots, and the CRM never reflects whether the call actually happened.

Build

What gets built

A Cal.com booking webhook starts a reminder sequence: email + SMS at fixed windows (24h, 1h) with quiet-hours respected and a stop condition if the lead replies or reschedules. After the slot, the workflow checks booking status; a no-show triggers a short recovery sequence offering a rebook link, capped at a set number of attempts before it hands off to a human task. Every state change writes back to the CRM so the record always shows confirmed, attended, no-show, or rebooked.

Build steps

Booking Reminder Flow with No-Show Recovery uses an event-driven automation layer for AI Automation. Timed reminders before a booked call and an automatic recovery path when someone no-shows, so the calendar stays full without the team chasing conf... The architecture connects on cal, cal, make, and booked handoff with an explicit control path.

  1. 01Trigger on Cal.com booking.created and verify the X-Cal-Signature-256 header
  2. 02Schedule 24h and 1h email + SMS reminders with quiet-hours and reply-stop conditions
  3. 03After the slot, read booking status to detect attended vs no-show
  4. 04Fire a capped no-show recovery sequence with a rebook link
  5. 05Hand off to a manual task after the attempt cap is reached
  6. 06Write confirmed / attended / no-show / rebooked status back to the CRM record

Stack

Tools and layers

  • Cal.com Webhooks
  • Make
  • Twilio SMS
  • Resend
  • GoHighLevel
  • Event layer: Trigger on Cal.com booking.created and verify the X-Cal-Signature-256 header
  • Validation layer: Schedule 24h and 1h email + SMS reminders with quiet-hours and reply-stop conditions
  • Branching layer: Cal.com Webhooks carries Booking Reminder Flow with No-Show through validated triggers, branches, writebacks, and exception paths.
  • Writeback layer: Make handles routine steps while a Cal.com booking webhook starts a reminder sequence: email + SMS at fixed windows (24h, 1h) with quiet-hours respected and a stop condition if the...
  • Exception layer: Fewer no-shows from consistent timed reminders; Auto-rebook no-shows get a recovery path instead of vanishing; Capped attempts stop and hand to a h...

Data flow

  1. 01Trigger on Cal.com booking.created and verify the X-Cal-Signature-256 header
  2. 02Schedule 24h and 1h email + SMS reminders with quiet-hours and reply-stop conditions
  3. 03After the slot, read booking status to detect attended vs no-show
  4. 04Fire a capped no-show recovery sequence with a rebook link
  5. 05Hand off to a manual task after the attempt cap is reached
  6. 06Write confirmed / attended / no-show / rebooked status back to the CRM record

Controls

  • Booked calls slip because reminders are inconsistent and no-shows just disappear.
  • A Cal.com booking webhook starts a reminder sequence: email + SMS at fixed windows (24h, 1h) with quiet-hours respected and a stop condition if the...
  • When automation confidence is low, route the record to a manual owner with the source, stage, and last action attached.

Research basis