Questions we answerAI and automation
Can AI handle customer enquiries?
Part of them, well, with a person holding the line. The split that matters is between enquiries with known answers and those needing judgement, empathy or authority.
Free · a few minutes · starts from “I think AI could help”
The short answer
Some of them, and the split matters more than the technology. Enquiries with known, stable answers — status, policy, how-to — are well suited, especially where the answers already exist somewhere reliable. Enquiries needing judgement, empathy, or authority to make an exception are not, and routing them badly costs more goodwill than the automation saves. The workable pattern is almost always a bounded one: handle the known cases, recognise the limits, and hand over cleanly with the context attached rather than making the customer start again.
Customer enquiries are the most common first AI project and one of the easiest to get visibly wrong, because the failures happen in front of customers rather than internally.
The good version is unglamorous: a narrow set of enquiry types, answered from a source you trust, with an obvious route to a person and the context carried across.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- A meaningful share of the queue is the same handful of questions.
- The answers exist somewhere accurate and maintained.
- There is a person available for anything the system cannot handle.
Signs it's something else
- Most enquiries need account-specific judgement or a decision about an exception.
- The answers are not written down anywhere reliable, so there is nothing to answer from.
- The volume is low enough that the setup would not pay back.
What's usually behind it
- A support queue growing faster than the team answering it.
- A high share of enquiries that are genuinely the same few questions.
- Out-of-hours demand nobody is staffed for.
What people usually get wrong
- Deploying across the whole queue rather than the enquiry types it handles well.
- Making the hand-off to a person hard to find, which converts a minor failure into a complaint.
- Building it on a knowledge base nobody maintains, so the answers drift out of date.
The options, and when each one fits
In no particular order. Which of these fits depends on your situation, not on the question you typed.
Answer the known enquiries
A real share of the queue is the same few questions with stable answers.
Assist the support team instead
Enquiries vary but drafting and finding information is the slow part.
Fix the cause of the enquiries
A large share of the queue exists because something upstream is confusing or broken.
When doing nothing is the right call
If the answers are not maintained anywhere, that is the project. A reliable, current source of answers improves the support team immediately and is the precondition for anything automated later.
What the diagnostic asks
- What the work is and whether it is repeatable.
- How much judgement it needs and how often it comes round.
- What happens when it goes wrong and how sensitive the information is.
- Whether software already exists for it.
“I don't know” is always an answer. Nothing is assumed on your behalf.
The routes it weighs
Every diagnostic weighs all ten routes. These are the ones that tend to matter for this question — a description of the rules, not a promise about your answer.
AI Assist
Keep a person in charge and give them AI for drafting, summarising, checking or analysis.
AI Agent
Delegate a defined, repeatable workflow to software inside boundaries you set, with human oversight.
Process improvement
Change how the work flows — remove steps, name an owner, fix the hand-offs.
Recruit
Recruit a new person for a durable, sizeable need that is central to the team.
Outsource
Hand a defined, ongoing scope of work to an external provider.
What changes the answer
- A large share of identical, answerable enquiries makes this credible.
- Sensitive customer information or expensive mistakes change how it must be built and by whom.
- An existing helpdesk with features you are not using is usually the cheaper first move.
Get your own read
A handful of short questions, then the strongest route for your situation, what's also credible, what we still don't know and what would change our view. No account, no setup.
Related questions
- When is an AI agent the wrong answer?When the process is undocumented, the work is rare, the judgement is high, the stakes are serious without a design to match, or a system you already pay for does most of it.
- Do I need an AI agent, or just better tools?Usually better tools first. An agent runs a defined workflow inside boundaries; a tool helps a person do their own work faster. The diagnostic tells you which the evidence supports.
- Can AI help my team?Often, but the useful question is where. AI that helps a person draft, summarise or analyse is a different decision from AI that runs a process.
- Is my process ready to automate?Four things have to be true: the steps repeat, they are written down, it happens often enough to pay back, and someone can say what a failure costs.
- Should I hire or automate this role?It depends on what the work actually is. Repeatable, frequent, low-judgement work can often be automated; durable, growing, judgement-heavy work usually needs a person. Most real roles are a mix, and the honest answer is often to automate part of it first.
- Should I use AI or hire someone?They answer different problems. AI reduces the effort in work that repeats; a person absorbs work that needs judgement, relationships and context.