What Should You Never Automate? A Written Boundary
What should you never automate? Complaints, bad news, negotiation, fake personal notes and the first serious conversation. Write the list down before you build.
What you should never automate is the relationship itself: replies to complaints and cancellations, bad news, negotiation, notes that pretend to be personal, and the first real conversation with a serious prospect. Write that list down before you build anything.
Automation is excellent at making sure the right thing happens, and poor at making someone feel known. A message that was obviously sent by a rule is received as a message sent by a rule, however warm the wording. Knowing where that line sits is not a matter of taste. It is a decision you make once, in writing, before the software makes everything feel possible.
What should you never automate: the usual entries
The guide gives a short list of moments that belong to a person. Each is a point where a relationship is made or lost, and where a template reads as indifference at precisely the moment the other person is paying attention.
| Moment | Why it belongs to a person | What a template does there |
|---|---|---|
| A complaint or a cancellation | The other person wants to know someone is listening | Reads as indifference |
| Bad news | It deserves to be delivered properly | Reads as indifference |
| A note posing as personal | It claims a person wrote it | Makes a claim that is false |
| Negotiation | It is where the relationship is made or lost | Removes the person from the table |
| The first real conversation with a serious prospect | Attention is at its highest | Wastes the moment |
Read the middle column as a way of seeing each moment from the other side, which is the point of drawing the line at all. In every row the other person is paying attention, and a rule cannot return it.
Why the line has to be written down
The temptation grows as the tooling gets easier. When it takes minutes to set up a rule, almost everything starts to look automatable, and a decision made in the moment tends to favour convenience. A written list works like a promise made when you were thinking clearly.
It also gives you something to check against. Before you build anything, one of the boxes you should be able to tick is that the process is not on your list of things you will never automate. That box only means something if the list exists.
Automating the relationship versus automating the follow-through
The distinction underneath the whole list is between the two kinds of work in a business. Follow-through is replying, assigning, reminding, tagging and confirming. The relationship is the careful reply, the call that needed making and the judgement about fit.
The rule of thumb is simple. If the step exists to make sure something happens, it can usually be handed over. If the step exists to make someone feel understood, it cannot. A good test is to ask what the recipient would feel on learning that a rule sent it. If the answer is nothing, the step is probably follow-through. If the answer is disappointment, keep it.
The same idea runs through what is workflow automation, which sets out why the machine should keep the promise and the person should keep the relationship.
Handling the awkward middle
Real cases do not always sort neatly. Some moments sit between the two kinds of work. Three approaches help, and none of them requires you to hand the human part to a machine.
- Automate the internal half. A complaint cannot be answered by a template, but the task to answer it, the owner assigned to it and the notification to a teammate can all be automated. The person who reads the complaint then turns up prepared, and the customer never sees the machinery.
- Automate the reminder, not the reply. A task that says a conversation is due keeps the promise that it will happen without writing the conversation.
- Keep the first message human. If a serious prospect arrives, a confirmation that a person will be in touch is honest only if a person then is.
This is the same idea that makes internal actions the safest place to start, and how to decide what to automate first explains the order.
The honesty test for personal notes
One entry on the list is easy to miss: anything that pretends to be a personal note from a specific person when it is not. This is not only about tone. A message signed by a named person, written as if they sat down to compose it, makes a claim about what happened. When the claim is false, the recipient eventually finds out, and the discovery colours everything else you have said.
The same checklist that guards a launch asks that no message pretends to be a personal note from someone who did not write it. A short, plain confirmation that says it is an automatic acknowledgement and that a person will follow up does not pretend anything. It keeps its promise and tells the truth.
| Honest | Dishonest |
|---|---|
| A confirmation that a person will be in touch | A "personal" note signed by someone who never saw the enquiry |
| A reminder to your own team that a reply is due | A message written to look as though it was typed that minute |
| A short acknowledgement that does not claim attention | A greeting that implies the sender has studied the recipient |
Why convenience is the wrong guide
Almost every exclusion on the list can be automated technically. A cancellation can be answered by a template in a few seconds. Bad news can be delivered by a scheduled message. Technical ease is therefore no evidence that a step should be handed over, and the more capable the tooling becomes, the less it tells you.
The question that matters is what the step is for. If it is there to keep a promise, a rule can usually keep it. If it is there to show that someone cares, only a person can. A list kept in writing is how you hold on to that distinction when a faster option is sitting in front of you.
Signs you have crossed the line
Even with a list, drift happens. Watch for the signals that a workflow has strayed into the territory you meant to protect.
- People reply asking whether a human is there.
- Replies and complaints suggest that people feel processed rather than helped.
- A message arrives at a moment of high feeling, such as just after a complaint, and reads as though nobody noticed.
- A workflow's wording has quietly grown more personal than its sender.
People asking whether a human is there is the clearest of these, and it is also one of the reasons the guide gives for switching a workflow off. Read more in when to switch off a workflow.
How to write your own list
- Start with the usual entries above and keep the ones that apply to your company.
- Add any moment where, if the recipient learned a rule had written the message, they would feel slighted.
- Write each entry as a plain sentence, such as "No rule answers a cancellation".
- Name the person who owns each entry, so that the human part has a human behind it.
- Check the list before you build and again at every review.
The list will be short. That is a feature. A long list of exclusions suggests that automation has not been aimed at the right target, and a short one means you can remember it without opening a document.
A quick way to sort a new idea
When a new workflow idea arrives, put it through three questions before you build it. They take a minute, and they stop most regrets.
| Question | If the answer is yes |
|---|---|
| Is the other person likely to be upset, anxious or paying close attention? | Keep the message with a person and automate only the internal support |
| Would the message claim to come from someone who did not write it? | Change the wording so that it does not, or do not send it |
| Does the step involve judgement about fit or terms? | It is still a job for a person |
| Does the step only make sure something happens? | It is a candidate for a rule |
None of these questions is about software. They are about the moment, and the moment does not change with the tool you use.
What staying human does for the rest
There is a quiet benefit to drawing the line. When the moments that need a person are protected, the machine can be trusted with the rest. The bookkeeping around the relationship is handled, and the attention you save goes into the conversations that count. Done well, automation makes the human parts of your business more human, and that only works if the human parts are actually left to humans.
Frequently asked questions
Can I automate a thank-you after a purchase?
A promised welcome that depends on the founder remembering is a real dropped handoff, so it is a reasonable candidate. Keep it honest: do not make it pretend to be a personal note from someone who did not write it.
Is it ever fine to automate part of a sensitive moment?
Yes, the internal part. The task, the owner and the notification to a teammate can be automated while the reply stays with a person.
What if I am a one person company and cannot answer everything?
Then a rule can make sure nothing is lost: a task that says a reply is due keeps the promise that you will answer, even if the reply itself is yours to write.
How do I know the list is right?
Review it with the rest of your workflows. If replies suggest that people feel processed rather than helped, something that belongs on the list has probably been automated.
The full method, with the checklists, is in The Automation Playbook, a free 29-page playbook.