Automations

Simple reminders and confirmations, quiet hours and execution guarantees. For waits and conditions, see rules.

Updated:

There are two automation tools:

  • Reminders: "when this happens, send that message". They are the simplest way to send reminders and confirmations. They are managed in Customer care → Automatic messages.
  • Rules: they wait, decide with conditions and act on tasks. See Rules and Conditions.

Reminders

A reminder 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: no reminder ever messages a customer while it is off.

Triggers

TriggerExample
Some time before the start24 h before: send a reminder
Some time after the endFollow-up message
Cancellation or rescheduleNotify the customer
A task tool is usedWhen someone reschedules or takes the task
Fixed time of dayTeam alerts, such as the day's agenda

Reminders 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 reminder you see the latest sends with their status and the reason if one failed.

Notices when a task enters a stage (and the confirmation)

The customer notice when a task enters a stage —for example "Out for delivery"— and the confirmation notice are no longer reminders: they belong to the service stage, in its "On arrival" block. There is a single place for them and the customer never gets the same notice twice.

  • Each notice has its own switch. The ones that come with your business type arrive turned off, including "Out for delivery".
  • The confirmation goes out only once, whether it comes from the bot, the deposit payment, the panel or a stage button. Tasks without a time do not get it.
  • On arrival can also notify the team: every person assigned to the task, by email and Telegram. If one channel fails, it is retried without repeating the one that already arrived.
  • The same guarantees below apply (quiet hours, test customers, paused channel), as well as the project's notice switches.
  • To wait some time, add conditions or call your own webhook when a task enters a stage, use a rule.

These notices are set up in the stage editor, in My business → Stages (and also through the API or MCP). The stage and confirmation reminders you had were moved to their stages automatically, keeping their state (on or off).

Fiuit ships a small set of recommended reminders for your business type (24 h reminder, review request after completion, team alerts…). They are installed turned off: nobody messages your customers until you decide.

  1. Go to Customer care → Automatic messages.
  2. Under Recommended for your business, check each reminder's message preview.
  3. Turn on the ones you want with the toggle. The section hides once nothing is left to activate.

Win back customers who stop coming

One of the recommended reminders is "Win back customers who stop coming": it messages customers on WhatsApp who have had no activity for N days (no completed tasks and no inbound messages; whatever the business sends does not count). The number of days is editable on the reminder (1 to 365; each template ships a sensible value for its trade). The sweep runs hourly, only during daytime (10:00 to 18:00, business time) and with a cap on new customers per run, so it writes gradually. Each customer gets one message per inactivity period: if they come back and lapse again, they may receive another one later. If the customer opted out of messages, or the channel or the AI is paused, they are skipped.

For a customer who already has a rhythm (3 or more visits), the days are not fixed: Fiuit considers them lost by their own rhythm, at 3 times their cadence. Someone who comes every week gets the message after 3 weeks and someone who comes every month, after 3 months. The N days stay for customers with no pattern.

Two more recommended ones, off until you turn them on: "Shall we book the next one?" messages customers who are due back by their rhythm and have nothing booked, and "Offer a fixed slot" offers a fixed slot to customers who always come on the same day, at the same time and for the same service. Both send a single message per visit and respect the customer's opt-out of automatic messages.

Automated messages, done responsibly

  • There is a cap of 30 automated sends per hour to customers, per project: sends are staggered automatically to protect the WhatsApp line.
  • On the customer profile (Owner and Manager), the "Do not send promotional automated messages" toggle marks those who asked not to receive them. Booking reminders keep going out as usual: the toggle only stops promotional messages, such as the win-back one.

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).

Service notices and delivery log

In Customer care → Automatic messages, the Owner or Manager configures service notices: creation without a time, assigned or changed person, modified data, in transit, arrival and completion. They start disabled. For modified data, select relevant field keys; consecutive edits are grouped until 60 seconds after the last edit. For progress, select a current service stage. If the stage already has a notice, its existing configuration is preserved. Texts are saved per language and support service and business placeholders.

The delivery log appears in these settings, task Activity and the customer page. It shows up to 50 attempts from the last 90 days: sent, skipped, deferred or failed, with channel, template and reason. “Sent” means accepted by the adapter; it does not prove delivery or reading. It stores neither message text nor contacts. It starts with this version without reconstructing earlier sends. Missing channels or expired reply windows cause an omission; there is no automatic fallback to email or another channel. Promotion opt-out affects reactivation, not operational notices.