Does AI for customer support actually improve anything?
AI for customer support improves the experience when it removes waiting and answers the ordinary questions instantly. It ruins the experience when it stands between a customer and a person who could have helped. The technology is the same in both cases. The difference is entirely in what you decided it may do, and how quickly it gives up.
Everyone has already met the bad version. That is the real starting condition for this project, and it means your machine has to earn trust that someone else spent.
What should a support machine answer?
The questions that have one correct answer, that you get constantly, and that a customer should not have to wait for.
Where is my order. What are your hours. Do you service my area. What does this product do. How do I reset it. Can I change my booking. Do you take that payment method. How long is this covered for. None of these need a human, and making someone wait until Monday for the hours on a Saturday is the kind of small failure that quietly costs you a sale.
The value here is not cost reduction, it is that the answer arrives at nine at night. That is the whole promise of never miss a lead, applied to people who are already customers.
When should it stop and hand over?
Immediately, on three signals: it does not know, the customer is unhappy, or the request has money or safety attached.
- It does not know. A machine that guesses is worse than no machine. Not knowing and saying so is a correct answer.
- The customer is frustrated. Detecting annoyance and escalating fast is worth more than any amount of clever answering. Nobody has ever been calmed down by a second automated reply.
- Money or safety. Refunds, credits, cancellations, complaints, anything that could hurt somebody, anything a regulator would care about. Those are people decisions, always.
- They ask for a person. Honour it on the first request, not the third. Making a customer fight for a human is the single most resented pattern in support automation.
Should you tell customers they are talking to a machine?
Yes, plainly, at the start, and there is no version of concealing it that ends well.
People are fine with a machine when it is fast and honest about what it is. They are not fine with discovering it, and the discovery reframes everything that came before as an attempt to deceive them. It is also the direction Australian expectations are heading: the AI Ethics Principles put transparency and contestability near the centre of them.
Disclosure has a practical benefit too. Customers who know they are talking to a machine ask simpler, clearer questions, and they escalate themselves sooner when it is not the right tool. Both make the system work better.
What makes support automation feel bad?
Four things, and every one of them is a design decision rather than a limitation.
Loops, where the same clarifying question comes back a third time. Dead ends, where there is no route to a person from wherever the customer is standing. Amnesia, where the customer explains everything again to the human who eventually arrives. And confident wrong answers, which do more damage than an honest "I will get someone", because the customer acts on them.
The fixes are ordinary engineering. Cap the attempts and escalate. Put a route to a person on every screen. Pass the full transcript across on handover. And make not knowing a first class outcome rather than something the machine tries to avoid.
What does it need to know to be useful?
It needs your actual information, kept current from wherever it already lives, and nothing beyond what the task requires.
A support machine running on general knowledge is a liability, because it will invent a policy you do not have. It needs your hours, your service areas, your products, your terms, your process, drawn from wherever those already live so they update when you update them. Static answers pasted in once will be wrong within a quarter and nobody will notice until a customer quotes them back to you.
Equally it should not have access to more customer data than the task requires. The Australian Privacy Principles are the reference for what you may hold and disclose, and least privilege is the right default for a system talking to strangers.
How do you know whether customers are better off?
Measure response time, the share of contacts resolved without a person, the escalation rate, and satisfaction on the escalated ones specifically.
That last one is the honest measure. Anyone can drive up self service resolution by making escalation hard, and the number will look excellent right up until the reviews arrive. Watching satisfaction on handed over conversations keeps the system pointed at helping people rather than deflecting them. The general approach to this is in how to measure ROI on AI.
Start narrow
Take the ten questions you answer most often, and let the machine handle only those, out of hours only, with a fast route to a person. Watch it for a month. Widen from evidence.
That is a smaller project than "AI customer support" and it is the one that works. If you want to talk through where the line should sit for your customers, get in touch, or see how we scope it in our method.