01What is worth automating first
The first process is not chosen by fashion, but by three plain criteria: it repeats, it has rules you can write down, and a mistake does not put an order, a payment or a customer at risk without someone being able to review it. A common order exception, a booking reminder or a follow-up that stalls in the CRM usually meet those three points. Automating «the whole operation» in the first month does not.
It also matters who holds the judgement today. If only one person knows how a return is handled, the system will not invent that rule. First you describe the process with the person who runs it; then you decide which part can run on its own and which part waits for approval. Without that order, you automate the mess and you multiply it.
The scope of that first process is set in writing, after a diagnosis. That is where you name the trigger, the tools, what runs on its own and what a person reviews. That work is part of the AI integration service; it is not improvised on the day the flow is switched on.
02Orders: alerts, exceptions and handing over to a person
On an order, what is usually worth automating is not closing the sale, but finding out in time when something leaves the normal path: a payment that does not match, stock that does not arrive, a shipment on hold, an incomplete address. The flow can watch those states, alert the team and leave ready the information needed to decide. The change to the order, or the message to the customer, stays with a person when the case is sensitive.
An alert is not an agent. If the rule is «when the status is X, write to this channel and create this task», this is an automatic workflow. It makes sense precisely because the condition is clear and the risk, if it is bounded, is low. When the next step depends on several pieces of data and someone has to choose what to do, the design moves closer to an agent, and then you need a perimeter and an approval queue, as I describe in the guide to what an AI agent is, and how it differs from a chatbot.
The handoff to a person must be explicit: who receives the alert, what data they see, and what happens if they do not respond in time. A flow that writes to an inbox nobody reads is not automating anything useful. That is tested with real cases —including the odd ones— before it is left running.
03Bookings and reminders
Bookings lend themselves to a fixed flow: a reservation lands in the calendar, a reminder goes out the day before, a cancellation frees the slot and alerts the team. AI can help draft the message or classify a request («I want to change the time»), but the rule stays clear. You do not need an agent to remind someone of an appointment.
What you do have to decide is the tone and the channel, and what is sent without review. A standard reminder, agreed in advance, can go out on its own. A message that changes the booking, offers an exception or talks about a payment is a different matter: in the work I describe, a person reviews it. The calendar you already use is the starting point, not a new system imposed by the project.
Exceptions also need a bound: a customer asking for a slot that does not exist, a booking type that was not in the rule, a notice outside business hours. The flow should not invent a solution in those cases; it should leave the case in a queue and alert someone.
04CRM: new records, follow-ups and drafts
In the CRM, what repeats is usually a new contact, a note from a conversation, a reminder of a follow-up nobody has done, and a draft of the next message. Automating that is not letting a system close a deal. It is not losing the thread, and not rewriting the same kind of note by hand over and over.
A new record or an internal reminder can run on their own if the rule is clear. A message to the customer, in the approach of this guide, is left as a draft for someone in the team to approve. The system does not «sell»; it prepares the next step and leaves it visible in the CRM.
05How this relates to commercial follow-up
This guide covers the process —orders, bookings, new records and follow-ups— as a first scope. The detail of commercial triggers (a lead with no reply, a stalled proposal, a customer who has not come back) and of how an outbound message is approved belongs in a separate guide on automating commercial follow-up and the CRM, once it is published. I do not copy it here: it is enough not to close a deal automatically, and to leave any sensitive message in an approval queue.
06How it connects to the tools you already use
You start from what already exists: the store, the CRM, email, the calendar, sometimes a messaging channel. If those tools have an API or a reliable connector, the flow can sit on top of them. If they do not, that shows up in the diagnosis; it is not assumed that «any system can be connected». You do not need to change CRM or store as a matter of principle.
The connection is not a node-by-node tutorial. What is agreed is the trigger, the data that crosses from one system to another, the permissions and the place where the record lives. Sometimes a flow in an automation tool is enough; sometimes you need a more custom integration. That decision is taken with the process in front of you, not the other way around.
| Process | Trigger | System | Automatic | Human review |
|---|---|---|---|---|
| Order with an exception | The order moves to an error or out-of-stock state. | Store and the team’s internal channel. | Alert to the team and a note with the order data. | The message to the customer or the change to the order. |
| Booking | A reservation is created, or the appointment is a day away. | Calendar and email or messaging. | A standard reminder agreed in advance. | Changes, exceptions and any message outside the template. |
| CRM follow-up | A contact has had no activity for a set period, or a new lead arrives. | CRM and email. | A task, an internal reminder and a draft of the next message. | The send to the customer and any entry that becomes firm in the file. |
The table is a generic example, not a client record. In a real project the triggers and systems are written with the names you already use, after the diagnosis.
07What stays outside the first scope
Outside the first scope you usually leave anything that still has no rule, anything that implies a commercial or financial decision, and any volume of processes that nobody has closed. Also left out, unless explicitly agreed, is the automatic sending of sensitive messages, and a change of CRM or store «just because». A second process can be planned once the first is running and documented.
The quote covers what is in the written scope, not an open list of future automations. If it is a fit, the next step is a 30-minute meeting or an email to hello@diegosanjuan.com. Contact is on the contact page.