聊天機械人負責回答，AI 智能體負責行動：淺白説明兩者的分別

Ask a chatbot about an invoice and you will get a good explanation. It will tell you what an invoice is, what usually goes on one, and how payment terms normally work. Then the conversation ends, and the invoice is still sitting in your inbox, unpaid and unanswered. That gap — between answering and doing — is the whole difference between a chatbot and an agent.

This article was drafted with AI assistance and reviewed by Abdullah Shafique, founder of Elarigent, who takes editorial responsibility for it. Everything below is written for people who run businesses, not for people who build software, so there is no jargon unless it is explained first.

The one-sentence difference

A chatbot answers. An agent does. A chatbot's job ends when it has produced text. An agent's job ends when a piece of work is finished — or, more honestly, when a finished draft is sitting in front of a human waiting for approval. If you remember nothing else from this article, remember that sentence, because almost every confusing product description in this field becomes clear once you ask: does this thing answer, or does it do?

Both are useful. A chatbot is a fine way to get an explanation, a summary, or a first draft of a letter. The confusion starts when something that only answers is sold, or described, as if it does the work. Then a business owner expects the invoice to be handled and discovers, weeks later, that it was only ever talked about.

The invoice test

Here is a practical way to tell the two apart. Put an invoice in front of each and see what happens.

A chatbot will read the invoice if you paste it in, and it will explain it: the total, the due date, the payment terms, maybe a note that one line looks unusual. That is genuinely helpful, and for a single invoice it may be all you need. But nothing has changed outside the conversation. No record has been updated, no reply has been drafted, no reminder has been set.

An agent built for paperwork works differently. It reads the invoice, pulls out the amounts, the dates, and the supplier name, and puts them where they belong — a record, a spreadsheet, a draft reply. If something does not add up, it flags it instead of guessing. Then it stops. The result is a finished draft for a human to check, not a payment made on its own. The point is not that the human disappears from the process. The point is that the human stops doing the copying and starts doing the checking, which is the part that actually needs judgement.

The inbox test

The same split shows up in the inbox. Ask a chatbot to write a reply to a customer and it will write a good one. You still have to notice the email, decide it needs a reply, paste it in, read the draft, copy it back, and send it. The chatbot saved you the writing. It did not save you the morning.

An agent built for inbox work takes on the routine around the writing. It sorts incoming mail, drafts replies in the owner's voice, and sets aside the messages that need a person — the angry customer, the unusual request, the one where the facts are unclear. The owner opens the inbox to a short list of decisions instead of a long list of chores. Again, the human is not removed. The human is moved to the only place they are strictly needed: the decision.

The follow-up test

Follow-up is where the difference costs real money, because follow-up is where small businesses most often lose work. A lead writes in, and nobody replies for an hour, a day, or ever — not out of rudeness, but because the message arrived while the owner was doing the actual job.

A chatbot cannot fix that on its own, because a chatbot waits to be asked. An agent built for follow-up watches for the new message, drafts a first reply right away, and lines up the next follow-up if nobody answers. The owner still approves what goes out. The difference is that the lead hears back in minutes instead of whenever someone finds the time, and the follow-up does not depend on anyone remembering to do it.

What an agent does not do

This is the part that usually gets skipped, so let us be plain about it. An agent can be wrong. It can misread a document, misunderstand a message, or draft something that sounds confident and is incorrect. That is why the pattern that works is always the same: draft first, act second. The system prepares; a human approves. Anything that sends money, messages, or commitments without a human saying yes is not a shortcut. It is a risk, and it is the first thing to be suspicious of in any tool that promises otherwise.

An agent also does not replace judgement, relationships, or knowledge of your own customers. It does not know which customer is going through a hard time, which supplier deserves patience, or which deal matters more than the numbers suggest. Those calls stay human, and any system that pretends otherwise is selling something it cannot deliver.

Four questions to ask any tool

If someone offers you a chatbot or an agent and you are not sure which one it is, ask these four questions. The answers will tell you more than any brochure.

First, what does it do, in one sentence — does it answer, or does it finish a job? Second, what does it touch: your inbox, your documents, your records, and what exactly can it change? Third, what can go wrong, and what happens when it does — does it stop and ask, or does it carry on? Fourth, who approves: is there a step where a human says yes before anything leaves the building? A tool that answers all four clearly is worth a closer look. A tool that cannot answer them is not ready for your business, whatever it calls itself.

The short version

A chatbot is a conversation. An agent is a worker with a defined job and a human checking its work. The first is good for explanations. The second is good for the repetitive jobs that eat a small business's week: reading documents, sorting the inbox, and following up. Neither replaces the owner. The best version of either one gives the owner their time back and keeps the decisions firmly in human hands.

Ready-made AI agents for small businesses, built in public.