How fast is visitor approval?

Instant in both directions. The front desk logs the visitor, the resident gets the request on their phone, and both screens update together, so no guest waits at the gate for a phone to be answered.

Are resident phone numbers visible to everyone?

No. They are hidden by default in the directory, so a resident's number is never one screenshot away from being forwarded.

Is access control enforced properly or just hidden in the interface?

It is enforced in the database. Each role can only read and change what it is allowed to, whatever request reaches the server.

E13In production

Society OS: a front-desk app for gated communities

Prospicience product for residential societies

Society OS is a Prospicience web app that runs the front desk of a gated community. Residents, front desk staff and admins each get their own view, an unexpected visitor becomes an instant approve or deny on the resident's phone, and parcels, repairs and notices move off paper and WhatsApp into one live record.

user roles: 3
visitor approval: instant, both sides
buildings supported: many
phone numbers: hidden by default

How it works

01
Built three views, resident, front desk and admin, each showing...
02
Lets residents pre-approve guests, and turns an unexpected...
03
Added a parcel log, repair requests tracked from open to...
04
Supports several buildings from one login

The gate

Who can see what is enforced in the database itself, not just hidden in the screens, so every resident reaches only their own data. Every screen updates live, so the front desk and the resident always act on the same status.

The challenge

Front desks tracked visitors, parcels and repair requests in paper logbooks, WhatsApp messages and phone calls. Deliveries went missing, visitor approvals waited on someone answering the phone, and there was no record of who came in or when.

Why it mattered

The front desk is where a society's security and service meet. A slow approval leaves a guest stuck at the gate or gets them waved through unchecked, a missed parcel turns into a complaint, and without a record there is nothing to settle a dispute with.

What we built

Built three views, resident, front desk and admin, each showing only what that role needs.
Lets residents pre-approve guests, and turns an unexpected visitor into an approve or deny request on the resident's phone the moment the front desk logs them.
Added a parcel log, repair requests tracked from open to closed, building notices, and a resident directory with phone numbers hidden by default.
Supports several buildings from one login, with a printable guide for a ten-minute demo.

The result

Visitor approvals happen in real time, with the front desk and the resident seeing the same status at the same moment.
Every visitor, parcel and repair request leaves a record instead of disappearing into a chat thread.
Admins switch between properties without logging out, so one team can run several buildings.
Resident phone numbers stay private by default.

Built for trust

The technology

Three views: resident, front desk, and admin
Residents pre approve guests
An unexpected visitor becomes an instant approve or deny on the resident's phone
Parcel log, repair requests, notices, and a directory with numbers hidden by default
Works across several buildings

Technical notes

Role scoped experiences with access enforced in the database, not only in the interface
Realtime subscriptions so the front desk and the resident see the same status at the same moment
Multi property switching, with a printable guide for a ten minute demo

Questions we get asked

How fast is visitor approval?: Instant in both directions. The front desk logs the visitor, the resident gets the request on their phone, and both screens update together, so no guest waits at the gate for a phone to be answered.
Are resident phone numbers visible to everyone?: No. They are hidden by default in the directory, so a resident's number is never one screenshot away from being forwarded.
Is access control enforced properly or just hidden in the interface?: It is enforced in the database. Each role can only read and change what it is allowed to, whatever request reaches the server.