AI Agent vs Chatbot vs Automation: Which Does Your Business Need?

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI Agent vs Chatbot vs Automation: Which Does Your Business Need?
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI Agent vs Chatbot vs Automation: Which Does Your Business Need?

Most small businesses need automation first: rules that handle fixed steps such as reminders and data entry, often on a free or $20-a-month plan. Add a chatbot if customers ask the same questions daily, and an AI agent only for multi-step jobs needing judgement across several tools, with a person approving anything that sends, pays or deletes.

The difference is who decides the next step. With automation, you decide every step in advance ("when a form arrives, add a row and send this email"). A chatbot holds a conversation inside limits you set, choosing its own wording. An agent is given a goal and works out the steps itself, often clicking through websites and apps to get there. A quick test: if you can draw the job as a flowchart with no "it depends" boxes, it's automation; if the job is mostly answering people, it's a chatbot; if it means looking things up, deciding and acting in several places, it's agent territory.

Follow me on Instagram@sagnikteaches

Cost and risk rise in the same order. Automation does the same thing every time and either works or stops. A chatbot can phrase a wrong answer beautifully. An agent can take a wrong action, which is harder to undo than a wrong sentence. So the usual sequence for a small business is automation for the routine, a chatbot where customers queue up with the same questions, and an agent for back-office research and drafting where someone reviews the result before it goes anywhere.

Connect on LinkedInSagnik Bhattacharya

One booking enquiry, handled three different ways

Take a message to a small podiatry clinic, arriving by WhatsApp at 9.40pm on a Thursday:

Subscribe on YouTube@codingliquids
Hi, my heel has been really painful for about three weeks, worst first thing in the morning. Do you do Saturday appointments and how much is a first visit?

Automation replies within seconds with the message everyone gets: opening hours, the price list link and the online booking link. It logs the enquiry in a spreadsheet and creates a call-back task for reception at 8.30am. It never registers "three weeks" or "worst first thing in the morning", and it can't answer anything it wasn't built to answer. That's fine. It's cheap, it's predictable, and reception still sees every enquiry.

A chatbot reads the message and answers from the clinic's own FAQ: Saturday clinics run 9am to 1pm, and an initial assessment is $75 (an illustrative price). Set up properly, it also recognises a description of symptoms, says it can't give clinical advice, and offers the booking link or a call-back. It can't hold the slot unless someone has connected it to the diary, and it shouldn't pretend otherwise.

An AI agent is given a goal ("get new patients booked") plus access to the diary and the messaging inbox. It finds a free 10.20am slot on Saturday, drafts a reply and, with approvals switched on, waits for a receptionist to confirm before holding the slot. Without approvals it might book a standard 30-minute slot when a first biomechanical assessment needs 45, or double-book because the diary sync lags by a few minutes.

Same message, three different jobs. The automation moved information, the chatbot held a conversation, and the agent made decisions and took an action. Only the last one needs somebody watching every time.

Seven questions that separate the three options

QuestionAutomationChatbotAI agent
Who decides the steps?You, when you build itYou set the limits; it chooses the wordingThe AI plans them while it runs
Does it talk to customers?Only with fixed messagesYes, that's its whole jobRarely; it's mostly back-office
Can it change things in your systems?Yes, exactly what you mappedOnly if connected to bookings or ordersYes, across several apps and websites
Same input, same result?YesSimilar meaning, different wordingNo; the route can differ each run
How is it usually billed?Per task or creditPer resolution or per messageInside a subscription allowance
Setup time for a small businessAn afternoon to a day per workflowA few days, including testingMinutes to start, weeks to trust
How does it fail?It stops, often silentlyA confident wrong answerA wrong or unwanted action

Read down the columns and the pattern is clear: moving from left to right you gain flexibility and lose predictability. For most admin in a business of under twenty people, predictability is worth more. If you're weighing up rules against AI for one specific task rather than choosing an overall approach, the rules-versus-AI comparison goes deeper on that single decision.

Why so many chatbots are now sold as agents

Vendors have stretched the word "agent" a long way. Intercom sells the Fin AI Agent, HubSpot has a Customer Agent, Meta offers the Meta Business Agent for WhatsApp, Instagram and Messenger, and Shopify Inbox now includes a free AI agent that answers shoppers. In the terms of this tutorial these are chatbots: they hold customer conversations, and some can take narrow actions such as looking up an order or offering appointment times.

General-purpose agents are a different animal. ChatGPT Work, which replaced ChatGPT agent in July 2026, and Claude in Chrome operate browsers, files and connected apps on your behalf for tasks you describe in plain English. This plain-English guide to AI agents explains how they plan and act.

When a salesperson says "agent", ignore the label and ask two questions: what can it change in my systems, and who approves those changes? A customer-service "agent" that can only answer questions and hand over to staff carries chatbot-level risk. A tool that can send emails, move money or delete records needs agent-level controls, whatever the brochure calls it.

The hybrid most owners need: a workflow with one AI step

Plenty of jobs are almost a flowchart, apart from one box that needs reading comprehension. Sorting incoming enquiries is the classic case. The answer is ordinary automation with a single AI step in the middle: rules handle the route, and the AI handles the one judgement.

In Zapier, an "AI by Zapier" step uses 1, 3 or 5 tasks per run depending on the model tier you choose (1 if you bring your own API key), and it's available on the Professional, Team and Enterprise plans rather than Free. Make works on credits, and its routers use none, so branching after an AI step costs nothing extra there.

Here's the AI step an electrician might place between the website form and the job software:

Read the enquiry below and reply with JSON only, using these fields:
job_type: one of fault, rewire, ev_charger, consumer_unit, inspection, other
urgency: one of emergency, this_week, flexible
address_given: yes or no
summary: one sentence, max 15 words, no customer name

Enquiry:
{{form_message}}

A typical output (illustrative):

{"job_type": "fault", "urgency": "this_week", "address_given": "yes",
 "summary": "Kitchen sockets dead since last night, breaker keeps tripping"}

Look at the urgency. The customer wrote "since last night", so the model filed it as this week. That's defensible, but an electrician might want dead sockets plus a tripping breaker treated as urgent. Now suppose that, in your own testing, the same prompt files a message about "a burning smell near the fuse box" as this_week once in twenty runs. The fix isn't a cleverer prompt. It's a plain filter step after the AI: if the message contains burning, smoke, sparks, scorch or shock, set urgency to emergency and text the owner, whatever the AI said. Safety-critical rules belong in the rules part of the workflow, where they behave identically every time.

What each option costs for a 200-enquiry month

The figures below are list prices in USD as of September 2026, and the quick sums are illustrative. Assume 200 enquiries a month and, for the chatbot rows, that the bot fully resolves 90 of them.

OptionExample and list priceQuick sumWhat moves the bill
AutomationZapier Professional, $19.99 a month billed annually for 750 tasksTwo action steps each = 400 tasks; add an AI step at the 1-task tier = 600; at the 3-task tier = 1,000, over the allowanceAction steps per run and the AI tier
AutomationMake, from about $9 a month for 5,000 creditsDepends on modules per run; a trigger checking every 15 minutes uses about 2,880 credits a month even when idleHow often triggers check
Website chatbotIntercom Fin, $0.99 per resolved outcome, plus a seat from $29 a month billed annually90 x $0.99 = $89.10, plus $29 = $118.10Resolution count, and how "resolved" is defined
WhatsApp chatbotMeta Business Agent, $2 per million tokens (Meta puts that at roughly 4-5 cents a message)200 conversations x 5 AI messages = 1,000 messages, about $40-$50Length of each conversation
AI agentChatGPT Work, included in ChatGPT Plus at $20 a monthOne person's plan; bigger tasks use more of the allowance Work shares with CodexTask size and review time
AI agentClaude in Chrome, needs Claude Pro at $20 a month or $17 billed annuallyA flat subscription rather than a price per actionReview time

The hidden line in every row is checking time. An automation needs a two-minute look at its run history each week. A chatbot needs its transcripts read, at least for the first month. An agent needs someone to read every proposed action until it has earned trust, so an agent that saves three hours but needs an hour of review saves two. For a fuller breakdown, see what an AI agent costs a small business.

How each one fails, and the early warning signs

Automation stops quietly

Rule-based workflows rarely do the wrong thing; they stop doing anything. A form field gets renamed or a password changes, and runs start failing. Zapier auto-pauses a Zap when 95% of its runs error over seven days, and it sends no error emails when an error handler has dealt with a failure. Power Automate switches a flow off after 14 days of continuous failure. The warning sign is a run count that drops to zero, so put a weekly check of run history in someone's diary.

Chatbots answer wrongly, with confidence

Consider a hearing-aid shop whose website bot quoted a customer the old price of a battery subscription. The bot had learned from a two-year-old news page announcing the scheme, and the page was still live. Nothing errored; the customer simply arrived expecting the old price. The signs are customers quoting figures you don't recognise and transcripts where the bot answers questions it should have passed on. Remove stale pages from its sources, tell it to say "let me check with the team" for any price not in the current list, and set clear rules for handing over to a person.

Agents act on the wrong thing

Agents fail by doing: sending a draft to the wrong contact, ordering the wrong pack size, or obeying instructions hidden in a web page or email, a trick known as prompt injection. OpenAI's documentation tells ChatGPT users to treat page content as untrusted, and ChatGPT asks for confirmation before sensitive actions such as submitting information, making a purchase or deleting data. Anthropic's safety guidance for Claude in Chrome tells users to avoid using it to manage financial accounts. The earliest warning sign is you: once you start approving actions without reading them, the approval step has stopped protecting you. What can go wrong when agents take actions covers the controls in detail.

A worked choice for a four-clinician podiatry practice

Take a podiatry practice with four clinicians and one receptionist, an illustrative case, that logs every enquiry for a month: 140 in total, arriving by web form, phone and WhatsApp. The receptionist estimates how many minutes each type takes.

Enquiry typePer monthMinutes eachBest fitMinutes saved (estimate)
Prices, opening hours, "do you treat...?"555Website chatbot with handover165, if it resolves 33
Reschedule or cancel354Automation: self-serve link in reminder texts100, if 25 use the link
New booking requests306Automation: form to booking link, plus a log90, at 3 minutes each
Questions about symptoms208A clinician, never a bot0
Total140355, about 6 hours

Running costs: Zapier Professional at $19.99 a month and a small-business chatbot plan at roughly $30-$60 a month, so $50-$80 in total. If an hour of reception time costs the practice about $20 once overheads are included (an illustrative figure), six hours is worth about $120 a month, before counting the evening enquiries that now get an answer. If you're still deciding which job to hand over first, what to automate first ranks the usual candidates.

Notice what's missing: an agent. Nothing in the enquiry log needs a tool that plans its own steps. The practice manager does have one job that fits, the monthly comparison of three suppliers' prices for dressings and insoles, so they try ChatGPT Work on their own Plus plan with a prompt that ends "draft the order but stop before sending anything". On the first run it compares a 100-pack of dressings with a 50-pack and calls the smaller pack cheaper. The manager adds "match pack sizes exactly and list any item you can't match", and the second run is right. That's the right home for an early agent: back office, reviewable and easy to undo.

Symptoms that you picked the wrong tool

  • An agent doing a flowchart's job. A plumbing firm asks an agent each evening to copy finished jobs from the job app into the invoicing sheet. It works for a fortnight, then skips two jobs whose notes say "invoice later", because it read the note as an instruction. A two-step automation copies every finished job the same way every night, and costs far less to run.
  • Automation stretched to cover judgement. A pharmacy's email routing grows to fourteen filter paths and still sends "not urgent, but the dose on my label looks wrong" to the general inbox. One AI classification step, plus one hard rule sending anything that mentions a dose or a medicine name to the pharmacist, does more with less.
  • A chatbot promising actions it can't take. An electrician's website bot tells a customer "you're booked in for Tuesday", because its instructions said to be helpful about bookings, but it has no connection to the diary. The customer waits in all Tuesday. The bot should never say anything is booked unless the booking system has confirmed it; until then it shares the booking link.

All three share a root cause: the tool was chosen for how impressive it looked, not for the shape of the job.

A one-page scoping sheet, filled in for an electrician

Before buying anything, answer these questions for each job you want to hand over. Here's the sheet completed for one everyday task: following up quotes that haven't had a reply.

QuestionAnswer for quote follow-ups
What starts it?A quote marked "sent" in the job software
Are the steps the same every time?Yes: wait 3 days, check status, email; wait 7 more, check, email again
Does it hold a conversation?No. Replies land in the owner's inbox
Where is judgement needed?Only in one personal line that mentions the job
What can it change?It sends emails from the business address
Who approves, and how often?The owner approves the template once, then reads the sent log weekly
Volume and cost60 quotes a month = 120 emails; with an AI step for the personal line, 240-720 Zapier tasks a month depending on the tier
VerdictAutomation with one AI drafting step; no chatbot, no agent

If most answers point to "the same every time", start with automation. If the job lives in conversations with customers, look at a chatbot. Keep an agent for jobs where the steps genuinely change from one run to the next and the result can be checked before it leaves the building.

Agents, chatbots and automation: follow-up questions

Is an AI agent just a chatbot that can do more?

Not quite. A chatbot's job is the conversation: it answers within limits you set. An agent's job is the outcome: it plans its own steps and acts in apps or websites to reach a goal. Some customer chatbots can take narrow actions, such as offering appointment slots, which blurs the line. The useful distinction is what the tool can change and who approves it.

Can one product be automation, chatbot and agent at once?

Increasingly, yes. HubSpot, for example, has a free rule-based chatbot builder, workflow automation, and Breeze AI agents on its Professional and Enterprise tiers. Buying one platform doesn't remove the decision, though. Each job still needs the right mode, and the agent features usually sit on the most expensive tier, so price the tier you would actually need.

Do I need a developer for any of these?

Usually not for a first version. Zapier and Make are built for non-developers, most chatbot builders learn from your website and FAQ without code, and ChatGPT Work takes plain-English instructions. You may want help when a system has no ready-made connector, when a chatbot must look up live orders or bookings securely, or when several workflows depend on each other.

What should I try first if I only have an afternoon?

Pick the most repetitive admin job with a clear trigger, such as new website enquiries, and build a two-step automation on a free plan: log the enquiry and send an acknowledgement. Watch it for a week. It costs nothing, teaches you how triggers and actions work, and shows whether the job is as predictable as you thought.

Further reads

Sources: Zapier pricing and help pages on tasks and AI steps; Make pricing and credits help; Intercom pricing page; HubSpot Customer Agent knowledge base; Meta Business Agent pages; OpenAI's ChatGPT Work and browser documentation; Anthropic's Use Claude in Chrome safely page and Claude pricing page (checked September 2026).

Not sure whether you need an agent, a chatbot or neither?

On a 1:1 call we'll list the jobs eating your week, sort each one into automation, chatbot or agent, and pick the first to build with the software you have now.

Book a 1:1 call with me