ZenotiHelp

Additional Guest Details Step

ZTZenoti Docs Team Updated September 7, 2026 4 min readGuide

The guest kiosk may present an Additional details step during the check-in or booking flow, asking guests to provide supplementary profile information before they proceed. This article explains what the step shows, how validation works, and what guests and staff should expect.

Audience: Front desk staff and kiosk administrators who configure or support the guest kiosk at their center.


On this page


Before you begin

  • The new guest kiosk must be enabled at both the organization level and the center level before guests can encounter this step. For setup instructions, see Set up new kiosk.
  • The Additional details step appears only when your center has configured supplementary profile fields to be collected during the kiosk flow. If no such fields are configured, guests skip this step entirely.
  • The kiosk operates under a guest token. No staff permissions are required to interact with this step as a guest. To configure which profile fields are collected, you need standard Edit access on the Organizations security object.

How the Additional details step works

When the kiosk is configured to collect supplementary profile information, guests see the Additional details step as part of the self-service flow. The screen displays the heading Please provide the following details and presents one or more input fields for the guest to complete.

The step appears between other kiosk flow steps β€” such as guest identification and service selection β€” and the guest must address any required fields before they can proceed.

Note: The Additional details step appears on the new kiosk only. The legacy kiosk handles supplementary profile collection differently, using the Prompt guest to collect their information and consent center setting.

Legacy experience: On the legacy kiosk, when Prompt guest to collect their information and consent is enabled, the kiosk surfaces profile and consent fields in a separate collection screen. The layout and placement of that screen differ from the Additional details step on the new kiosk.

What guests see

When the Additional details step is active:

  1. The screen heading reads Please provide the following details.
  2. Each configured supplementary field is listed with its label and an input control appropriate to the field type.
  3. Fields marked as required are enforced β€” guests cannot proceed until they complete them.
  4. After completing the fields, the guest selects the action to continue to the next step.

Field validation on the Additional details step

The kiosk validates field entries as the guest submits the step. Two inline validation messages can appear:

Situation Message displayed
A required field is left blank {field name} is required
A field value does not match the expected format {field name} is invalid

In both messages, {field name} is replaced with the label of the specific field that failed validation. For example, if a date of birth field is left blank and the field is required, the guest sees a message indicating that the date of birth is required.

Note: Validation messages appear inline, directly associated with the field that caused the issue. Guests can correct the value and resubmit without losing information entered in other fields.

Worked example

A center configures the Additional details step to collect a guest's date of birth using a DD/MMM/YYYY date field, and marks this field as required.

  • If the guest taps Proceed while leaving the date of birth blank, the kiosk displays: Date of birth is required
  • If the guest enters text in an invalid format β€” for example, typing letters where a date is expected β€” the kiosk displays: Date of birth is invalid

The guest corrects the entry and proceeds. No other fields on the screen are cleared.

Tips

  • Keep required fields to a minimum. Every required field on the Additional details step adds friction to the guest's check-in experience. Limit required fields to information that is genuinely necessary before the service can proceed.
  • Use field labels that are self-explanatory. The validation messages display the field label verbatim (for example, Date of birth is required). Clear, plain-language labels make validation messages easier for guests to understand without staff assistance.
  • Test the step before go-live. After configuring supplementary fields, walk through the kiosk flow as a guest and intentionally leave required fields blank, then enter invalid formats, to confirm that both validation messages display correctly.
  • Review the forms step separately. The Additional details step collects profile-level supplementary fields. Service-specific or consent forms are presented at the Fill out the forms to provide the necessary information step, which appears separately in the flow. Do not conflate the two. For forms configuration, see Complete forms at new kiosk.

Troubleshooting

The Additional details step does not appear for guests.

The step only displays when supplementary profile fields have been configured for the kiosk flow at this center. If no fields are configured, the step is skipped automatically. Verify that at least one supplementary profile field has been added and is set to appear at the kiosk. If the setting is confirmed but the step still does not appear, confirm that the new kiosk is fully enabled at both the organization level and the center level β€” see Enable New Kiosk β€” Organization and Center Gating.

A required field does not show a validation message when left blank.

Confirm that the field is explicitly marked as required in the field configuration. A field that is configured as optional will not trigger the {field name} is required message; the guest can leave it blank and proceed normally.

Guests report seeing a validation message they do not understand.

The validation message uses the field's configured label verbatim. If the label is unclear β€” for example, an internal code name or an abbreviated string β€” update the field label to plain language so that the resulting message reads naturally to guests (for example, Date of birth is required rather than DOB is required).

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