Sales & Notifications · n8n

No-Show Reducer: WhatsApp reminders that cut missed appointments by half

An n8n workflow that catches every new Calendly booking, then sends two perfectly-timed WhatsApp reminders via Twilio — 24 hours before (with a reschedule link) and 2 hours before (short and warm) — the pattern clinics, salons, and consultants use to halve no-show rates.

difficulty Intermediatesetup 40 minresult No-shows drop from ~20% toward single digits — pure recovered revenue
  1. 1

    Catch the booking

    Calendly → Integrations → Webhooks, event invitee.created, pointing at your n8n Webhook node. The payload carries name, phone (make phone a required booking question), slot time, and the reschedule/cancel links you'll reuse.

  2. 2

    Schedule both reminders

    A Code node computes the two send times (slot −24h, slot −2h), skipping any in the past. Two Wait nodes with dynamic resume times hold each branch until the moment — n8n persists waiting executions, so restarts don't lose reminders. Cancelled bookings (a second webhook on invitee.canceled) mark the row and the Wait branches check it before sending.

  3. 3

    Send the 24-hour reminder

    A Twilio node sends the approved WhatsApp template: appointment details, location/link, and the Calendly reschedule link with a 'life happens — grab a better slot' framing. Making rescheduling guilt-free is what converts would-be ghosts.

  4. 4

    Send the 2-hour nudge and log

    Short and warm: 'See you at 15:00, Jane! 📍 [address]'. Both sends append to the log sheet with delivery status from Twilio's response. After a month, compare no-show rates before/after — this recipe is one of the clearest ROI wins in the whole collection.

Frequently asked questions

Why WhatsApp instead of email or SMS?

Open rates. Appointment-reminder emails sit unread; WhatsApp messages are seen within minutes in most of the world (in the US, the same Twilio node sends SMS instead — one parameter). The 24h reminder with a reschedule link converts 'silent no-shows' into reschedules, which is the real win: the slot gets refilled.

Do I need WhatsApp Business API approval?

Twilio handles it: you register a WhatsApp sender through their console (approval typically takes days, not weeks) and pre-register the reminder as a message template, which is required for business-initiated WhatsApp messages. The workflow file includes the exact template text to submit.

What about clients who book two hours before the slot?

The Code step compares booking time to slot time and skips any reminder that would fire in the past or within 30 minutes of booking — a client who just booked doesn't need a reminder seconds later. Each reminder decision is logged so you can audit exactly what was sent to whom.

Related recipes

Daily KPI Digest: all your numbers, one message, zero dashboards

An n8n workflow that pulls your key metrics every evening — revenue from Stripe, orders from Shopify, traffic from your analytics sheet — has Claude write a three-line summary highlighting what changed and why it matters, and sends it to Telegram at 21:00.

Beginner · 30 min setup

Failed-Payment Rescue: recover churning subscribers with a kind email, not a scary invoice

An n8n workflow that catches Stripe's failed subscription payments, waits for the retry to fail too, then has Claude write a warm personal email with a one-click update-card link — recovering revenue that default dunning emails lose to their robotic tone.

Intermediate · 35 min setup

Stripe Payment Notifier: a cha-ching in Slack for every successful payment — with context

An n8n workflow that listens to Stripe's payment webhooks and posts a rich notification to Slack or Telegram for every successful charge: customer, product, amount, whether they're new or returning, and running total for the month.

Beginner · 20 min setup
About this recipe. Recipes on FlowRecipesHub are written for business owners, not developers, and are tested before publishing — how recipes get made. Some ingredient links are affiliate links that cost you nothing — full disclosure.