A booking should still be remembered the morning of.
No-shows cost real money. This demo shows the confirmation, T-24h reminder, reschedule and no-show branches that keep a booking on the books without nagging.
What triggers this workflow
Cal.com booking fires a webhook with the customer, service and time.
Source: Cal.com webhook
Workflow steps
- Twenty CRM + Cal.comCaptureBooking lands in Twenty CRM with the customer, service and time.
- Listmonk + n8nConfirmConfirmation email with calendar invite, what-to-bring and reschedule link.
- Twilio + n8nT-24h reminderSMS reminder 24h before — only if the customer hasn't already replied.
- Cal.com + ListmonkRescheduleSelf-serve reschedule link in the reminder and confirmation.
- Twenty CRM + ChatwootNo-showNo-show branch applies the policy and sends a rebook message.
Tools used
Human handoff
The no-show policy is human-approved
Automated no-show handling only sends the rebook message — never a fee, penalty or accusation. Fee decisions are made by a human reviewer against the agreed policy.
- Customer is a no-show for the second time
- Customer disputes the no-show claim
- Booking is for a high-value or contract service
Try it in your browser
Edit the sample inputs, choose a branch, and see what the workflow produces. The sandbox runs offline — no accounts touched, no messages sent.
Try it in your browser
Edit the inputs, pick a branch, and see what the workflow produces. Runs entirely in your browser — no messages are sent, no accounts are touched.
1. Booking created
2. Confirmation message
Subject: Your consultation is booked — Thu 2:00 PM Hi Hannah, You're booked in for Thu 2:00 PM. You'll get a text reminder 24 hours before. If anything changes, reply to this email or text Sam direct. What to bring: • Anything you want to talk through • Photos if it helps (for home-service bookings) — Tidewater Spa, Manly
3. Branch handling
Hi Hannah, reminder: your consultation is tomorrow at Thu 2:00 PM. Reply YES to keep, RESCHEDULE, or CANCEL. — Tidewater Spa
Sample data only. Numbers, names and messages are placeholders for illustration. Wire the live workflow separately using the setup notes below.
Setup for production
Wiring it for production
Live deployment needs Cal.com, the SMS sender and a clear no-show policy.
- Configure Cal.com webhooks for booking.created and booking.rescheduled.
- Set the T-24h reminder window in the n8n workflow.
- Document the no-show policy and have a human reviewer approve it.
- Add a STOP-keyword handler for the SMS reminders.
Production prerequisites
- Cal.com event type with a real duration and availability
- Customer consent for the SMS channel
- No-show policy signed off and visible on the booking page
Nothing here runs by default. Configuration has to be in place before any live send, booking or contact write.
Questions
Does the workflow ever charge a no-show fee automatically?
No. Automated no-show handling only sends the rebook message. Fees are decided by a human reviewer against the agreed policy.
Can a customer reply STOP to the reminder?
Yes — STOP is honoured across the SMS channel and removes the contact from future reminders, while leaving the booking intact.
More demos you can run in your browser
Booking Confirmation & Reminder across the platform
Want this booking confirmation & reminder workflow running on your stack?
Pick the demo you're curious about or describe your own. We'll come back with what a real deployment looks like for your business — the workflow, the prerequisites, the people involved.