The WhatsApp Business AI guide: rules first, automation second.

The three WhatsApp products, and which one you need

People say “WhatsApp Business” to mean three different things, and the difference determines whether automation is possible at all.

• The WhatsApp Business app: free, phone-based, fine for a sole trader. No API, so no AI agent and no proper multi-user inbox.
• The Cloud API, hosted by Meta: the standard route for businesses that want automation, multiple agents on one number, and templates at volume.
• A Business Solution Provider such as Twilio: the same platform reached through a provider that handles onboarding, billing and infrastructure on your behalf.

ChatnCall supports both the Meta Cloud API directly and Twilio as a provider, because the right choice usually depends on where your number and billing already live rather than on capability.

The 24-hour customer service window

This is the rule that shapes every WhatsApp deployment. When a customer messages you, a 24-hour window opens during which you can reply freely with whatever the conversation needs. That is where an AI agent does almost all of its work.

Once the window closes, free-form messages are refused. To restart a conversation you must send an approved template message, and a new window opens only if the customer replies. In practice the platform is designed around the customer starting the conversation, and any outbound strategy has to be built on templates.

Message templates and how approval works

A template is a pre-written message submitted to Meta for review, with placeholders for the variable parts — a name, a date, an order number. Approval is usually quick, and rejections are usually for the same reasons: the message is promotional but submitted as a utility, the placeholder structure is ambiguous, or the wording is vague enough that a reviewer cannot tell what the customer will actually receive.

The practical advice is to write templates like a receipt rather than an advert: concrete, specific, obviously tied to something the customer did. Appointment reminders, booking confirmations and order updates approve easily and are the messages customers actually want.

• Keep the promotional and utility categories honest — miscategorising is the fastest route to a rejection.
• Write one template per real use case rather than one clever template for everything.
• Include an obvious way to stop receiving messages, and honour it immediately.

Opt-in, quality rating and staying unrestricted

You need permission before messaging someone, collected anywhere the customer clearly understands they are opting into WhatsApp messages from your business — a website form, a checkout tick box, a reply to your own message. Keep the record of when and how it was given.

Meta then applies a quality rating to your number, driven largely by how recipients respond. Blocks and “report” taps push it down; replies and engagement hold it up. A number in poor standing has its messaging limits cut, which is a self-inflicted wound almost always caused by broadcasting to people who did not expect it.

The defensive rule is simple: send fewer, more relevant messages to people who asked for them. Broadcasts are a tool for confirmations and genuinely useful updates, not a mailing-list substitute.

Where AI fits — and where the team takes over

The natural split on WhatsApp is that AI handles the incoming volume inside the 24-hour window while humans handle the conversations that need judgement, from the same inbox.

That means an agent answering product, pricing, availability and status questions from your knowledge base within seconds of a message arriving, and a shared team inbox where a colleague can take over the same thread mid-conversation without the customer noticing a seam. Assignment, internal notes and a full history per contact are what make this workable for a team rather than an individual.

• AI: first response, routine questions, capturing details, booking, out-of-hours cover.
• Human: complaints, negotiation, anything sensitive, and any thread the agent flags as unresolved.
• Both: one thread, one history, no “as I explained to your colleague earlier”.

A sane rollout order

1. Connect the number

   Onboard through the Cloud API or your provider, verify the business, and confirm the display name customers will see.

2. Load the knowledge

   The same knowledge base that serves your phone line and web chat should serve WhatsApp — one source, three channels, no divergent answers.

3. Turn on inbound AI only

   Let the agent answer incoming messages for a couple of weeks with the team watching the inbox. No outbound anything yet.

4. Add the useful templates

   Booking confirmations and appointment reminders first. They are the ones customers welcome and reviewers approve.

5. Then consider broadcasts

   Only to a properly opted-in list, only when you have something specific to say, and always with a working opt-out.