How it works

How a WhatsApp AI agent works

What happens in the two seconds between a customer pressing send and an answer appearing — and the four steps that get you from an empty inbox to an agent handling real conversations.

The short version

A WhatsApp AI agent works in four stages. Meta's WhatsApp Business Cloud API delivers each incoming message to the agent by webhook. The agent retrieves the passages of your own content that relate to the question. A language model writes an answer grounded in those passages and in the rules you set. If the answer requires an action — booking, ordering, saving a lead — the agent calls the connected tool, then replies with the result.

Start to finish, usually two to five seconds.

Anatomy

The four moving parts

You never touch most of this. It is worth understanding anyway, because each part explains one thing the agent can and cannot do.

1. The channel — WhatsApp Business Cloud API

Your number is registered with Meta's official API, which posts every incoming message to the agent as a webhook and accepts replies back. This is also what imposes WhatsApp's own rules: the 24-hour customer-service window, approved templates for messages you send first, and opt-in before you contact anyone. Those are Meta's rules, not the software's.

2. The knowledge — your own content

Your website, price list, FAQ, policies and opening hours are split into passages and indexed. When a question arrives, the agent retrieves only the handful of passages that relate to it and answers from those. This is why it knows your Saturday hours and why it does not know things you never wrote down.

3. The actions — your connected tools

A calendar, a product catalog, a payment provider, a CRM. The agent is told what each tool can do and is allowed to call it mid-conversation: read Thursday's free slots, check whether the double is in stock, create the checkout link, write the lead. This is the line between a bot that answers and an agent that finishes.

4. The safety net — handoff and the shared inbox

Every thread lands in an inbox your whole team can see. Rules decide what never reaches the agent at all — refunds, complaints, legal or medical questions, named VIP customers — and the agent itself escalates when it is unsure. A person taking over silences the agent in that thread automatically.

Message lifecycle

What happens when
a message arrives.

A customer writes "do you have anything free Saturday?" at 9:41 PM. Here is the whole sequence, in order.

  1. Meta delivers it

    WhatsApp posts the message, the sender and the thread history to the agent's webhook, typically within a second.

  2. Intent and language are read

    The agent works out that this is an availability question in English, and which service the customer means from what they said earlier.

  3. Your content is retrieved

    It pulls the passages covering opening hours, the service list and the booking policy — not your whole website, just what is relevant.

  4. The calendar is checked

    Because the question needs live data, the agent calls your calendar and gets the slots that are genuinely free on Saturday.

  5. An answer is written and sent

    Grounded in those passages and that data, in the customer's language, with quick-reply buttons for the two open times.

  6. The outcome is recorded

    When they pick a slot it is written to the calendar, the lead is saved with its source, and a reminder is scheduled. Your team sees all of it in the inbox.

Setup

Four steps to live

Most businesses do this in an afternoon. Nothing here needs a developer.

  1. Connect the number

    Sign in with Facebook, create or choose a WhatsApp Business account and link your number through Meta's embedded signup. If the number is in the WhatsApp Business app today, migrate it here and keep it. Expect ten minutes, including the verification code.

  2. Load what you already have written

    Point the agent at your website and let it read. Then add the things that live in a drawer rather than online: the current price list, the cancellation policy, the holiday hours, the answers your staff give on the phone.

  3. Turn on actions and draw the handoff line

    Connect the calendar, catalog or CRM you want it to use. Then decide what the agent must never handle alone, and what it should do when it is unsure. These two settings do more for quality than any amount of prompt tweaking.

  4. Ask it the hard questions, then switch it on

    Test the awkward ones — the price nobody can remember, the refund edge case, the thing a competitor does better. Correct what reads wrong. Then go live and read the first fifty real conversations.

What to prepare beforehand
  • A Facebook Business account, or an admin who can create one
  • The phone number you want to use, able to receive an SMS or call once
  • Your current price list — the real one, not last year's
  • Opening hours, including holidays and the exceptions
  • Your refund, cancellation and delivery policies in writing
  • The ten questions your team answers most often, and the right answers

A number can only live in one place

Once a number moves to the Cloud API it stops working in the WhatsApp Business app on a phone — conversations happen in the shared inbox instead. If your team is attached to the phone app, a common first move is to put the agent on a second number and point your website, ads and Google profile at it, then migrate the main number later.

Being honest about it

What it does badly

Every vendor page lists strengths. These are the four things worth knowing before you promise your team it will handle everything.

  • It only knows what you gave it. An agent trained on a thin website gives thin answers. Most disappointing deployments are a content problem wearing an AI costume.
  • It is the wrong tool for an angry customer. A complaint wants a person who can make an exception. Route those to a human on the first message, not the third.
  • It cannot promise what your business cannot deliver. If your calendar is not accurate, the agent will confidently book into a slot that is not free.
  • It needs reviewing. Read the conversations weekly for the first month. The questions it failed are a precise list of what your knowledge base is missing.
Common questions

About the mechanics

Does it need a phone that stays switched on?

No. The agent runs on Meta's servers and Categent's, not on a handset. Once your number is on the Cloud API, there is no phone to keep plugged in and no QR code to re-scan — which is exactly why unofficial “WhatsApp automation” tools built on the web client are fragile and risk a ban.

How fast does it actually reply?

Usually in two to five seconds — the time it takes to retrieve the right passage from your knowledge base, generate an answer and hand it back to WhatsApp. Customers see the familiar typing indicator while that happens.

What happens if two people message at once?

Nothing different. Each conversation is handled independently and in parallel, so a hundred simultaneous enquiries get the same reply speed as one. This is the part that is genuinely hard to staff for and trivial for an agent.

Can it work alongside my team rather than replacing them?

That is the normal setup. The agent takes the repetitive questions and the after-hours traffic; your team takes anything with judgement in it. You decide where the line falls, and you can move it any time from the handoff rules.

Set yours up this afternoon.

Connect your WhatsApp Business number, point the agent at your website, and have it answering tonight's messages. Free to start.

Free plan · live the same day · cancel whenever