Agents Lookup

Learn / Basics

Agents vs workflows vs chatbots: which you need

How to tell a chatbot, a workflow and an agent apart, and a simple way to pick the cheapest one that does the job.

Updated 2026-11-19. "(source N)" refers to the numbered list at the end.

Three different tools

People use the words chatbot, workflow and agent as if they mean the same thing. They do not, and the difference matters for cost, risk and how much time you will spend fixing things.

Here is the plain version.

Why simpler usually wins

Anthropic, which builds agents for a living, tells developers to begin with the simplest option and add complexity only when it clearly helps. Often a single well-written model call, with the right reference material pasted in, is enough (source 1).

The reason is cost and risk. Agents use more tokens because they loop, and each loop is another chance to go wrong. Anthropic notes that mistakes can compound over many steps (source 1). A workflow, by contrast, does the same thing every time, which makes it easy to test.

OpenAI's guide says the same from the other side. Before you build an agent, check that the task really needs one. If it does not, a fixed, rule-based approach may be all you need (source 2).

Workflow patterns that cover most needs

Anthropic describes a handful of workflow shapes that solve many problems without full autonomy (source 1). Each one keeps you in charge of the order of steps.

When an agent earns its keep

OpenAI points to three kinds of work where agents beat rules (source 2). First, judgment calls with lots of exceptions, such as whether to approve a refund. Second, rule books that have grown so big no one wants to touch them, such as vendor security reviews. Third, work buried in messy text, such as reading an insurance claim.

Real usage lines up with this. In LangChain's practitioner survey, the most common agent jobs were customer service at 26.5% and research and data analysis at 24.4% (source 3). Both involve open-ended text and a lot of small decisions.

Anthropic's own usage data shows another pattern. When businesses call Claude through the API, the work is far more directive, meaning the model is told to do a job with little back-and-forth. Two API uses that at least doubled in share over three months were sales outreach and market monitoring (source 4).

A quick way to choose

Answer these in order and stop at the first yes.

Mixing them is normal

Most good systems blend all three. A shop might use a chatbot on its website, a workflow to file each new order, and a small agent that handles return requests that do not fit the usual rules.

Start with the workflow and only hand the hard branch to an agent. That keeps the agent's job narrow, which makes it easier to test and cheaper to run.

Whatever you pick, plan an exit. OpenAI recommends that agents hand control back to a person when they keep failing or when an action is risky, such as a large refund or a cancelled order (source 2). A workflow can include the same check as a fixed step.

Cost and speed in practice

A chatbot reply might use a few thousand tokens. An agent that loops ten times, each time re-reading its instructions and tool list, can use ten or twenty times that. Speed follows the same pattern: each loop is another round trip to the model.

That is why the question is not which is best but which is enough. Pick the smallest tool that meets your quality bar, measure it, and upgrade only when the numbers say you should.

Sources

Written by Agents Lookup in our own words. Facts come from these pages: