A chatbot answers questions. An AI agent resolves them. That sounds like marketing, so here is the concrete version.
A chatbot works from paths somebody drew in advance. Press 1 for billing, press 2 for faults. Every branch is hand built, and the moment a customer phrases something the script did not anticipate, it apologises and offers to find a human. Published benchmarks put most of these at 20 to 40% of conversations handled without escalation.
An AI agent works the other way round. It reads what the customer actually said, in their own words, decides what that means, pulls the relevant record from your systems, and does something with it. Raises the ticket. Checks the line. Books the engineer. Sends the invoice.
The test that separates them
Ask what happens when a customer says something nobody planned for.
A chatbot falls off the tree. There is no path, so there is no answer, and it hands over. An agent has no tree to fall off, so it reasons from what it knows and either answers or escalates deliberately.
That is the whole distinction. Everything else follows from it.
Where the difference actually shows up
Not in conversation quality. Modern chatbots can be perfectly polite. The difference lands in three places.
Can it act, or only talk. A chatbot can tell a customer how to check their balance. An agent checks it for them. That requires an integration layer wired into your CRM, billing and helpdesk, which is the part nobody puts on a slide and where most of the build time goes.
Resolution rate. Well integrated agent deployments reach 70 to 90% of conversations handled end to end. The gap between that and the 20 to 40% band is almost entirely integration depth, not model choice.
What it does when unsure. A chatbot escalates because it ran out of script. A good agent escalates because it has a confidence threshold and dropped below it, and hands over with the customer already verified and the issue captured.
Where the line gets blurred
Plenty of products marketed as AI agents are chatbots with a language model bolted on the front. They understand the question fine and then have nothing to do about it, because there is no integration underneath.
The way to tell is to ask a vendor to show you a live one and describe what happens after it understands. If the answer is about conversation quality rather than about systems it writes to, you are looking at a chatbot in a better coat.
Why this matters commercially
Customers learned to distrust the first category. Most people type "agent" the moment a chat window opens, because a decade of decision trees taught them that the bot is an obstacle between them and a person.
That trained reflex is the real cost of the chatbot era, and it is why a badly built agent is worse than none at all. It confirms what the customer already suspected.
Across our own deployments the pattern has been consistent: the volume that disappears first is not the clever conversation, it is the boring high-frequency question that was quietly eating the team alive. Where is my order. When is the engineer coming. Why is this bill different.
None of that needs a tree. All of it needs live data.
