Every vendor selling you "AI" is selling you either a chatbot, an agent, or something in between — and most of them use the words interchangeably. That's a problem, because the two are architecturally different, solve different problems, and cost very different amounts to build and run.
Here's the clear version.
TL;DR
- A chatbot generates a response to a question. An agent takes actions to complete a task.
- Chatbots are better for: answering questions, handling FAQs, first-line support deflection.
- Agents are better for: multi-step processes that require reading systems and doing something with the result.
- Cost gap is real: a production chatbot runs $10K–$40K. A production agent runs $25K–$80K.
- Most businesses should start with a chatbot. Add an agent when you've identified a specific multi-step process costing significant human time every week.
What a chatbot actually is
A chatbot is a conversational interface. The user sends a message. The chatbot generates a response. That's the complete loop.
Modern AI chatbots use large language models instead of keyword matching, which makes them dramatically better than the scripted chatbots of 2018. A well-built chatbot with RAG (Retrieval-Augmented Generation) can accurately answer questions from your documentation, policy docs, or product catalog — in natural language, at scale.
What a chatbot cannot do is take action. It can tell a customer their order status (if it can look it up) but it can't change the order, reroute the shipment, or issue the refund. It can answer a support question but can't update the CRM record or escalate the ticket.
The moment you need the AI to do something — not just say something — you've crossed into agent territory.
What an AI agent actually is
An AI agent is software that can perceive input, make decisions, take actions using tools, observe the results, and continue until a goal is accomplished.
The key addition is tools — functions the agent can call to interact with other systems. A tool might be:
- A CRM API call (read a contact record, update a field)
- A database query (look up order history, check inventory)
- An email send (draft and send a message on behalf of the user)
- A web search (find current pricing, check competitor updates)
- A code executor (run a script, process a file)
The agent decides which tools to call and in what order, based on what it's trying to accomplish. It's not following a fixed script — it's reasoning about the task and choosing actions.
The clearest way to see the difference
Same scenario, both approaches.
Scenario: A customer emails saying their order arrived damaged.
Chatbot:
- Reads the email
- Generates a reply: "We're sorry about this. Please reply with your order number and photos, and our team will process a replacement within 2 business days."
- Done — a human still has to handle the follow-up
Agent:
- Reads the email
- Searches the CRM for the customer's order using their email address
- Finds the order, checks the item and return policy — damaged items are eligible for immediate replacement
- Checks warehouse inventory — replacement available
- Creates a new replacement order in the fulfillment system
- Sends the customer a confirmation email with the replacement order number and tracking ETA
- Updates the CRM record with a note and flags the original shipment for quality review
- Done — no human involved
The chatbot moves the conversation forward. The agent closes the loop.
When to use a chatbot
Chatbots are the right tool when:
Your primary need is answering questions. If visitors are asking about your product, pricing, or policies — and the answer is in your documentation — a RAG chatbot handles this better and cheaper than an agent.
You want to deflect support volume. 60–80% of support tickets are repeat questions with known answers. A chatbot handles these without touching your team.
You're starting your AI journey. Chatbots are faster to build (1–2 weeks for a production RAG chatbot), cheaper to run, and easier to evaluate. They're a sensible first step before committing to agent infrastructure.
You're in a regulated industry. Chatbots are easier to audit than agents. Every response can be traced back to a source document. Agents make decisions that are harder to explain after the fact.
When to use an AI agent
Agents are the right tool when:
A human is executing a multi-step process repeatedly. If someone on your team spends hours every day reading inputs, making decisions, and taking actions across multiple systems — that process is a candidate for an agent.
The work requires accessing and updating multiple systems. Agents are built for this. A task that touches your CRM, your support system, and your accounting software is exactly what agents handle.
"Telling" the user something isn't enough — you need the work done. Lead qualification, invoice processing, customer onboarding, meeting scheduling — these aren't answered by a chatbot; they're completed by an agent.
You have the volume to justify the build. The ROI on agents comes from scale. If this process runs 10 times a week, the math may not work. If it runs 200 times a week, it almost certainly does.
Cost and complexity comparison
| Chatbot | AI Agent | |
|---|---|---|
| What it does | Answers questions | Executes tasks |
| Actions | None (or read-only) | Read + write across systems |
| Typical build cost | $10K–$40K | $25K–$80K |
| Time to production | 1–4 weeks | 4–12 weeks |
| Maintenance | Low | Moderate–high |
| Needs evals? | Recommended | Required |
| Failure mode | Wrong answer | Wrong action |
The failure mode difference matters. A chatbot giving a wrong answer is a bad experience. An agent taking a wrong action — sending an unintended email, modifying the wrong record — can be a real business problem. Production agents need guardrails, human-in-the-loop escalation paths, and monitoring.
What most vendors are actually selling you
The confusion in the market is partly deliberate. "AI agent" sounds more advanced and justifies a higher price tag, so vendors call things agents that are really sophisticated chatbots.
The test: can it take actions that change the state of your systems? If no — if it can only read and respond — it's a chatbot, regardless of what it's called.
Some vendors build "agentic" chatbots — chatbots with one or two tool calls bolted on, like looking up an order status. This is a reasonable intermediate step. Just be clear about what you're buying and what the system can and can't actually do.
How to decide what you need
Two questions are enough:
1. What's the end state I want the AI to produce?
- A response to a question → chatbot
- A completed task across one or more systems → agent
2. What's the volume and value of the process?
- Low volume (< 50 instances/week) → consider whether automation pays off at all
- High volume, low decision complexity → traditional automation may be faster and cheaper
- High volume, high decision complexity → agent
If you're still unsure, a Discovery Sprint — one week, fixed scope — maps your processes, identifies the right approach, and produces a working prototype you can evaluate before committing to a full build.
The bottom line
Chatbots respond. Agents act. Both are valuable — the question is which problem you're trying to solve.
For most $1M–$15M businesses starting their AI journey, the path is: chatbot first for customer-facing Q&A, then agent for the internal processes eating the most team time. You don't have to choose one forever; you choose one to start.
Next step: Explore AI agent development →
Not sure which is right for your business? The AI Profit Leak Audit identifies which processes are best suited to each approach — and gives you a prioritized roadmap before you commit to a build.