Customer service touchpoints you should never automate

Customer service touchpoints you should never automate

A man's grandmother died. He needed to fly interstate for the funeral. Before booking, he asked the airline's chatbot whether he could claim a bereavement discount.

The chatbot said yes. He booked the ticket. The airline said no. When he took them to tribunal, their defence was that the chatbot was essentially a separate entity, not their responsibility. The tribunal called that argument remarkable. They lost. (Moffatt v. Air Canada, 2024 BCCRT 149.)

If a company with an entire legal team didn't think through what their automated system was communicating to customers, what does that mean for the rest of us? Your automated system speaks for you. Whether you know what it's saying or not.

Key takeaways

  • Only 33 per cent of Australians trust organisations to use AI responsibly, the lowest of any country surveyed (Qualtrics, 2025).
  • 58 per cent of Australians are specifically afraid that automation will stop them reaching a real person when something goes wrong.
  • Bucket three tasks: complaints, first conversations with new clients, and anything where trust is at stake. These must stay human, no exceptions.
  • 31 per cent of Australians say nothing after a bad experience. They just leave (Qualtrics, 2025).
  • The fix is not removing all automation. It is knowing exactly which touchpoints need a person on the other side.

Why are Australian clients specifically afraid of automated customer service?

Not worried. Afraid.

Qualtrics surveyed 1,500 Australians in 2025. Fifty-eight per cent said they were afraid that if something went wrong, they wouldn't be able to get to a real person. That's the specific fear: not that AI is impersonal, not that it's imperfect, but that it will stand between them and a human when something actually matters.

Only 33 per cent of Australians trust organisations to use AI responsibly. The lowest of any country in the study.

Zoom and Morning Consult found that 51 per cent of Australians are more frustrated by AI customer service than any other country surveyed. And 86 per cent said they'd stop buying from a brand entirely if their issue wasn't resolved.

This isn't a vague preference for human connection. It's a specific, documented fear that your automated systems will be the thing standing between your client and help when they actually need it.

"Your automated system speaks for you. Whether you know what it's saying or not."

What makes a customer service touchpoint a "bucket three" task?

The bucket framework gives you one question to sort every task in your business: would the client you'd least want to lose feel less valued knowing a system handled this?

Yes means bucket three. It stays with you. Always.

Bucket three isn't about the complexity of the task. It's about what the task means to the client. And the tasks that belong there share three characteristics.

1. The client is worried or upset

When something has gone wrong, or when a client feels uncertain about money, a deadline, a job outcome, or their own decision-making, they need to know a real person is across it. An automated response in that moment doesn't just fail to help. It actively confirms their worst fear: that they're dealing with a system that doesn't know them and doesn't care.

2. The client is making a significant decision

Hiring you. Agreeing to a scope of work. Signing something. Committing budget. These moments carry weight. When a client is deciding whether to trust you with something that matters, an automated response tells them the decision doesn't matter to you.

3. The client is in a relationship, not a transaction

When something happens, a question, a concern, a check-in, and it routes through automation, you're telling a client who chose you for the human element that the human element is no longer available. That's the moment they start comparing.

The three-bucket framework gives you the full decision filter and how to sort every task in your business.

Which specific customer service touchpoints should never be automated?

This section gives you the specific list, and for each one, what happens when you get it wrong.

1. Client complaints

This is the clearest bucket three task in any service business. When something has gone wrong, your client needs two things: acknowledgement and accountability. Both require a person.

In 2023, Klarna stopped hiring altogether and went all in on AI for customer service. By 2024, their CEO was publicly declaring AI could do every job a human does. About a year later, satisfaction had collapsed and they were hiring human agents again. The CEO told Bloomberg: from a brand perspective, he believes it's critical that customers always know a human is available if they want one. (Bloomberg, May 2025.)

An automated response to a complaint doesn't just fail to resolve the issue. It tells the client their problem isn't worth a real person's attention. Most of them won't tell you that. They'll just leave.

Roy Morgan's Snap SMS Survey (October 2025) found that 65 per cent of Australians say AI creates more problems than it solves, up eight points since 2023. An automated complaint response is one of the fastest ways to become a data point in that statistic.

What never to automate: complaints

  • An automated acknowledgement that fires before you've seen the complaint is fine, if it's honest about when a person will respond.
  • An automated response that attempts to resolve the complaint: never. Even when the words are technically correct, clients rate AI-generated support as less sincere when they know a human didn't choose to write it.
  • A routing system that makes a client fill in a form before speaking to anyone. This is the thing 58 per cent of Australians are specifically afraid of. Don't build it.
A phone screen showing an automated message response next to a notepad and pen, representing the contrast between automated and human customer service
Automation handles the admin. A person handles the moments that matter.

2. First real conversations with new clients

The initial enquiry can be acknowledged by an automated system, and should be, so the person knows you've received it and when to expect a reply. But the first real conversation, the one where they tell you what they actually need, has to involve a human.

This is where the client is evaluating whether they can trust you. An automated response that attempts to qualify, propose, or move the conversation forward without a human reading their actual situation is making commitments on your behalf that you haven't agreed to. That's the airline problem, scaled down.

When a new client reaches out for the first time, ask yourself: is there a real person on the other side of this first interaction, or is there an automation pretending to be one? The distinction matters, and clients can feel it.

3. Sensitive financial or legal conversations

An ATO letter arrives and your bookkeeping client panics. A tradie's quote comes in higher than expected and the homeowner needs an explanation. A consultant's client discovers the project has gone over scope.

These conversations involve money, trust, and often a degree of client vulnerability. Routing them through automation, even a well-written automated response, signals that you're not available for the hard conversations. That signal lingers long after the conversation is resolved.

4. End-of-relationship conversations

When a client says they're going to pause, move on, or not renew, that conversation needs a human. Not to talk them out of it. To understand what happened.

Thirty-one per cent of Australians say nothing after a bad experience. They don't complain. They don't ask for a refund. They just leave.

The clients who do reach out to tell you they're leaving are giving you a gift: the chance to understand what went wrong, make it right if possible, and leave the relationship in a state where they'd refer you anyway. Routing that conversation through an automated system closes that door permanently.

"The clients who do reach out to tell you they're leaving are giving you a gift."

5. High-stakes onboarding moments

The intake form can be automated. The scheduling can be automated. But the moment when a client has said yes to something significant, a major project, a retainer, a service they've never used before and are nervous about, that moment deserves a real person.

A personal message or call at the start of a high-stakes engagement tells your client: you're not just a transaction in my system. It costs you ten minutes and it's remembered for the life of the relationship.

6. Anything the client is worried about before it becomes a complaint

A client who sends a message asking "just checking in on the progress of X" is not asking for an automated status update. They're signalling mild anxiety. The automated response might answer the literal question. It won't address what's actually going on.

When you train yourself to read client messages for what they're actually saying, not just what they're literally asking, you start to catch these moments before they become complaints. That's a human skill. It doesn't automate.

How do I know if my automation is handling something it shouldn't?

One exercise. Write down every way a new client first interacts with your business: enquiry form, website, DM, email, phone. Then go through each one and ask: is there a human here, or is there an automation pretending to be one?

If the answer is mostly automated, that's where you're losing people. Not in your product. Not in your pricing. In the gap between what you set up to run without you and what your client actually needed from a real person.

The silence test

Thirty-one per cent of Australians say nothing after a bad experience. They don't complain. They don't ask for a refund. They just stop calling.

The next time a long-term client goes quiet, or a promising enquiry drops off without explanation, consider whether an automated touchpoint might have been the last thing they experienced before they decided to look elsewhere.

You won't always know. That's the point. The silent leaver is the hardest problem to measure and the most important one to prevent.

The practical audit

Pick one client who has been with you for two years or more. Trace the last three touchpoints they had with your business. How many were automated? How many involved a real person? If the ratio is mostly automation, you already know what to work on.

So what should you automate in client-facing interactions?

Automation belongs at the front door in a specific, limited role: acknowledging contact, confirming information, and handling the administrative details that surround real conversations.

Automation that serves clients (bucket one)

  • Booking confirmations and reminders: your client just wants to know the time and where to go.
  • Invoice reminders: they just want to know when payment is due.
  • Document requests and intake forms: administrative, outcome-focused.
  • FAQ responses to common questions, as long as the FAQ is honest and routes complex situations to a person.
  • Enquiry acknowledgements: not responses that resolve, just acknowledgements that set a timeline.

The common thread: none of these tasks require your judgement, your relationship knowledge, or your accountability. They just need to happen consistently. Automation does that better than you do.

The moment a task requires you to know this specific client's situation: stop. That's a bucket three moment, and it needs you.

The airline didn't brief its chatbot properly. It didn't check what the chatbot was telling people. And when it went wrong, the tribunal held them responsible for every word it said.

Your automated system speaks for you. The question is whether you know what it's saying.

Not sure what to hand off and what to protect?

The AI Task Audit takes three minutes and gives you a personalised result.

Take the free audit

Frequently asked questions

Do Australians trust AI customer service? +

No. Only 33 per cent of Australians trust organisations to use AI responsibly, the lowest of any country in the Qualtrics 2025 survey. Fifty-eight per cent are specifically afraid that automation will prevent them from reaching a real person when something goes wrong.

Should I automate my client complaints? +

Never. An automated acknowledgement that tells a client their complaint has been received and a person will respond within a specific timeframe is acceptable. An automated response that attempts to resolve, dismiss, or categorise the complaint is not. Trust is built when a real person takes responsibility. Automation can't do that.

Will clients tell me if my automation is costing me their trust? +

Mostly no. Thirty-one per cent of Australians say nothing after a bad experience (Qualtrics, 2025). The clients who are quietly put off by your automated systems don't send a complaint. They just stop referring you, stop renewing, or choose someone else the next time they have a need. You'll see it in the data before you hear it in the feedback.

How do I test whether my automated systems are hurting my client relationships? +

Map every touchpoint a new client goes through from enquiry to close. Read each automated message as if you're a client experiencing your business for the first time. Ask yourself: does this feel like a real business run by a real person, or does it feel like a system? Then ask a recent client the same question directly.

Is there any automated first contact that works? +

Yes: the honest acknowledgement. A message that confirms you've received the enquiry, tells the client exactly when a real person will be in touch, and doesn't pretend to be a person is fine. "Thanks for getting in touch, I'll be back to you by end of tomorrow" is not automation pretending to be human. It's a system doing admin so you can focus on the actual conversation.

How do I know which tasks belong in bucket three? +

The filter question: would the client you'd least want to lose feel less valued knowing a system handled this? Yes means bucket three, every time. For a structured audit across your specific business, the AI Task Audit maps your task mix and tells you exactly where to start. Three minutes. Free.

 

Find out exactly what to hand off and what to protect.

Take the free AI Task Audit — three minutes, personalised result.

Take the free audit
Nardia Barrett, founder of BossKit

Nardia Barrett

Founder of BossKit. Small business systems consultant with over a decade in mortgage broking and eight years running WEBS, a free networking group for small business owners in Western Sydney. BossKit helps service businesses work out what to automate, what AI can assist with, and what to keep human.