Kiosk Entry Mode β Check-In, Pay, and Book-Future Route Values (New Kiosk)
The new guest kiosk supports three named entry modes that control which workflow a guest sees when they arrive at the kiosk screen. Each mode is passed to the kiosk via a route query string value, so your team or integration can deep-link guests directly into the correct flow β checking in to an existing appointment, paying an outstanding invoice, or booking a future appointment β without requiring the guest to navigate from the welcome screen.
Audience: Center administrators and IT staff who configure kiosk URL routing or integrate the guest kiosk with third-party signage, queue displays, or booking confirmation flows.
On this page
Before you begin
- The new guest kiosk must be active at both the organization level and the center level before entry mode routing has any effect. For activation steps, see Enable New Kiosk β Organization and Center Gating.
- Confirm that the center is running the new kiosk, not the legacy kiosk. A center runs one generation at a time; entry mode route values described in this article apply to the new kiosk only.
- Entry mode routing is typically configured by whoever constructs the kiosk URL β a system administrator, an IT team member, or a third-party integration. Front desk staff who only operate the kiosk do not need to perform these steps.
- No additional staff permissions are required to append a query string to the kiosk URL. Admin kiosk settings require standard Edit permission on the Organizations security object.
Note: Entry mode routing does not bypass guest identification. Regardless of which entry mode is active, the kiosk always presents the guest identification step first so the system can match the guest to their record.
Steps
Understand the three entry modes
The new kiosk recognizes three entry mode values that you pass as a route query string. Each value launches the kiosk into a specific starting workflow.
The table below describes each mode and the guest experience it produces.
| Entry mode value | Guest workflow | Typical use case |
|---|---|---|
checkin |
The guest is guided through check-in for an existing appointment. After identification, the kiosk displays the Who's checking in? screen and walks the guest through service confirmation and check-in completion. | A QR code or NFC tap on an appointment reminder email routes the guest directly to check-in. |
pay |
The guest is guided to pay an outstanding invoice. After identification, the kiosk displays the outstanding balance and the Select Payment Method screen. | A display at the reception desk prompts guests with a balance to tap and pay before leaving. |
book-future |
The guest is guided to book a future appointment. After identification, the kiosk presents the service catalog and slot selection flow. The guest can choose a future date when Enable future date bookings is on at both the organization and the center; otherwise the booking is for today. | A post-service screen or lobby display invites guests to book their next visit before they leave. |
Important: The new kiosk books same-day by default. The
book-futureentry mode lets guests choose a future calendar date only when Enable future date bookings is on at both the organization and the center (off by default). With the setting off, the booking is for today.
Pass an entry mode via route query string
To launch the kiosk in a specific mode, append the entryMode query parameter to the kiosk URL you use for the device or integration.
The general format is:
https://<account-name>.zenoti.com/kiosk?entryMode=<value>
Replace <account-name> with your Zenoti organization's account name and <value> with one of the three recognized values: checkin, pay, or book-future.
Example URLs:
| Intent | URL |
|---|---|
| Direct guests to check in | https://example.zenoti.com/kiosk?entryMode=checkin |
| Direct guests to pay a balance | https://example.zenoti.com/kiosk?entryMode=pay |
| Direct guests to book an appointment (a future date when future date bookings are on) | https://example.zenoti.com/kiosk?entryMode=book-future |
You can provide these URLs as:
- A QR code printed on appointment confirmation cards, reminder emails, or lobby signage.
- A direct browser URL entered as the home page on the kiosk device.
- A deep link embedded in a third-party queue display or digital signage system.
Tip: If your center uses a single kiosk for all guest actions, use the plain kiosk URL without an
entryModeparameter. The kiosk defaults to the check-in flow, which suits most general-purpose installations.
Understand the fallback behavior
If the entryMode query string value is absent, misspelled, or contains a value the new kiosk does not recognize, the kiosk automatically falls back to Check-in mode. The guest always reaches a valid starting point β no error screen is shown and no manual intervention is required.
The fallback applies in all of these situations:
- The URL contains no
entryModeparameter (plain kiosk URL with no query string). - The
entryModeparameter is present but the value is empty (for example,?entryMode=). - The
entryModeparameter contains an unrecognized value (for example,?entryMode=walkinor?entryMode=checkout).
Important: Only the three values listed in the table above β
checkin,pay, andbook-futureβ are recognized. Any other value, including variations in capitalization or spacing, triggers the fallback.
Worked example: A center creates a QR code for a lobby sign intended to let guests pay their balance. A staff member accidentally types ?entryMode=payment instead of ?entryMode=pay. When a guest scans the QR code, the kiosk receives an unrecognized value and falls back to check-in mode. The guest sees the Who's checking in? screen instead of the payment screen. The staff member corrects the URL and regenerates the QR code.
Tips
- Test each entry mode URL before going live. Scan the QR code or navigate to the URL on the kiosk device and confirm that the correct starting screen appears. Verify that the
paymode surfaces the Select Payment Method screen and that thecheckinmode surfaces the Who's checking in? screen. - Use lowercase for query string values. The recognized values β
checkin,pay, andbook-futureβ are lowercase. Although the kiosk may tolerate minor casing variations in some environments, always use lowercase to avoid triggering the unrecognized-value fallback. - Keep
book-futureURLs current with your center's operating hours. When Enable future date bookings is off at either level, abook-futureURL only presents open slots for today, and guests who arrive after the last bookable slot for the day will see no available times. Consider suppressing thebook-futurelink on lobby signage after a certain hour, or turning future date bookings on, to avoid confusion. - Combine entry mode routing with the device home-page setting. Set the kiosk device's browser home page to the appropriate entry-mode URL so the device always resets to the correct mode after a session ends or the browser restarts.
- Document your entry mode URLs in your center's internal runbook. Storing the exact URLs (including the query string) alongside QR code source files prevents staff from regenerating codes with incorrect parameters.
Troubleshooting
The kiosk is showing the check-in screen even though the URL contains ?entryMode=pay.
The kiosk may be receiving an unrecognized entry mode value. Check the following:
- Confirm the URL uses exactly
?entryMode=payβ no extra characters, spaces, or capitalization differences. - If the URL was embedded in a QR code, regenerate the QR code from the corrected URL and test by scanning with a second device before replacing the printed version.
- Confirm the new kiosk is active for the center. If the center is still running the legacy kiosk, entry mode routing for the new kiosk has no effect. See Enable New Kiosk β Organization and Center Gating.
Guests scanned the book-future QR code but see no available appointment slots.
When Enable future date bookings is off at either the organization or the center, new kiosk booking covers the current day only. If all bookable slots for the day are full or the center's working hours have ended, the slot selection screen will show no options. If the setting is on at both levels, the guest can choose another date. Possible resolutions:
- Advise guests to speak with the front desk to book for a future date.
- Remove or cover the
book-futureQR code or signage after the center's last bookable slot for the day. - For future-date booking capability, refer guests to the Webstore or contact your Zenoti administrator. For appointment scheduling, see Appointment scheduling.
The pay entry mode routes the guest to check-in instead of a payment screen.
This typically means the guest has no outstanding invoice that the kiosk can locate after identification, or the entry mode value was not recognized. Check the following:
- Verify the URL value is exactly
pay(lowercase, no extra characters). - Confirm the guest has an outstanding invoice on their account. If the invoice has already been settled, the kiosk has nothing to surface in payment mode.
- For POS payment details, see Payment and invoices.