article · cross business
AI agent, chatbot, or ordinary automation: which does this task need?
Compare ordinary automation, chatbots, fixed AI workflows, and agents using one support request and a decision table for choosing a suitable approach.
The direct answer
Use ordinary automation when rules describe the task. Use an AI-assisted workflow when the steps are fixed but a language task needs interpretation. Consider an agent when the next useful step depends on what the system finds. A chatbot is a conversation interface; it can sit in front of any of these approaches.
One task, four approaches
Synthetic example: A customer asks where to find an onboarding guide. The approved answer says it is in the welcome email. If that email is missing, a person must check access. These are teaching inputs, not client observations.
| Approach | How it handles this request | What you need to check |
|---|---|---|
| Ordinary automation | An explicit form choice, “Find my guide,” returns the approved instructions. | The rule matches the selected issue and offers a human route. |
| Chatbot | Asks whether the customer can find the welcome email, then displays an answer. | The interface alone says nothing about how the answer was selected. |
| Fixed AI-assisted workflow | Reads the message, drafts from the supplied FAQ, and places it in a review queue. | The draft is supported by the FAQ and makes no access promise. |
| Model-directed agent | Chooses an allowed knowledge lookup, examines the result, then drafts or escalates. | Its lookup was permitted, evidence was sufficient, and it stopped within its limits. |
Separate interface, reasoning, and authority
A chat window describes how someone interacts with a system. It does not establish whether the system follows rules or chooses tools. An AI agent makes some choices about steps; a fixed workflow follows a route its builder defines. This distinction follows Anthropic’s workflow and agent framing.
Authority is another decision. Each approach can be restricted to reading or drafting. Do not infer permission to send a message from the ability to compose one. Put the approval boundary in the workflow and in the account permissions.
Decision table
| What the task needs | First approach to try | Evidence that might justify more complexity |
|---|---|---|
| Copy known fields between systems | Ordinary automation | A field requires interpretation that rules cannot handle adequately. |
| Interpret varied wording on a fixed route | AI-assisted workflow | Relevant evidence cannot be found using the predetermined route. |
| Ask a person clarifying questions | A form or chatbot interface | Conversation meaning requires bounded language interpretation. |
| Choose among approved information sources | A bounded agent experiment | Tests show the choice improves the result enough to justify oversight. |
Limits and non-example
A scheduled sequence that always reads a sheet, summarizes it, and stores a draft is not model-directed merely because the summary uses AI. Conversely, asking a model to choose tools does not prove the choices are useful. More possible routes create more cases to test.
When the task is rare, its rules are unsettled, or nobody can check the output, keep it manual while you resolve those gaps.
Try this exercise
Take one actual task, remove private details, and write its trigger, inputs, decisions, and output. Circle decisions that require interpreting language. Underline decisions that change the next source or tool. If nothing is underlined, explain why a fixed workflow would not suffice before proposing an agent.
Sources and scope
The terminology source is linked above. The comparison and decision table are original editorial guidance with a synthetic example, not a product benchmark. No tool execution or business outcome is claimed.
Next step
Use the workflow brief to record the simplest suitable approach and the action a person retains. Suggest a correction if this distinction is unclear.
Change notes
Foundation draft prepared October 20, 2026. No public publication or successful live-tool test is claimed.
Next learning step: One-page workflow brief