Skip to content

No. 1August 7, 20262 min read

Why we say system and not bot

A bot answers. A system answers, writes it down, books the time, tells the right person and stops where it should. The word matters because it decides what gets built.

Most of what is sold as AI to a business is a bot. It sits in a corner of the website or at the end of a phone line, it answers, and then nothing happens. The answer is not written anywhere. Nobody is told. The caller still has to call back on Monday to get the thing they wanted.

We use a different word on purpose. A system is the bot plus everything around it: the record it writes, the calendar it books into, the person it tells, and the line it will not cross.

The four parts

Every system we build has the same four parts, whatever it is for.

Something that listens. A phone line, a chat, an inbox, a folder that documents land in. This is the part people see, and it is the smallest part.

Something that writes it down. Every call, message or document becomes a record in the software the business already uses. Not a transcript in a vendor's dashboard: a contact, a booking, a ticket, a bill, in the place where the team already looks.

Something that acts. A booking made, a confirmation sent, a reminder set, a bill drafted. The actions are chosen before the build and written on one page, so everyone knows what the system may do on its own.

Somewhere it stops. Anything outside that page goes to a person with the details already collected. A cancellation, a complaint, a price, an emergency: the system does not improvise. It hands over.

Why the word matters

When a business asks for a bot, it gets a bot, and six months later the team is retyping what the bot heard. When it asks for a system, the conversation starts with the records and the hand-offs, which is where the work actually is.

It also changes how you judge the result. A bot is judged on whether its answers sound good. A system is judged on whether the booking is in the calendar, the bill is in the books and the person on duty was told. Those can be checked. Sounding good cannot.

What to ask a vendor

One question sorts the two: "Where does it write things down, and who gets told when it cannot handle something?" If the answer is a dashboard you have to go and look at, it is a bot.

That is the whole newsletter. Short notes like this one, on what it is like to run these systems inside a business, as often as we have something worth saying.

If you have a question, write to us. We read everything.

Written by webridgeAI

We design, build and run AI systems inside businesses. The newsletter is what we learn doing that, in a few hundred words at a time.

The next edition, by email.

Sent when an edition is written, and nothing else.

You can unsubscribe at any time. Privacy

All editions