Help Center
Chat Features

Custom Forms

Last updated:

Custom forms let you build your own multi-step forms and use them in place of the built-in Lead Collection or Human Contact Form. You choose the fields, the thank-you message, and the submit button, then bind the form to the section where you want it shown.

Where to find forms

Select your chatbot and navigate to Settings > Forms. This page lists your saved custom forms. When you have not created any yet, it shows "No custom forms yet" with a Create your first form button. Custom forms are available as a premium feature - an upgrade prompt appears if your plan does not include them.

Create a form

Click New form (or Create your first form when the list is still empty) to open the form builder.

Settings > Forms with the New form button highlighted

Build the form

The builder has everything you need to define the form on one screen, with a live preview on the right. For a pizzeria, you could collect contact details in the first step and order preferences in the second.

The custom form builder

  • Form name - an internal name so you can identify the form in the dropdowns later.
  • Thank-you message - the confirmation text shown after a visitor submits the form.
  • Submit button - set the button label, pick an optional icon, and choose its color.
  • Build and Custom CSS tabs - build the fields visually, or switch to Custom CSS to apply your own styles.

Add fields

On the Build tab, give the step an optional title, then click a field-type button to add that field. A form supports up to 10 steps, 50 fields in total and 3 File upload fields. Choice fields support up to 100 options each.

The field-type buttons in the form builder highlighted

  • Name - a single-line field for the visitor's name.
  • Email - captures an email address, validated as an email.
  • Phone number - captures a phone number.
  • Date - a date picker.
  • Time - a time picker.
  • File upload - lets the visitor attach and upload a file (see below).
  • Short answer - a single-line free-text field.
  • Long answer - a larger multi-line field for longer responses.
  • Checkbox - a single tick box, for example to accept terms.
  • Dropdown - a menu where the visitor picks one option from a list.
  • Single choice - a set of options where the visitor picks exactly one.
  • Multiple choice - a set of options where the visitor can tick several at once.

Each field has a Label (what the visitor sees) and a Name (the internal key used in exports and notifications). You can mark a field Required, set its Width so fields sit side by side, and drag fields to reorder them. Dropdown, Single choice, and Multiple choice fields also take a list of options, one per line.

Add steps

For longer forms, split the fields across steps instead of one long screen. Click Add step, then add fields to that step. Dragging reorders fields within a step. Each step is its own card with an optional title.

Visitors see each step as a separate screen in the chat and move between them with Next and Previous buttons, which appear automatically once a form has more than one step. When a form is multi-step, the builder also lets you set the label, icon, and color for the Next and Previous buttons.

Give each step a short, action-oriented title (for example "Your details", then "Your request") so visitors always know where they are in the form.

File upload fields

A File upload field lets a visitor attach a file to their submission. For each file field you can set:

  • Accepted extensions - a comma-separated list, for example pdf, png, jpg. Only files with these extensions are allowed.
  • Max size - the maximum file size in MB, up to 10 MB.

Uploads are checked on submission: the extension must be in your allowed list, the file must be within the size limit, and its actual contents must match the declared type.

Live preview

The Live preview panel on the right shows the form exactly as visitors will see it, updating as you add fields, add steps, and change the styling.

When the form is ready, click Save. The form now appears in your list under Settings > Forms.

Use a custom form

A saved custom form does not appear to visitors on its own. Bind it to a section:

  • Settings > Lead Collection - open the Form shown to the visitor dropdown and select your custom form instead of the built-in form.
  • Settings > Human Contact Form - open the Form shown to the visitor dropdown and select your custom form instead of the built-in form.

The visitor then sees your custom form wherever that section is triggered.

Enable the chosen section first. Lead Collection lists forms containing a Name field and an Email or Phone number field. Human Contact Form lists forms containing an Email field; its first Long answer field supplies the support message. See Lead collection and Human Support Contact Form for triggers and notification settings.

You can also offer a form independently through Settings > Actions > Add action for custom form. Configure when the AI should display it; saving a form alone does not activate an action.

How it looks to the visitor

See it in a conversation

Collect a structured request

Create a form and bind it to a supported feature or action. Example values are prefilled; the demonstration does not submit a real request or confirm a booking.

ChatLab exampleIllustrative conversation

Visitor: I would like to request a table for Friday.

Play the example or read it below. No real customer data is used.
1 / 5

A relevant request triggers the configured form.

Playback pauses when this example leaves the screen. This is a simulation, not a live chat. Widget controls inside the playback are not interactive.
Read the complete example
  1. A relevant request triggers the configured form.

    Visitor: I would like to request a table for Friday.

  2. First, the visitor completes their contact details.

    Name: Anna Weber; Email: anna@example.com

  3. Next moves to request preferences; Back returns to contact details.

    Preferred time: Friday, 7 pm; Number of guests: 4

  4. Example values collected by the form.

    Name: Anna Weber; Email: anna@example.com; Preferred time: Friday, 7 pm; Number of guests: 4

  5. A received request is not a confirmed reservation.

    Assistant: Your request has been received. The team will confirm availability.

The form appears inside the chat window. The animation shows a table request with contact details followed by request preferences. The static screenshots below show a separate pizza-order enquiry: the visitor first completes Your details, then moves to the next step.

View the static screenshot

Your details step of a custom form in the chat widget|width=40

Step 2, Order preferences, shows a Preferred pizza dropdown and Additional notes. The visitor can return with Back or submit with Send request. These are the button labels configured for this example; your form uses the labels you choose in the builder. After submission, the configured thank-you message appears in the chat. This example does not include a file upload field.

View the static screenshot

Order preferences with Preferred pizza, Additional notes, Back and Send request|width=40

See submissions in the Leads tab

When a visitor submits a custom form that is bound to Lead Collection or the Human Contact Form, the submission is saved as a lead. Open the bot's Leads tab to review it.

Alongside the standard Name, Email, Phone, Collected date, and Entry point, a Form data column shows the full submission: each field's label followed by the value the visitor entered, one line per field. For a File upload field, the uploaded file's name is shown; the lead notification email and the CSV export (the Export button on the Leads tab) both include a download link to the file itself.

A custom form submission shown in the Leads tab

From each lead you can also click through to the full Conversation to see the chat around the submission.

Test the selected trigger in Overview, complete all steps and submit the form. Confirm the thank-you message and check the saved submission. Test notification delivery with an address you control if notifications are enabled. Standalone action forms are recorded in the conversation; do not assume that every standalone submission creates a lead.

Related articles