Find the visit
Use a narrow lookup method that avoids exposing unrelated visitor or host information.
Visitor management kiosk
Visitor check-in kiosk with a clear path when self-service stops working
Design expected-visitor lookup, data confirmation, policy acknowledgement, host notification, waiting, badge handoff, and staffed exception response as one arrival journey.
A kiosk is not only a form on a stand. The operational test is what happens when the visit is missing, the host is late, the policy answer changes, or the person needs help.
- Self-service arrival and host notification
- Staffed exception handoff
- Hardware, badge, identity, and access boundaries made explicit
Front-desk check-inTurn the expected visitor into a current onsite record
Confirm the invitation, visitor, site, host, arrival, identity check, badge, escort, and current location. Reception takes over whenever self-service needs help.
- Expected-visitor lookup
- Identity, badge, and escort choices
- Staffed exception handoff
Working front-desk formSee arrivals, current visitors, and exception response beyond the check-in screen
The check-in form creates or updates the current visit. Reception uses the connected queue and exception view when a host is late, a check fails, or checkout becomes overdue.
Keep the arrival path short and recoverable
The kiosk should reduce reception work without trapping visitors when the expected path fails.
- 01
Choose expected or walk-in
Let the visitor find an approved visit with a small set of stable facts or start the correct walk-in path.
No long search result exposing other visitors. - 02
Confirm the visit
Show only the visitor, host, purpose, destination, and arrival window needed to confirm the record.
No duplicate registration. - 03
Complete required policy
Collect the current acknowledgement, evidence, or answer required for that visitor type and site.
Version and result remain on the visit. - 04
Notify the host
Create the active visit, record arrival, and send the host the location and response action.
Waiting starts at a known time. - 05
Hand off the badge or escort
Reception or another role completes the physical handoff when the policy requires it.
Badge, escort, and destination are current. - 06
Escalate exceptions
Missing visit, failed check, host delay, accessibility need, or device problem moves to a visible staff queue.
One owner and response target.
Ask only what is necessary at each kiosk screen
Long forms, tiny controls, hidden validation, and unclear progress increase abandonment at the front door.
Confirm, do not retype
Reuse the approved visitor, host, purpose, site, destination, and time when they already exist.
Explain the check
State why an acknowledgement, photo, document, or answer is needed before asking for it.
Show the next wait state
Tell the visitor whether to wait, collect a badge, meet the host, or speak with reception.
Offer help visibly
Do not hide the staffed path behind an error code or repeated restart.
Use Jodoo for the configurable workflow around the kiosk
Choose a dedicated kiosk or identity product when the arrival experience depends on native device, badge, camera, scanner, or verification capabilities.
Jodoo web check-in
The need is configurable visit forms, approval, expected-arrival lookup, host response, exceptions, records, and dashboards on a managed browser device.
Dedicated kiosk product
Native device lockdown, camera or scanner integration, badge printing, identity verification, offline behavior, remote device management, or access control defines success.
Hybrid design
Specialist kiosk or access hardware handles the physical interaction while Jodoo coordinates approvals, exceptions, related business records, and management views.
Visitor check-in kiosk questions
01Can Jodoo run on a kiosk tablet?+
A Jodoo web form can run in a browser on a managed tablet. Device lockdown, remote device management, native scanning, badge printing, identity verification, and offline behavior may require specialist software or hardware.
02Should a kiosk allow walk-ins?+
Only when policy permits it. Give walk-ins a separate path with required host, purpose, approval, and staff review rather than treating them as pre-approved visitors.
03What happens when the host does not respond?+
Move the visit into a waiting exception with elapsed time, host, alternate owner, escalation target, and visible instructions for the visitor.
04How many fields should a kiosk form contain?+
Use the minimum needed for that step. Pre-fill approved details, split long policy interactions into clear screens, and test completion with first-time visitors.
05Can the kiosk print a badge?+
Jodoo can store the badge or pass data. Direct printer control and label design depend on the selected hardware and integration path; verify the full device workflow before rollout.
Test the real visitor operation
Open the check-in workflowTest the kiosk when the happy path fails
Run a missing visit, host delay, failed check, accessibility request, printer issue, and staff handoff on the actual device.