Form Widget

The Form widget lets you build lead capture and contact forms with flexible fields and submission actions.

Add a Form widget

Form Builder tabs

Fields

• Search and browse field categories.
• Drag fields into the preview to add them.
• Drag existing fields to reorder.
• Select a field to edit its label, placeholder, required state, options, and mapping.
• Checkbox groups show their field heading, including the required marker when applicable, on published forms as they do in the builder preview.
• Custom fields refresh their saved type and option list when their definition changes in Fields; republish the page to make refreshed field structure live.
• Phone fields show a compact country and calling-code picker on published forms. Visitors can search by country name, country code, or calling code, and valid numbers are saved in international form. Validation uses the field's country or the website's default country consistently, and an optional phone field left blank does not block the rest of the submission.

Design

• Identity: Form Name,Form ID , show/hide the title.
• Styles: Form Style, Button Style, Submit Button Text, and Button Alignment.

Submission

• After submission: show a message, redirect to a link, or register the contact for a published event.
• Success Message or Send to page after submission.
• Email Notification: enable it, set Recipient Email and Email Subject.
• Email subscription: subscribe or resubscribe contacts after submission, show an optional unchecked signup checkbox with your own message, or preserve each contact's current subscription state.
• Require Terms Agreement: add a required checkbox above the submit button, customize the agreement and link text, and choose an optional terms link.
• Tags & Lists applied after submit.
• Source Identifier for tracking.

Choose email subscription behavior

Keep Email subscription on when submitting the form should subscribe a new contact or resubscribe someone who previously unsubscribed. Contacts recorded as bounced or complained remain suppressed.

Turn the main switch off when submission alone should not change subscription status. You can then show an optional email signup checkbox. The checkbox starts unchecked, and only visitors who select it are subscribed or resubscribed. If you leave the optional checkbox off, each contact keeps their current subscription state.

Customize the checkbox message so visitors understand what they are requesting. Publish and submit each path with test contacts before connecting the form to a campaign or marketing Flow.

Register form contacts for an event

Choose Register for an event under

After submission when the form itself should reserve a place for the contact.

1. Select one published event from the website.
2. Confirm the form includes a usable name and email mapping.
3. Publish the page and submit a private test entry.

After a successful submission, Hiveality stores the form response, registers the contact, sends the event's applicable confirmation, and opens the event page with the visitor already recognized. For an ended webinar with a gated replay, the same path can unlock playback after signup. If the saved event is later unpublished, the Form Builder flags it so you can choose another event.

An event-registration problem does not discard the form response. Review the event's publication, guest-registration, capacity, and replay settings if a test contact submits successfully but is not registered.

Collect SMS permission

SMS controls stay hidden on forms that do not contain a phone field and do not already have SMS consent configured. When a form has a phone field, use the compact SMS opt-in row under Tags & Lists to collect permission for a specific texting program.

1. If needed, choose Set up and create the website-wide public sender, program, and exact disclosure. You can also manage these under Website Settings → SMS Messaging.
2. Choose Add SMS opt-in fields. Hiveality adds or connects a phone field and a plain consent checkbox to the selected sender and program.
3. Decide whether consent is optional or required for this form. Leave it optional for a broader form unless the form exists specifically for SMS enrollment.
4. Review the disclosure, publish the page, and submit a test entry before using the permission in a Flow.

The website setup is reusable; it does not need to be recreated for every form. Changing to a newer disclosure version updates the form checkbox for future submissions without rewriting earlier consent evidence. If the connected phone or checkbox field is later changed, use Repair fields before publishing so the form can record permission correctly.

When the same Form ID appears on more than one published page, popup, header, or footer, Hiveality checks that the shared field and SMS permission setup still agrees before publishing. If a visitor submits an older open copy after the permission fields or disclosure changed, the form asks them to refresh instead of silently dropping a checked permission choice.

Published forms also include quiet spam checks. Hiveality evaluates timing, browser interaction, hidden-field activity, and SMS gateway email addresses before saving a submission. A single browser signal may be treated as advisory to avoid blocking autofill, while higher-confidence combinations are rejected. If a current browser submission cannot be verified, the visitor is asked to refresh and enter the details again instead of seeing a false success message.

When terms agreement is required, visitors must check the agreement box before submitting. The submitted record keeps the accepted text, link, and timestamp so your team can review what the visitor agreed to later.

Form IDs and copied forms

The Form ID connects a form to its submissions, automations, and reporting.

• Keep the same Form ID when copied forms should share one submission stream.
• Create a unique Form ID when a copied form should collect its own submissions or uses different fields.
• A new Form dragged from the widget picker starts with its own Form ID, even when another form has the same name.
• Changing the form name does not change the Form ID automatically, which helps keep reporting stable across page edits.
• If Hiveality detects the same Form ID in multiple places, the Form Builder explains whether those forms are linked or should be separated.

When a shared form's fields and settings have not changed, you can republish its page without replacing that form's existing submission connection.

Ask AI

Use Ask AI from the Form toolbar or Form Builder when you want a faster starting point or cleaner field labels.

• Improve labels: rewrite field labels for friendlier clarity.
• Add placeholders: add helpful placeholder text where it improves the form.
• Add field: add one useful field that matches the existing form.
• Custom prompt: ask AI to rewrite labels, add placeholders, add or remove fields, or adjust options.

AI form edits keep required field shape intact and try to preserve contact-field mappings where possible. Review field types, required settings, mappings, and submission behavior before publishing a form generated or edited with AI.

Connected assistant and API updates

Approved assistants and API-key workflows can read a form's complete saved fields and submission settings, including email notifications, tags, lists, redirects, and email subscription behavior. They can set whether future submissions subscribe the contact, show an optional unchecked signup box, or preserve the contact's current subscription state.

Form reads also report the latest known notification outcome from recent submissions. A recipient update warns when its domain cannot receive mail; confirmed delivery, bounce, complaint, suppression, and failed-attempt results remain available for follow-up after messages are sent.

A focused field or settings change keeps the rest of the form setup intact and updates linked page or popup copies. If the form changed after it was read, or if a requested edit would break a connected SMS permission field, Hiveality stops the change so the current setup can be refreshed and reviewed.

Toolbar actions

• Form Builder
• Alignment
• Animation
• Copy
• Delete

Quiz and form follow-up

• Use Quiz Widget and Quizzes when you need quiz-type experiences.
• Review submissions in Forms.
• Use Flow Triggers with Form Submitted to route follow-up automation.