--- title: "AI agent, copilot, automation or assistant: the difference" description: "Answer three questions and find out what AI you already run: an agent, a copilot, an automation or an assistant. What each one does, and what it doesn't." url: https://studiochat.io/is-it-or-is-not-ai locale: en translations: { es: https://studiochat.io/es/is-it-or-is-not-ai.md, pt: https://studiochat.io/pt/is-it-or-is-not-ai.md } site: https://studiochat.io --- Tool # What AI you already run in your processes: agent, copilot, automation or assistant Three questions, none of them technical, and the tool names which of the eight shapes you already run. Question 1 of 3 Who starts the work? * A person, when they need it * The system on its own, at a set hour or when something happens The tool classifies by decision rights, not by brand or by model. Nothing you answer is stored. The eight shapes ## The eight shapes of AI a company usually already has installed Eight concrete shapes, grouped into the four patterns. What separates them isn't the brand or the model: it's who starts the work and who decides the next step. ### A general-purpose AI chat Assistant Handles whatever comes up: a question, an email, the summary of a long text, an explanation, thinking something through. It's the most common shape and the fastest to adopt. It doesn't it doesn't reach company systems and leaves no trace inside the process. If nobody opens the tab tomorrow, the work happens exactly as before. ### A project/Gem Saves the context and instructions, so nobody repeats them and answers look more alike across people. It doesn't it doesn't start on its own: it still waits for someone to open it and ask, and it doesn't touch the systems. ### An artifact/canvas Produces something you edit right there: a document, a spreadsheet, a calculator. It doesn't it isn't maintained or connected to the operation unless someone publishes it. A month later the data inside is stale. ### An assistant with connectors Reads and writes in the connected tools when someone asks: pulls the record where it lives, updates it, sends the message. It doesn't doesn't start on its own and doesn't pick the next step. If nobody opens it and asks, nothing happens, and what it did stays in the chat instead of in the process. ### A routine/scheduled task Automation Runs on its own and leaves the result ready: the Monday report, the weekly summary. It doesn't it doesn't choose what to do with what it found. If the result calls for an action, a person still takes it. ### A licensed copilot Copilot Drafts, calculates or suggests inside the tool the team already uses, and waits for approval. It doesn't it doesn't shrink the team: somebody reviews one by one, and as volume grows that review is the bottleneck. ### A flow with an AI step inside Runs without anybody opening it and writes into the systems at the planned steps. The model solves one specific step: classify, summarise, tag. It doesn't it doesn't handle the case that wasn't in the drawing: there it stalls, flags, or carries on down the default branch. ### An agent Agent Decides the next step and executes it: asks for what's missing, checks the system where the data lives, writes the result and hands off when it should. It doesn't it isn't bought without three things in writing: the scope of what it can do alone, the cases where it must hand off, and where what it decided gets logged. The full reasoning, with the four patterns and the three questions that work in a demo, is in [the article on assistant, automation, copilot and agent](/blog/asistente-automatizacion-copiloto-agente). Why it matters ## What it costs not to know which of the eight you have This isn't an argument about names. The category sets what you pay, what goes unhandled, and who answers when it goes wrong. ### Paying too much Buying an agent for a three-fixed-step process is paying for decisions nobody needs. An automation handles it better and cheaper. ### Paying too little Buying an automation for a process with twenty real variants guarantees the team keeps handling the seventeen that didn't fit the diagram. ### Who answers A copilot leaves responsibility with whoever approves. An agent leaves it with the company that put it to work. That line gets defined before signing, not after the first mistake. Frequently asked questions ## Differences between agent, copilot, automation and assistant ### What is an AI agent, and how is it different from an assistant? An agent decides the next step within a defined scope and executes it without anyone approving each action. An assistant answers, and the person who asked keeps doing the work, even when that assistant has connectors and touches the systems. The difference isn't the model or the brand: it's who picks the next step. ### Is a chatbot an agent? It depends on what it does when the conversation leaves the script. If it follows a decision tree and repeats or hands off when something unexpected appears, it's an automation with natural language on top. If it decides the next step and takes actions in company systems, it's an agent. ### Is this useful for evaluating a vendor's proposal? It's useful for organising the conversation, not for replacing it. Answering for what you were shown in the demo, the tool tells you which category it is. What to ask for next is always in writing: the scope of what the system can do alone, the cases where it has to hand off, and where what it decided gets logged. ## The playbook already exists. We multiply it. [Talk to us now](https://cal.com/studiochat) [Book a demo](https://cal.com/studiochat) [Or write to hey@studiochat.io](mailto:hey@studiochat.io)