TR
AZ
ENWhich experience fits which need?
SE Visit explores pre-registration and visits; SE Lobby multi-office reception. Demo codes and approvals do not grant access through real turnstiles or QR systems.
Visitors & receptionCompare web and mobile experiences.
Visitor workflows begin before reception. Pre-registration, host approval, check-in, meetings and pass returns need a connected journey.
Define the scope clearly.
Specify office/floor mappings, host roles, visit purposes, retention policies and hardware connections.
Explore, try and compare.
From first record to completion.
- 01Pre-registered
- 02Review
- 03Host approved
- 04Checked in
- 05In meeting
- 06Checked out
This is the sample process available to explore. Your organisation’s rules, exceptions and permissions are defined separately for production.
- Visit details and host checked
- Visitor pass returned
Before you decide.
Which demos are in this category?＋
SE Visit, SE Lobby. SE Visit explores pre-registration and visits; SE Lobby multi-office reception. Demo codes and approvals do not grant access through real turnstiles or QR systems.
What must be defined before production use?＋
Specify office/floor mappings, host roles, visit purposes, retention policies and hardware connections.
Can web and mobile be planned together?＋
Yes. Web, iOS and Android can be separate deliverables within one proposal. These are browser prototypes; real accounts, servers, integrations and store packages must be scoped for production.
Is a demo a customer reference?＋
No. Records and images are illustrative scenarios. Real work is listed separately under Projects; sample data does not represent customer outcomes.
Turn your requirements into a production scope.
Share your business structure and target platforms for an Izmir or Baku project discussion. Delivery scope, testing and support are agreed in the proposal.