Use guest forms on Webstore, kiosk, and the Customer Mobile App
Guests can fill forms through the Webstore, the kiosk, and the Customer Mobile App in addition to the admin interface. Zenoti supports multiple form types for guest self-service: guest custom forms, service custom forms, loyalty forms, membership forms, and package forms. This article covers how guests interact with forms across each guest-facing surface, including sign-in enforcement, form link sharing, and the kiosk check-in form flow. Providers fill forms with guests in MyZen, Zenoti's employee app β see Use forms in MyZen.
Note: For conceptual background on form types and their platform availability, see Forms overview.
Audience: Administrators and front desk staff who configure and support guest-filled forms on the Webstore, the kiosk, and the Customer Mobile App.
On this page
- Before you begin
- Guest forms on the Webstore
- Guest sign-in enforcement
- Form link sharing
- Fill a form via email link or Webstore
- Kiosk form flow
- Skip forms on the kiosk
- Handle a form version update on the kiosk
- Guest forms in the Customer Mobile App
- Fill a service form during an appointment
- Membership form action types
- Tips
- Troubleshooting
Before you begin
- Guest-facing forms must be configured and associated with the appropriate services, memberships, or loyalty programs. See Forms overview.
- Guest access to forms is controlled by protection settings configured at the organization level. These determine whether guests must sign in before filling specific form types.
- For kiosk forms, the kiosk must be configured and operational at the center. For kiosk setup and hardware configuration, see the Point of Sale category.
- Administrators manage form settings at Configuration > Forms. See Configure form settings.
Permission: Edit under Service Custom Data in the Appointment Book section of the security role β Required for administrators to configure form associations and protection settings that control guest form access, and to edit service form data submitted by a guest.
Permission: Edit under Guest Custom Data in the security role β Required to view and edit guest profile form data submitted by a guest.
Note: Guest access to Webstore and kiosk forms is controlled by protection settings, not by direct admin permissions. Administrators configure which form types require guest sign-in through the form settings. See Configure form settings.
Steps
Guest forms on the Webstore
The Webstore supports five form types for guest self-service:
| Form type | Description |
|---|---|
| Guest custom form | Captures guest profile-level data such as medical history, preferences, or intake information. |
| Service custom form | Captures service-specific data tied to an appointment, such as consent forms or treatment notes. |
| Loyalty form | Captures data during loyalty program enrollment. |
| Membership form | Captures membership agreement data during enrollment, cancellation, freeze, renewal, upgrade/downgrade, or transfer actions. |
| Package form | Captures data related to package purchases. |
Each form type has its own Webstore component. When a guest navigates to the appropriate page or clicks a form link, Zenoti loads the correct form type and renders it for the guest to fill.
Note: Form builder forms require Webstore V2. If your organization uses Webstore V1, form builder forms are not supported. Contact Zenoti support to enable Webstore V2 if needed.
Guest profile form
The guest profile form captures data held against the guest record rather than against a single appointment.
- The guest opens the form link or navigates to the forms page on the Webstore.
- If guest data protection is enabled, the guest signs in first.
- The guest fills the form and submits it. The data is saved to the guest record.
- The guest can switch between the form and their guest details to correct profile information such as name, email address, or mobile number without leaving the page.
If the link has expired, the Webstore shows an expiry message instead of the form.
Service and class form
The service form captures data tied to a booked service, and the same component also presents class-level forms for guests enrolled in a class.
- The guest opens the form link for the appointment or class, or selects the form from the Webstore.
- If service data protection is enabled, the guest signs in first.
- The guest fills the form and submits it. The submitted data is stored against the appointment or class enrollment, where the provider can review it.
Loyalty enrollment form
The loyalty form collects the information your organization requires when a guest enrolls in a loyalty program online. The guest fills and submits the form as part of enrollment. If loyalty data protection is enabled, the guest signs in before the form opens.
Membership agreement form
The membership form presents the agreement a guest must complete for a membership lifecycle action β signup, cancellation, freeze, renewal, upgrade/downgrade, or transfer. The action the guest is performing determines which form is shown. See Membership form action types below. If membership data protection is enabled, the guest signs in before the form opens.
For membership-specific form enforcement and PDF sending during lifecycle actions, see Memberships overview.
Package form
The package form captures the information your organization requires when a guest buys or uses a package online. If package data protection is enabled, the guest signs in before the form opens. For how package forms are associated, see Package form association.
Guest sign-in enforcement
Your organization can require guests to sign in before filling certain form types on the Webstore. When a protection setting is enabled for a form type, the guest must authenticate before they can view or fill the form.
Sign-in enforcement is configured per form type:
- Guest data protection β Requires sign-in for guest custom forms.
- Service data protection β Requires sign-in for service and tag forms.
- Loyalty data protection β Requires sign-in for loyalty forms.
- Membership data protection β Requires sign-in for membership forms.
- Package data protection β Requires sign-in for package forms.
When protection is enabled, guests who click a form link or navigate to the form page are prompted to sign in first. After successful authentication, the form loads and the guest can proceed.
Note: A form configured as Make this form read-only for guests (applies to Webstore and CMA) displays to the guest in read-only mode on the Webstore and in the Customer Mobile App. The guest can view but not edit the form fields.
Form link sharing
Zenoti generates shareable form URLs that you can send to guests via email or text. These links direct the guest to the Webstore form page.
Form links have a configurable expiry time. Once a link expires, the guest sees an expiry message and must request a new link. The expiry duration is set at the organization level through the form URL expiry setting.
To include form links in appointment notifications, enable the send link in notifications flag on the form-service association. When enabled, the form link is included in the appointment confirmation or reminder sent to the guest. The same association also sets the visit mode β whether the form is requested on the guest's first visit, on subsequent visits, or always β which determines when the link is sent. See Assign forms to services and Configure form notifications.
Fill a form via email link or Webstore
Guests can fill forms by clicking a link in an email or text notification, or by navigating to the forms section on the Webstore.
- The guest clicks the form link in the email or text notification, or navigates to the form through the Webstore.
- If sign-in is required, the guest authenticates with their credentials.
- The system loads the form. Pre-populated fields display the guest's name, appointment details, and other context-specific data.
- The guest completes the form fields.
- The guest clicks Submit to save and submit the form.
Note: The system confirms the submission. The form data is stored with the guest's record or appointment.
If the form link has expired, the guest sees an expiry message. They must request a new link from the center or wait for a new notification.
Worked example: Priya books a 60-minute deep tissue massage at your Riverside center through the Webstore. The service has one associated service custom form, Massage Intake, set for the first visit with the notification flag enabled, and the form URL expiry is set to 72 hours. Priya receives the confirmation email with the form link. Because service data protection is enabled, she signs in with the email address on her guest profile before the form opens. The first two fields already show her name and appointment time. She fills the remaining fields and clicks Submit. When she arrives and taps her name on the kiosk, the Forms page shows no outstanding forms, so she taps Check-in immediately. Her therapist opens the appointment and sees Massage Intake with a Filled status.
Kiosk form flow
The kiosk presents forms to guests at two distinct points: during appointment booking and during check-in. Both flows display any forms associated with the service that the guest has not yet filled.
The kiosk form selection screen
The Forms page on the kiosk lists every form the guest still needs to complete for that visit β both guest profile forms and service forms β with the fill status of each.
- The guest reviews the list of forms on the Forms page.
- The guest taps a form in the list to open it.
- The guest fills the form and submits it. The list updates to show the new status, and the guest taps the next form.
Booking-time form flow
When a guest books an appointment at the kiosk and the selected service has associated forms, the kiosk presents the forms before confirming the appointment:
- The guest logs in to the kiosk using their phone number or email address.
- The guest selects a service and a provider and taps Confirm.
- The kiosk displays the Forms page with all forms required for that service.
- The guest completes each form. If multiple forms are required, the guest uses Save & Fill Next Form to move through them in sequence.
- After all forms are submitted, the guest taps Check-in. The appointment is confirmed and the guest is placed in the queue.
Note: The Forms page only appears if the selected service has at least one associated form. If no forms are required, the appointment is confirmed directly.
Check-in-time form flow
When a guest checks in for an existing appointment at the kiosk, the kiosk presents any unfilled forms before completing the check-in:
- The guest opens the kiosk home page (by navigating to the kiosk URL or launching the kiosk from the Zenoti Mobile iOS settings).
- The kiosk home page shows the guest list and their queue position.
- The guest taps their name. A phone number confirmation popup appears.
- The guest enters the last 4 digits of their phone number and taps Submit.
- The kiosk displays the Forms page with all unfilled forms for the appointment.
- The guest selects and fills each form. Use Save & Fill Next Form to navigate between multiple forms.
- After submitting all forms, the guest taps Check-in. A "You are Checked-In" confirmation appears.
- The guest taps OK and returns to the kiosk home page with their updated queue position.
Note: If a mandatory form field is left empty, the kiosk displays an alert asking the guest to complete the field before proceeding.
Skip forms on the kiosk
Depending on your organization's configuration, guests may be allowed to skip forms during kiosk check-in.
- Fill Later β The guest can skip the current form and return to it later. The check-in continues with the remaining forms.
- Continue Without Forms β The guest can skip all remaining forms and complete the check-in. Skipped forms keep a Not Filled status for the provider to address later.
Availability: Fill Later and Continue Without Forms appear only when your organization's kiosk configuration permits check-ins with unfilled forms.
If your organization requires all forms to be completed before check-in, the skip option is not available and the guest must fill all forms to proceed.
Handle a form version update on the kiosk
If a provider publishes a new version of a form while a guest is filling it on the kiosk, the kiosk detects the version change and prompts the guest to switch to the latest version.
- If the current draft has no unsaved changes, the kiosk loads the new version automatically.
- If the current draft has unsaved changes, the kiosk displays a warning and lets the guest choose to keep their draft on the old version or switch to the new version. Switching discards the unsaved draft.
Guest forms in the Customer Mobile App
Guests can also fill their required forms on their own phone in the Customer Mobile App. Guest profile forms, service forms, and membership agreement forms are all available there, and the data a guest submits in the Customer Mobile App appears in the same guest record or appointment as data submitted on the Webstore or kiosk. See Digital forms.
Providers fill and review forms with the guest in MyZen, Zenoti's employee app β see Use forms in MyZen.
Fill a service form during an appointment
Forms a guest did not complete on a guest-facing surface remain available to the provider during the appointment. The provider opens the appointment, selects the form, and fills the remaining fields with the guest. Anything the guest already submitted online is shown in the same form, so the provider continues from where the guest stopped rather than starting again.
- The provider can select Save as draft to keep the entries without submitting. The message Form saved as draft confirms the save.
- Submitting the form shows Form submitted successfully and sets the form to a Filled status.
- A form can be locked for editing depending on the appointment status and your organization's restrict-editing configuration. When a form is locked, the fields are read-only.
For the full in-appointment procedure, including adding a dynamic form (Forms on the Fly) and reviewing submitted data, see Use forms in appointments.
Membership form action types
Membership forms support specific action types that determine when the form appears during the membership lifecycle:
| Action type | When the form appears |
|---|---|
| Sign-Up | During new membership enrollment. |
| Cancellation | When the guest cancels their membership. |
| Freeze | When the guest freezes their membership. |
| Upgrade/Downgrade | When the guest changes to a different membership tier. |
| Transfer | When the membership is transferred to another guest or center. |
| Renewal | When the guest renews their membership. |
| Locker | When the guest is assigned or manages a locker associated with their membership. |
Each membership form definition specifies which action types it applies to. The system displays the appropriate form based on the lifecycle action the guest is performing on the Webstore.
Tips
Tip: Enable guest sign-in for sensitive form types (such as membership agreements and medical intake forms) to protect guest data and ensure the correct guest is filling the form.
Tip: Set a reasonable form URL expiry time. Too short may cause frustration if guests do not fill the form immediately. Too long may pose a security concern for sensitive data.
Tip: Match the visit mode on each form-service association to how often you need the data. Set intake forms to the first visit so returning guests are not asked to refill them, and reserve the always option for consent forms that must be signed at every visit.
Tip: Check outstanding forms before the day starts. The Service forms report lists forms by submit status so the front desk can send links ahead of arrival instead of handing guests a form at the kiosk.
Troubleshooting
| Problem | What to check |
|---|---|
| The guest reports that the form link shows an expiry message. | The link is past the form URL expiry duration set for your organization. Send the guest a new link, and consider a longer expiry if guests often fill forms days after booking. |
| The guest is asked to sign in and cannot get past the sign-in screen. | The protection setting for that form type requires sign-in. Confirm the email address or mobile number the guest is using matches the one on their guest profile, correct the profile if needed, and resend the link. The guest can also fill the form at the center on the kiosk. |
| The form link is not included in the appointment notification. | Confirm the send link in notifications flag is enabled on the form-service association and that the visit mode matches the guest's visit. If Zenoti reports "Link to form could not be sent as the guest has an invalid email address", correct the email address on the guest profile and resend. |
| An expected form does not appear on the kiosk Forms page. | The kiosk lists only unfilled forms associated with the booked service. Confirm the form is associated with that service, that the visit mode applies to this visit, and that the guest has not already submitted it. |
| The guest submitted a form online but the provider does not see the data. | Confirm the guest submitted against the correct appointment, and reopen the form from the appointment. If the form definition was republished after the guest submitted, the provider may be viewing a newer version β see Handle a form version update on the kiosk. |
| The kiosk shows an alert and will not advance to the next form. | A mandatory field is empty. The guest must complete the highlighted field before the kiosk accepts the submission. |