Skip to main content

Forms

A form collects answers from people who are not in a conversation yet — a contact request, a demo booking, a job application. You design the fields, and each submission is stored, can become a contact, can be written into a table, and can set off intake rules.

Open Forms from the left sidebar.

Building it​

Each field has a label, a key and a type. As with table columns, the key is the storage name and cannot be changed later.

A form stays a draft until you publish it. Only a published form can be opened or submitted, so you can build in peace.

Where the answers go​

Every submission is always kept on the form's Submissions tab, whatever else happens to it. That list is the record; everything below is in addition to it.

Into a table​

Choose a table and each submission appends a row. Because a form's field keys and a table's column keys are two lists you wrote at different times, the Settings tab shows every field next to where it lands and lets you point them at each other.

Each field is on one of three settings:

  • Auto — goes to a column of the same name. This is why an obvious form needs no setting up at all.
  • A named column — goes there, whatever the field is called.
  • Don't send — deliberately left out of the table.
"Goes nowhere"

A field on Auto with no column of that name never reaches the table. The builder marks it in amber while you are looking at it, so you can point it somewhere or rename the field. The answer is still kept on the submission, so nothing is lost while you sort it out.

Onto a person​

Tick Create or update a Contact and the submission becomes a lead. Say which field carries the e-mail, name, surname and phone, and the rest of the answers can be mapped onto your own contact fields — a company, a sector, a budget — using the same three settings as above.

Two rules protect what you already know:

  • People are matched by e-mail. A submission with a new e-mail address makes a new contact.
  • A later submission fills blanks only. It never overwrites a name, phone or custom field that somebody has already filled in.

If your workspace has a default stage, new contacts land in it.

Sharing it​

The Share tab offers three ways to use a published form.

A link. Send it, print it as a QR code, put it in an e-mail signature.

You can pre-fill answers you already know by adding them to the link: …[email protected]. Two fields deliberately refuse to be pre-filled this way — the spam trap and the consent box — because a link that filled them would mark visitors as spam, or claim a consent nobody gave.

An embed. A few lines of script that place the form on your page. It sizes itself to the form as it is filled in, so nothing is clipped and no gap is left underneath.

Your own form. If you already have a form on your website, keep it. The snippet posts what it collects to this form instead, using your existing design and your existing thank-you page. The field names to use are listed underneath.

From your website's server. To keep where each visitor came from (the ad, the campaign) with the submission, connect your website and let your server send the form with a server key — see Connect your website. Such submissions show Website (server) as their source, and can be answered with Message on WhatsApp or Call (Follow up on a lead).

Keeping bots out​

A hidden trap field. Add a field, then choose it under Spam protection. ConnectWiz keeps it out of sight of people — off-screen, unfocusable, hidden from screen readers — while a robot filling in the page still walks into it. A submission that fills it is filed as spam and goes no further.

A bot check. Turn on Ask visitors to pass a bot check and a Cloudflare challenge appears above the submit button. It only works where your workspace has bot-check keys set (Settings → Widget → Bot check); if it does not, the form builder tells you so on the spot rather than letting the tick imply a protection that is not there.

Turn on the consent box and write the sentence beside it. When somebody ticks it, ConnectWiz records the consent together with the sentence they were shown, the page they were on, their IP address and their browser — the things a regulator asks for, rather than a note that says somebody agreed to something somewhere. See contacts for where consent is then visible.

Telling your team​

Under Notifications, list the addresses that should get every submission of this form. For "only tell somebody when the answers look like X", use an intake rule instead.

What a form is for​

Every form has a purpose — contact request, survey, appointment request, reservation, consent, health history (anamnesis), registration / application, feedback, or other. The purpose sets a sensible starting point (a consent or health-history form starts private, see below) and groups your forms; it never switches on a hidden mode.

New form → Start from lists ready-made forms by sector — clinic, dental, aesthetics, beauty, restaurant, hotel, education, recruitment, general. Each one creates an ordinary draft you can edit freely: an NPS or satisfaction survey, an appointment or reservation request, a registration or job application, a treatment or photo consent, a health history, a KVKK explicit consent. The legal texts are generic starting points and say so — adapt them to your own practice before you publish.

Besides the usual field types a form can ask for multiple choice, a star rating, an NPS score (0–10), a date and time, an appointment time (free times come from a service's diary when booking is on; the person picks one and you confirm it) and a heading with explanatory text.

Who can open it​

  • Anyone with the link — the shareable link and the embed work for everyone.
  • Only through a personal link or the kiosk — for forms about one known person. Nobody can fill a consent in somebody else's name from a public link.

Sending a form to someone​

Use Send form in a conversation (the clipboard button in the composer, on the panel and in the mobile app) or on the person's Forms tab. Pick a published form and ConnectWiz sends them a personal link:

  • It is for that person only. Answers through it are filed on their record — even if they type a different e-mail address, no second contact is created.
  • What you already know (name, e-mail, phone, mapped contact fields) is filled in for them. Sensitive (health) fields are never pre-filled.
  • It expires (1 day to 30 days, 3 days by default) and works once.

Each sent form shows its status: Sent → Opened → Completed, or Expired. Resend sends a new link (the old one stops working) with a fresh deadline; Withdraw link closes it.

WhatsApp's 24-hour window

WhatsApp accepts a free-text link only within 24 hours of the customer's last message. After that the dialog asks you to pick an approved template and places the link in it ({{form_link}} for the whole link, {{form_path}} for a button whose base address is part of the template). On the phone you can open the templates or share the link another way. You can always only create the link and send it however you like.

A flow's Form step sends the same personal link when it knows who it is talking to, and the flow trigger Form submitted fires for every answer. Reminders (for example a consent before an appointment) use the same sending.

Turn on Signing (consent) in a form's settings and write the text being signed and its statements. The person then:

  1. reads the text,
  2. ticks each statement on its own — optional statements (photos in marketing, being contacted) can be left unticked,
  3. types their full name,
  4. signs in a box with a finger, pen or mouse.

What is kept is evidence, not a tick: the exact text and version they were shown, every statement with its answer, the typed name, the signature, the time, their IP address and device, and a fingerprint (SHA-256) of the content.

  • A signed record cannot be changed — not from the panel, not by the database itself. Deleting the form is refused while it has signed answers; unpublish it instead.
  • Changing the text starts a new version. A page opened on the old text cannot be signed; the person is asked to reload.
  • A PDF of the signed form is filed in the person's files under Consent forms, always in a sensitive folder (only members allowed to see sensitive files open it there), and can be downloaded from the answer.
  • Withdrawal is recorded on top: what was signed stays as signed, and the withdrawal is added with who recorded it, when and why.

Sensitive answers​

Mark a field Sensitive (health) answer (a health-history template does this for you). Its answers are stored encrypted and apart from the others, and are shown only to members with See sensitive answers. They are never copied to contact fields, tables, webhooks, rules or flows. Everyone else sees that a sensitive answer exists, not what it says.

When a contact is deleted, their form answers go with them; when two contacts are merged, the answers move to the one that stays. Export on the Forms tab gives a person's answers as data (sensitive ones only for members allowed to see them).

Front-desk kiosk and QR code​

On the Share tab:

  • QR code of the link — for posters, counters and tables.
  • Front-desk kiosk — a separate link for a tablet at reception. It opens private forms too, finds the person by phone or e-mail (or adds them), and clears itself for the next person. New kiosk link replaces it; Switch off closes it.

Results​

The Results tab counts the answers and where they came from (website, personal link, kiosk, flow), the personal links still open, and per question the tallies, the average rating and the NPS (promoters 9–10 minus detractors 0–6).

Forms on the contact card​

A person's Forms tab (on the contact page and in the mobile app) and the Forms block of the conversation's contact panel list what they were sent, with its status, and every answer they gave — open one to see it as they saw it.

Who can use this​

  • Manage forms — build forms, see their submissions and results, record a withdrawal. Not a default for any role but admin.
  • See forms on a contact — the Forms tab and block. An agent default.
  • Send forms — the Send form button. An agent default.
  • See sensitive answers — health answers, signatures and the signed PDF. Only admins by default.

Sending forms, the kiosk and signed forms are part of the Forms sent to contacts feature of your plan. Submitting a form needs nothing at all — that is the point.