Skip to content
Since98
Insights · AI & Automation

AI agent vs chatbot: the difference is what it is allowed to do

A chatbot holds a conversation: it answers questions and collects details. An AI agent receives a task and carries out steps in your systems, such as reading an invoice, updating a record or preparing a document. Many real projects combine both: the chatbot talks to the customer, the agent does the work behind it.

02 — Short answers

Short answer

What is the difference between an AI agent and a chatbot?

Short answer
A chatbot replies inside a conversation and stops there; a person or another system acts on what it collected. An AI agent is allowed to take actions: it calls tools, reads and writes data in your software and decides the next step within limits you set.
How we do it
We separate the two by the permissions each needs when we scope projects: read-only conversation versus write access to systems.
Limits
Vendors use both words loosely. A product sold as an "agent" may only chat, and some chatbots already create bookings. Ask what it can change, not what it is called.

The short difference

The useful line between the two is what the software is allowed to change. A chatbot produces text for a person. An agent produces actions in your systems.

Both usually run on the same kind of large language model. The difference is the wiring around the model: which tools it can call, which data it can read, what it can write and who checks the result.

Chatbot and agent side by side
AI chatbotAI agent
Starts withA message from a customer or employeeA task: a new email, a file, a schedule, a chat request
Main outputA reply in the conversationChanges in systems: records, documents, messages to others
Access neededYour knowledge base, prices, FAQAPIs or exports of CRM, accounting, order or HR systems
Typical riskA wrong or outdated answerA wrong action: an incorrect record, a sent document
ControlHand-off rules to a personPermissions, approval steps, logs and a way to undo
ExampleAnswers price questions on Zalo OA and books a callReads supplier invoices and drafts entries for the accountant

What a chatbot does well

A chatbot fits when the main job is answering and collecting. A clinic gets the same questions about prices and opening hours in Zalo at night. A language center needs to ask a parent about the child's age and level before a counselor calls back. A chatbot handles these conversations in Vietnamese and English and passes a complete request to a person.

The value comes from speed and consistency of answers. The chatbot does not need write access to your core systems, which keeps the project smaller and the risk lower.

What an agent does well

An agent fits when work arrives as documents, emails or records and someone moves the information between systems by hand. Examples: reading delivery documents and filling the shipment record, checking a supplier invoice against the purchase order, preparing a weekly summary from the CRM for the sales director.

Here the value is time that staff no longer spend copying and checking. The cost is a larger project, because the agent must have exact permissions, and every action with money or customers needs a rule about who approves it.

When you need both

Many useful setups combine the two. A customer writes to your Zalo OA asking where the order is. The chatbot part understands the question and asks for the order number. The agent part looks up the order in your system, reads the status and prepares the answer. If the status shows a problem, it creates a task for a staff member instead of guessing.

Splitting the design this way also helps control: the conversation layer can be broad, while the action layer stays narrow and logged.

Three questions to choose

Answer these about the task before you read any proposal.

  • Does the task end with a reply to a person, or with a change in a system? Reply: chatbot. Change: agent.
  • If the software makes a mistake, what breaks? A wrong answer a person can correct is a chatbot-sized risk; a wrong payment or record is an agent-sized risk with approvals.
  • Can a person describe the steps in writing, with the systems named? If not, map the process first; neither a chatbot nor an agent fixes an undefined process.

Notes for companies in Vietnam

Customer conversations here often run through Zalo, so the chatbot side usually starts on a Zalo Official Account, with Messenger and the website as additional channels. What an OA may send outside an active conversation, and what that costs, depends on Zalo's current rules; we confirm them on the audit.

The agent side often meets local software: accounting tools, e-invoice providers, local CRMs and POS systems. Whether they offer an API or only file exports decides how much an agent can do. That is checked system by system, not assumed.

Neither a chatbot nor an agent should give medical, legal or financial advice on its own; those questions go to a qualified person.

03 — FAQ

Questions readers ask

Is ChatGPT a chatbot or an agent?

Used in a chat window, it works as a chatbot. When a product gives the same model tools, such as browsing or editing files, and lets it decide steps, it behaves as an agent. The model is the same; the permissions differ.

Is an AI agent more expensive than a chatbot?

Usually yes, because it connects to more systems and needs approval steps and logs. Our lead assistant starts from $2,500; agent work is quoted after the audit because the systems decide the scope.

Can a chatbot become an agent later?

Yes. A common path is to start with a chatbot that answers and collects requests, then give it one action at a time, such as creating a booking, once the answers are reliable.

Do AI agents replace employees?

In the projects we scope, an agent takes over repetitive steps and a person keeps decisions with money, customers or contracts. We do not promise headcount reductions.

04 — Sources

Sources and notes

  1. 01Our published starting price for the lead assistantOur published prices and terms on this site
  2. 02How we separate chatbot and agent workStudio scoping practice; see the AI chatbot and AI agents service pages
05 — Author

Who wrote this

Dmitry DanilovArchitecture · AI · In web since 1998

One of the two founders of Since98. We write about what we set up for clients: what works, what it costs and where the limits are.

About the founders
06 — Articles

Read next

  • AI & Automation · 3 min read

    How to build an AI agent

    Seven steps from choosing one task to monitoring: data, permissions, tests and the hand-off to people.

  • AI & Automation · 4 min read

    Hiring an AI agent developer

    Freelancer, agency, SaaS vendor or in-house team: the trade-offs, and the questions to ask before you sign.

  • AI & Automation · 4 min read

    AI chatbot cost

    What you pay for in an AI chatbot: scope, channels, integrations, hand-off and the monthly running costs.

08

Next step

Describe the situation in a few lines. One of the founders replies and says whether we can help and what the first step would be.

Book an AI audit call
Or write in a messenger: