B2Shift · Published · Updated

The three terms get used interchangeably in sales decks and mean genuinely different things in production. The distinction is not the underlying model — it is what the system is allowed to understand, decide and change.

What is a chatbot?

A chatbot holds a conversation. Its output is language: an answer, a summary, a suggestion. Modern ones retrieve from a knowledge base before answering, which makes them far more accurate than the scripted decision trees of a decade ago, but the boundary is the same. When the conversation ends, nothing in your systems has changed.

That is the right tool when the outcome you want genuinely is an answer — opening hours, product specifications, policy questions, first-line support deflection. It is the wrong tool when the customer's actual goal is to book, buy, cancel or amend something, because the chatbot has to hand them off to do it.

What is an AI agent?

An agent interprets a request, chooses from a set of actions you have permitted, and uses tools to carry them out. It can read the calendar, create the CRM record, send the confirmation and decide, within your rules, which of those steps this particular case needs. The defining feature is bounded autonomy: it picks the path, but you drew the map.

This is the right tool when the outcome requires a small decision that a fixed rule cannot express cleanly — is this enquiry qualified, does this request need a specialist, is this invoice an exception. It is the wrong tool when the sequence never varies, because you are paying a model to re-derive a decision you already know the answer to.

What is workflow automation?

Workflow automation connects deterministic steps across systems. A trigger fires, data moves, rules apply, records update, someone gets notified. There need be no model involved at all. What it offers instead is reliability: the same input produces the same output, failures are visible, and a retry does not produce a different result.

This is the right tool when reliability and system-to-system execution matter more than flexibility — invoice pipelines, data synchronisation, scheduled reporting, provisioning. It is the wrong tool on its own when the input is unstructured language or a scanned document, because deterministic rules have nothing to grip.

Which one does a real business need?

Usually all three, in layers. A production workflow often starts as deterministic automation, calls a model at the two or three points where judgment is genuinely needed, and exposes a conversational surface only where a human is on the other end. Arguing about the label is less useful than answering four questions: what may this system read, what may it change, what happens when it is unsure, and who is accountable for the result.

If those four answers are clear, the architecture tends to design itself. If they are not, no amount of agent framework will save the project.

Compare chatbot, workflow and agent by control

Choose a pattern from the work the system must perform
PatternAutonomyTool accessRisk and operating cost
ChatbotResponds to a person, usually one turn at a timeOptional read-only searchLower when answers stay within approved knowledge
WorkflowFollows defined triggers, rules and branchesExplicit app actionsPredictable; effort goes into integrations and exception handling
AgentSelects steps toward a goal based on contextOne or more tools chosen at run timeMore variable; needs strict permissions, limits and monitoring

Apply the choice to an internal policy question

Suppose an employee asks whether a purchase is reimbursable. A chatbot can explain the current policy and cite the relevant section. A workflow can check whether the submitted form has required fields and route it by amount. An agent could search several sources and propose an answer, but it should not approve or pay the expense without a defined authorization path. Start with the least autonomous pattern that meets the need; increase autonomy only when evaluation shows the added decision-making is reliable and worth the operating cost.

Distinguish a chat interface from the system behind it

A chatbot describes how a person interacts with software; it does not by itself explain how the answer is produced or what actions the system can take. A chatbot may use a fixed decision tree, retrieve approved documents, call a deterministic workflow or give an agent access to tools. Ask what happens after the message is received: which data is searched, which component chooses the next step, whether external systems can be changed and who can review the result.

Likewise, a workflow can include a conversational interface without becoming an AI agent. The important design choice is the decision boundary and the authority granted at each step, not the label on a product page. A useful architecture diagram shows the user, model, retrieval sources, workflow rules, connected systems and approval points. That makes it easier to compare options that use different names for similar capabilities.

Choose autonomy from the consequence of an error

Use a read-only chatbot or retrieval assistant when the main need is to explain current information and a person can act separately. Use a deterministic workflow when the trigger, fields and business rules are known, such as checking a form and creating a task. Consider an agent only when a goal requires selecting among several permitted steps based on context that cannot be represented simply in fixed branches. Even then, keep the available tools narrow and make high-impact actions require approval.

Estimate the cost of an incorrect or incomplete outcome alongside the cost of review. A wrong answer about a low-impact internal procedure may be corrected in the conversation; a mistaken payment, account change or disclosure can be harder to reverse. If the process needs precise thresholds, repeatable audit evidence or guaranteed ordering, keep those controls in ordinary software and let the model interpret only the parts that benefit from language understanding.

Use a support request to compare three implementation patterns

For a customer asking where an order is, a chatbot can retrieve the current delivery policy and cite it. A deterministic workflow can look up an order after the organisation's identity checks, return the verified delivery state and create a case when it is late. An agent might decide whether it needs to search the policy, query the order system or create an escalation, but its tools should be limited to those operations and it should not invent a shipment event or issue compensation without an approved rule.

Compare the patterns against the same acceptance cases: valid order, ambiguous identity, missing record, late delivery, conflicting status and unavailable connector. Record the source each answer relies on, the permitted write action, the expected handoff and the behavior when a tool fails. This shows whether agent autonomy solves a real routing problem or only adds more steps to a workflow that could be explicit and easier to test.

Set tool permissions, approval and recovery boundaries

For an agent, expose only the tools needed for the task and separate read operations from write operations. Validate arguments before a call, constrain records and fields the tool can access, set limits on repeated actions and require confirmation for irreversible changes. Treat content retrieved from websites, documents and emails as data rather than instructions that can change the agent's access policy. Log the requested action, validated arguments, system response and any human approval.

Decide what happens when a tool times out after it may have completed. Check the destination state before retrying so a second action does not duplicate a payment, ticket or message. Keep a person able to stop the run and resume the business process manually. A nominal approval button is not an effective control if the reviewer lacks the source context, time or authority to reject the proposed action.

Evaluate answer quality and action quality separately

A chatbot can provide a grounded answer yet still fail the task if the link is inaccessible or the user cannot reach a person. A workflow can complete every system step and still route the case incorrectly. An agent may choose a valid sequence but call an unsuitable tool or repeat an action. Define separate measures for answer grounding, task completion, correct routing, action accuracy, escalation quality, latency, cost and human review effort.

Use a representative test set with straightforward requests, missing information, contradictory sources, off-topic questions, prompt injection attempts, tool failures and requests outside policy. Record the expected response and action boundary for each case. Have the process owner review failures and set thresholds for critical errors before rollout. Test again after changing the model, prompt, retrieval index or connected tool because each can alter behavior independently.

Estimate the full operating cost before increasing autonomy

The visible model charge is only one part of the cost. Include integration work, knowledge cleanup, evaluation, security review, monitoring, tool calls, exception handling, human approvals and the time needed to update policies. An agent may reduce manual routing but increase tool execution and review cost; a workflow may need more initial mapping but have more predictable operations. Compare cost per correctly completed case using the same volume and quality assumptions.

Start with a narrow pilot, such as read-only answers or a suggested next action, and measure where people still intervene. Expand tool access only when test results and live samples support it. Keep the model, configuration and tool policy versioned so an operating cost or quality change can be traced to a release. If the simplest pattern meets the service requirement, adding autonomy creates obligations without a demonstrated benefit.

Sources

OpenAI — A practical guide to building agents

Discuss your workflow