ZenotiHelp

Form builder components

ZTZenoti Docs Team Updated November 3, 2026 20 min readGuide

The form builder is Zenoti's drag-and-drop form design tool. It provides a wide range of input components, layout tools, and Zenoti-specific integrations for building custom forms. This article is the reference for every component available to you.

Note: If you are new to forms, start with Create and manage custom forms and come back here as you decide which components to add.


On this page


Before you begin

  • The form builder must be enabled for your organization.

  • You need the following permissions:

    Permission: Add under CustomFields in the Administrator section of the security role β€” Required to create new forms.

    Permission: Edit under CustomFields in the Administrator section of the security role β€” Required to modify existing forms.

  • To use EMR components, the EMR (Electronic Medical Records) feature must be enabled for your organization and you need:

    Permission: View under Medical Record in the Administrator section of the security role β€” Required to access EMR data in form views.

  • Determine which components your form requires before you start building. The builder organizes components into groups so you can navigate them quickly.

Component groups

The form builder organizes components into groups, displayed in the sidebar:

Group Description
Guest Info Guest information components that auto-bind to guest profile fields.
Guest Address Guest address components that auto-bind to guest address fields.
Medical Records EMR components for clinical data. Only available when the EMR feature is enabled for your organization.
Basic Standard input fields including text, number, selection, date, and file upload components.
Layout Structural components for organizing form layout including columns, tabs, and panels.
Others Additional components that do not fit the above groups.

Basic input components

Use these components to collect standard data from guests and providers.

Component Description
Text Field A single-line text input for short values such as names, codes, or brief responses.
Text Area A multi-line text input for longer free-form responses, notes, or descriptions.
Email An email input field with built-in email format validation.
Number A numeric input that accepts only numbers. Use for quantities, measurements, or scores.
Phone Number A phone input with an input mask that formats the number as the user types.
Date / Time A combined date and time picker for selecting both a calendar date and time of day.
Day A day selector for choosing a specific day.
Time A time picker for selecting a time of day.
Currency A currency-formatted input that displays values with currency symbols and decimal formatting.

Using macros in text fields

Text Field, Text Area, Email, and Date / Time components support automatic pre-population from a macro. Open the component's Basic tab, select a value from the Macros list, and the field is pre-populated when the form renders β€” for example, with the guest's name or appointment date.

To prevent the user from overriding a macro-populated value, enable the Disabled checkbox on the same Basic tab.

For the full macro catalog and which macros are available per form type, see Use macros in forms.

Selection components

Use these components when users must choose from predefined options.

Component Description
Select A dropdown list where the user picks one value. Bind to a custom list to populate the options.
Radio A set of radio buttons where the user selects one option from a visible list.
Select Boxes A set of checkboxes where the user can select multiple options from a visible list.

Select (dropdown) configuration options

Option Where Description
Label Basic tab The display name for the dropdown.
Placeholder Basic tab Guidance text shown when no option is selected (for example, "Select a value").
Allow unique values Basic tab When enabled, prevents duplicate options from appearing in the list.
Make field read-only for guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.
Hide field from guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.
Data source values Data tab Enter option labels one row at a time. Values are auto-generated from labels and are used in calculated field logic.

Radio and Select Boxes configuration options

Radio allows a single selection; Select Boxes allow multiple selections. Both components share the following configuration options.

Option Where Description
Label Basic tab The display name for the field.
Inline Layout Basic tab When enabled, displays the options horizontally side by side instead of the default vertical stack. Saves vertical space when options are short.
Options label position Basic tab Controls the alignment of option labels relative to the buttons or checkboxes.
Make field read-only for guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.
Hide field from guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.
Values Data tab Enter option labels one row at a time. Values are auto-generated but editable β€” they are used in calculated field logic. You can optionally enter a single-character keyboard shortcut per option (for example, E for English, S for Spanish) to support keyboard-driven data entry.

Signature component

The Signature component captures digital signatures via touch input (on tablets and mobile devices) or mouse input (on desktop). Use signatures for consent forms, review sign-off, membership agreements, and any form that requires a guest or provider signature.

Signature configuration options

Option Where Description
Label Basic tab The display name shown above the signature pad.
Footer Label Basic tab Text displayed below the signature pad, such as a declaration or consent statement.
Background color Basic tab The background color of the signature pad. Accepts standard color codes (for example, rgb(245,245,220) or #f5f5dc).
Pen Color Basic tab The color of the digital pen. Accepts standard color codes (for example, rgb(0,0,139) or #00008b).
Make field read-only for guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.
Hide field from guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.

Note: External signature pad devices (dedicated hardware signature tablets) can be integrated with Zenoti to capture signatures via a hardware pad rather than touch or mouse input. To set up an external signature pad integration, contact Zenoti Support.

Image and annotation components

Component Description
Annotation pad A custom drawing canvas where users can draw shapes, markups, and text overlays on uploaded images. Use for clinical documentation, marking treatment areas, or highlighting specific details on diagrams and photos.
Image Displays and allows annotation of images within the form. Users can upload an image and add visual markups.

Annotation pad navigation tools

When working inside the annotation pad, the following tools are available in the toolbar:

Tool Description
Draw Freehand drawing on the image.
Shapes Insert geometric shapes onto the image.
Marker Apply a marker-style highlight or annotation.
Lines Draw straight lines on the image.
Text Add text overlays onto the image.
Measure Measure distances or areas on the image.
Border Set border properties for shapes.
Fill Set fill color for shapes.
Shape Color Change the color of drawn shapes.
Text Color Change the color of text overlays.
Border Color Change the border color of shapes.
Patient Gallery Select a previously uploaded guest image as the annotation background.
From Device Upload a new image from the device.
Clear Annotations Remove all annotations from the current image, keeping the background.

Note: Selecting a thumbnail from Patient Gallery applies it immediately as the annotation background β€” there is no separate confirm step.

Table component

The Table component provides a structured tabular data entry grid within forms. Use tables when you need to collect repeated sets of related data, such as a list of medications with dosage and frequency columns, or a multi-row treatment plan.

After placing a Table on the form, add other components inside each cell to build out the table structure.

Table configuration options

Option Where Description
Number of rows Basic tab Sets the initial number of rows in the table.
Number of columns Basic tab Sets the number of columns.
Cell alignment Basic tab Controls horizontal alignment of cell content (left, center, or right).
Clone row components Basic tab When enabled, the same component type is replicated across every row in a column. Use this when every row captures the same type of input (for example, a text field in each row for a health condition list).
Striped Basic tab Alternates the row background color for easier row identification.
Bordered Basic tab Adds visible borders around each table cell.
Hover Basic tab Highlights a row when the user's pointer is over it.
Condensed Basic tab Reduces row spacing for a more compact display.
Make field read-only for guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.
Hide field from guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.

File upload components

Component Description
File A standard file upload field that lets users attach documents, images, or other files to the form.
Bulk file upload A custom component for uploading multiple files at once. Use when users need to attach several documents or images in a single step.

Note: You can upload a maximum of 10 files at a time. Each file cannot exceed 10 MB. If the form has more than a total of 20 files, the form may be slow to load.

File upload configuration options

Option Where Description
Label Basic tab The display name for the upload field.
Image size File tab Maximum image dimension in pixels for uploads to this specific field (for example, 200 limits images to 200 px). This is a per-field setting. Organization-wide file size limits are set separately in your form configuration settings.
Make field read-only for guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.
Hide field from guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.

Content component

The Content component displays static HTML content within a form. Use it for instructional text, business logos, disclaimers, or informational paragraphs that do not collect data. Content components are display-only and do not contribute to form submission data.

To display your business logo on a form:

  1. Open the form in the form builder.

  2. Drag a Content component to the location where the logo should appear. The top of the form (above the first section) is the typical choice.

  3. Open the Content component's HTML editor.

  4. Insert an image tag pointing to a hosted logo image, and set sensible width and alignment. Example:

    <p style="text-align:center;">
      <img src="https://your-cdn.example.com/logo.png" alt="Business name" style="max-width: 200px; height: auto;" />
    </p>
    
  5. Save the form and preview it on the platforms your guests use (Webstore, kiosk, Customer Mobile App). Logos that are too wide can force horizontal scrolling on small kiosk screens β€” cap at 200–300 pixels wide for best rendering across devices.

Tip: Host the logo on your own CDN or Zenoti asset host. Avoid hotlinking to a social-media profile image, which may expire or be blocked.

Layout components

Use layout components to organize the visual structure of your form.

Component Description
Columns Creates multi-column layouts so you can place fields side by side. Useful for forms where related fields should appear together horizontally.
Tabs Organizes form content into tabbed sections. Users click tab headers to navigate between sections.
Panel Creates collapsible and expandable sections within a form. Use panels to group related fields and let users show or hide sections as needed.

Columns configuration options

After placing the Columns component, add one component inside each column to build out the layout.

Option Where Description
Column Properties Basic tab Sets the relative width for each column. Select from xs, s, m, l, or xl.
Auto adjust columns Basic tab When enabled, columns automatically resize to fit their content.
Make field read-only for guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.
Hide field from guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.

Tabs configuration options

Tip: Add the Tabs component as the first element on the form. Tabs placed at the top level organize the entire form into navigable sections. Adding Tabs partway down only organizes that portion of the layout.

Option Where Description
Labels Basic tab β†’ Tabs table Enter a label for each tab. Use Add Another to create additional tabs.
Vertical Layout Basic tab When enabled, displays tab headers vertically on the side instead of the default horizontal row at the top.
Make field read-only for guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.
Hide field from guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.

Panel (collapsible section) configuration options

Option Where Description
Panel Title Basic tab The heading text displayed in the panel header.
Collapsible Basic tab When enabled, users can expand and collapse the section by clicking the panel header.
Initially collapsed Basic tab When enabled, the panel starts in a collapsed state when the form loads. Only available when Collapsible is also enabled.
Theme Basic tab Applies a visual style (color scheme) to the panel header and border.
Hide Label Basic tab Hides the panel title from view.
Make field read-only for guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.
Hide field from guest (on CMA, Kiosk, Webstore, ZMA guest mode) Basic tab See Guest visibility control.

Calculated fields

A calculated field displays a value computed automatically from the values of other fields on the form using custom JavaScript logic. Use calculated fields for derived measurements such as BMI, total scores, or clinical dose calculations. The calculated value is display-only β€” the field is locked so the user cannot override it.

Set up a calculated field

  1. Add the input fields the calculation depends on (for example, two Number components for height and weight).

  2. Add a third component to display the result (typically a Number or Text Field).

  3. Open the result field's settings. Under the Basic tab, select the Disabled checkbox. This locks the field and ensures only the JavaScript formula can set its value.

  4. Open the Data tab, expand Calculated Value, and then expand the JavaScript section.

  5. Write the JavaScript formula. Reference other fields by their Field Key (shown in each component's Basic tab). Example for BMI:

    var h = data.heightKey;   // replace with the actual field key
    var w = data.weightKey;   // replace with the actual field key
    value = w / (h * h);
    
  6. Save the form. The calculated field updates automatically as the user fills in the input fields.

Note: Find a component's Field Key in its Basic tab settings. Use these keys to reference field values in your formula. Calculated fields require the Disabled checkbox to be selected β€” if the field is left editable, users can manually override the computed value.

Tip: Calculated fields work on text and number input components. The Calculated Value panel is not offered for the Select, File, and Day components or for the Guest Info components. You can use a Text Field as the result component if you want to display a formatted string rather than a plain number.

Conditional display rules

The form builder supports conditional display rules that show or hide fields based on the values of other fields in the form. For example, you can show a signature field only after a guest checks an agreement checkbox, or display female-specific health fields only when the gender field is set to a specific value.

Configure a conditional display rule

  1. Select the field you want to conditionally display.

  2. Open the field's Conditional tab.

  3. In the Simple section, configure the following:

    Setting Description
    This component should Display Set to True to make the field visible when the condition matches.
    When the form component Select the source field whose value controls visibility.
    Has the value Enter the exact trigger value. When the source field equals this value, the current field appears.
  4. Save the form. The field appears or hides dynamically as the user fills in the form.

Important: Value matching is case-sensitive. If your source field stores the value F (uppercase), entering f (lowercase) as the trigger value will not match. Check the exact values stored in the source component's Data tab if the condition is not triggering as expected.

A clinical intake form has a Radio component labeled "Sex assigned at birth" with two options: Male (value M) and Female (value F). A second field, Number labeled "Weeks pregnant", should only appear when the guest selects Female.

Configure the Weeks pregnant field's Conditional tab as follows:

  • This component should Display β†’ True
  • When the form component β†’ Sex assigned at birth
  • Has the value β†’ F

When the guest selects Female, the Weeks pregnant field appears. When they select Male, it remains hidden. Because value matching is case-sensitive, the trigger value must be F β€” not f or Female.

Guest visibility control

Form designers can mark individual fields as read-only or completely hidden from guest-facing form views. This lets you include provider-only fields β€” such as clinical notes, annotation pads, or review signatures β€” on the same form that guests fill online.

Guest-facing surfaces affected: CMA (Customer Mobile App), Kiosk, Webstore, and ZMA guest mode (guest mode on the employee mobile apps, used when a staff member hands the device to the guest).

To configure guest visibility for any component:

  1. Select the component in the form builder and open its settings.

  2. Under the Basic tab, configure one of the following:

    Option Behavior
    Make field read-only for guest (on CMA, Kiosk, Webstore, ZMA guest mode) The field is visible to guests but cannot be edited by them. Staff see the field in edit mode. Use for therapist signatures, annotation pads, or doctor notes that guests should see but not change.
    Hide field from guest (on CMA, Kiosk, Webstore, ZMA guest mode) The field is completely hidden from guest-facing views. Staff see the field normally. Use for internal fields, provider instructions, or any data guests should not see.
  3. Save the form.

Guest information components

The form builder includes a set of guest information components that automatically bind to the guest's profile fields. When a guest fills the form, these fields are pre-populated with their existing profile data.

Which components write back to the guest profile. Only Guest information components and Guest address components update the guest profile on form save. Standard input components β€” text fields, dropdowns, checkboxes, numbers, and all other components β€” capture their data in the form record only. They do not update any guest profile field, regardless of what label you give them. To ensure a form response updates the guest profile, use the guest information or address components for that field.

How auto-sync works for guest info components. If the guest updates a value in one of these fields, the guest profile is updated to match when the form is saved β€” but only when the field has Allow guest to edit enabled. Read-only fields still display the profile value to the guest, but do not push any value back to the profile on save.

Profile values always replace typed values. Guest information components behave as profile-bound controlled inputs. Whenever the bound profile value changes β€” for example, because the guest's record was updated elsewhere β€” the field replaces whatever the user has typed with the current profile value. This is the expected behavior of a profile-bound component, not a rendering defect. If a field must hold typed text that should not be read from or written to the guest profile (for example, a "Manager name" field), use a standard Text Field component instead of a guest information component. A guest information component behaves as a profile field regardless of the label you apply to it.

Available guest information components:

  • First name, Last name β€” The guest's name fields.
  • Email β€” The guest's email address.
  • Phone β€” The guest's phone number.
  • Address β€” The guest's street address.
  • Gender β€” The guest's gender selection.
  • Country, State β€” The guest's country and state/province.
  • Pronoun β€” The guest's preferred pronoun.
  • Birthday β€” The guest's date of birth.
  • Marketing messages β€” The guest's marketing communication preference.
  • Transactional messages β€” The guest's transactional communication preference.

Guest address components

A separate set of address-specific components auto-bind to the guest's address fields:

  • Address line 1, Address line 2 β€” Street address fields.
  • City β€” The guest's city.
  • State β€” The guest's state or province.
  • Country β€” The guest's country.
  • Postal code β€” The guest's postal or ZIP code.

EMR components

Availability: EMR components are only available in the form builder when the EMR feature is enabled for your organization. Contact your Zenoti administrator to confirm whether this feature is active.

When the EMR feature is enabled for your organization, additional clinical components are available in the form builder under the Medical Records group:

Component Description
Allergy records Captures and displays the guest's allergy information. Binds to the guest's EMR allergy records.
Medication records Captures and displays the guest's current medications. Binds to the guest's EMR medication records.
Medical history Captures and displays the guest's medical history. Binds to the guest's EMR medical history.
Social history Captures and displays the guest's social and lifestyle history. Binds to the guest's EMR social history records.

Permission: View under Medical Record in the Administrator section of the security role β€” Required to access EMR data in form views.

One guest identity per form

Every form instance carries a single guest identity. Every guest information component and every guest address component on a given form instance resolves its binding to that same single guest profile β€” there is no per-component guest identity and no guest collection on a form instance.

This means a form filled by two people β€” for example, a couples or family booking β€” cannot keep their entries separate, because every guest information and guest address component resolves to the same profile. The recommended design is one form instance per guest when more than one person will fill the form.

Tips

  • Start with guest information and address components for intake forms. These auto-populate from the guest profile and save time.
  • Use conditional display rules to keep forms concise. Show fields only when they are relevant based on earlier responses.
  • Use panels to organize long forms into collapsible sections so guests are not overwhelmed by a long scrolling form.
  • Use the content component to add instructions, disclaimers, branding, or your business logo to your forms.
  • Mark internal-use fields as hidden from guest view so guests see only the fields relevant to them.
  • Test your form on multiple platforms (desktop, tablet, kiosk, Customer Mobile App) before activating it to ensure the layout renders well across screen sizes.
  • For calculated fields, always set the result component to Disabled before writing the formula. Leaving the field editable allows users to overwrite the computed value.
  • When a form needs to hold a value that should not bind to the guest profile β€” such as a referring provider's name or an internal case number β€” use a standard Text Field rather than a guest information component. Guest information components always bind to the profile regardless of their label.
  • For forms collected on kiosk or the Customer Mobile App where more than one guest participates (such as a couples appointment), create a separate form instance for each guest. A single form instance cannot hold separate data for two different guest profiles.
  • The form builder does not provide a print or export action for submitted form data. To review or analyze submission data from the form builder, use the Service forms report under Medical hub.

Troubleshooting

A conditional display rule is not showing the field when expected. Value matching is case-sensitive. Open the source component's Data tab and verify the exact stored value. Confirm the trigger value in the Has the value field matches exactly β€” including capitalization and spacing.

A guest information component is not writing back to the guest profile after form submission. Check that the component has Allow guest to edit enabled. Read-only guest information fields display the profile value but do not push updates back to the profile on save.

A guest information field keeps replacing what I type. This is the expected behavior of a profile-bound component. Guest information components are controlled inputs: whenever the bound guest profile value changes, the field replaces the displayed value with the current profile value, with no guard for text you have already typed. If the field is not intended to bind to the guest profile β€” for example, a field labeled "Emergency contact name" β€” rebuild it as a standard Text Field component. A standard Text Field captures what is typed and does not interact with the guest profile.

EMR components do not appear in the form builder sidebar. The EMR feature must be enabled for your organization before the Medical Records group appears in the builder. Contact your Zenoti administrator to confirm the feature is active. Also verify that your role has View under Medical Record in the Administrator section.

A calculated field is showing an incorrect or blank value. Confirm that the Field Key values referenced in the JavaScript formula exactly match the keys shown in each source component's Basic tab. Field keys are case-sensitive. Also confirm the result field has the Disabled checkbox selected β€” if the field is editable, a user may have manually overwritten the computed value.

The form layout looks different on the kiosk than in the builder preview. Kiosk screens are narrower than desktop displays. Columns set to xl or l widths may wrap or overflow on smaller screens. Use Auto adjust columns on the Columns component, or switch to a single-column layout for sections that must render correctly on kiosk.

The Select, File, or Day component does not show a Calculated Value option in its Data tab. These components do not support calculated values. Use a Text Field or Number component as the result field and reference values from the Select, File, or Day fields by their Field Key in the formula β€” the formula field on the result component will pick up values entered in any other component type.

Was this article helpful?
Your feedback helps us improve our documentation.