Technology, explained
Agents, chatbots and automations: what the difference actually is
Three words get used interchangeably and shouldn’t be. A chatbot talks. An automation runs a fixed path without being asked. An agent decides what to do next. Confusing them is how firms buy the expensive one for a job the cheap one does better. Here is the honest breakdown.
By Seb Lawson · 27 May 2026 · 4 min read
These three words are not interchangeable, and treating them as if they are is how firms overspend. A chatbot talks to a person. An automation runs a fixed sequence of steps without anyone asking it to. An agent decides what to do next by itself. Different shapes, different costs, different risks. The expensive, fashionable option is the agent, and most of the value in a professional services firm sits in the boring automation nobody is tweeting about. Get the category right and the project usually works. Get it wrong and you have bought a self-driving car to fetch the post.
A chatbot: it answers
A chatbot is a conversation. A person asks something in plain language, the system replies. That is the whole of it. The good ones are grounded in your own documents so the answers are accurate and can be traced back to a source, which is the retrieval approach we cover in RAG explained. The weak ones are grounded in nothing and will happily invent a policy that does not exist.
Chatbots fit where a human needs an answer from a body of knowledge: an internal assistant over your procedures, a client-facing helper on your website, a search layer over years of files. What a chatbot does not do is act. It tells you the fee is due. It does not raise the invoice. The moment you want something to happen in the real world, you have left chatbot territory.
An automation: it runs
An automation is a fixed path that runs on a trigger. When an email lands, extract the attachment, pull out the key fields, drop them into the system, flag anything odd for a human. Every step is defined in advance. It does the same thing the same way every time, which is precisely what makes it trustworthy and cheap to run. There is often AI inside an automation, doing the one clever step a rules engine cannot, like reading a scanned document. But the path around that step is fixed and predictable.
This is where most of the real return lives. The repetitive, rules-bound, high-volume back-office work that eats your team’s week is almost always an automation problem. It is unglamorous, it is measurable, and it pays back fast. If you only ever do one AI thing, it should probably be this.
An agent: it decides
An agent is given a goal and works out the steps itself. Instead of a fixed path, it has a set of tools and the freedom to choose which to use, in what order, until the goal is met. ‘Research this counterparty and draft a summary’ might have the agent search, read, cross-check, and write, deciding each move as it goes. When the task genuinely varies every time and cannot be reduced to a fixed sequence, that flexibility is the point.
That same flexibility is the risk. An agent that chooses its own path can choose a wrong one, and the more it can do without asking, the more damage a wrong choice makes. In regulated work that is a live concern, not a hypothetical. Agents are the right tool for genuinely open-ended tasks. They are the wrong tool for a process you could have written down as steps, which, honestly, is most processes. The industry is selling agents hard right now. Be sceptical when the job on the table has a fixed shape.
How to tell which you need
Ask two questions. First, does a human need to have a conversation, or does something need to happen? Conversation points to a chatbot. Something happening points to automation or an agent. Second, is the path the same every time, or does it genuinely differ? Same path is an automation. Genuinely different every time is an agent. Most firms discover their pressing problems are chatbots and automations, and that the agent can wait until those are earning.
- Chatbot when a person needs a grounded, traceable answer from your knowledge.
- Automation when a defined process runs the same way on a trigger, with a human checking the exceptions.
- Agent when the task is genuinely open-ended and the steps cannot be fixed in advance, and you have built the oversight to match.
Why the label matters commercially
Because it sets the cost, the risk and the governance. An automation with a human checking exceptions is cheap to run, easy to audit, and easy to explain to a regulator. An agent making its own decisions needs far more oversight, testing and change control before it goes near client work, and it should. Buying the agent for a job the automation does better is the single most common way we see AI budgets wasted. The related question of building it yourself, buying it, or wiring together no-code tools is covered in build, buy or no-code.
If you are not sure which of the three your problem is, that is the useful first conversation. Book a review and we will tell you plainly whether you need the clever thing or the boring one. Usually the boring one, and usually that is good news.