What is a WhatsApp bot?

A WhatsApp bot is an automated presence on a WhatsApp Business number. It reads messages that come in and replies on its own, running logic you built. When a customer sends “hi” at midnight, the bot answers. When someone asks your opening hours, it tells them. Nobody has to be at a desk. That’s the whole idea. Not a robot pretending to be human, not artificial intelligence in the sci-fi sense. Just a number that listens and responds by a set of rules you decided on. With Paige, you build that logic by chatting with an AI Code Agent — you describe what you want in plain words, and it writes the bot for you. Paige then hosts and runs the bot around the clock. You don’t need a server, and you don’t need a developer.

​

What a bot is, and isn’t

The word “bot” carries a lot of baggage. It helps to be precise about what you’re actually making. Read the right column as the misconceptions to let go of. A bot is narrower, calmer, and more useful than the word suggests.

​

What a bot can do

At a basic level, a bot handles the parts of a conversation that repeat. A few of the common jobs:

• Answer common questions. Hours, location, prices, “do you deliver?” — the same handful of questions you answer by hand every day.
• Collect information. Ask for a name, an address, an order number, one field at a time, and save what comes back.
• Book or take orders. Walk someone through picking a slot or an item, confirm it, and record it.
• Send notifications. Order ready, appointment tomorrow, payment received — messages that go out to reach the customer where they’ll actually see them.

Each of these is a small, self-contained job. That’s the point of the next section.

​

Start small, and finish

Here’s the argument this whole page is building toward: a bot that does one job well beats a bot that tries to do everything. It’s tempting to sketch the dream bot — the one that answers every question, books every appointment, upsells, follows up, remembers birthdays. That bot is hard to build, hard to test, and easy to abandon halfway. Most first bots that try to do everything never launch at all. A narrow bot is different. You can describe it in a sentence. You can build it in an afternoon. You can test it by sending it a few messages yourself. And you can put it live — a real bot, on a real number, doing a real job — while the everything-bot is still a diagram. Launching one small thing teaches you more than planning a big thing ever will. Once it’s running, you add the next job. Scope grows from something that works, not from a wish list. So pick one narrow first job. Here are concrete starting points — column one is the idea, column two is the single job it does: Any one of these is a complete, launchable bot. None of them needs the others to be useful.

​

Common misconceptions

“Customers will think it’s a real person.” They won’t, and they don’t need to. A good bot is upfront that it’s automated. People are happy to talk to a bot when it answers fast and gets them what they came for. “It has to handle everything, or it’s not worth it.” The opposite is true. A bot that nails one job is worth far more than one that half-does ten. Narrow is a feature, not a limitation. “I need to write code, or run a server.” No. With Paige you build the bot by chatting with the AI Code Agent, and Paige hosts and runs it for you. There’s no server to keep alive and no developer to hire. “A bot replaces talking to customers.” It doesn’t — it clears the repetitive messages so the real conversations get your attention. When something needs a human, the bot can hand the chat over to a person. The bot handles the routine; you handle the rest.

​

Where to go next