Advance invitation
Create the right before arrival with only the information the site needs.
Temporary arrivals
Visitor management for parking and controlled sites
Combine preregistration, plates, QR codes, intercom assistance and automatic expiry into a clear visitor journey. Hosts and reception staff retain the context needed for last-minute changes.
Preregistration
Plate or QR
Temporary rights
Entry assistance
Passage history
Operating design
Keep temporary access temporary
Appointments, deliveries, events and contractors have different durations, but each can have an owner, a defined scope and an expiry instead of remaining on a general allow list.
Temporary identifier
Attach a plate or code to a defined period and set of zones.
Assisted arrival
Give authorized staff enough context to handle an unplanned case.
Automatic expiry
Remove rights that no longer have an operating purpose.
Passage history
Review the access result when staff need to answer a question.
Visit types
Keep guests, suppliers, contractors and event attendees distinct.
Decision path
From identification to an operating decision
Each step remains visible enough for staff to understand and support the result.
01 — Invite
Host and purpose recorded
02 — Identify
Temporary plate or code
03 — Arrive
Right checked at the lane
04 — Assist
Context available if needed
05 — Expire
Access removed on time
Lexoh field evidence
Self-service arrival with a path to help
A kiosk can combine identification, instructions and assistance. That matters when a visitor does not know the site or reception is far from the entrance.
What this changes in the project
Equipment placement, civil work, communications and operating procedures are validated together before commissioning.
Turnkey delivery
What turnkey delivery covers
Lexoh coordinates the field work, platform rules, testing and operating handoff as one project.
- 01Map visit types and owners
- 02Define the minimum data required
- 03Choose plate, QR, intercom or a combination
- 04Configure zones and validity periods
- 05Connect the process to lanes and assistance
- 06Test planned and unexpected arrivals
Operating contexts
Operating contexts this design supports
Business appointments
Day-limited access to the expected parking area.
Deliveries
A time window and lane matched to vehicle and destination.
Contractors
A longer right limited to the work period and zones.
Events
Arrival volume planned with identifiers distributed in advance.
Before specifications
Questions to settle before specifications
Who creates and changes the right?
Keep host, reception and security responsibilities simple.
Which information is necessary?
Collect what supports access without burdening the invitation.
What if the vehicle changes?
Provide a quick correction or assistance path.
How are after-hours arrivals handled?
Define who receives the call and what they can authorize.
Questions asked before a project
Clear answers about scope, operation and integration.
Not necessarily. A journey can use a preregistered plate or a code sent before arrival.
Yes. The right can apply only to the lanes, zones and times needed for the visit.
Authorized staff can correct it or assist the driver through the lane procedure.
They can be configured with a defined end time so they do not remain active.
Make arrival simple without losing control
Let us map the visitor types, responsibilities and exceptions at your site.
