Chatbot or agent?
A chatbot primarily responds to a user. An agent also selects and uses tools, changes state, or continues a workflow. The boundary is not always clean, so choose based on permissions and consequences rather than the label.
Choose a chatbot when
- the task is answering from approved information
- the user remains in control of every action
- the system does not need to update external records
- a wrong response can be corrected before it causes material harm
Choose an agent when
- the workflow requires multiple tool calls
- state must persist across steps
- the system must read or update other systems
- rules can bound the available actions
- human approval can protect high-impact steps
Start with the least authority
A safe progression is:
- answer only
- recommend an action
- prepare a draft action
- execute after approval
- automate only low-risk, well-tested cases
Cost and delivery
There is no reliable universal cost table for chatbots and agents. Cost depends on integration complexity, model use, evaluation, security, traffic, and support. Agent systems usually require more engineering because they need permissions, retries, idempotency, audit logs, and failure recovery.
The right question is not “agent or chatbot?” It is “what is the smallest amount of autonomy that completes the workflow safely?”
Fact-check sources
Sources and product documentation can change. Recheck time-sensitive pages on the publication date.