Chatbot vs AI agent: what changes for customer support

The chatbot vs AI agent question sounds like a vocabulary debate. In practice it decides what your customers get when they write to you, and what your business gets out of the conversation. This guide explains the difference, the risks on each side, and how to set up an agent that works for your business.

​

What a chatbot is

A classic support chatbot is a decision tree with a text box in front of it. Someone on your team maps the questions they expect, writes an answer for each, and links them with buttons or keywords. When a customer’s words match a branch, the bot replies. When they do not, it shows a menu again or hands over a link to a help article. Most chatbots are built to deflect. The goal is to close the conversation without a person, and success is counted in tickets avoided. That is a fair product for a queue of simple, repeated questions such as opening hours or a returns address. It breaks down in three places:

• Questions nobody planned for. Every tree is a bet on what customers will ask. A customer with a slightly different problem falls off the edge.
• Anything that needs doing. A bot that can only answer cannot change an order, check a delivery or book a slot. The customer still has to call.
• Moments that decide revenue. A deflection bot has no goal beyond ending the chat, so it treats a customer about to cancel the same way it treats a question about parking.

​

What an AI agent is

An AI agent reads the customer’s message in their own words, finds the relevant facts in material you gave it, and writes an answer. It can also act: call your systems to look up an order, update a cart, open a ticket or hand the conversation to a person. The useful way to think about an agent is as a representative of your business. It knows your products, your policies and how you talk to people. It has a goal you set, such as a resolved problem, a booking, or a customer who stays. It works inside rules you wrote down. Every promise it makes should be one you would sign. That changes what you measure. A chatbot is judged on how many conversations it ended. A representative is judged on what happened for the customer and the business: was the issue resolved, did the handoff reach the right person, did the customer come back.

​

The differences that matter

​

What to watch for

An agent that writes its own answers and takes actions needs more care than a tree of canned replies. Most problems come from a few causes. No knowledge, confident tone. A language model with no material to draw on still writes fluent sentences. Give the agent your real content before it talks to anyone, and check that it says “I don’t know” when the answer is not there. Rules that live only in a prompt. Instructions such as “never offer a refund over 50 dollars” are guidance the model follows most of the time. A rule that must hold every time belongs in the tool itself: what the tool is allowed to do, which inputs it accepts, and whether the customer must confirm. Write policy where it is enforced, and keep the prompt for tone and judgement. Actions without confirmation. Changing an order or an address should need an explicit yes from the customer. Read the conversation afterwards to see whether that step held. No way out. Some customers want a person, and some problems need one. Plan the handoff before launch: who receives it, on which channels, and what the customer is told while they wait. No test before customers see it. Run simulated conversations against the agent, including a difficult customer and a customer who tries to get it to break its rules, before you switch a channel on.

​

The other side is getting agents too

Customers are starting to use personal AI assistants that write, compare and follow up for them. When one of those reaches your support, it will ask precisely, keep asking, and read your terms closely. A bot built to end conversations does poorly against that kind of counterpart. A representative that knows your policies and holds to them is what you want on your side of the conversation.

​

Build an agent with Centillion

Centillion builds AI agents that answer your customers from knowledge you control, use the tools you enable, and hand off to your team through the helpdesk. Start from creating an agent. For tasks with several steps, such as a return or a booking, write a Procedure: a trigger, the steps and the tools each step needs. Every agent has Version control. A version saves the prompts, model, knowledge, tools, procedures and evaluation criteria together, so you can see which rules a conversation ran on.

​

Questions

​

Is an AI agent just a chatbot with a language model?

It uses a language model, and the bigger change is the job it does. A chatbot picks a reply from a list. An agent reads the question, retrieves the relevant part of your knowledge, writes an answer, and can call tools you enabled.

​

Will an AI agent make things up?

It can, when it has nothing to answer from. Give it your real content, tell it in the instructions to say when it does not know, and test with questions it should not be able to answer. In Centillion, the agent answers from the six most relevant passages it finds for each question.

​

Do guardrails block forbidden replies?

In Centillion, guardrails are instructions added to the agent’s prompt. Nothing checks a reply against them afterwards. For a rule that must always hold, enable only the tools the agent needs, and let your own API behind a custom tool refuse what your policy does not allow. Only use in procedures keeps a tool out of reach until a procedure calls for it.

​

Can the agent change orders or accounts?

Only through tools you enable under Tools. The Shopify tools, for example, ask the customer to confirm before they create an order, make a return or exchange, or change a profile or address.

​

When should I keep a person in the loop?

When the customer asks for one, when the agent cannot find the answer, and for decisions you would not delegate, such as exceptions to your policies. Set up Escalations or Centillion live chat so those conversations reach your team.

​

Try it

Create an agent, write two paragraphs about who it works for, and give it your website. Then ask it the question your customers ask most, and one it should not be able to answer. Or ask the assistant on this page.

​

Related