Skip to content
Docs home

CORE CONCEPTS · UPDATED AUGUST 2026

Notifications & Templates

Four verified events (confirmed, reminder, cancelled, staff notify) delivered over email, SMS, and WhatsApp, with per-template control and a delivery log.

Events and channels

The notification system dispatches on four verified event keys: booking_confirmed, booking_reminder, booking_cancelled, and staff_notify. Delivery runs over three channels: email, SMS, and WhatsApp. Each event's template set is editable per tenant, so businesses control the voice of their own messages without touching code.

Failure model

Notification dispatch is best-effort and never throws back to the caller: the booking creation that triggered it completes regardless of whether a message could be sent. Failures are recorded in the per-tenant notification log, where operators can see which messages did not deliver and why. The reminder orchestration layer adds rate protection (a per-minute SMS cap) and bounded retries with declared attempt limits.

Delivery is provider-dependent

QUE sends; carriers and providers deliver. A message leaving QUE is not the same as a message arriving on a phone. Template, channel, and retry behavior are documented here — carrier delivery rates and settlement are the provider's domain.

STILL READING

Something here still feels worth checking together.

This documentation describes the product exactly as it is implemented. If a behavior you expected is not here — or is here and does not match your deployment — tell the team. Implementation questions start on the contact page.