Native rendering
Flows render with the customer's own keyboard and date picker. WhatsApp handles the runtime.
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 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.
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 endpoint that decrypts incoming payloads with AES-128-GCM and signs the response.
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.
WBIZ does not hide the Flow JSON behind a proprietary format. The Flow you author here is the Flow WhatsApp renders, with a visual builder, encryption keys per account, a version lifecycle and an encrypted endpoint when you need dynamic screens.
Flows render with the customer's own keyboard and date picker. WhatsApp handles the runtime.
AES-128-GCM payload decryption and a signed response, handled by WBIZ for every dynamic Flow.
An RSA keypair per account. Rotate it, re-upload, and keep your dynamic Flows running.
Capture Flow submissions back into WBIZ.
Learn moreSend a Flow from any trigger.
Learn moreThe Flow button type opens a Flow inline.
Learn moreAuthor the real Flow JSON visually, with encryption keys handled for you.
Set up a free workspace in minutes, see the plans, or talk to the team about your setup.