A visitor waiting, a host who doesn't know
Reception looks up the host's number and calls while the guest stands there — and first impressions are made exactly here.
One path from invitation to departure: the guest is invited ahead with a code, scans it at reception, their host is notified instantly, and the record keeps who came in and when they left. Installed on your own server, so your visitor data stays with you.
This is not about how reception looks. It is about people waiting in the lobby, a security responsibility with no record behind it, and personal data sitting open on a page every subsequent visitor can read.
Reception looks up the host's number and calls while the guest stands there — and first impressions are made exactly here.
Every visitor reads the name, affiliation and appointment of the one before them. That alone is enough to raise a data-protection question.
When the evacuation alarm sounds: how many guests are inside, and on which floor? The book does not even know who left.
"Who visited the third floor last Tuesday?" — someone leafs through a paper book, if it has not been filled and thrown away.
The employee invites their guest from the panel or the app: name, organization, time and floor. The guest receives an email with a QR code and the building location.
The guest scans their code at reception and is in within seconds. Anyone arriving unannounced is registered on the spot, with the host chosen from the directory.
The host gets a push notification and an email the moment the guest checks in — no waiting in the lobby.
Check-out closes the visit. The record keeps who came in, when, to see whom, and through which entrance.
Today's visitors are right there: who has arrived, who is waiting, who has not turned up yet. Search by name or mobile number, check someone in with one tap, and print a badge if you want a physical one.
The most valuable thing a visitor system gives you is not a faster reception desk. It is being able to answer when someone asks.
A live list of everyone who checked in and has not checked out — employees and visitors — broken down by floor.
The safety officer opens the list on their phone at the assembly point and ticks off who is accounted for — instead of a paper log in a drawer.
Who visited, who hosted, which floor, and for how long — filtered by date, site and host, exported to PDF and CSV.
No visitor sees another's details: permissions are granular, the record lives on your server, and you set the retention period.
An API for access-control systems, so a visitor is granted only what they are cleared for and only while their visit is valid.
A welcome screen naming the visiting delegation, alongside announcements — on the same screen that shows the floor directory.
A visitor's name, organization, appointment and who they met are personal data under Saudi Arabia's Personal Data Protection Law. When they live on a server inside your own estate, setting the purpose, the retention period and the access rights becomes an internal management decision rather than a clause in a cloud provider's agreement.
We will walk the whole visit through on your data in a single session: invitation, code, check-in, host notification and the record.