How to choose a WhatsApp automation platform

A checklist you can actually use

1–2. Official WhatsApp access and the team inbox

Start here because everything else depends on it. The WhatsApp Business Platform (often called "the API") is Meta's official channel for businesses to send and receive WhatsApp messages at scale through an approved provider. Some tools instead automate the consumer WhatsApp Business App with browser scripts or device farms — this violates WhatsApp's terms and risks the number being banned with no warning. Ask directly: "Do you connect through the official WhatsApp Business Platform, and who is the underlying Business Solution Provider?"

Once access is confirmed, look at what happens after a message arrives. A team inbox should show every conversation in one place, let you assign a thread to a person or team, leave internal notes invisible to the customer, and track whether something is open, waiting or resolved. If multiple agents work the same number, this is not optional — without it, messages get answered twice or not at all.

• →Is the WhatsApp Business Platform (API) connection official, or a workaround?
• →Can conversations be assigned, tagged and tracked by status?
• →Is there a clear queue view so nothing sits unanswered?

3. Templates, the 24-hour window, and automation depth

WhatsApp requires pre-approved message templates for business-initiated outbound messages outside an active conversation, and gives a 24-hour window of free-form replies once a customer messages you first. A platform should make managing template approval, categories and variables straightforward, and should clearly explain what happens to automation when that 24-hour window closes on a given thread.

Beyond templates, ask what "automation" actually means in the product: a linear decision-tree of button clicks, or something that can branch on what the customer actually says. This is the dividing line covered in more depth in our AI agent vs chatbot guide.

4. AI capabilities: assist vs. autonomous

Nearly every vendor now says "AI-powered." The useful question is what the AI is allowed to do without a human in the loop. Reply-assist AI drafts a suggested response that an agent reviews and sends — useful, but it doesn't reduce headcount on the qualifying work itself. An AI agent, by contrast, can ask qualifying questions, retrieve information from connected business systems, decide what to do next, and hand off to a human only when it should — not by default.

Ask for a live example of the AI handling an ambiguous, multi-turn conversation — not a scripted single-question demo. That is the fastest way to tell the two apart.

5. CRM integration: does it read, or does it write?

Many tools describe "CRM integration" when they mean a one-way webhook that posts a new-lead notification into a channel. Real integration goes both directions: creating and de-duplicating contacts, updating deal or lead fields based on what was learned in the conversation, logging the full transcript against the record, and creating follow-up tasks for a human. Confirm which CRMs have a genuine, tested connector — common ones include Zoho, HubSpot, Salesforce and Bitrix24 — versus which are "any CRM via API," which usually means you or a developer builds the mapping yourself.

If your leads currently arrive from property portals or ad platforms, also ask how those get connected — portal and social lead sources are typically wired in as connectable feeds rather than official integrations, and a platform should say so plainly rather than imply a certified partnership that doesn't exist.

6. Workflows, analytics and compliance

Look for configurable workflows — routing rules, qualification branches, escalation triggers — rather than a fixed script you cannot adjust. On analytics, ask what is actually measurable: response times, conversation volume by channel, qualification outcomes, and where conversations stall. On compliance, confirm how consent and opt-out are captured and respected, and where conversation data is stored and processed, since this affects data-protection obligations in your market.

7. Deployment: cloud or self-hosted

Cloud SaaS is the default for most teams and gets you running fastest. Some organizations — often in regulated industries or with strict data-residency requirements — need a self-hosted deployment where the platform runs inside infrastructure they control. Both are legitimate; the wrong choice is picking a vendor that only offers one when your governance requirements need the other.

8. Total implementation cost, not just the sticker price

The advertised platform fee is rarely the whole bill. WhatsApp conversation-based charges from Meta apply regardless of vendor. Integration work — connecting your specific CRM, mapping fields, building qualification logic for your business — takes implementation time, whether done by the vendor or your own team. Ongoing AI usage, support tiers and custom workflow requests can all be separate line items. Our cost-components guide breaks each of these down in detail so you can build an apples-to-apples estimate across vendors.