Skip to content
qiyas.cc
Problem Solver
cc · blog · Business 2026-11-13 · 8 min

What a WhatsApp bot actually does for a business (and what it doesn't)

Your customers are already on WhatsApp. A bot answers at 3 a.m., takes orders and filters leads. It does not fix bad service. Rules, prices and risks, without the sales pitch.


In Baku, where I live and work, WhatsApp is the front desk. A business can have a website and a busy Instagram, and the customer still ends up typing “hi, how much?” into WhatsApp.

So people ask me: “Do we need a bot?” Wrong question. The useful one is which part of the work can a bot take, and which part can’t it? Here is my honest answer, with the rules Meta actually enforces and the prices as they stand at the end of 2026.

First: which WhatsApp?

“WhatsApp bot” can mean three very different things. Mixing them up is where most of the expensive mistakes start.

WhatsApp Business app WhatsApp Business Platform (Cloud API) QR-code bridge
What it is The Business app on a phone Meta’s official API Unofficial libraries speaking the WhatsApp Web protocol
Automation Greeting and away messages A real bot, a panel, integrations A real bot
Cost Free Per message, at Meta’s rates Your server
Risk None None if you follow the rules Losing the number

For a small shop the Business app is often enough. Real bots live in the second column. The third column gets its own section below, because it looks cheap and that is exactly why people go there first.

One newer option worth knowing: Meta now lets a business keep the same number in the Business app and on the Cloud API at the same time (they call it coexistence). Staff keep chatting from the phone, the bot runs on the same number. Those numbers are capped at 20 messages per second, which no small business will notice.

What a bot really gives you

An answer at 3 a.m.

A customer writes at 11 p.m. and you answer at 9 a.m. By then they have messaged three of your competitors. A bot answers at 3 a.m. In sales, the speed of the first reply decides a lot.

The same five questions, handled

Price, address, opening hours, delivery, “do you have real photos?”. Someone on your team types these a hundred times a day. A bot does it without getting tired, and your people keep the conversations that need a person.

Orders and bookings that finish

A good bot doesn’t just reply. It closes the loop: picks the product, asks for the address, sends a payment link, writes the order into your panel. I wrote separately about the payment part: connecting Epoint payments to a website.

Filtering leads

Not every “hi” is a buyer. A few questions tell the bot who is serious, what they want and what they can spend, and the salesperson gets a ready lead instead of a chat that goes nowhere.

The clearest example from my own work is Khalif System, which runs a real estate agency in Baku over WhatsApp. A buyer describes what they want and is told how many homes match. A seller answers a few questions and sends photos or video, and the listing goes to an admin for one-tap approval.

Voice notes and languages

Here people don’t type, they talk. A bot that can’t handle a voice note is half a bot in this market. Khalif System transcribes voice notes and videos with a local Whisper service and replies in the customer’s own language: Azerbaijani, Turkish, English or Russian.

A CRM behind it

A bot is only useful when it is connected to the rest of the business. The conversation, the number, what they asked for and who took over all need to land in one place. Otherwise the bot is just a second source of chaos. For real estate I went into this in CRM for real estate agencies.

A way out to a human

The most important button. When the bot doesn’t know, it should say “I’ll connect you to a manager”, not make something up. This is also one of Meta’s rules (see below).

What a bot won’t do for you

Few people say this part out loud, so I will.

  • It won’t fix bad service. If the delivery is late or the price is wrong, the bot just delivers the bad news faster.
  • It doesn’t know what it doesn’t know. A bot with no access to your stock or your price list will either stall or lie. It has to be wired to a real source of truth.
  • It won’t handle complaints or negotiations. Angry customers, discounts, complicated orders: that is people work.
  • It isn’t a spam cannon. People who get messages they didn’t ask for block you, and blocks and reports drag down your number’s quality rating.
  • It isn’t a general-purpose AI. Since January 15, 2026 Meta has barred services whose main product is a general-purpose AI assistant from the Business Platform. That rule doesn’t touch businesses using AI to serve their own customers. Your bot should talk about your business, not write poems.

Meta’s rules, briefly

On the official API, these are your rules too.

The 24-hour window. When a customer messages or calls you, a 24-hour customer service window opens. Inside it you can send any message, automated replies included.

Templates. Outside that window you can only send a template Meta has approved. Templates come in three categories: marketing, utility (order updates, reminders) and authentication (one-time codes).

Opt-in. You may only message someone who gave you their number and agreed to hear from you. Finding a number somewhere and writing to it is not allowed.

Opt-out. If someone asks you to stop, on WhatsApp or anywhere else, you stop.

A clear escalation path. Automation is allowed inside the 24-hour window, but there must be a prompt, clear way to reach a person: an in-chat human handover, a phone number, email, a support form and so on.

Messaging limits. A new business portfolio can message 250 unique people per 24 hours outside the window. Verifying the business lifts that to 2,000, and it grows automatically while quality stays high. The limit applies to the whole business portfolio, not to each number.

Pricing at the end of 2026

A lot of outdated advice floats around, so here it is with dates.

  • Since July 1, 2025 Meta charges per message, not per conversation, and only for messages that are delivered.
  • Messages customers send to you are free.
  • The price depends on the category (marketing, utility, authentication, service) and on the recipient’s country. Numbers in Azerbaijan (+994) aren’t priced as a separate market: they fall under Meta’s “Rest of Central & Eastern Europe” region.
  • Since October 1, 2026 each business phone number gets 1,000 free service messages a month and pays beyond that. Utility templates sent inside an open 24-hour window are charged again too.
  • When a customer writes to you from a Click-to-WhatsApp ad, a free entry point window opens that can stay open for up to 7 days.

I’m not printing exact rates here, because Meta revises them several times a year. I always run the numbers against Meta’s current rate card. For most small and mid-sized businesses the real cost is marketing templates. Conversations the customer starts stay cheap.

QR-code bridges: cheap, until they aren’t

Libraries like Baileys speak the WhatsApp Web protocol. You scan a QR code once, and from then on your code chats from your number as if it were a phone. No Meta fees, no templates, no approval. Very tempting.

The catch: WhatsApp’s Terms of Service forbid bulk messaging, auto-messaging and accessing the service through automated or unauthorized means, and WhatsApp can disable or suspend accounts that break them. Baileys’ own README says the project isn’t affiliated with WhatsApp and that its authors discourage bulk or automated messaging.

I use this route only for narrow jobs. Autoreply, for example, sends a WhatsApp message a minute after you miss a call. It goes through a small server bridge linked to your own number with a QR or pairing code, and it only writes to the person who just called you. For a sales list, campaigns, or writing to hundreds of new people it is the wrong tool. Losing the number is the most expensive thing that can happen to a business that lives on WhatsApp.

Short version: if your business runs on WhatsApp, use the official API.

The technical side, for developers

On the Cloud API a bot is really a webhook. Meta POSTs incoming messages to your server, and you reply through the API. In my open source webhook, qiyaswba, it works like this:

  1. On GET /webhook/ it checks hub.verify_token and echoes hub.challenge. That is how Meta verifies the endpoint.
  2. On POST /webhook/ it computes an HMAC-SHA256 of the raw body with the app secret and compares it to the X-Hub-Signature-256 header. Mismatch, 403.
  3. The raw event goes into an immutable audit log first, then gets split into contacts and messages. Meta has no API to re-fetch old webhooks, so keeping the raw payload matters.
  4. Replays are deduplicated by wamid, so retries are safe.
  5. Even when processing fails it returns 200, otherwise Meta keeps redelivering the same event. Failed events can be reprocessed from the admin.

The signature check is this small:

import hashlib
import hmac

def is_from_meta(raw_body: bytes, signature_header: str, app_secret: str) -> bool:
    expected = "sha256=" + hmac.new(app_secret.encode(), raw_body, hashlib.sha256).hexdigest()
    return hmac.compare_digest(expected, signature_header or "")

Use compare_digest. A plain == leaks timing information that helps someone guess a valid signature.

Questions to answer before you build

  1. How many messages arrive a day, and how many of them are the same questions?
  2. Where will the bot read from: prices, stock, free slots?
  3. When a chat goes to a human, who picks it up and where do they see it?
  4. Will you message customers first, or only reply? (That changes both the price and the rules.)
  5. What happens if you lose the number?

If you have answers, a bot will pay for itself. If you don’t, fix the process first and add the bot later. I also wrote up the technical problems I run into most in businesses.

If you’re thinking about a WhatsApp or Telegram bot, here is what I build and how. Questions are welcome on the contact page.

Sources

related