ZenotiHelp

Forms overview

ZTZenoti Docs Team Updated October 26, 2026 5 min readGuide

Zenoti forms let your organization create, distribute, and manage custom forms across appointments, guest profiles, the Webstore, kiosk check-in, and mobile apps. You design forms with a visual builder, associate them with services and business processes, and track completion through reports and compliance rules.

Before you deploy

Verify the following before activating forms for a center.

Prerequisite Why it matters
Admin_Manager module license active (with GuestCustomFields, ServiceCustomFields, and Lists features enabled) Required for guest custom fields, service custom fields, and custom list management β€” the building blocks of every form.
Appointment_Book module license active Required for form rendering during appointments, the forms report, and compliance tracking.
Add or Edit under CustomFields in the Administrator section of the security role Allows administrators to create and edit form definitions, fields, and lists. The custom fields organization setting must also be enabled for the menu to appear.
View or Edit under ServiceCustomData in the Appointment Book section of the security role Required for staff who fill in or review service forms during appointments.
Training license with Classes feature (only if you use Class forms) Required for the Class form type.

For step-by-step setup, see Get started with forms and Configure form settings.

How forms work

Forms separate the form definition (the template) from form data (what guests and providers fill in). This means you can reuse the same form across multiple services and contexts.

Form lifecycle

Every form follows a standard lifecycle:

  1. Definition β€” An administrator creates a form using the form builder, selecting field types, validation rules, and display logic.
  2. Association β€” The form is linked to services, guest profiles, memberships, packages, or other business processes.
  3. Rendering β€” The form appears to guests and staff through the Appointment Book, Webstore, kiosk, or mobile apps.
  4. Submission β€” Completed forms are saved with audit trails and optional review requirements.
  5. Review and compliance β€” Submitted forms can require explicit review. Compliance tracking monitors submission rates against targets.

Form types

The system supports nine form types, each designed for specific business contexts:

Form type Description Review supported Expiry supported Webstore access
Service Collects data during service appointments. Supports service-level macros. Yes Yes No
Tag Attaches to services via a tag identifier for flexible, reusable data collection. Yes Yes No
Guest Collects guest profile information. One per organization. No Yes Yes
Membership Captures data during membership lifecycle actions (signup, cancellation, freeze, renewal, upgrade/downgrade, transfer). No No Yes
Package Captures data related to package enrollment. 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. One per organization. No No Yes
Class Collects data during class sessions. Supports service-level macros. No Yes No
Employee Survey Captures employee feedback. Available only in the form builder. No No No

Single-instance form types

Three form types allow only one form per organization: Guest, Entity, and Loyalty. If a form of one of these types already exists, the system prevents you from creating another and links you to the existing form.

Form builder versions

Zenoti supports three form builder technologies:

Version Description
V1 (Key-Value Pair) The original form format with simple field definitions. Limited field types and layout options.
V2 (HTML) An HTML-based form builder with richer layout capabilities.
V3 (JSON) The modern form builder with the most flexibility. Supports advanced field types, conditional logic, dot phrases, import/export, and guest information auto-binding. Recommended for all new forms.

Not all form types support all versions. Employee Survey forms are only available in V3. Tag and Membership forms are not available in V1.

Multi-platform availability

Forms render consistently across Zenoti's ecosystem:

  • Appointment Book β€” Staff-facing form completion during service delivery
  • Webstore β€” Guest self-service form completion before or after booking
  • Kiosk β€” Check-in flow integration with missing form detection
  • Zenoti Mobile (Mobile POS) and Therapist App β€” Native form rendering on iOS and Android devices
  • MyZen β€” Employee mobile app: providers view, fill, and review a guest's forms from the appointment or guest profile
  • Customer Mobile App β€” Guests fill required forms on their own phone

Licensing and feature requirements

The forms module requires specific licenses and organizational settings:

  • The custom fields feature must be enabled for the Form creation section of Configuration > Forms to be visible.
  • The Enable dot phrases toggle (Configuration > Business details > Business setup > Features) must be on for the Dot phrases section and settings to appear.
  • The service entities feature must be enabled for custom entity management.
  • The form builder requires the V3 form setting to be enabled. When disabled, only V1 and V2 form types are available.
  • The Employee Survey form type requires the employee survey setting to be enabled.
  • The Class form type requires the classes setting to be enabled and the Training / Classes module license.

Data structure and custom fields

Forms are built using custom fields that define the data collection structure:

  • Guest custom fields β€” Stored at the guest profile level, persisting across all interactions.
  • Service custom fields β€” Captured per service instance, maintaining service-specific data.
  • Custom list β€” Reusable value sets for dropdown and radio button fields that ensure consistent data entry across forms.
  • Custom entities β€” Equipment, room, or resource types with their own custom attributes.

Key features

  • Dynamic forms (Forms on the Fly) β€” Add forms to appointments at appointment time without pre-configured service associations.
  • Dot phrases β€” Text shortcuts that expand into longer phrases during form filling. Type a period (.) followed by a short code in V3 form text fields to insert predefined text.
  • Review workflows β€” Optional review requirements with assignee management, automatic signature appending, and bulk review capabilities.
  • Compliance tracking β€” Automated monitoring of form submission rates by center and employee job role with daily statistics and review randomization.
  • Job-based permissions β€” Role-specific form access controls determining which providers can view or fill specific forms.
  • Form associations β€” Flexible linking between forms and services with visit mode controls (first visit only, subsequent visit only, or always).
  • Import and export β€” Bulk form definition management and .zenform file format for transferring V3 form designs between organizations.
  • Audit logging β€” Comprehensive tracking of form interactions including opens, saves, submissions, reviews, field changes, and AI-assisted fills.
  • Guest authentication β€” Configurable sign-in enforcement for online form access, separately controllable per form type (guest, service/tag, loyalty, membership, package).
  • Form versioning β€” Active, Deprecated, and Draft version statuses let you publish new versions while preserving historical data.
  • Macro substitution β€” Server-side macro resolution for guest, center, service, membership, package, entity, and custom macros.
  • Form builder components β€” Modern drag-and-drop form builder with text fields, selection fields, signatures, annotation pads, tables, file uploads, layout tools, and guest information auto-binding.
  • Auto-save β€” When the form auto-save setting is turned on, the system periodically saves form-fill progress in the background so providers do not lose work if a session is interrupted. See Configure form settings.
  • Localization β€” V3 forms support translation into all active organization languages.
  • HIS integration β€” Emirates ID card reader integration for health information system-connected forms.

UK clinics: if your organization operates under CQC oversight, see How Zenoti supports CQC compliance (UK) for the related Forms surface.

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