Understand Kiosk Behavior
The kiosk serves a customer without an operator touching it. A supported QR code starts its operation immediately; there is no separate confirmation button.
Ready state
Section titled “Ready state”The kiosk waits on a menu of three choices, and the camera is off until one is taken:
- Scan my code turns the camera on. It turns itself off again after about forty-five seconds without a code, and as soon as a result is shown.
- No app? Enter your phone opens a keypad the customer uses themselves. This is the only way a customer without the app can be served: the QR code is drawn by the customer app for a signed-in customer, so somebody who has never registered has no code to present.
- Get the app shows a QR code pointing at this company’s customer app, so a customer can install it while standing there.
Customer QR codes
Section titled “Customer QR codes”A visit is recorded the same way whether the customer scanned their code or typed their number on the keypad. When the kiosk has a phone number, it:
- records one regular visit;
- requests the customer’s updated visit progress;
- shows one of two results, depending on whether that phone number has an account;
- returns to scanning on its own.
For a registered customer the kiosk shows Visit counted (or Visita registrada) on a green screen with the customer’s name, progress, and whether a free service is available, then returns to scanning after about five seconds.
For a phone number with no account yet the kiosk shows Visit saved (or Visita guardada) on an amber screen. It states that the number is not registered, how many visits are being held, and that installing the app and registering with that number adds them to the new account. This screen stays for about twelve seconds, because it asks the customer to read an instruction rather than a number. The kiosk never displays the phone number itself.
A confirmation beep may play, but the visible result is authoritative. Browser sound policies can prevent the beep.
Repeat scans
Section titled “Repeat scans”After a scan, the same code is not accepted again for 60 seconds. A repeat shows This code was just scanned (Este código se acaba de escanear) with the seconds left.
This is a short device-side guard, not a permanent fraud or duplication control. It survives a page reload and ends with the browser session; the device keeps only a one-way fingerprint of each code for that minute, never the phone number itself.
Reward QR codes
Section titled “Reward QR codes”A reward QR redeems the reward at the kiosk. The screen turns violet, names the reward, and shows Reward redeemed or Recompensa canjeada for about twenty seconds — longer than any other result, because it is a call for a member of staff to come and hand the reward over.
The reward is spent at the moment of the scan, and the redemption is recorded against the account the kiosk device is signed in as. In Redemption Log it therefore appears under that account, not under the person who carried the reward to the customer.
A reward that has already been used shows This reward has already been used instead. The kiosk does not spend it twice, and the same reward scanned again within sixty seconds is ignored entirely.
The kiosk still does not record a free visit on its own. Free visits are spent against an earned reward in the Operator Workspace.
Unknown QR codes
Section titled “Unknown QR codes”An unsupported QR displays an informational message and returns to scanning after about five seconds. Ask the customer to open the current Frequenta customer QR, or use the Operator workspace to enter the required value manually.
Offline state
Section titled “Offline state”When the device loses network access, No internet connection or Sin conexión a internet appears and the kiosk stops taking visits: the start screen says Visits are paused (Visitas en pausa), the scan and phone-number buttons are disabled, and an open camera or keypad closes. A scan the kiosk could not deliver is not taken at all, rather than taken and lost; nothing is queued for later. The buttons return with the connection. See Troubleshoot a Kiosk.