Automations
Reminders, confirmations and alerts as "when this happens, do that" rules.
Automations are rules made of a trigger, optional conditions and an action. Each business template ships with sensible defaults you can edit.
Triggers
| Trigger | Example |
|---|---|
booking.confirmed | Send the booking summary |
booking.starts_in(Δ) | 24 h before: ask for YES/NO confirmation |
booking.ended(+Δ) | 1 h after: suggest checking attendance |
booking.cancelled, booking.rescheduled | Notify staff |
hold.expired | Follow up with the customer |
payment.paid | Confirm and thank |
daily_at(hh:mm) | Send the day's agenda to staff |
Conditions
Service, resource, party size above N, channel, customer tag, number of past no-shows.
Actions
Send a message or template to the customer, notify staff, request a YES/NO confirmation, change the booking status, create an internal task, call a webhook.
Defaults by business
| Template | Automations |
|---|---|
| Barbershop, aesthetics, clinic | Reminder 24 h before with YES/NO · staff heads-up 2 h before · attendance check 1 h after · daily agenda 7:30 |
| Restaurant | Reminder the day before · confirmation required for parties above 6 · daily agenda |
| Deliveries | "On the way" 1 h before · delivery received confirmation |
Execution guarantees
- Jobs are created in the same transaction as the booking event, so they are never lost.
- Before running, a job re-checks the booking. If it was rescheduled or cancelled, the old job is discarded.
- Each job runs once (idempotency key) and retries with backoff; after 5 failures it shows up in the dashboard.
- Quiet hours: nothing is sent to customers between 21:00 and 08:00 in their time zone.
- YES/NO answers are parsed without AI (
sim,sí,ok, 👍,não…), which is instant and free.