Questions, answered straight

No. ChatWise works with the WhatsApp number you already use for your business. Your customers keep messaging the number they know.

No. Every agent is already written. You answer a handful of plain questions about your business — your hours, what you sell, your policies — and the tone you want, and that is the whole setup.

On the QR connection, minutes: pick your agent, answer the questions, scan a QR code with your phone. The Business API route takes longer because Meta has its own application and business-verification process to go through first.

No — one agent per account, deliberately. It means there is never a question about which agent replied to a customer or which one to correct. A business that genuinely needs two runs two accounts.

Yes, but it replaces your current setup rather than sitting alongside it — you will go back through setup for the new one. There is no way to end up running two agents, or a QR connection and the API, at the same time.

It says so and passes the conversation to you, rather than guessing. Agents only answer from the knowledge base and business details you gave them — they are not permitted to invent hours, prices or policies.

Yes. Any chat in your inbox can be taken over mid-thread — the agent pauses, you type, and you hand it back when you're done.

A background agent that reads along with every conversation and keeps your contact records current, whichever agent is doing the talking. It isn't one of the nine you choose from and it doesn't count against the one-agent rule. If you edit a lead by hand, it won't overwrite what you wrote.

Both need a paid plan; what differs is who else bills you. The QR connection works the way WhatsApp Web does: you scan a code, your phone stays linked, it's instant, and your monthly plan is the whole bill — but it is an unofficial route. The Business API is Meta's official channel, more reliable and built for volume, but you have to apply for it and Meta charges you per conversation on top of your plan, at their own rates.

On the QR connection, yes — that risk is real, and we would rather you hear it from us. Messaging people who never asked to hear from you, or messaging too often, is what puts a number at risk. That is why QR bulk sends are capped at 25 people at a time and spaced out, and why we show a warning before the first one. If you need to reach large lists, the Business API is the safe route.

Your dashboard shows the true state of the connection in plain words — connected, reconnecting, or disconnected and needing you — rather than quietly failing. It reconnects on its own where it can, and tells you when it can't.

On the QR connection, 25 at a time, sent with a gap between each rather than all at once. On the Business API, much larger lists, using templates Meta has approved. The 25 limit is enforced by the system itself, not just discouraged.

They are recorded as opted out and excluded from every future send automatically, on both connections. Outgoing bulk messages also carry a line telling people how to opt out.

No. Each customer's data is separate, and on the QR connection each WhatsApp session runs in its own isolated process — so another customer's session dropping, or their number being banned, cannot reach your account or your chats.

Encrypted, and only ever used by the server. API tokens and session data are never sent to your browser, and they never appear in the app's code.