Forms that live inside WhatsApp — with RSA-encrypted data exchange.
Author static WhatsApp Flow JSON in a visual builder. Static and dynamic Flows, version 7.1 by default with auto-upgrade for deprecated versions, RSA keypair plus AES-128-GCM data-exchange encryption per WaAccount, and a CRUD-and-publish lifecycle (draft → publish → deprecate → archive).
Visual builder over Meta's real Flow JSON schema — no proprietary intermediate format.
Visual builder over Meta's schema
Author Flow JSON without writing JSON.
A visual builder over Meta's Flow JSON schema, version 7.1 by default. Save a draft, publish it, deprecate it when a new version ships, archive when retired. Old or deprecated Flow JSON versions are auto-upgraded on save so your library never goes stale.
- Visual builder over Meta's real Flow JSON schema (v7.1 default)
- Lifecycle: draft → publish → deprecate → archive
- Force-upgrade of deprecated Flow JSON versions on save
- Categories: SIGN_UP, SIGN_IN, APPOINTMENT_BOOKING, LEAD_GENERATION, CONTACT_US, CUSTOMER_SUPPORT, SURVEY, OTHER
Book a test drive
Step 2 of 3 · in-chat form
Full name
Preferred date
Showroom
Encryption keys per WaAccount
RSA keypair + AES-128-GCM data exchange — managed for you.
Dynamic Flows require encrypted data exchange between Meta and your backend. WBIZ generates an RSA keypair per WaAccount, uploads the public key to Meta, rotates keys on demand and exposes an encrypted data-exchange endpoint that decrypts incoming payloads with AES-128-GCM and signs the response.
- RSA keypair generated and stored per WaAccount
- AES-128-GCM data-exchange encryption / decryption
- Public-key upload to Meta + key rotation
- Encrypted data-exchange endpoint for dynamic Flows
Book a test drive
Step 2 of 3 · in-chat form
Full name
Preferred date
Showroom
Library + categories
A category-tagged library across every WBIZ surface.
Tag each Flow with a Meta category — SIGN_UP, APPOINTMENT_BOOKING, LEAD_GENERATION and so on — and reuse it from the Inbox composer (send_flow), Automations (send_flow action), the FLOW template button type, or the REST API.
- CRUD with versioning per Flow
- Used by Inbox, Automations, the FLOW template button and the API
- Lead-form-style submissions land back as a webhook
- Pre-fill screens from contact attributes
Flows library
6 activeAppointment booking
Date + slot picker
Product catalog browse
3-step buy in chat
Lead capture form
Name, email, source
NPS survey
0-10 + open feedback
By the numbers
What teams ship on WBIZ.
0.1
Default Flow JSON version (auto-upgrades)
0
Categories: SIGN_UP, BOOKING, SURVEY...
0
RSA keypair per WaAccount + rotation
0
AES-128-GCM data-exchange encryption
A real Flow toolchain on top of Meta's schema.
WBIZ doesn't hide Meta's Flow JSON behind a proprietary format — it builds on top of it. Visual builder for authoring, encryption keys per account, version lifecycle, force-upgrade on save and an encrypted data-exchange endpoint when you need dynamic screens. The Flow you author here is the Flow Meta sees.
Native rendering
Flows render with the user's OS keyboard and date picker — Meta handles the runtime.
Static + dynamic
Static Flows ship from JSON. Dynamic Flows hit your encrypted data-exchange endpoint per screen.
Encrypted endpoint
AES-128-GCM payload decryption and signed response — handled by WBIZ for every dynamic Flow.
Key rotation
RSA keypair per WaAccount. Rotate, re-upload to Meta and keep your dynamic Flows running.
Power any backend
Flows is the frontend. Wire it to your stack via webhooks + REST.
No prebuilt connectors — connect WhatsApp Flows to whatever booking, inventory or CRM system you run via the encrypted data-exchange endpoint and outbound webhooks.
Encrypted endpoint
AES-128-GCM data exchange
REST API
Send a Flow programmatically
Automations
send_flow action from any trigger
Inbox composer
Send a Flow inline in any thread
Templates
FLOW button type opens a Flow
Lead forms
Capture submissions back into WBIZ
FAQ
Flows, answered.
A Flow is a native multi-screen mini-app that renders inside WhatsApp itself. Customers tap, fill fields and submit without leaving the chat. WBIZ stores the underlying Flow JSON, builds a visual editor on top of it and publishes to Meta on your behalf.
WBIZ generates an RSA keypair per WaAccount and uploads the public key to Meta. Each dynamic data-exchange request is decrypted with AES-128-GCM and the response is signed in the same exchange. You can rotate keys on demand.
Yes — the initial Flow payload accepts data; map contact attributes (name, email, last order, custom fields) and the screens arrive prefilled.
WBIZ force-upgrades deprecated Flow JSON to the current default (7.1) on save, so your library doesn't stop working when Meta moves the version pointer.
Two options: a final submit webhook (decrypted, verified by WBIZ) or wire the Flow into the lead-forms module so submissions land in the WBIZ submission list.