Skip to documentation content
Book a demo Start free trial
Start free trial
Polski
3 min read Reviewed August 20, 2026

Create and manage lead forms

Build reusable visitor forms for Chat Flows and Contact Options, manage their status, and protect active dependencies.

On this page
  1. Create a form
  2. Manage forms
  3. Design for completion
  4. Test the saved form

When a visitor is ready for follow-up, a well-designed form should make the next step clear without asking for more information than the team needs. Lead Forms let you prepare that experience once and reuse it in Chat Flows and Contact Options.

Each form has an internal name for your team, visitor-facing copy and styling, a set of fields, and optional consent checkboxes. This guide covers the form itself; the flow or Contact Option decides when the visitor sees it.

In this article, you'll learn:

Create a form#

Start with the follow-up your team intends to provide. That outcome tells you which fields are necessary and what the visitor-facing message should promise.

  1. Open Automations > Lead Forms.
  2. Select Add lead form.
  3. Enter a unique internal lead form name.
  4. Under Appearance, set Form title, Custom message, Button text, Button color, and the text alignment.
  5. Add at least one field and mark each as required or optional.
  6. Add any reviewed consent checkboxes and links.
  7. Check the chat preview.
  8. Select Save lead form.

The chat preview updates as you work, allowing you to compare copy, fields, consent, and button styling before saving. Active forms can be selected by Capture lead blocks and compatible Contact Options.

Manage forms#

Use the All, Active, Paused, and Draft tabs to find forms by status. Search by the internal name, open a form to edit it, change its status, or delete a form that is no longer required.

Before pausing or deleting a form, review where it is used. A form can look independent in the list while still supporting a visitor path elsewhere.

Zeltino protects forms referenced by enabled Contact Options. Select a compatible replacement in Contact Options before changing or removing the current form.

Design for completion#

Ask for the minimum information needed for the promised next step. Use a short title, explain why the details are needed, and make only essential fields required. A visitor who understands the purpose of the form is more likely to know what information belongs in it.

The completion message belongs to the surrounding Contact Option or flow journey, so test the complete visitor path rather than reviewing the form preview alone.

Test the saved form#

Open the installed widget and complete the form as a visitor. Test valid and invalid values, required and optional fields, consent, and the submission result.

Then open the resulting lead and confirm it contains the expected labels and values. If a later flow action creates a ticket, confirm that every route into that action captures email first.

For field and consent options, see Configure lead form fields and consent. For dependency rules, see Understand automation dependencies.