An agent is not a chatbot on a button

Almost every week a brief arrives saying: «we want a chatbot on the website». And almost every time, after the first call, it becomes clear they don't need a chatbot. They need an agent inside a process.

The difference is simple. A chatbot answers a question. An agent closes a task. A chatbot is a window. An agent is a teammate.

Classic example: e-commerce. Chatbot in the corner: «Hi! How can I help?». Metric — clicks on the widget. Outcome — nothing. Same business, but with an agent. It qualifies the lead, pulls history from CRM, builds a cart tailored to the person, drives them to checkout, and hands off to a human manager only on the hard cases. Metric — qualified leads in pipeline. Outcome — +34% conversion.

An agent lives inside your infrastructure, reads your CRM, checks your inbox, works with your documents. It has tools, roles, and limits. It makes mistakes — and they show up in the log. It gets fixed — and that's part of the SLA.

When we hear «chatbot» it's usually a technical framing. When we hear «agent» it's a framing about accountability. We prefer the second one. Because only the second lets us take a real commitment on the outcome.

If your task sounds like «we want a chatbot» — start with the question «which process should it close end-to-end?». If there's no answer — you may need a CRM, not automation. If there is — you already have the spec for an agent.