The five steps of the visitor path
The visitor path has five steps: the invitation with a QR code is sent to the visitor, the visitor arrives at the kiosk, the kiosk reads the code and checks the invitation, the visitor receives a QR badge printed at reception, and the visitor enters the hall with the badge. Each step leaves a record in the system, so the board sees who entered and when.
In the demo, the scene is run on a demo account with a test address. No real visitor data is used, and no invitation reaches a real person. The scenario can be shortened, but it must not skip the badge step, because the badge is the element that security most often asks about.
Registration at the kiosk with a QR code
The visitor scans the QR code from the invitation at the kiosk. The kiosk reads the invitation, shows the visit details and asks the visitor to confirm the data. This takes a few seconds and needs no login or password from the visitor. The kiosk runs in the browser, so a tablet or a computer with a screen is enough.
The presenter should show the screen at the kiosk before the board enters, so that the board sees the exact layout. A screenshot of the flow is a good way to show the result when the kiosk is unavailable.
- scan the QR code from the invitation at the kiosk
- confirm the visit details shown on the screen
- wait for the badge print at reception
QR visitor badge printed at reception
After registration the badge is printed at reception. The badge carries a QR code that identifies the visitor for the duration of the visit. The reception employee sees on their screen the same visit data as the visitor, so there is no need to re-enter them.
The badge is the proof that the visitor is registered. The security department can check the badge at the gate and in the hall. After the visit the badge is returned at reception and the visit closes.
Daily health declaration: an optional setting
The daily health declaration is a feature disabled by default. When the client enables it, a visitor without today's declaration does not enter, and the entry is not recorded. The board should know that this is a setting the client chooses, not a requirement imposed by the system.
In the demo the presenter can show both modes: with the declaration disabled, the path runs without this step, and with it enabled, the visitor must complete the declaration before the badge is issued. This shows that the process can be adjusted to the plant's procedures.
What to check before the demo
Check that the kiosk reads the QR code from a demo invitation, that the badge prints at reception and that the visitor data on the screen match the test account. Do this a few minutes before the board enters, and keep a spare invitation on paper in case the scan fails.
InnerWeb does not supply access control readers. The visitor path shows the registration process, while physical gates and readers remain the plant's existing equipment, connected to the system through its own integration.
Checklist
Video
Frequently asked questions
Do visitors need an account to register at the kiosk?
No. The visitor scans the QR code from the invitation and confirms the visit details on the screen.
What happens if the health declaration is enabled and the visitor has not filled it in?
The visitor does not enter, and the entry is not recorded. The declaration is an optional setting that the client chooses.
Does InnerWeb supply the gate readers?
No. InnerWeb is a software vendor. Gates and readers remain the plant's existing equipment.
Is real visitor data used in the demo?
No. The demo runs on demo accounts with test addresses, so no invitation reaches a real person.
Show the visitor path on your plant's data
We will prepare the kiosk and the badge print for the demo. Book a call about the scope.
Let's talk