Configure lead fields and consent

Every extra required field gives the visitor another decision to make before submitting a form. The best field set is therefore not the largest one—it is the smallest set that supports the follow-up you promised.

Zeltino gives you standard contact fields, a small number of custom fields, and configurable consent checkboxes. This guide explains how to choose them and how Contact Option dependencies can protect required Email or Phone fields.

In this article, you'll learn:

• Which standard and custom fields are available
• Which fields Callback and Inquiry require
• How to add consent text and policy links
• How to test validation and submitted data

Add fields#

Begin with the standard visitor fields: Name, Surname, Email, and Phone. A form can also include up to three custom fields with these types:

• Text
• Long text
• Email
• Phone
• Number
• URL

1. In the form editor, select Add field.
2. Choose the field and enter a clear label.
3. Set it to Required or Optional.
4. Remove fields that do not affect the follow-up.

A form needs at least one field. Use the appropriate Email or Phone type when the value must be validated and used by later automation steps. Use a clear visitor-facing label for every custom field so the resulting lead remains understandable to the team.

Meet Contact Option requirements#

Callback and Inquiry use the selected form as part of their readiness check. Their required contact method must be both present and required:

• An enabled callback option requires an active selected form with a required Phone field.
• An enabled inquiry option requires an active selected form with a required Email field.

Zeltino protects these required fields while the form is used by the enabled option. This prevents an apparently small form edit from breaking an active visitor path. Choose another compatible form under Contact Options before removing the protected field.

Add consent checkboxes#

Add consent only when your organization has decided the purpose and approved the wording. You can add up to five consent checkboxes. For each one:

1. Write the complete Consent text.
2. Set Requirement to Required or Optional.
3. Add policy links when needed. Each consent supports up to four links with a label and public URL.
4. Review the chat preview.

Use clear, purpose-specific language. Do not combine unrelated purposes in one sentence when visitors should be able to choose separately. Link text such as Privacy policy should lead to a current public page.

Test data quality#

Open the form through the installed visitor path. Submit valid and invalid values, skip optional fields, and attempt to continue without required fields or required consent.

After a successful submission, confirm that the resulting lead contains understandable labels and only the information your team expects. This final review often reveals a field label that looked clear in the editor but is ambiguous in the team record.

Return to Create and manage lead forms for status and lifecycle guidance.