Good to know

WhatsApp Web must be open#

WAFlow runs inside WhatsApp Web. Scheduled items, broadcasts, bots, the AI assistant, webhooks and reminders only run while WhatsApp Web is open in Chrome.

How the screens behave#

• A screen you open from the top bar (Send Message, Chatbots, Kanban in WhatsApp and so on) closes when you click a conversation in WhatsApp's chat list, so that chat shows. The X in its corner and Esc close it too.
• While WhatsApp's picture, video or Status viewer is open, the WAFlow bar and the shortcut bar hide, so the viewer's own header (sender, time, buttons) is not covered. They return when it closes.
• The full-screen Kanban page needs WhatsApp Web open in another tab. Chats, labels and open chat go through that tab. Your boards, notes and reminders are shared between both.

AI and webhook calls#

AI and webhook calls go to sites you choose. Chrome asks your permission once per site.

WhatsApp can change#

WhatsApp Web is a third-party page. When WhatsApp updates it, part of WAFlow may need an update to follow. WAFlow uses a bundled open-source library (wa-js, Apache-2.0) to talk to WhatsApp Web, and that library may need updating too. If a tool stops working after a WhatsApp update, reload WhatsApp Web, and write to support if it does not come back.

Sending limits#

WhatsApp can restrict numbers that send many similar messages quickly. Keep delays natural and start small. See Safe sending.

What is not included#

These need a server, which WAFlow does not have:

• Cloud Connect 24/7: running bots without WhatsApp Web open.
• Multi-agent chat transfer: handing a chat between team members inside WAFlow.
• Number warm-up matching.
• An inbound webhook URL: WAFlow sends webhooks out, but does not receive them.
• Billing.

Without a license#

Without a valid license, nothing is sent, no bot answers and no timer runs. The shortcut bar and blur are off. Everything you saved stays, and comes back when a license is applied.