What WhatsEngage does

Everything below is in the product today, on every plan. Where something is deliberately not built, it is not listed here.

Campaigns

Send to a segment, schedule it, and know what it will cost before it goes.

Saved audiences — a stored filter, not a frozen contact list, so it re-resolves at send time and somebody who opted out yesterday is not messaged today.
Scheduling up to months ahead. A scheduled campaign re-checks consent, the frequency cap and your balance when it fires, not when you set it.
Retargeting on what actually happened: everyone who read but did not reply, or who never received it.
A pre-flight that names every excluded contact by reason — opted out, frequency-capped, no usable number — instead of quietly sending to fewer people than you expected.
Click tracking per recipient, on links inside the message. Meta never reports a click, so this is the only place one comes from.
Automatic pause if Meta re-categorises your template into Marketing mid-campaign — the same message then costs about seven times more and carries different consent rules.

Your whole team on one WhatsApp number, without stepping on each other.

A live countdown of the 24-hour service window, so nobody drafts a free-form reply WhatsApp will refuse. When it closes the composer switches to templates on its own.
Assignment, presence and unread counts across the team.
Quick replies, reactions, media, and the full conversation history per contact.
Notes and a consent trail on every contact, so the next agent sees why the last one stopped.

Two different tools, because they solve two different problems.

Automations are trigger-and-step: something happens, a sequence runs. Delays survive a restart — the steps are queued in the database, not held in memory.
Flows are a visual graph with per-contact state: ask, wait for the answer, branch. Delay and timeout nodes, so a customer who goes quiet mid-flow is handled rather than left open forever.
Both are consent-guarded and window-gated on every send, including steps that fire days later.

Included on every plan — not an add-on.

Retrieval over your own documents, so answers come from your material rather than a general model’s guess.
Bring your own provider key. Your usage and cost are yours, logged per conversation.
Hands off to a human on request, on low confidence, or when an agent is already in the thread.
A per-conversation cap and an account rate limit, so a loop cannot run up a bill overnight.

Build, submit, sync — and send one-time passwords properly.

All three OTP button types: copy-code, one-tap and zero-tap.
A per-template delivery window, so a code that arrives too late to be useful is not sent at all.
Meta owns authentication copy — we submit the flags it expects rather than body text it will reject, and keep a local preview so the picker still shows something readable.
Category, status and quality synced back from Meta, with the messaging tier and remaining quota visible before you launch.

The part that decides whether your number survives.

STOP and START work in every account, always. You can add your own keywords and replies; you cannot switch the built-in ones off.
Opted-out contacts are hard-filtered on every campaign path and guarded on every bot send. It fails closed.
A frequency cap per contact, and a warm-up ramp that respects Meta’s messaging tier rather than guessing it.
Quality Guard pauses marketing on a quality drop — and only marketing. An OTP held back to protect a metric breaks the product for the person waiting on it.

The reason this product exists in the shape it does.

Money is held when a message is sent and taken only when WhatsApp confirms delivery. A failure releases it.
What Meta says it billed is recorded on every status callback and reported beside what we charged, per message, with the drift.
Three currencies, never converted. A rate we can only find in another currency is reported, not exchanged.
An unpriceable country is reported, never counted as free.

One login, as many projects as you run.

A project is one WhatsApp number with its own contacts, campaigns and team. Switch between them from the header.
Roles from viewer to owner, with invitations and ownership transfer.
Per-plan limits on seats, tags, custom fields and audiences — enforced in the database, so they hold however the row was written.

For everything that should not be done by hand.

A public API over contacts, conversations, messages, broadcasts and webhooks, under scoped keys.
Send and verify one-time passwords through two endpoints.
Outbound webhooks with signed payloads, retries and an auto-disable after repeated failures — so a dead endpoint of yours does not silently swallow events.
CSV exports for campaigns, a daily overview, the consent trail, team activity and the billing reconciliation.

The AI assistant and the flow builder are included, not sold separately. Plans differ on limits and speed.