AI agent vs chatbot: what's the difference? (And when each wins)
A chatbot answers inside a chat window and waits for a person to act on the reply. An agent is handed a job, reaches into your tools, and finishes it: sends the email, updates the record, closes the ticket. The model behind both is often identical. What changes is who does the acting.
A chatbot that gets things wrong 10 percent of the time is still useful, because a person reads the answer before doing anything with it. An agent wrong 10 percent of the time has already sent the email and already changed the record. Same model underneath, very different tolerance for error, and that gap is what should decide which one you build.
At a glance
| Aspect | Chatbot | AI agent |
|---|---|---|
| What it hands you | An answer to read | A finished task, already done |
| What starts it | You typing a message | A new email, a form, a schedule |
| Where it works | One chat window | Across your tools (Gmail, HubSpot, Slack) |
| How it is billed | Per seat, per month | Per action or per case resolved |
Pick a chatbot when
The job ends with an answer. A help widget on the pricing page, an internal bot that finds the right leave policy, a question box over your own documents.
Pick an agent when
The job repeats and the steps happen outside a chat window. A new lead arrives, gets researched, gets scored, gets posted to a channel. Hand a job over only once you can name the exact point where it has to stop and ask you first.
The billing is the honest label
Intercom charges $0.99 per resolution for Fin, and counts one only when the customer confirms or stops asking. Anything sold purely by the seat, with no meter on actions taken, is a chatbot wearing an agent label. Start with a chatbot for question-shaped work, and move to an agent only for a job your team repeats the same way every week.
Last updated: May 20, 2026