Chatbots answer. Agents act.

Most “AI chatbots” do one thing: they answer. You ask a question, they return a sentence. That was genuinely useful a few years ago, when the alternative was a customer staring at a contact form.

But answering is only the first half of what a customer wants. Someone messaging a clinic at 9pm doesn’t want a paragraph about your opening hours — they want a slot on Saturday. The reply is a means; the booking is the end.

The line between the two

The simplest way to tell a chatbot from an agent is to ask what happens after the reply.

• A chatbot answers and stops. If the customer wants to book, they’re handed a link, a form, or a “someone will be in touch” — and the work lands back on your team.
• An agent answers and then does the thing: it checks the calendar, books the slot, writes it into the record, and sets the reminder so the customer actually shows up.

One produces a transcript. The other produces a booking.

Why it matters more than it sounds

Every handoff back to a human is a place a customer drops off. The form they don’t finish. The callback that comes too late. A chatbot that answers brilliantly but can’t act just relocates the work — it doesn’t remove it.

An agent removes it. It carries the request from “hi, are you open Saturday?” all the way to a confirmed appointment, and only pulls in a person when something genuinely needs one.

That’s the bar we think customer-facing AI should be held to now: not “did it reply?” but “did it finish the job?” If you want the longer version of how that works, we wrote up what an AI agent actually is.