Explainer

AI agents vs copilots vs chatbots: what the difference costs you

AI agents vs copilots vs chatbots — three words used interchangeably in marketing that mean different things for your budget. Who drives, what triggers it, and why per-seat pricing caps document work.

Published 10 min

Short answer

A chatbot answers questions inside a conversation. A copilot works alongside a person in a tool they are already using. An AI agent is triggered by an event and completes a multi-step task on its own. The practical consequence is pricing: chatbots and copilots scale with headcount, agents scale with volume of work.

Key takeaways

  • Chatbots manage conversations, copilots make one person faster, agents move process throughput.
  • The test is who holds the thread: a person present at every step, or a trigger and a queue.
  • If your benefit grows with volume rather than headcount, per-seat pricing is the wrong instrument.
  • Much software sold as an agent is a chatbot with a longer prompt. Ask what triggers it with nobody logged in.
  • Agents behave like integration projects, not products — slower to start, harder to remove.

Chatbot, copilot, assistant, agent. The words are used interchangeably in marketing and they mean genuinely different things in terms of what you are buying, what it costs, and what can go wrong. Getting the distinction right before you talk to a vendor will save you a budgeting argument later.

The three shapes, in plain terms

What it doesWho drivesWhat you pay for
ChatbotAnswers questions from a defined body of knowledgeThe user, one question at a timeConversations or seats
CopilotSuggests, drafts and completes inside a tool someone is already usingThe user, continuouslySeats, almost always
AgentCarries out a multi-step task end to end and reports what it didA trigger — an email, a file, a scheduleWork completed, or a project

The practical difference is who is holding the thread. With a chatbot or a copilot, a person is present for every step and the value scales with how many people are using it. With an agent, the work happens whether or not anyone is watching, and the value scales with volume of work rather than headcount.

Why this decides your pricing model

Seat pricing makes sense when the value is proportional to the number of people using the thing. It stops making sense when the work is document-shaped. If your case is "four hundred drawings a month need checking", a per-seat licence is the wrong instrument: you either buy seats for people who barely touch it, or you buy too few and quietly cap the process you were trying to scale.

Where each one actually earns its money

None of these is better than the others. They fit different work, and most companies eventually run all three.

  1. 1Chatbots earn their keep on repeated questions with one right answerOpening hours, order status, where a document lives, what a specification says. High volume, low stakes, and the cost of being wrong is that somebody asks a human instead.
  2. 2Copilots earn their keep where a skilled person is already workingDrafting, summarising, writing code, first-pass analysis. The person's judgement is the product; the copilot removes the typing.
  3. 3Agents earn their keep on work that arrives whether or not anyone is freeInbound email, incoming drawings, quotation requests, catalogue updates. The work has a trigger, a defined outcome, and a queue that builds up when nobody gets to it.

The part vendors are vague about

"Agent" has become the fashionable word, so a great deal of software that is really a chatbot with a longer prompt is now sold as an agent. Two questions cut through it.

  • What triggers it without a person present, and what happens to the result when nobody is logged in? If the honest answer is "a user opens it and types", you are buying a chatbot.
  • What does it write to, other than the screen? An agent that cannot put its output into your systems — your inbox, your PIM, your documents, your ERP — is a demo with good manners.

What this means for how you buy

Chatbots and copilots are products: you evaluate them on a trial, you pay per seat, and switching is relatively cheap. Agents behave more like integration projects, because most of the work is in the connections to your systems and the rules that encode how your company actually operates. That makes them slower to start and considerably harder to rip out — which cuts both ways, and is worth knowing before you sign rather than after.

In short

None of the three is better than the others; they answer different questions about who is present when the work happens. Decide that first, because it determines whether you are buying a product you can trial and swap, or commissioning an integration you will live with for years. Vendors blur the words. Your budget does not.

Frequently asked questions

What is the difference between an AI agent and a chatbot?

A chatbot responds inside a conversation and does not act outside it — someone asks, it answers. An agent is triggered by an event such as an incoming email or file, plans a sequence of steps, calls other systems, and writes a result back. The chatbot needs a person present; the agent does not.

Is a copilot the same as an agent?

No. A copilot is not the primary actor — a person is, and the copilot suggests, drafts and summarises while they work. Remove the person and a copilot does nothing, whereas an agent carries on. That single difference drives the pricing model and most of the integration effort.

Which is cheapest?

Chatbots and copilots have the lower entry price and are usually per seat. Agents cost more up front because most of the work is integration and encoding your rules, but they do not charge you per person for work that is measured in documents. Model your real annual volume against both shapes before signing.

How do I tell whether a vendor's agent is really an agent?

Two questions. What triggers it when nobody is logged in? And what does it write to besides the screen? If the honest answers are "a user opens it and types" and "nothing", you are buying a chatbot with better marketing.

Can we use all three?

Most companies eventually do, and they should — they fit different work. A chatbot for repeated questions with one right answer, a copilot where a skilled person is already working, an agent for work that arrives whether or not anyone is free.

Half an hour on your process

Tell us the task your people resent doing and we will tell you, straight, whether it is a good first AI project — including when the answer is that it is not.

Book a call