Let visitors begin themselves
A QR entry point opens the configured visitor flow in a browser. Place it where people naturally arrive, with clear instructions and a staffed alternative.
QR CHECK-IN & KIOSKA simpler arrival.
A simpler arrival.
From their own phone.
Let visitors start at a QR code, while keeping a helpful person at the desk. Choose the check-in flow that fits your location and the people who use it.
From entrance to next stepScan. Check in.
Scan. Check in.
Know what’s next.
Entry point→Registration→Queue status
A browser-based journey, with a staffed alternative.
A welcome without the bottleneck.
The first minute sets the tone.
When every arrival starts with the same questions at reception, the line can grow before service even begins. A visible QR entry point gives confident phone users another way to start, without making self-service compulsory.
INSIDE ADO Q
This is where the visitor starts.
The real browser-based check-in form connects a new arrival to the selected queue.
Keep control of the entry point
Configure static or dynamic QR behavior, active status, size and error-correction settings. Preview the code before printing and test it on the devices visitors use.
Connect check-in to the visit
Bring arrivals into the queue workflow. A personal status link helps the visitor follow the next step instead of repeatedly returning to reception.
- 1Configure
Set up the visitor entry point and review the fields you need.
- 2Place & test
Display the code at reception and test a full check-in from a phone.
- 3Welcome
Keep staff-assisted registration available alongside self-service.
HOW IT FITS TOGETHEROne clear step
One clear step
after another.
- 01
Configure
Set up the visitor entry point and review the fields you need.
- 02
Place & test
Display the code at reception and test a full check-in from a phone.
- 03
Welcome
Keep staff-assisted registration available alongside self-service.
Try it around your actual workflow.
Bring one everyday service scenario to your demo: who arrives, who handles the visit and what information needs to follow them. We’ll walk through the relevant controls and discuss your staff roles, devices and selected plan. Start with a small evaluation using sample records before planning a wider rollout.
GOOD QUESTIONSA little more
A little more
clarity.
Does a visitor need to download an app?
No dedicated visitor app is needed for the browser-based check-in and status flow.
Is kiosk hardware included?
No. Discuss the browser-based flow and device requirements separately. A printed QR code and a staffed desk may be sufficient for your pilot.
Can we switch off a QR entry point?
QR settings include an active or inactive status. Confirm the resulting visitor experience before changing a code already displayed at your site.