ZenotiHelp

Kiosk FAQ

ZTZenoti Docs Team Updated September 16, 2026 10 min readFAQ

Answers to common questions about the guest self-service kiosk in Zenoti.


On this page


Before you begin

The following answers apply when the legacy guest kiosk is enabled at both the organization level (Enable Kiosk) and the center level (Enable Kiosk mode). For the new kiosk, the corresponding activation settings are Enable new Kiosk at both scopes (same label at org and center). A center runs either the legacy or the new kiosk, not both.

How do I set up the guest kiosk?

Enable the legacy kiosk by turning on Enable Kiosk at the organization level and Enable Kiosk mode at the center level. Once enabled, the legacy kiosk is available as a standalone page that you load on a tablet or touchscreen device at your center. For remote guest access, also turn on Enable online kiosk (Deprecated) at the organization level.

Enable the new kiosk by turning on Enable new Kiosk at both the organization level and the center level. The new kiosk runs as a native mobile app (ZMA (Zenoti Mobile App) or ZKA) and supports the full self-service journey: check-in, payment, tips, donations, and post-service feedback. See New Kiosk overview for details.

For the full setup guide including branding and display options, see Set up the guest kiosk.

Can guests register as new guests at the kiosk?

Legacy kiosk: Yes, if the Allow new guests to sign up at the Kiosk center setting is enabled. When a guest enters their phone number or email and no matching profile is found, the legacy kiosk offers an Add New Person action that opens a registration form. The form collects the guest's first name, contact information, and optional fields such as date of birth, gender, and referral source.

New kiosk: No β€” the new kiosk does not support in-app new-guest registration. When the kiosk cannot find a matching profile, it shows a QR code that redirects the guest to the Webstore. The guest registers and books on the Webstore, then returns to the kiosk to check in.

For details, see Identify and register guests at the kiosk.

Does the kiosk support payments?

Yes. The kiosk supports credit card prepayment using PCI-compliant payment processing. After check-in, the guest can enter card details for prepayment or card-on-file storage. When auto-pay is enabled at both the organization and center level, the system can automatically pre-authorize payment using the card on file. The kiosk also supports a self-checkout flow with tipping, donations, and receipt delivery options.

For details, see Process payments at the kiosk.

Can guests rebook their next appointment at the kiosk?

Yes. After their service is completed, the kiosk can display a feedback screen followed by a rebook flow. The guest selects a preferred date and time using a date picker, and the system checks availability and books the follow-up appointment. The rebook flow appears after feedback collection when Collect Feedback is enabled, or the guest can skip directly to rebooking.

For details, see Collect feedback and rebook at the kiosk.

How do guest forms work at the kiosk?

Guest forms on the kiosk are controlled by three settings that decide which forms are shown, whether the guest must complete them before check-in, and how forms can be delivered by email instead of inline on the device.

  • Block check-ins if forms are not filled (center setting, default off). When this setting is on, the kiosk disables the check-in action until the guest has completed every form assigned to their appointment. When it is off, the guest can skip forms and proceed straight to check-in.

  • Hide internal service and tag forms (center setting, default off). When this setting is on, forms flagged internal (internal service forms and tag forms) are not shown on the kiosk screen, so the guest only sees public, guest-facing forms. If an internal form has its own Email form link property turned on, that form is still excluded from the kiosk screen but its link is emailed to the guest.

  • Email form link (per-form property, not a center setting). Turning this on for a specific form causes that form to be emailed to the guest with a deep link instead of being rendered inline on the kiosk. This property is set on the form itself, not at the center level.

How the three interact:

  • When Hide internal service and tag forms is on, internal forms disappear from the kiosk screen. Any internal form that has Email form link on is emailed instead β€” the guest completes it from their own device.
  • When Block check-ins if forms are not filled is on, the guest must complete every form that appears on the kiosk screen before check-in is enabled. Forms that were hidden (either because they are internal and hidden, or because they were emailed out of band) do NOT count toward this requirement β€” only the forms actually shown on the kiosk are required to proceed.
  • When both settings are off, the kiosk shows every assigned form and the guest may skip them and still check in.

For details on configuring these settings, see Configure kiosk settings.

What devices and browsers are supported?

The guest kiosk is a web application that runs in a modern browser. It is optimized for tablet-sized touchscreen devices (10-inch and above) in landscape orientation. The kiosk works on:

  • iPads -- Safari or Chrome. All iPad models are supported, including iPad Mini.
  • Android tablets -- Chrome. Requires Android 10 or later.
  • Windows touchscreen devices -- Chrome or Edge.
  • Desktop browsers -- any modern browser, typically used for testing and for online kiosk mode.

Not supported:

  • Amazon Fire tablets (Fire OS / Silk browser) are not a supported kiosk device. Even though the kiosk is a responsive web app, Zenoti does not validate behavior on Fire OS and you should not deploy the kiosk on Fire tablets in-store.

For the best in-store experience, use a dedicated tablet mounted at the reception area with the kiosk URL loaded in full-screen or kiosk mode in the browser. For device lockdown instructions, see Set up the guest kiosk.

The kiosk keeps crashing or windows close unexpectedly

The kiosk runs in a browser, so the usual cause is browser state rather than the kiosk itself. Work through these in order:

  1. Allow third-party cookies. Blocked third-party cookies are the most common reason windows close on their own mid-session. See Troubleshoot Windows cookie issues.
  2. Clear the cache and cookies for the kiosk device, then reload the kiosk URL and sign in again.
  3. Check for sign-in problems specific to the browser. See Troubleshoot login and browser issues.
  4. Rule out slowness rather than a crash. A device that appears to freeze is often struggling for a different reason β€” see Troubleshoot slow or unresponsive Zenoti.
  5. Confirm the device is supported. Amazon Fire tablets are not a supported kiosk device β€” see What devices and browsers are supported?.

If the kiosk still crashes after all five, note the device, browser and version, and the step in the guest journey where it fails, and contact Zenoti support with those details.

Does the kiosk work offline?

No. The kiosk requires an active internet connection to function. Every step -- guest identification, service loading, provider availability, slot reservation, and payment processing -- requires real-time communication with the Zenoti server. If the internet connection drops during a kiosk session, the guest sees an error message and the session cannot continue until connectivity is restored.

Ensure your center has a reliable Wi-Fi or wired network connection for kiosk devices.

Can the kiosk display in multiple languages?

Yes. The kiosk supports localized text through Zenoti's translation system. When your organization operates in multiple languages, the kiosk loads the appropriate translation files based on the center's language configuration. Labels, messages, and prompts are translated for the login screen, service selection, check-in, payment, and feedback screens.

If a translation is not available for a specific label, the kiosk falls back to the default English text.

For details, see Customize kiosk branding and display.

How does the kiosk handle group bookings?

When the Enable Group booking center setting is enabled, the kiosk supports four booking types:

  • Single -- standard one-guest booking (default)
  • Group -- multiple guests with different services or providers
  • Bulk -- multiple guests with the same service
  • Couples -- two guests with simultaneous services

The primary guest identifies themselves first, then adds other guests to the booking. The kiosk validates slot availability for all guests before confirming. All guests in the group are checked in simultaneously.

For details, see Check in and manage appointments at the kiosk.

What happens if a guest's card payment fails?

If a card payment fails during prepayment or card-on-file storage, the kiosk displays an error message and prompts the guest to try again with the same card or enter a different card. Common reasons for payment failure include:

  • Invalid card number or expired card
  • Insufficient funds (for prepayment charges)
  • Network connectivity issues during tokenization
  • Card issuer declined the transaction

If the guest cannot complete payment on the kiosk, they can skip the payment step (if the center's configuration allows) and complete payment at the front desk instead.

For details, see Process payments at the kiosk.

How does the kiosk protect guest data?

The kiosk implements several data protection measures:

  • Session timeout -- after check-in, the kiosk automatically returns to the login screen after a configurable countdown (default: 30 seconds). This prevents the next guest from seeing the previous guest's information.
  • No local data storage -- the kiosk does not store guest data locally on the device. All data is retrieved from and saved to the Zenoti server in real time.
  • PCI-compliant payments -- credit card details are sent directly to the payment processor for tokenization. Card numbers are never stored on the kiosk device or in Zenoti.
  • OTP verification -- optional one-time password verification can be enabled to confirm guest identity during login or card-on-file operations.

For payment security details, see Process payments at the kiosk.

Can guests receive wait time notifications?

Yes. When Enable wait time notifications for guests is turned on at the center level, guests receive alerts as their turn approaches. You can configure threshold notifications that alert the guest when their estimated wait time drops below configurable values (for example, 30 minutes remaining and 5 minutes remaining).

Notifications are sent via SMS or email based on the guest's contact information on file.

For details, see Configure wait time notifications.

Does the kiosk support tipping and donations?

Yes, in the self-checkout flow. After a guest's service is completed, the checkout screen presents:

  • Tip options -- preset percentages (10%, 20%, 30%) and a custom amount field. For group appointments with multiple providers, the guest can assign a separate tip to each provider.
  • Donation options -- a short list of preset donation amounts configured by your center (commonly $1, $3, and $5) plus a custom amount field for charitable contributions.

Tipping and donations are part of the self-checkout flow and are added to the invoice total before payment.

For details, see Process payments at the kiosk.

Why do inactive forms still appear on the kiosk?

If a form is set to Inactive in Zenoti but remains assigned to a service, the legacy kiosk may still display it during the check-in flow. To stop a form from appearing on the kiosk, remove the form's assignment from the service in addition to deactivating it. Deactivation alone does not remove an existing service-form assignment.

Can centers have a different logo on the kiosk?

Displaying a center-specific logo on the kiosk (rather than the organization-level logo) requires a configuration change by Zenoti. Contact Zenoti Support to request per-center logo customization. You cannot configure center-specific logos directly from the Zenoti settings panel.

Can I launch the kiosk from the Zenoti Mobile App?

Yes. When Enable Kiosk relaunch from ZMA is turned on at the organization level, the Customer Kiosk option appears in the ZMA settings menu. To launch the kiosk from ZMA:

  1. Open the Zenoti Mobile App on the tablet.
  2. Tap Settings.
  3. Select Customer Kiosk.

The legacy kiosk opens. To exit and return to ZMA, tap Cancel on the kiosk screen. Note that exiting requires re-entering ZMA credentials.

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