Where ZappBot listens, where it sends each lead, and how it connects to your own tools. Everything here is what the code does today; plan names are read from the service's own data.
Your website: a chat widget you add with one script line. Plans: all.
WhatsApp, Zalo OA and Facebook Messenger: the same rules and the same facts as the website bot. Plans: Growth and Pro.
E-mail: a message forwarded to your inbound address becomes a lead, quoted replies and signatures cut. You can answer a lead that came by e-mail from the dashboard.
Your own Zalo bot chat. Plans: all.
E-mail alert. Plans: Growth and Pro.
WhatsApp alert. Plans: Pro.
Lead webhook, a signed POST to your own address. Plans: Growth and Pro. See the API and webhooks page for the body, signature, retries and duplicate key.
Google Sheets: a ready Apps Script adds one row per lead (time, name of the business, kind, contact, summary, lead id) and ignores a repeated alert. The ZappBot operator sets the webhook up for you on request.
CSV: download your leads from the dashboard.
Inbound lead API: add a lead from your own form or tool. There is no other API: you cannot read chats or change settings from outside.
Bank transfer with a VietQR code and automatic matching, and a deposit QR for a confirmed stay.
Appointments: the visitor gets an add-to-calendar file for the request. The event says "requested": the bot never confirms a booking, your team does.