01
Expected visitors and walk-ins use the same reception flow.
Guests can arrive by QR invitation or register at reception. The visit record keeps host, site, arrival time, policy result, consent, and ID context together.
Service pillar · Visitor management
Visitor management software for arrivals that need a decision.
Invitations, consent, and badges keep normal arrivals moving. Infodeck also records what happens when a visit is denied, flagged, overdue, or unexpected, then lets reception escalate it into linked work in one step.
Denied or flagged arrivals become owned follow-up.
Accepted terms, signatures, and decisions stay on the visit record.
One visit record from invitation to follow-up.
Reception workspace · London HQ · Floor 12
Tuesday · 14:02
Live Policy: London standard
Attention required 2
Marcus K.
Flagged · reviewPivotal Labs · Passport · ****4567 · Host: Priya S.
Restricted profile · 2024-09-12 · host not expecting · policy requires re-approval.
Fatima H.
Overstay · duration 02:14
Expected
next 14:30
Sara T. · Mike J. · Ana P.
Walk-ins
mode: receptionist
Diego R. · Liam O. (ask to wait)
Linked work created WR-4412
Follow-up assigned · Flagged visitor denial
Flagged denial · VIS-0924 · context carried through
Owner: David M. Plain answers
What does visitor management include?
Infodeck manages invitations, walk-ins, host decisions, consent, visitor records, flagged arrivals, overstays, and linked follow-up work from one reception flow.
02
Hosts and policies decide what happens next.
Reception can see host response, escort requirements, flagged profile matches, overstay status, and site rules before approving, holding, or denying entry.
03
Exceptions can become owned work.
A denied visit, flagged match, or overstay can become a linked work request with the visitor context carried through to the owner and audit trail.
01 · Reception decisions
Not every visitor is routine. Infodeck catches the ones that aren't.
Flagged match. Host says "not expecting." A guest overstays. A contractor walks in without an invitation. Reception sees the context before making the call: profile tags, retention, policy outcome, host response, site rules. Every decision flows through the same approval inbox as work orders and permits.
- Flagged profile match surfaces before check-in completes.
- Overstay flagged the moment policy duration lapses.
- Escort required badges hold until a staff owner accepts.
Attention required · Flagged match
Needs review Marcus K.
Pivotal Labs · Passport · ****4567
- Host
- Priya S. · Facilities Ops
- Site
- London HQ · Floor 12
- Arrival
- 14:02 · 4 min late
- Policy
- London standard · NDA required
Restricted profile match · 2024-09-12 Reason: previous escort incident, flagged by compliance. Action: warn reception, require approval.
Host response
On my waySelected
Ask reception to wait
Not expecting
02 · Visitor record
Every arrival is a record, not a sticker on a clipboard.
When Marcus arrives again, reception sees the last visit, the restriction reason, and the ID on file before anyone waves him through. The host and compliance see the same record, not a copy.
Marcus K.
Pivotal Labs · Contractor
- ID doc
- Passport · ****4567
- Retention
- Until 2027-04-23
- Prior visits
- On file · last 2026-02-18
- Tags
- Contractor · Escort required
Restricted match reason: escort incident 2024-09-12. Flagged by compliance.
Visit history
2026-02-18 · Q1 vendor review Completed
2025-11-04 · Equipment delivery Completed
2025-08-19 · Project kickoff Overstay
2024-09-12 · Contractor visit Escort breach
Visit history surfaces what happened on each prior arrival: consent capture, NDA version, policy outcome, and any incidents. Compliance can reconstruct the history without leaving the record.
03 · Differentiator
When an arrival goes wrong, the front desk isn't the end of the trail.
Deny a visitor. Flag a restricted match. Record a host denial. On the visitor record, one click escalates the visit into a linked work request. Host, site, visit reason, masked ID, flagged match, and deny reason all carry through. One incident, one trail, one owner.
Most visitor tools focus on welcome, check-in, and reporting. Infodeck carries the exception into facilities work with linked context.
Visit · VIS-0924 Denied
14:06 · Reception · London HQ Marcus K. · Pivotal Labs
Visit reason: Q2 vendor review · Host: Priya S.
- Flagged match
- Restricted profile · 2024-09-12
- Host response
- Not expecting
- Deny reason
- Host unaware, policy requires re-approval
- Decided by
- Sara T. · Reception
Escalated to facilities work · 14:07 · by Sara T. · Linked context preserved.
Linked work WR-4412
Follow-up assigned · Flagged visitor denial
Priority: high · Due 14:30 today
- Owner
- David M.
- Site
- London HQ · Reception
- Linked to visit
- VIS-0924
- Linked to profile
- Marcus K.
Carried context
- · Flagged match reason
- · Host not-expecting response
- · Deny reason + decider
- · Masked passport, photo on file
04 · Captured on the visit
What was signed, what was shown, what was said: captured on the visit.
Reception does not chase paperwork after the guest leaves. The visit keeps what was accepted, signed, shown, and decided. Compliance can reconstruct the arrival later.
Visit record timeline · VIS-0924 · Marcus K.
Tuesday · 13:45 to 14:06
13:45
Invitation accepted · pre-arrival acknowledgement
Guest · public link
13:58
ID shown · Passport · ****4567
Reception tablet
13:59
Photo captured · stored on visit
Reception tablet
14:00
NDA signed · London standard v4
Guest signature
14:04
Flagged match surfaced · action: warn reception
Site policy
14:06
Entry denied · host not expecting
Sara T.
14:07
Linked to work request · WR-4412
Sara T.
05 · The routine day
Most days, visitors walk in and walk out. This still works.
Expected guests get a QR before they arrive. Walk-ins follow the site mode at reception. Hosts can answer from a link, and guests check themselves out when policy allows. Reception runs on any web-capable tablet, the same pairing model as your meeting-room kiosks .
Invitation · Priya S. at London HQ
QR code
Thursday · 10:00
Entrance B · 1st floor
I accept the site visit terms
NDA will be presented at the kiosk
Self check-out available at departure
06 · Across sites
When compliance asks what happened last week, the answer is already grouped by site.
See which sites had flagged arrivals, denials, overstays, consent capture, and linked follow-up. Export the report, or notify security and HR from the same visitor events. See how the full operating record ties service and governance together. Explore the platform
Policy outcomes · 4 sites · rolling 30 days
Last exceptions by site
London HQ
Reception · Floor 12
Last exception: Tuesday 14:06. Flagged arrival denied after host response "not expecting."
4 flagged2 denied1 follow-up
Berlin
Front desk
Last exception: Monday 11:30. Overstay closed by reception after policy duration lapsed.
1 flagged1 denied1 follow-up
New York
Reception
No exceptions this period. All arrivals completed with consent and host response.
Clean
Dublin
Lobby
No exceptions. 18 arrivals, 100% consent on file for the period.
Clean
Notifies your systems
Registration event Check-in event Check-out event to security, HR, or meeting-room hardware
Turn every arrival into a record your team can act on.
See how reception, host, and compliance share one visit record. Exceptions become owned work in one step.