Create and manage custom forms
Custom forms let you collect structured information from guests, providers, and staff during appointments, membership enrollment, check-in, and other workflows. You design forms in a visual builder, associate them with services or other entities, and control who can access them.
Note: For conceptual background, see Forms overview.
On this page
- Before you begin
- Form types
- Single-instance rules
- The guest form and how it is sent
- Create a custom form
- Configure form properties
- Configure expiry settings
- Form versioning
- Start from a template
- Import and export forms
- Form builder limitations and tips
- Configure job-based form permissions
- Configure membership form action types, renewal, and expiry
- View and manage the forms list
- Franchise organizations
- Tips
- Troubleshooting
Before you begin
- You need administrator access at the organization level. A form definition is owned by the organization β there is no separate per-center version of it, so any change you make applies to every center.
- Decide on the form type before you create the form. Each type has distinct behavior and cannot be changed after creation.
- A form does not become active until it is associated with at least one service, package, or membership. Creating a form is not sufficient β staff cannot fill the form until the association exists.
- Forms built with the form builder cannot be opened or edited in the legacy form builder (and vice versa). Decide which builder version to use before creating the form.
Permission: Add under CustomFields in the Administrator section of the security role β Required to create new custom forms.
Permission: Edit under CustomFields in the Administrator section of the security role β Required to modify existing custom forms.
Permission: Delete under CustomFields in the Administrator section of the security role β Required to delete form definitions.
Permission: Export under Export_Admin in the Administrator section of the security role β Required to export the forms list to Excel, PDF, or CSV.
Additional permissions required for specific form data and workflows:
| Permission | Required to |
|---|---|
| View under GuestCustomData in the Guest Manager section | View guest custom form data |
| Edit under GuestCustomData in the Guest Manager section | Edit guest custom form data |
| View under ServiceCustomData in the Appointment Book section | View service form data |
| Edit under ServiceCustomData in the Appointment Book section | Edit service form data |
| Add under DotPhrases in the Administrator section | Create new dot phrases |
| Edit under DotPhrases in the Administrator section | Edit existing dot phrases |
| View under Medical Record in the Administrator section | View EMR data in form views |
| Add under ServiceEntities in the Administrator section | Create custom entity definitions |
| Edit under ServiceEntities in the Administrator section | Edit custom entity definitions |
Form types
Each form type determines which macros are available, which platforms the form appears on, and which features (review, expiry, Webstore access) are supported. Select the type that matches your use case.
| Form type | Description | Review | Expiry | Webstore |
|---|---|---|---|---|
| Service | Collects data during a service appointment. Supports service-level macros. | Yes | Yes | No |
| Tag | Attaches to a service via a tag identifier for flexible, reusable data collection across services. | Yes | Yes | No |
| Guest | Collects guest profile information. Supports guest-level macros. One per organization. | No | Yes | Yes |
| Membership | Captures membership agreement and enrollment data. Supports membership-level macros. | No | No | Yes |
| Package | Captures data related to package enrollment. Supports package-level macros. | No | No | Yes |
| Entity | Collects data for custom entities such as equipment or room types. One per organization. | No | No | No |
| Loyalty | Captures data for loyalty program enrollment. Supports loyalty-level macros. One per organization. | No | No | Yes |
| Class | Collects data during class sessions. Supports service-level macros. Requires the Training or Classes module. | No | Yes | No |
| Employee Survey | Captures employee feedback such as engagement pulses, training reviews, or post-shift checkpoints. Available only in the form builder. Use Employee Survey forms when the data is collected from staff (not guests) and is not tied to a service appointment. | No | No | No |
Note: The Employee Survey form type is only available when the employee survey feature is enabled for your organization. The Class form type requires the Training or Classes module. The Entity form type requires the service entities feature to be enabled. Contact your Zenoti representative if these types do not appear in your dropdown.
Single-instance rules
The following form types are limited to one form per organization:
- Guest β Only one guest form can exist at a time. If a guest form already exists, the system prevents you from creating another and links you to the existing form.
- Entity β Only one entity form can exist per organization.
- Loyalty β Only one loyalty form can exist per organization.
All other form types support multiple forms per organization.
The guest form and how it is sent
The guest form is a distinct object from service forms and tag forms. Your organization has exactly one guest form. It is managed at the organization level and does not appear in the same list as service or tag forms β which is why searching the custom forms list for a guest form by name may not return the result you expect.
The guest form is sent automatically by a form notification when a new guest profile is created in Zenoti. If a guest reports that they never received the form, the most common cause is that the notification did not fire because the guest profile was created through an import or an integration path that bypasses the standard guest-creation trigger, rather than through the normal guest-creation workflow.
For details on configuring which notification sends the guest form, see Configure form notifications.
Create a custom form
Worked example: A spa creates a service form named "Pre-Treatment Health Check" with code
PTHC-001. They enable Require review so that a provider must review each submission before the appointment proceeds. They set expiry to Expires after and enter365so guests re-fill the form annually.
Navigate to Configuration > Forms > Form creation > Custom forms.
Click Add. The Create custom form page opens.
Select a Form type (Service, Guest, Tag, Memberships, Packages, Entities, Loyalty, or Classes).
Enter the form details:
Field Description Name A descriptive name for the form. Must be unique within the organization. Code A unique alphanumeric code that identifies the form. Must be unique within the organization. Description A brief description of the form's purpose. Create form using Form builder, HTML code, or V1 (key-value pair). Use Form builder for new forms. Status Whether the form is available for use: Active or Inactive. Form validity The expiry rule for the form (see Configure expiry settings). Click Save & Proceed, then configure additional form properties as needed on the GENERAL tab (see Configure form properties).
On the DESIGN tab, design the form layout using the form builder. Add fields, sections, signatures, annotation pads, EMR widgets, and other components as needed. For the full reference of available components, see Form builder components.
Click Save.
Tip: If a form with the same name or code already exists, the system displays a validation error. Change the name or code and try again.
Alternative paths:
- Start from a template β Instead of building from scratch, choose a predefined template from the template library at step 6. See Start from a template.
- Import a form β Import a
.zenformfile exported from another organization. See Import and export forms.
Configure form properties
After you select a form type and enter basic details, configure the following properties based on your requirements. Not all properties are available for every form type.
These properties are accessible on the GENERAL tab of an existing form definition, as well as during initial form creation. To update properties on a form that already exists, open the form from the custom forms list and select the GENERAL tab β you do not need to recreate the form.
| Property | Description | Available for |
|---|---|---|
| Require review | When enabled, submitted forms require explicit review before they are marked as complete. | Service, Tag |
| View-only | When enabled, the form is displayed in read-only mode. Guests and providers can view but not edit the form. | All types |
| Copy previous data | When enabled, the system copies data from the guest's previous form submission into the new form. | All types |
| Prefill old version data | When enabled, the system prefills data from a previous version of the form into the current version. | All types |
| Custom script | When enabled, allows you to add custom JavaScript to the form. This property is only available when the custom script feature is enabled for your organization. | All types (gated) |
| HIS integration platform type | Specifies the health information system integration, such as Emirates ID card reading. Only visible when an HIS integration is configured for your organization. | Service, Guest |
| Email copy of the form to guest on submission | When enabled, a submitted copy of this form can be sent to the guest by adding the [SubmittedFormCopy] macro to a notification template. For service forms, this property is hidden and force-disabled when the form's builder type is V1 (key-value pair) β it is only available on HTML code builder-type service forms. For guest forms, it requires the organization to have Only Webstore 2.0 enabled. See Configure notification template macros for the full set of conditions the macro checks before it resolves. |
Service, Guest |
Configure expiry settings
Expiry settings control how long a completed form remains valid before the guest must fill it again. The available expiry options depend on the form type.
The options appear under Form validity both on the Create custom form page and on the GENERAL tab of an existing form definition. If you need to adjust validity on a form that already exists, open the form from the custom forms list, select the GENERAL tab, and update the Form validity setting there β you do not need to recreate the form.
Important: Changing the validity rule on an existing form applies from the next submission. It does not re-open or invalidate form submissions guests have already completed.
| Expiry option | Description | Available for |
|---|---|---|
| No expiry - Common form for all services on the same day | The form never expires and a single submission applies across all services on the same day. | Service, Tag, Guest |
| No expiry - Applicable to a single service | The form never expires, but a separate submission is required for each service. | Service, Tag |
| No expiry - Common form for all classes on the same day | The form never expires and a single submission applies across all classes on the same day. | Class |
| No expiry - Applicable to a single class | The form never expires, but a separate submission is required for each class. | Class |
| Expires after | The form expires after the number of days you specify. | Service, Tag, Guest, Class |
| Expires on | The form expires on a specific calendar date you specify. | Service, Tag, Guest, Class |
When you select an expiry option that requires a value, enter the number of days or the specific date in the field that appears.
Form versioning
Each form definition supports multiple versions with three statuses:
| Status | Description |
|---|---|
| Active | The current live version. This is the version that guests and providers see during form fill. Only one Active version can exist per form at a time. |
| Deprecated | A previously active version that has been replaced. Deprecated versions are retained for historical reference. |
| Draft | A version that is in progress and not yet published. |
Important: Do not confuse form builder versions (the form builder versus the legacy form builder) with form definition versioning (Active, Deprecated, Draft). These are separate concepts. Form builder version refers to the technology used to design the form; form definition versioning refers to the lifecycle of a specific form definition.
To view the version history of a form:
- Open the form from the custom forms list.
- Select the HISTORY tab.
The system displays all versions with their status, creation date, and modification date.
You can also view the settings change history for a form to see when form properties were modified.
Note: The HISTORY tab is not available for forms created with the V1 (key-value pair) builder or for Employee Survey forms.
Start from a template
Instead of building a form from scratch, you can start from the template library. Templates are predefined form designs for common use cases.
- Navigate to Configuration > Forms > Form creation > Custom forms.
- Click Add, enter the form details, and click Save & Proceed.
- On the DESIGN tab, choose a template from the Form List. Only templates that match the selected form type appear.
- The form builder loads the template design. Modify the layout, fields, and properties as needed.
- Click Save.
The DESIGN tab opens with the prompt "Select a sample, recent or blank form and click on the 'Use Form' button to proceed." and a Form List with two tabs:
- Sample β Predefined form templates filtered by the form type you selected (plus Blank Form).
- Recent β Forms of the same type that you recently edited, for use as a starting point.
Select a template, a recent form, or Blank Form and click Use Form to load it into the builder.
Import and export forms
You can transfer form designs between organizations by exporting and importing .zenform files. A .zenform file is a JSON-format file that contains the complete form definition.
- Export β Open a form in the form builder and use the export action to download the form as a
.zenformfile. - Import β On the forms list page, use the import action and select a
.zenformfile to load the form definition into your organization.
The full procedure β including bulk imports of custom field definitions and service-form associations β is in Import and export forms.
Form builder limitations and tips
Keep these constraints and recommendations in mind when designing forms.
What form builder forms cannot do
| Limitation | Detail |
|---|---|
| No export of submitted data via the form builder | Completed forms built with the form builder cannot be exported or printed directly from the builder. Only forms built with the legacy form builder support the form-level export and print action. To review submitted form data, use the Service forms report β it covers all form types and is not restricted by builder version. The Forms data export report supports legacy form builder forms only and cannot be used for form builder submission data. |
| Webstore requires Webstore v2 | To display a form builder form on the Webstore, your organization must have Webstore v2 enabled. If guests cannot see the form on the Webstore, contact Zenoti Support to confirm your Webstore version. |
| Legacy forms are not editable in the form builder | Legacy form builder (HTML-based) forms cannot be opened in the form builder. To migrate a legacy form, recreate it in the form builder. |
Design for performance
Large or complex forms can affect rendering speed, especially on kiosk and mobile devices. Follow these guidelines:
- Use fewer than 10 panels per form.
- Use no more than 5 tables or annotation pads per form.
- Break very long forms into multiple forms associated with a tag, rather than one form with dozens of panels.
Automatic guest profile updates
Form responses only update the guest profile when the form uses components from the Personal Information (guest info) or Address Information (guest address) component groups. These components auto-bind to profile fields and write the submitted values back to the guest record.
Standard input components β text fields, dropdowns, checkboxes, and similar β capture data in the form record only. They do not update any profile field, regardless of the field label.
Configure job-based form permissions
You can restrict which employee job roles can view or fill a specific form. The full procedure is in Restrict form access by job role.
In franchise organizations, job-based form permissions are configured on the form definition at the franchisor level. If the PERMISSIONS tab controls are unavailable when you open a form, route the change request to your franchisor rather than attempting to configure permissions locally.
Note: The PERMISSIONS tab is not rendered for membership, package, or Employee Survey forms.
Configure membership form action types, renewal, and expiry
Membership forms support additional properties that control when the form is presented during the membership lifecycle and how renewal works.
Form action types
A membership form can be associated with one or more of the following membership lifecycle actions. The form is presented to the guest when the corresponding action occurs.
| Action type | When the form is presented |
|---|---|
| Sign-Up | When a guest enrolls in a new membership |
| Cancellation | When a guest cancels a membership |
| Freeze | When a guest freezes a membership |
| Upgrade/Downgrade | When a guest upgrades or downgrades a membership |
| Transfer | When a membership is transferred to another guest |
| Renewal | When a membership is renewed |
| Locker | When a locker assignment is made in conjunction with a membership |
To set the form action type:
- Open the membership form in the form builder.
- In the form properties, locate Form action type and select the applicable action or actions.
- Click Save.
Note: For membership form enforcement settings β such as requiring form submission before a freeze or cancellation can proceed β see Memberships overview.
Renewal form and membership expiry period
- Renewal form β Select an existing membership form to serve as the renewal form. When a membership is up for renewal, the system presents the bound renewal form to the guest.
- Membership expiry period β Set the number of days after which the membership form expires and must be re-submitted.
To configure renewal and expiry:
- Open the membership form in the form builder.
- In the form properties, locate the Renewal form field and select the desired form.
- Set the Membership expiry period in days.
- Click Save.
View and manage the forms list
The forms list displays all custom forms for your organization in a paginated, searchable grid with the columns Code, Name, Status, Form Type, AI Ready, and AI Instructions.
Note: The banner at the top of the forms list reads: "Only forms created using the form builder can be made AI Ready."
- Navigate to Configuration > Forms > Form creation > Custom forms.
- Use the search bar ("Name, Code") and click Search to find a form by name or code.
- Use the AI Ready and Status filters to narrow the results.
Export the forms list
You can export the forms list to Excel, PDF, or CSV format for offline review.
- On the forms list page, click the Excel, PDF, or CSV export icon.
The system generates and downloads the file containing all forms that match your current search and filter criteria.
Permission: Export under Export_Admin in the Administrator section of the security role β Required to export the forms list.
View version history and settings change history
From the forms list, you can access the version history and settings change history for any form:
- Locate the form in the list and open it.
- Select the HISTORY tab.
- Expand the form template history to view all versions (Active, Deprecated, Draft) with their dates.
- Expand the form settings history to view a log of when form properties were modified and by whom.
Franchise organizations
In franchise organizations, form definitions are held at the franchisor level. Center administrators within the franchise cannot create new forms or modify form definitions β those controls are not available at the center level.
If you are a center administrator and you cannot find the form-creation options described in this article, route the request to create, modify, or delete a form definition to your franchisor rather than attempting it locally.
Similarly, job-based form permissions β which control which employee job roles can view or fill a specific form β are configured on the form definition at the franchisor level. If the permission controls on a form are unavailable when you open the form, route the change request to your franchisor rather than attempting to configure permissions locally.
Tips
- Name forms consistently. Use a naming convention that includes the form type and purpose, such as
[Service] Pre-Treatment Health Checkor[Membership] Signup Agreement. This makes the forms list easier to scan and filter. - Test expiry settings before activating. Set a short expiry period in a test environment to confirm that the system prompts guests to re-fill the form at the expected interval before deploying to production.
- Use the template library for common use cases. Starting from a predefined template is faster than building from scratch and reduces the risk of missing required fields for standard workflows such as health intake or consent capture.
- Associate forms immediately after creation. A form that is not associated with a service, membership, or other entity is invisible to staff and guests. Complete the form association step before marking the form active. See Assign forms to services.
- Use dot phrases to speed up form filling. Providers can type a short phrase during form fill to expand it into a longer block of text. Configure dot phrases in advance for common clinical notes or standard responses. See Configure dot phrases.
- Keep membership form action types accurate. If a membership form is associated with the wrong action type, it will not appear at the correct point in the membership lifecycle. Review action type assignments whenever membership workflows change.
Troubleshooting
A guest says they never received the guest form. The guest form is sent by a form notification that fires when a new guest profile is created through the standard guest-creation workflow. If the profile was created through a bulk import or an integration, the notification may not have fired. Verify how the guest profile was created and, if needed, manually send the form or ask the guest to complete it at their next visit. See Configure form notifications.
The Guest, Entity, or Loyalty form type is not available in the dropdown. These form types are limited to one per organization. If a form of that type already exists, the system removes the type from the dropdown and links you to the existing form. Navigate to the forms list and search for the existing form.
A form is not appearing for guests or providers during an appointment. Confirm that the form is associated with the relevant service and that the association's visit mode (first visit, subsequent, or always) matches the guest's visit history. Also confirm that the form status is Active β Draft and Deprecated forms do not appear during appointments. See Assign forms to services.
The Employee Survey or Class form type does not appear in the dropdown. The Employee Survey form type requires the employee survey feature to be enabled for your organization. The Class form type requires the Training or Classes module. Contact your Zenoti representative to enable these features.
A form built with the form builder does not appear in the Forms data export report. The Forms data export report supports legacy form builder forms only. Form builder forms do not appear in this report. Use the Service forms report to review submitted data for form builder forms.
The custom script property does not appear in the form properties panel. The custom script property is only available when the custom script feature is enabled for your organization. Contact your administrator or Zenoti representative to enable this feature.
You cannot find the form-creation options as a center administrator. Form definitions are organization-level objects, and in franchise organizations they are managed by the franchisor. If the Add button or form-creation controls are not visible at your center, first confirm you hold Add under CustomFields at the organization level; if you do, route the request to your franchisor rather than attempting to create the form locally.