One state machine on the appointment. Stamps for each reminder, completion, no-show, both no-show emails, and cancellation live on the row so every step fires exactly once. A cron sweeps every five minutes.
Also called: meeting reminders · no show follow up · cancel a meeting · what happens after a booking
- 1Reminders fire at 24 hours, 1 hour and 5 minutes before, to the prospect and the host, each with a Join button when there is a meeting link.
- 2Done captures an outcome note; No-show starts the empathy-first sequence; Cancel asks for a reason and shows the exact message the prospect will receive.
- 3Google-sourced personal events are excluded from every step — they carry no automations.
- 4Every email is sent with a source tag of appt:<id>:<step> so opens and clicks can be read back per appointment.
Migration 246 and the flow file record it as. The tone is prescribed, not incidental: no-show email one is 'empathy first ("is everything okay?"), nothing about rebooking', and email two is 'still humble: checking in again, zero pressure, door open'.
- Silent no-shows
- Reminders sent twice or not at all
- Cancellations with no explanation
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →