Automation
Automation is a flow that runs a series of jobs, such as messages and tasks, by itself when an event happens, following rules you set up.
Automation means describing a repeated job once and letting a flow do it, instead of doing it by hand every time. A flow starts with an event, checks a rule if needed, waits if you ask it to, and finally does something. Sending a message or opening a task are typical examples. You write the rule, and the flow applies it the same way every time.
In e-commerce it helps most with orders, carts and customer messages. A thank-you note after an order or a nudge to a customer who has not been back for a while uses the same logic. Automation does not make decisions, it applies the rule you described. That is why a good flow needs a good plan first: who gets which message, and when.
Why It Matters
- When the team stops repeating the same job, its time goes to customers and the product.
- Because the rule is written down, a customer gets the same care whatever day or hour they shop.
- Flow statistics can be tracked, so you see what works from records instead of guesses.
How It Works
- Pick an eventDecide what starts the flow: a new order, an abandoned cart, an incoming message or a scheduled rule. This starting point is called a trigger.
- Decide who continuesA condition decides whether everyone who enters the flow carries on. A customer without marketing consent, or with a very small cart, can drop out here.
- Wait if neededA wait step delays the next job until a sensible moment. Half an hour for a cart reminder, a few days after delivery for a review request.
- Define the jobThe action is the job done at the end of the flow: a message, a task, a notification. Messages can carry details such as the customer name and order number.
Example
At Liva Butik, Elif Arslan adds the Linen shirt to her cart but closes the site before paying. The store owner has set up a flow for this. The event is the abandoned cart, the condition is that the customer has marketing consent, the wait is 30 minutes, and the action is a message with the shirt's card and a payment link. Elif has consent, half an hour passes and the message goes out. For a customer without consent, the same flow stops at the condition and nothing is sent.
| Part | Question it answers | Example | Place in the flow |
|---|---|---|---|
| Trigger | What starts it? | Cart abandoned | At the start |
| Condition | Who continues? | Has marketing consent | After the start |
| Wait step | When does it continue? | 30 minutes | Wherever needed |
| Action | What gets done? | Message with a product card | At the end |
Not to Be Confused With
Automation is not an AI that runs without rules or decides on its own. You describe the steps and the flow applies them. It also differs from an AI employee that talks with customers: it follows steps written in advance.
In Creato
In Creato automations, the event, condition, wait and action are combined in a visual editor.
- Messages can include variables such as customer name, order number, amount and product.
- Statistics and records are tracked for every flow.
- People who write STOP (DUR) do not receive automation messages; when an agent steps into a conversation by hand, the flows in that conversation pause.
- The available actions vary by channel.
Frequently Asked Questions
Is automation the same as a bulk message?
No. A bulk message targets a chosen group at a moment you pick. Automation starts from something an individual customer does: someone leaves a cart, an order comes in. Each customer enters the flow at their own time. The two work on different logic.
Do I need to code to set up an automation?
No. In Creato you build the flow in a visual editor and do not write code. Planning on paper first still helps: which event, for whom, with which message? Reviewing the steps one by one before you switch the flow on also reduces mistakes. See the Automations page for details. Each flow's statistics show how many people entered.
Can automation annoy customers?
It can if the rule is poorly written. A condition that leaves out customers without consent, a wait that spaces messages out, and one clear purpose all reduce the annoyance. Flows should stop when a customer writes STOP. That is why contact consent is the first condition of a flow.