Reaching out
Bulk broadcasts with variables and spintax, an audience built from groups, countries, contacts or a CSV, paced by a delay you set. Plus scheduled messages for the moment that actually matters.
Broadcasts, scheduling, keyword and AI replies, templates, export and outgoing webhooks — all running inside the WhatsApp Web you already use, on your own number. No API account, no approval queue, no per-message fee, and no server holding your chats.
7-day free trial · no credit card · works with your existing number
Not a flow builder with boxes and arrows. Just the handful of things you actually repeat every day.
Bulk broadcasts with variables and spintax, an audience built from groups, countries, contacts or a CSV, paced by a delay you set. Plus scheduled messages for the moment that actually matters.
Keyword rules that run entirely on your machine, or a semantic chatbot that understands what someone meant and answers from a knowledge base you wrote. Both pause before they send.
Templates for text, media, documents and contact cards — reused across broadcasts, replies and schedules. Plus export to get your list out as CSV, Excel or vCard.
Outgoing webhooks fire on the events that matter — a message or attachment arrives, someone joins or leaves a group, a location or a call comes in — so your CRM, sheet or n8n/Make flow hears about it. One outgoing endpoint, on Expert.
The reply assistant drafts from this customer's stage, your notes and what's already been said — and stops in your composer. Translation both ways for the ones you can't read.
The follow-up radar works out who's waiting on you and who went quiet after a quote — computed on your machine, no AI required. Professional and up.
Everything here is a consequence of one decision: it runs in your browser instead of on our servers. That buys you a lot, and it costs you these.
No server means nothing sends unless your machine is awake with WhatsApp Web open. A scheduled message that comes due while you're away goes out when you return — but only if it's under about 2 hours late. Past that it's marked missed, because a “good morning” landing at 3pm is worse than not landing.
Webhooks go out: Wanova tells your tools what happened in WhatsApp. It does not take inbound commands to send on your behalf. An extension that only lives while a tab is open is the wrong shape for server-triggered sending — if that's what you need, WhatsApp's official Cloud API is the honest answer, and we'd rather point you there than pretend.
Automating WhatsApp Web isn't something WhatsApp blesses, so there's real terms-of-service risk and no tool — ours included — removes it. Pacing and number validation reduce the odds; they don't buy immunity. Anyone selling you “ban-proof” is selling you a feeling.
The tempting version of this product sends things while you sleep and tells you about it later. We didn't build that, on purpose.
I can hold $4.80/unit at 500 pcs through Friday.
The reply assistant writes into your composer and stops. Anything with a price, a promise or a person's patience in it should have you in the loop, and the fastest way to lose a customer is a confident machine answering a question it didn't understand.
Nothing sends without youSemantic auto-replies can answer on their own — that's the point of them at 2am. But every reply waits a few seconds where you can see it, and typing in that chat cancels it. Wanova never tries to guess whether you're “available”; it just gives you a window you can always grab.
Grace window — typing cancels itOne price per account — not per person and not per number. Every plan covers several WhatsApp numbers and as many teammates as share them. The AI co-pilot starts on Professional.
Automation runs locally · AI is opt-in · See full pricing
No. Everything runs in your browser, so your machine has to be awake with WhatsApp Web open for anything to send. That's the trade: no server ever holds your chats, and the cost is that the laptop has to be on. If a scheduled message comes due while you're away, it sends when you return — but only if it's less than about 2 hours late; after that it's marked missed rather than arriving at the wrong moment.
No. Wanova automates the WhatsApp Web you already use, with your own number — there's no Business API account, no approval process, no per-message fee and no template pre-approval. The flip side is that it's not officially supported by WhatsApp, so it carries terms-of-service risk that no tool can remove. If you need guaranteed delivery at scale with WhatsApp's blessing, the official Cloud API is the honest answer.
No, and we'd rather say so plainly. Wanova pushes outgoing webhooks — it can tell your systems what happened in WhatsApp (a message arrived, someone joined a group, a call came in). It does not accept inbound commands to send on your behalf. A browser extension that only works while a tab is open is the wrong shape for server-triggered sending; the official Cloud API is the right one.
The reply assistant drafts into your composer and you press send. Semantic auto-replies are the one thing that can answer on their own — and even then the reply is held for a few seconds in plain sight, and typing in that chat cancels it.
There's real risk and no tool removes it — automating WhatsApp Web isn't something WhatsApp officially supports. Pacing and number validation are risk controls, not ban protection. What actually keeps risk low is who you message: people who expect to hear from you, at a volume a person could plausibly send.
No. Everything works on a personal number — Wanova runs inside the WhatsApp Web you already use, and nothing here needs a WhatsApp Business account.
Try every feature free for 7 days. No credit card.
Start free trial