Buyer's guideNo named competitors

How to choose a WhatsApp business tool

Six questions that matter more than the feature list any vendor hands you — plus the one constraint every tool built on Meta's Cloud API shares, whether its marketing page mentions it or not.

Start free trial Read the Wavy page

What this guide will not do

No named or characterised competitorNo invented statistic or ratingHonest where our own answer is a limit

Before you buy

This is not a scorecard, because a vendor-built scorecard always wins.

Every WhatsApp business tool on the market is built on the same Meta Cloud API, which means every one of them inherits the same rules and the same traps. A comparison table with checkmarks next to named competitors is easy to rig and is out of date the day a competitor ships something — so this page does not have one. What it has instead is six questions worth asking any vendor, including us, and an honest answer to each about how Automix's WhatsApp agent, Wavy, actually behaves today.

The questions below are not generic best-practice advice. Each one is a specific way a WhatsApp tool can look like it is working while quietly failing — a 'sent' receipt for a message the customer never saw, a campaign that reaches someone who never opted in, an analytics dashboard that reports a zero it cannot actually justify. If a vendor's answer to any of these is a shrug or a demo that conveniently avoids the question, that is the answer.

Ask what it refuses to do

A tool with no refusals has not thought about the edges of your business.

These are specific refusals in Automix's own code, named so you can ask the same question of anything else you evaluate.

It will not send a free-form reply once the service window has closed

Checked before a provider is ever touched, and refused with the approved-template alternative named in the same response — never a delivery reported that did not happen.

It will not launch a campaign around a contact with no consent record

Every recipient queued for a marketing send is checked against a category-matched consent record, and a contact with no record is treated as not consented — never assumed yes.

It will not let an internal staff note reach the customer

A note is stored as a different kind of row entirely — no direction, no provider id, no delivery status — so there is no code path from a note to a customer to accidentally leave open.

Evaluation criteria

6 questions to ask any vendor in this category.

Ask these of Automix and of anything else on your shortlist. The status pill is how the honest answer scores today, not a claim of perfection.

What happens when a message is sent outside the 24-hour service window?

Why it matters. Meta's Cloud API only guarantees delivery of a free-form reply within 24 hours of the customer's last message. Send a free-form reply after that window closes and the API still returns success — the request is accepted and then silently dropped. This is true of the platform itself, not any one vendor's implementation of it, so every WhatsApp tool has to decide what to do about it: check before sending, or trust the API's success response and pass the false 'sent' status straight to you.

How Automix answers it. Wavy computes the window from real message timestamps and checks it before a provider is ever called. A free-form reply outside the window is refused with a 409 that names the approved template you can send instead, rather than reporting a delivery that did not happen. This only applies to a connected cloud number — a QR-paired handset has no Meta window to enforce, because it is a phone.

Works today

Does a paused-and-resumed campaign re-check the same rules it started with?

Why it matters. A launch-time consent check is not worth much if pausing and resuming a campaign skips it the second time. Consent can be withdrawn while a campaign sits paused, and a tool that only checks once, at the original launch, will happily message someone who opted out an hour later.

How Automix answers it. Resuming a paused campaign re-runs every guard the original launch ran — permission, template gate, and the consent sweep — in that order, and rolls back entirely if nobody left in the audience still consents. The guard logic runs with no credential connected. Actually delivering the campaign needs a connected WhatsApp Business Account, which is the part still waiting on your setup.

Needs your setup

If an AI agent replies, does the customer know, and can a person take over instantly?

Why it matters. An AI agent answering as if it were a person is a disclosure problem and, in some contexts, a legal one. The question worth asking is mechanical, not aspirational: is there a code path where an AI session starts with no disclosure, and how long does a handoff to a human actually take once requested.

How Automix answers it. An AI agent session cannot be created without a disclosure the customer sees first. Handing off to a person is immediate and idempotent, and it marks the conversation operator-handled so the bot stops replying — calling handoff twice does not double-queue a person.

Works today

Which numbers on the analytics dashboard are the tool's own, and which are Meta's?

Why it matters. Sent, delivered and failed counts can be computed locally from your own send records. Whether a message was actually read, or a link inside it clicked, is data Meta holds — a tool with no connected account cannot know it, and the honest response is to say so, not to show a zero. A zero reads as 'nobody opened this,' which is a different claim from 'we cannot see whether anyone did.'

How Automix answers it. Sent, delivered, failed and pending counts are always real, counted from Wavy's own send records. Read and clicked figures stay null without a connected WhatsApp account — never a fabricated zero — because a zero would assert something Wavy cannot see. An hourly ingestion worker now exists to pull Meta's own read/click and cost figures into a snapshot table ahead of Meta's short retention window closing, but it needs two things most workspaces will not have out of the box: the connected channel's own cloud_access_token, and Meta's business_management/whatsapp_business_management permission on that token — a scope Embedded Signup does not request today, so getting it means a separate Meta App Review. Until both are in place, the worker records exactly why it skipped a workspace rather than writing a zero, and it has been tested only offline against a mocked Graph API response, never against a live account.

Needs your setup

Does the tool check a template against Meta's own rules before you submit it?

Why it matters. A template Meta rejects, or worse, approves and then flags as miscategorised, can cost a WhatsApp Business Account a utility restriction lasting a week or more — not something an owner can appeal quickly. A tool that lets you submit anything and waits for Meta's rejection to tell you is passing that risk straight to your account.

How Automix answers it. Category limits, button caps, and the header and media restrictions authentication templates carry are all checked before a submission leaves Wavy's server. Whether Meta actually approves a template it passed those checks on, and syncing that approval state back, needs a connected account — that decision is Meta's, not ours to assert.

Needs your setup

Can a permission be revoked and take effect immediately, with a record of who did what?

Why it matters. A role and permission system is decorative if the routes that should check it do not actually read from it. The failure mode is specific: a catalogue of permissions sits next to a set of route guards that quietly hard-code their own rules instead, so revoking a permission in the settings screen changes nothing about what that person can still do.

How Automix answers it. Route guards consult the same permission catalogue the settings screen edits, and every one of its sixteen permissions governs at least one route. A workspace can revoke a permission and the next request on that route reflects it immediately — there is no separate, unread copy of the rule. Campaign, template, assignment and integration changes are written to a queryable audit log; quieter workspace edits are not.

Works today

Where we do not measure up yet

In one place: which of the answers above is not a green light.

Pulled straight from the criteria above, not a separate list — a guide that scores itself full marks on every criterion is not one you should believe, ours included.

Does a paused-and-resumed campaign re-check the same rules it started with?

Resuming a paused campaign re-runs every guard the original launch ran — permission, template gate, and the consent sweep — in that order, and rolls back entirely if nobody left in the audience still consents. The guard logic runs with no credential connected. Actually delivering the campaign needs a connected WhatsApp Business Account, which is the part still waiting on your setup.

Needs your setup

Which numbers on the analytics dashboard are the tool's own, and which are Meta's?

Sent, delivered, failed and pending counts are always real, counted from Wavy's own send records. Read and clicked figures stay null without a connected WhatsApp account — never a fabricated zero — because a zero would assert something Wavy cannot see. An hourly ingestion worker now exists to pull Meta's own read/click and cost figures into a snapshot table ahead of Meta's short retention window closing, but it needs two things most workspaces will not have out of the box: the connected channel's own cloud_access_token, and Meta's business_management/whatsapp_business_management permission on that token — a scope Embedded Signup does not request today, so getting it means a separate Meta App Review. Until both are in place, the worker records exactly why it skipped a workspace rather than writing a zero, and it has been tested only offline against a mocked Graph API response, never against a live account.

Needs your setup

Does the tool check a template against Meta's own rules before you submit it?

Category limits, button caps, and the header and media restrictions authentication templates carry are all checked before a submission leaves Wavy's server. Whether Meta actually approves a template it passed those checks on, and syncing that approval state back, needs a connected account — that decision is Meta's, not ours to assert.

Needs your setup

Questions

Common questions.

Is the 24-hour window an Automix rule or a Meta rule?

It is Meta's own rule for the WhatsApp Cloud API, which applies to every tool built on it, not just Wavy. What differs between tools is whether they check it before sending or only display a countdown and let the API's misleading success response through.

If a vendor's demo doesn't mention the service window at all, what does that tell me?

Ask directly what happens to a free-form reply sent after the window closes. If the answer is vague, or the demo has never shown a refused send, you have not yet seen how that tool behaves in the one situation where the API itself will mislead you.

Can I see a real refusal happen, not just read about it?

Yes — connecting a WhatsApp number during onboarding and attempting a free-form reply after the window has closed on a real conversation will trigger the same 409 described above.

Does 'consent enforced' mean Automix guarantees compliance with Indian telecom or data law?

No. It means a specific, checkable thing: a campaign will not launch or resume against a contact with no matching consent record. Whether your own opt-in language and process meet a specific regulation is a question for your own compliance review, not something a product page can settle.

Why does the read/click data stay blank instead of showing something?

Because Meta's own read receipts and link-click data require a connected WhatsApp Business Account, and showing a zero when nothing is connected would claim 'nobody opened this' when the true state is 'we cannot see it yet.' Those are different facts, and only one of them is true with nothing connected.

What still needs my own setup before Wavy actually sends anything?

A connected WhatsApp Business Account. The window guard, the consent sweep, the template validator and the shared inbox all work against Wavy's own data before that — but turning a reply, a campaign or a reminder into a message that actually leaves the workspace needs a number.

Apply it

Apply these six questions to Wavy, and to anything else on your shortlist.

Connect a WhatsApp number during onboarding and see the window guard, the consent sweep and the role-based permissions run on real conversations — the same guardrails described above, not a demo environment built to look good.

Start free trial Read the Wavy page

Wavy's own status today:Available

More buyer's guides

Buyer's guide

What to look for in a CRM for a small sales team

The feature list on a CRM's homepage is never the reason a required field gets skipped six months in. Six questions about what actually holds under an import, a bulk edit, or a rushed Friday afternoon — plus Automix's own honest answers.

Read the guide

Buyer's guide

Choosing a social media scheduling tool

The word 'scheduled' hides more than it reveals. Six questions about approvals, invented engagement data, and what actually happens when a post's date arrives — with Automix's own honest answer, including the one place nothing actually publishes yet.

Read the guide

Buyer's guide

Choosing bookkeeping software you can hand to a CA

The books your accountant actually trusts are the ones where nothing can be quietly edited after the fact. Six questions about append-only entries, honest reconciliation, and what a tool should never claim to do on your behalf — with Automix's own answer to each.

Read the guide

How to choose a WhatsApp business tool

Six questions that matter more than the feature list any vendor hands you — plus the one constraint every tool built on Meta's Cloud API shares, whether its marketing page mentions it or not.

What this guide will not do

No named or characterised competitorNo invented statistic or ratingHonest where our own answer is a limit

How to choose a WhatsApp business tool

This is not a scorecard, because a vendor-built scorecard always wins.

A tool with no refusals has not thought about the edges of your business.

It will not send a free-form reply once the service window has closed

It will not launch a campaign around a contact with no consent record

It will not let an internal staff note reach the customer

6 questions to ask any vendor in this category.

What happens when a message is sent outside the 24-hour service window?

Does a paused-and-resumed campaign re-check the same rules it started with?

If an AI agent replies, does the customer know, and can a person take over instantly?

Which numbers on the analytics dashboard are the tool's own, and which are Meta's?

Does the tool check a template against Meta's own rules before you submit it?

Can a permission be revoked and take effect immediately, with a record of who did what?

In one place: which of the answers above is not a green light.

Does a paused-and-resumed campaign re-check the same rules it started with?

Which numbers on the analytics dashboard are the tool's own, and which are Meta's?

Does the tool check a template against Meta's own rules before you submit it?

Common questions.

Apply these six questions to Wavy, and to anything else on your shortlist.

Evaluate the rest of your stack.

What to look for in a CRM for a small sales team

Choosing a social media scheduling tool

Choosing bookkeeping software you can hand to a CA

How to choose a WhatsApp business tool

This is not a scorecard, because a vendor-built scorecard always wins.

A tool with no refusals has not thought about the edges of your business.

It will not send a free-form reply once the service window has closed

It will not launch a campaign around a contact with no consent record

It will not let an internal staff note reach the customer

6 questions to ask any vendor in this category.

What happens when a message is sent outside the 24-hour service window?

Does a paused-and-resumed campaign re-check the same rules it started with?

If an AI agent replies, does the customer know, and can a person take over instantly?

Which numbers on the analytics dashboard are the tool's own, and which are Meta's?

Does the tool check a template against Meta's own rules before you submit it?

Can a permission be revoked and take effect immediately, with a record of who did what?

In one place: which of the answers above is not a green light.

Does a paused-and-resumed campaign re-check the same rules it started with?

Which numbers on the analytics dashboard are the tool's own, and which are Meta's?

Does the tool check a template against Meta's own rules before you submit it?

Common questions.

Apply these six questions to Wavy, and to anything else on your shortlist.

Evaluate the rest of your stack.

What to look for in a CRM for a small sales team

Choosing a social media scheduling tool

Choosing bookkeeping software you can hand to a CA