Automations
Simple reminder and confirmation rules, quiet hours and execution guarantees. For waits and conditions, see flows.
Updated:
There are two automation tools:
- Rules: "when this happens, send that message". They are the simplest way to send reminders and confirmations. They are managed in Automation → Rules.
- Flows: they wait, decide with conditions and act on tasks. See Flows and Conditions.
Rules
A rule has a trigger, the message it sends (a template with preview) and, if you want, a filter by stage or action. Each business creates, activates and adjusts its own: industry templates do not turn rules on by themselves.
Triggers
| Trigger | Example |
|---|---|
| Booking confirmation | Send the summary |
| Some time before the start | 24 h before: send a reminder |
| Some time after the end | Follow-up message |
| Cancellation or reschedule | Notify the customer |
| Stage or action change | When the task moves to another stage (for example "Out for delivery") |
| Fixed time of day | Team alerts, such as the day's agenda |
Rules aimed at customers go out through WhatsApp. Team alerts go out through Telegram, WhatsApp or email, depending on how each person receives alerts: see Team Telegram.
In each rule you see the latest sends with their status and the reason if one failed.
Execution guarantees
- Each send is scheduled together with the event that causes it, so it is not lost.
- Before going out, the system checks the task again. If it was rescheduled or cancelled, the old send is discarded.
- Each send goes out once and, if it fails, retries with growing waits; after 5 failures it shows in the panel.
- Quiet hours: nothing is sent to customers between 21:00 and 08:00 in the business's time zone. The send is deferred, not lost.
- YES/NO replies ("yes", "ok", "👍", "não"...) are interpreted without AI: instant and free.
Coming soon
Triggers for expired holds and for payments do not exist yet (they arrive with deposit collection).