A tablet at the door.
The right host, notified.

01: Capability

Three layers, one visit.

Visitor check-in in LiteHQ is deliberately small: one page at the door, one notification to the right person, one log to look back at. It reads your live member roster, so a guest can only be checked in against someone who actually works out of your space.

• Web check-in

  One page, open in any browser on the tablet at reception. The guest types their name, an optional email, why they are here, and starts typing the name of the person they are visiting.

  No app install, no guest account, no password.
• Host notify

  The person the guest picked gets an email and an in-app notification as the check-in lands. A notification problem can never fail the check-in itself.

  Email and in-app, set by the operator, overridable per tenant.
• Visitor log

  Who is on site right now, and the last hundred visits: guest, host, location, arrival time, time on site. Scoped to your workspaces and filterable by location.

  Names and contact details are anonymized after 90 days.

02: Visit lifecycle

From the front door to the log, in four steps.

Every visit follows the same shape. Two of the four steps are things nobody has to remember to do: the escalation when an arrival goes unacknowledged, and the privacy cleanup ninety days later.

1. Step 1

   Guest checks in

   Name, optional email, purpose of visit, and the host they are here to see. The page knows which workspace it belongs to, so the visit files itself.

   Guest · Daniel Reyes09:58 AM
2. Step 2

   Host notified

   Email plus an in-app notification, to the host the guest selected. Reading that notification is what marks the arrival as acknowledged.

   Host · Jordan L.09:58 AM
3. Step 3

   Nobody answers

   Twenty minutes unacknowledged and the operator admins get pulled in by email and in-app. Once per arrival, never twice.

   Operator admins10:18 AM
4. Step 4

   Logged, then forgotten

   The visit sits in the log with its host, location and time on site. Ninety days on, a nightly job strips the name and contact details and keeps the row for occupancy.

   System+90 days

04: Visitor log

Every visit, in one list.

Who arrived, who they came to see, which site, and how long they stayed. Filter it by location. Time on site counts from arrival to check-out, or to right now for anyone still in the building.

The log is scoped to your own workspaces, and a nightly job clears the name, email, phone and company off any visit older than 90 days while keeping the row itself for occupancy. That retention window is fixed, not a per-tenant setting.