The three waves
Every new booking plans three reminder waves at creation time: booking_created (immediate), day_before (the day preceding the appointment), and two_hours (two hours before). The wave set and its default offsets are defined in the reminder orchestration contract and enforced at the schema level — a wave outside the contract cannot be saved.
| Wave | When it fires | Purpose |
|---|---|---|
| booking_created | At booking creation | Confirm the booking and share the management link |
| day_before | Day before the appointment | Reduce no-shows with a timely prompt |
| two_hours | Two hours before the appointment | Final prompt while the plan is still actionable |
Recipients and channels
Reminder recipients can be the customer, the appointee, or an employee. Channels include SMS, WhatsApp, email, voice, and in-app notification, with the tenant's enabled channels controlling what actually delivers. Customers who have opted out of SMS reminders are skipped for SMS waves (the booking_created wave is exempt, since it carries the confirmation itself).
Rate protection and retries
The dispatcher enforces a per-minute SMS cap and retries failed sends up to a declared attempt limit before marking a message failed. Every planned reminder carries a status — pending, sent, failed, suppressed, or cancelled — so operators can see exactly what happened to each message rather than guessing.
Reminder ≠ delivery guarantee
QUE schedules, dispatches, and retries; carriers deliver. A message marked sent has left QUE. A message marked failed has exhausted its retries and is logged for operator review. Do not treat reminder success as proof the customer saw anything.