Keyword auto-replies
A rule matches a keyword and sends your template. That's the whole mechanism — which is why it's completely local: no AI is involved and nothing leaves your machine. Rules are unlimited on every plan.
Fully local · no AIAnswer the questions you've already answered a hundred times — by keyword, entirely on your machine, or by what the customer actually meant. Every reply is held for a few seconds first, and typing cancels it.
7-day free trial · no credit card · works with your existing number
Most of your inbox is the same five questions. One kind of auto reply matches how they're worded; the other works out what was asked. They're built differently, and it matters where your data goes.
A rule matches a keyword and sends your template. That's the whole mechanism — which is why it's completely local: no AI is involved and nothing leaves your machine. Rules are unlimited on every plan.
Fully local · no AI“Do you have a minimum order?” and “what's the MOQ?” are the same question, and a keyword list will miss one of them. A semantic reply answers both — from the knowledge base you wrote in your own words: prices, policies, the FAQs you keep retyping. It answers from those facts; it doesn't invent them.
AI · opt-in · Professional & ExpertThis is the part that makes an auto reply survivable: nothing is sent the instant it matches.
When a reply is about to go out it's held first, with a countdown above your composer. You can see what's queued and how long you have — it isn't happening somewhere you can't watch.
Type in that chat, or send anything yourself, and the pending reply is dropped — you've taken over. You never have to race the automation for your own conversation.
There's no presence detection here, deliberately. No heuristic deciding whether you're at your desk — that kind of guess is wrong at exactly the wrong moment. You get a window you can always grab instead.
Save the reply as a template and point a keyword rule at it. For semantic replies, write the facts — prices, MOQ, lead times, policies — into your knowledge base as plain text.
Set the conditions a reply has to meet, the per-contact cooldown and the daily cap. AI stays off entirely until you switch it on.
When a reply matches, the countdown appears above your composer. Let it run and it sends; type and it's yours again. Everything happens in the WhatsApp Web you already use.
It buys you minutes at 2am. It doesn't buy you a business that answers itself, and we'd rather say so than sell you one.
And it shouldn't be sold as one. It covers the questions you've already answered a hundred times, at hours you're asleep. It doesn't replace you — anything it can't answer from your knowledge base should reach you rather than be improvised.
It isn't officially supported. That's real terms-of-service risk, and no tool — ours included — can remove it. The window and the cooldown keep the automation something you're steering; they aren't a promise about your account, and anyone offering you immunity is selling you a feeling.
AI is off until you turn it on. When it's on, the extension discloses what was sent and to which provider, and one request carries at most the 40 most recent messages or 24,000 characters of that chat. Wanova never stores your chat contents. Keyword rules send nothing at all.
An auto reply covers the answers you already know by heart. The conversations that decide a deal are still yours — which is why Wanova is a co-pilot first.
I can hold $4.80/unit at 500 pcs through Friday.
For the replies that actually matter, the co-pilot writes the draft and drops it in your composer. You edit it, you send it.
You always press sendIncoming messages are translated as they land, and you reply in your own language while Wanova sends theirs.
Opt-in · cachedThe ones no auto reply should touch: who's still waiting, who went quiet after a quote, what you promised and when.
Runs locallyOne 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.
Keyword rules run locally on every plan · See full pricing
Yes — keyword auto-replies are exactly that. A rule matches a keyword and sends your template, and it runs entirely on your machine: no AI, and nothing leaves it. Every plan includes them, and there's no cap on how many rules you create.
A keyword rule fires on the words you list. A semantic reply understands what was meant — “do you have a minimum order?” and “what's the MOQ?” get the same answer — and writes it from your own knowledge base rather than inventing it. Semantic replies are AI, opt-in, and available on Professional and Expert.
That's the grace window. Every auto reply is held for a few seconds first, with a countdown above your composer. Start typing in that chat, or send anything yourself, and the pending reply is cancelled — you've taken over.
No, and that's deliberate. Wanova does not try to detect whether you're present — there are no heuristics guessing whether you're at your desk. Instead every reply pauses in front of you and typing cancels it, so nothing has to guess right.
It answers from the knowledge base you wrote — your prices, policies and FAQs. It is not an unattended bot: anything it can't answer from what you gave it should reach you rather than be improvised. It buys you minutes at 2am; it doesn't replace you.
AI is off until you switch it on. When it's on, the extension discloses what was sent and to which provider, and a single request carries at most the 40 most recent messages or 24,000 characters of the current chat. Wanova never stores your chat contents.
Automating WhatsApp Web isn't officially supported, so it carries real terms-of-service risk that no tool can remove — ours included. The grace window, the per-contact cooldown and the daily cap exist so the automation stays something you're steering. They are not a promise about your account.
Try every feature free for 7 days. No credit card.
Start free trial