WhatsApp Form
WhatsApp-native lead capture forms are planned — not available today.
A WhatsApp form would let you share a link or QR code that opens a structured data-collection flow inside WhatsApp, capturing fields like name, phone, and intent, then saving the submission as a contact in your Wavy workspace. This capability is planned. No form builder, no wa.me form link generator, and no in-chat structured-field collection flow has been built. Contacts can be created manually, imported via CSV, or synced from Airtable — but not through a WhatsApp-native form.
What does not exist
Removed from this page because it is not built.
These capabilities are waitlisted. They are not part of any live form offering.
- Form builder — There is no UI for defining form fields, validation rules, or success messages within a WhatsApp conversation. No form object exists in the data model.
- WhatsApp form link — There is no generator for a wa.me or deep link that opens a pre-structured form flow in WhatsApp. The standard wa.me link opens a blank chat, not a form.
- In-chat field collection — The rules engine can send a welcome message, but it does not collect structured fields (name, email, intent) in a multi-step flow. There is no form-state machine.
- Form-to-contact mapping — While contacts can be created from inbound messages, there is no mapping from form fields to contact attributes. A form submission does not become a structured contact record because the form does not exist.
What does exist
Contact creation paths that work today — and their limits.
Wavy can create contacts through three paths, but none is a WhatsApp-native form.
- Manual creation — The contacts API accepts a name, phone, source, lead stage, and attributes. This is a manual entry, not a form submission.
- CSV import — Contacts can be imported in bulk via CSV upload. The importer parses rows and creates contact records. This is a batch operation, not a real-time form.
- Airtable sync — Inbound contacts can be upserted to a server-configured Airtable base. This is a sync path, not a form. It also does not provide a per-workspace OAuth connection.
- Inbound message contact — When a new contact messages the business number, a contact record is created from the inbound webhook. This captures the phone number and conversation, but not structured form fields.
The intended path
What a WhatsApp form would look like when built.
If and when a WhatsApp form is built, the intended path would let you define a set of fields (name, phone, email, intent, custom attributes) in the workspace UI, generate a shareable link or QR code, and have the form guide a contact through a structured multi-step conversation in WhatsApp. Each field response would be captured, validated, and mapped to a contact record on submission.
The form would need a state machine to track which fields have been answered, a timeout and resume behaviour for abandoned submissions, and a mapping from form fields to contact attributes. It would also need to respect the opted_in flag and the channel's configured state. None of that work has been started. This page will be updated and the noindex directive removed when a form path reaches a configuration-dependent state.
Questions
WhatsApp forms — straight answers.
Can I create a WhatsApp lead capture form today?
No. There is no form builder, no form link generator, and no in-chat structured-field collection flow. Contacts can be created manually, via CSV, or from inbound messages — but not through a WhatsApp-native form.
Does the wa.me link work as a form?
A standard wa.me link opens a blank WhatsApp chat with your business number. It does not present a form, collect structured fields, or map responses to contact attributes. It is a deep link, not a form.
Can I collect contact information through the welcome message?
The built-in welcome rule sends a greeting, but the rules engine does not collect structured fields in a multi-step flow. There is no form-state machine to track which fields have been answered.
Will WhatsApp forms be added in the future?
It is a planned capability. When it reaches a configuration-dependent state — a form builder exists, generates a link, and maps submissions to contacts — this page will be updated and the noindex directive removed.
Can I use Airtable or Google Sheets as a form backend?
Airtable sync can upsert contacts to a server-configured base, but it is a sync path, not a form. Google Sheets sync is planned but not started. Neither provides a WhatsApp-native form experience.
Forms are planned, not shipped.
Explore Wavy's available contact management, campaigns, and automation capabilities today. When a WhatsApp-native form is built, this page will say so plainly.