Foundation · Recognize your patterns
Why an Automated Customer Reply Often Only Exposes an Existing Problem Instead of Solving It
By Editorial Team··10 min. read
Your automated customer reply feels impersonal when your text was already generic before: it fit every enquiry and therefore referred to none. By hand you barely noticed, because you made up the difference case by case. Automation removes that compensation and multiplies the text. Check the pattern first, and you solve it before it grows.
Why does an automated reply feel impersonal even though the content is correct?
It feels impersonal because it is correct but has no reference. Correct means: the information is right. Reference means: your customer recognises their own enquiry in the reply. A reply can fully deliver the first and not deliver the second at all.
Take the sentence "Thank you for your enquiry, we will get back to you shortly." Nothing about it is wrong. It fits a request for an appointment, a complaint and a request for a quote.
That is exactly the mechanism. A sentence that fits everything tells your customer nothing about their matter. What they read is: my message has arrived. What they do not read is: my message has been understood.
The whole difference lies between those two readings. A confirmation of receipt answers the question of whether the technology worked. But your customer asked a different question. They wanted to know whether someone is taking care of their matter, who that is and by when.
If that question stays open, your customer closes the gap themselves. They write a second time, they call, or they ask another provider in parallel. For you, that creates extra work at exactly the point where you wanted to save work.
This shows you where to start. A different tool changes nothing about that sentence, and faster delivery does not either. The only thing you can change is what the sentence says.
This is not a technology problem. This is a text problem.
The pattern was there before: you compensated for it by hand
The generic text in your business was not created by the automation. It came about because you answer many enquiries in little time. A building block that always fits is a sensible solution under that pressure.
As long as you replied by hand, a second job ran alongside it. You added a half-sentence, mentioned the name of the project, made a quick call on a sensitive enquiry. None of that work was in any template. It was still the part that reached your customer.
An example to illustrate. A customer writes that they need a quote before their move in three weeks. Your template says "We will get back to you shortly." You type after it: "We can do that before your move, I'll call you tomorrow." That second sentence is in no building block. It comes out of your head, because you read the enquiry.
That second sentence is the compensation. Compensation means: case by case, you add what the template lacks. You do it so naturally that you do not count it as separate work. That is why it appears in no description of your process.
The automation takes over the template. It does not take over the compensation, because that was never written down anywhere.
I compare it to an amplifier. It makes whatever goes in louder and adds nothing. If a clear text goes in, clarity reaches your customers in larger numbers. If a generic text goes in, the generic reaches them in larger numbers.
Something follows from this that takes weight off you. The impersonal effect says nothing about your care. It shows that your care so far sat in a place that could not be transferred: in you instead of in the text. As soon as you write it down, it can be transferred.
Automation multiplies what is there.
How do your customers notice that a reply is automated?
Your customers rarely notice it by the speed. They notice it because the reply misses their message. Four signs give it away:
- The reply picks up no word from the enquiry.
- It answers a question your customer did not ask, or leaves the one they asked open.
- It names no next step with a time, only "shortly" or "soon".
- It names no person your customer can turn to.
Read the list again. None of these signs has anything to do with technology. Each of them can also appear in a reply you typed yourself.
Take the third sign as an example. "Shortly" is an honest statement to you, because you know you will take care of it. To your customer it is not a statement at all. They cannot use it to plan whether to ask again tomorrow or wait until Friday. A time they do not know is, to them, no time.
The fourth sign works in a similar way. A reply without a name comes, to your customer, from a company, not from a person. They then have nobody to refer to when they have a follow-up question. They start from scratch with every follow-up.
A fast reply with all four pieces of information, on the other hand, strikes your customer as attentive, even if it arrives within seconds. Speed only becomes suspicious once the content misses them.
So your customer does not distinguish between automated and by hand. They distinguish between meant and not meant.
How do you spot the pattern before you automate it?
You spot it with a swap test. Swap test means: you check whether your reply would also fit a different enquiry. If it fits, it carries no reference.
Here is how you proceed. Take your last ten replies to customers. Remove the greeting and the names. Lay the ten enquiries next to them, shuffled. Match each reply to its enquiry.
If you manage the match for most of them, the reference is in the text. Then you can translate it into a rule. If you manage it for only a few, the reference so far was in you and not in the text.
The test becomes more accurate when someone else does the matching. You recognise your own replies by things that are not in the text: the day, the customer, the memory of the conversation. So hand the two piles to an employee who does not know the cases. Whatever they can match is really there.
Then comes the second step. Write down what you added by hand. Which detail from the enquiry did you pick up? Which date did you name? When did you reach for the phone? That list is the real template for your automation.
The list gives you a classification you did not have before. Some additions repeat with every enquiry of the same kind, such as the time for the callback. Those can be captured as a rule. Others occur only in individual cases, such as the call to an annoyed customer. Those stay with you. Now you know which part you can hand off and which you cannot.
You are thinking: that costs time before anything is even running. The maths works differently. A text you correct once. An automated text that is already being sent you correct after it has reached every customer who wrote in the meantime.
Whoever checks first corrects a text. Whoever checks afterwards corrects an impression.
How does your customer communication stay personal when it runs automatically?
It stays personal when every reply contains three details from the specific enquiry: the matter in your customer's words, the next step with a time, and the name of a person. Personal does not mean the first name appears in the greeting. Personal means the reply fits this one enquiry only.
A comparison. Generic: "We have received your enquiry and will get back to you shortly." With reference: "You are asking for an appointment to service your system. Ms Berger will call you by Thursday, 12 noon, and agree the day with you." The names are an example, the construction is the rule.
Run the swap test on the second version. It does not fit a complaint and it does not fit a request for a quote. It fits only this one customer with this one question. That is how you know the construction holds, regardless of who or what sends the reply.
Each of the three details requires a decision in your business. You can only name the matter if you have defined which kinds of enquiries exist in your business. You can only name the time if you know what you can keep to. You can only name the person if responsibility is settled. So the text is the result, not the starting point.
A second rule belongs with it: define when your automation does not reply. If one of the three details is missing, the enquiry goes to a person. The same applies to complaints and to anything that cannot be assigned to a clear kind of enquiry.
That boundary is not an admission that the automation cannot do enough. It is the part of your previous compensation that deliberately stays with you. You hand off the recurring cases and keep the ones where your judgement makes the difference.
You could instead make the tone warmer, with friendlier words and a longer thank-you. That does not solve the problem. A warm sentence that fits everything remains a sentence that fits everything.
How often should you review an automated customer reply?
Review it at every change in your business and, on top of that, at a fixed date. Change means: a new offer, a new deadline, a new responsibility, a new process. Any of these can make a sentence in your reply wrong without anyone reporting it to you.
The reason once again lies in the compensation. By hand you automatically took a changed deadline into account, because you had it in your head. An automated text knows only what is written in it. If responsibility passes from Ms Berger to someone else, the reply keeps naming Ms Berger until you change it.
For the fixed date I recommend once a quarter, and more often in the first weeks after introducing it. That is my recommendation, not a measured figure. What matters is that the date is in the calendar and carries a name.
The name matters more than the interval. A review that everyone is responsible for ends up being done by nobody. A review that sits in one person's calendar takes place.
The review itself is the same swap test. Take ten sent replies and their enquiries and match them. Also read your customers' follow-up questions. If someone asks about something the reply should have settled, you have found the spot.
The follow-up questions are your most accurate source. Each one shows you a detail your customer needed and did not get. Collect them over a few weeks and you will see which detail is missing most often. That is where you change the text first.
The pattern does not only affect your texts
The generic text is one example of something larger. For years you closed a gap with your own effort and therefore never saw it as a gap. It only becomes visible once your effort at that spot falls away.
That applies in more places in your business than the inbox. Wherever you yourself are the compensation, a new tool first shows you what was already there. That is not bad news. It is the most accurate information you can get about your business.
Think of handing a job over to an employee. The description is brief, and you fill in the rest in a conversation in the corridor. If you are away for a week, exactly that rest is missing. The description was just as brief before. You simply did not notice, because you were there.
This is where effort and result connect. A large part of your work flows into compensation that is recorded nowhere. It works in the individual case and has to be performed again tomorrow. That is why the result grows more slowly than your effort would lead you to expect. I describe why your business cannot grow past the person running it in Your Business Grows Exactly as Far as You Do.
Behind the compensation stands a habit that shapes your decisions: you would rather close the gap yourself than name it. That is fast and reliable as long as you personally reach every spot. With every tool and every employee, there are more spots where you are not standing.
Whoever knows their patterns decides what they multiply.
If you want to recognise the patterns you have been deciding and acting by so far, the Challenge is the first step: four days, free, no selling during that time. Go to the Challenge on impruvement.com
Frequently Asked Questions
Because it is correct but has no reference. The information is right, yet your customer does not recognise their own enquiry in it. A sentence that fits every request tells them only that their message arrived, not that it was understood.
All articles on Foundation · back to the Blog
Also available as Markdown.