Forms that live inside WhatsApp, with encrypted data exchange.
Author WhatsApp Flow JSON in a visual builder. Static and dynamic Flows, on version 7.1 by default with auto-upgrade for older versions, an RSA keypair plus AES-128-GCM data-exchange encryption per account, and a draft-to-publish-to-archive lifecycle.
A visual builder over the real WhatsApp Flow JSON schema, with no proprietary intermediate format.
Visual builder over the real schema
Author Flow JSON without writing JSON.
A visual builder sits over the WhatsApp Flow JSON schema, on version 7.1 by default. Save a draft, publish it, deprecate it when a new version ships, then archive it when retired. Older Flow JSON versions are auto-upgraded on save, so your library never goes stale.
- Visual builder over the real Flow JSON schema (v7.1 default)
- Lifecycle: draft, publish, deprecate, archive
- Auto-upgrade of older 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 account
RSA keypair and AES-128-GCM data exchange, managed for you.
Dynamic Flows need encrypted data exchange between WhatsApp and your backend. WBIZ generates an RSA keypair per account, uploads the public key for you, rotates keys on demand, and runs an encrypted data-exchange endpoint that decrypts incoming payloads with AES-128-GCM and signs the response.
- RSA keypair generated and stored per account
- AES-128-GCM data-exchange encryption and decryption
- Public-key upload and key rotation handled for you
- Encrypted data-exchange endpoint for dynamic Flows
Book a test drive
Step 2 of 3 · in-chat form
Full name
Preferred date
Showroom
Library and categories
A category-tagged library across every WBIZ surface.
Tag each Flow with a category (sign up, appointment booking, lead generation and so on) and reuse it from the inbox composer, automations, the Flow template button type, or the REST API.
- Create, edit and version each Flow
- Used by the inbox, automations, the Flow template button and the API
- 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 and more
0
RSA keypair per account, with rotation
0
AES-128-GCM data-exchange encryption
A real Flow toolchain on top of the real schema.
WBIZ does not hide the Flow JSON behind a proprietary format. It builds on top of it: a visual builder for authoring, encryption keys per account, a version lifecycle, auto-upgrade on save, and an encrypted data-exchange endpoint when you need dynamic screens. The Flow you author here is the Flow WhatsApp renders.
Native rendering
Flows render with the customer's own keyboard and date picker. WhatsApp handles the runtime.
Static and dynamic
Static Flows ship from JSON. Dynamic Flows hit your encrypted data-exchange endpoint per screen.
Encrypted endpoint
AES-128-GCM payload decryption and a signed response, handled by WBIZ for every dynamic Flow.
Key rotation
An RSA keypair per account. Rotate it, re-upload, and keep your dynamic Flows running.
Power any backend
Flows is the frontend. Wire it to your stack via webhooks and REST.
There are no prebuilt connectors. Connect WhatsApp Flows to whatever booking, inventory or backend system you run through the encrypted data-exchange endpoint and outbound webhooks.
Encrypted endpoint
AES-128-GCM data exchange
REST API
Send a Flow programmatically
Automations
Send a Flow from any trigger
Inbox composer
Send a Flow inline in any thread
Templates
The 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 it for you.
WBIZ generates an RSA keypair per account and uploads the public key for you. 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 such as name, email and custom fields, and the screens arrive prefilled.
WBIZ auto-upgrades older Flow JSON to the current default (7.1) on save, so your library does not stop working when the version pointer moves.
Two options. Use a final submit webhook, decrypted and verified by WBIZ, or wire the Flow into the lead-forms module so submissions land in the WBIZ submission list.