Confirmation Requests
The Confirmation Requests feature is only released in the Japan market.
This page is used to configure guest check-in confirmation requests. The Confirmation Requests page is only shown to users with the Administrator role.
- Enable Confirmation Requests: Enable/disable feature. Default value is false.
- Automatic Confirmation Timeout Seconds
- Configures after how many seconds will the Kiosk Client continue with the check in operation without staff confirmation. The default value is 60 seconds.
- If set to 0 seconds, staff confirmation is required to continue the check in process.
- Confirm / Deny Timeout Seconds
- Configures after how many seconds of inactivity (i.e. lack of staff confirmation) will the application raise the not confirmed pop-up. The default value is 60 seconds.
- This setting is only used when automatic confirmation is set to 0.
- Confirmation Requests Webhook
- Webhook name for sending external notifications to confirm check in.
- This needs to be set to the webhook URI of the UIP trigger responsible for sending confirmation notifications to external messaging systems.
- Typically, this will be confirmation.
- Leave this setting empty if an external notification system is not required.
- Webhook name for sending external notifications to confirm check in.
Staff confirmation fields are listed and are based on the Guest Details feature fields. The guest details feature must be enabled in order to populate fields which are not part of the reservation.
- Name
- Matches the Translation Key of the Guest Details field to be shown when confirming a guest check-in.
- Mandatory string, accept any digits, letters and underscores chars w/o spaces.
- Display Name
- The text that Kiosk Admin will show for each field on the Guest Check-In Confirmation page.
- Display in Confirmation Page
- Boolean value, to be interpreted as:
- True => show field in Kiosk Admin → Guest Check-In Confirmation
- False => field is not shown in Kiosk Admin → Guest Check-In Confirmation
- Boolean value, to be interpreted as:
A default list is provided as an example. The list can be modified by editing, adding, or removing confirmation fields as needed. Note: For an update install, you need to Restore Defaults to see a new confirmation field added as default. Because once the DB collection is created it is not touched on an upgrade unless Restore Defaults is used. Note: For a fresh install (meaning a clean Kiosk DB), though, confirmation fields added as default should be visible from the start.