Good visitor access without phone calls means your guest can arrive at the estate gate, prove they were invited and enter without the gateman calling you three times.
The resident approves the visitor before arrival.
The visitor receives a temporary code or digital pass.
Security verifies it at the gate.
And the estate records who entered, who they came to see and when they left.
That is much faster than making every visitor wait while security searches for a resident's phone number.
Why do phone calls slow down estate gates?
The traditional process sounds simple.
A visitor arrives.
The guard asks who they are visiting.
The guard calls the resident.
The resident answers.
The guard allows entry.
But several things can go wrong.
The resident may:
- be driving;
- be in a meeting;
- have poor network coverage;
- not recognise the gate number;
- have their phone on silent;
- or simply miss the call.
Now the visitor waits.
Another car arrives behind them.
Then another.
The entrance gradually becomes a queue.
The process also creates weak records.
A guard may write:
Mr John - House 14
in a visitor book.
That does not necessarily tell management:
- who actually approved John;
- when approval was given;
- which guard checked him;
- when he entered;
- whether he left;
- or whether the same person returned later.
The problem is not the phone itself.
The problem is making real-time phone contact the only proof that a visitor is authorised.
A better visitor management system for Nigerian estates moves the approval before the visitor reaches the gate.
How does a visitor code system work?
The resident creates a temporary pass before the visitor arrives.
The pass is connected to:
- the visitor;
- the resident or household;
- a validity period;
- and the estate.
The visitor receives a code or QR pass.
At the gate, security verifies it.
If valid, the system shows the relevant visitor and host information and records the entry.
When the visitor leaves, the exit can also be recorded.
A simple journey looks like this:
Resident
Creates pass for Chinedu.
Visitor
Receives six-digit code.
Gate
Chinedu gives the code to security.
Security
Verifies that Chinedu is visiting House 18.
Entry
Visit is recorded.
Exit
Departure is recorded later.
Nobody needs to call House 18 unless something does not match.
For the technology behind this process, see how a visitor code system works.
The pass should also expire.
A code issued for a Saturday afternoon visitor should not continue working indefinitely.
Temporary access should actually be temporary.
What about family members and regular visitors?
Not every visitor is a one-time guest.
Residents may regularly receive:
- parents;
- partners;
- close relatives;
- domestic staff;
- drivers;
- tutors;
- caregivers;
- cleaners;
- or other trusted people.
Calling the resident every morning for the same person creates unnecessary work.
A visitor system can therefore support different validity periods.
For example:
One-time visitor
Valid for one entry or a short visit.
Weekend guest
Valid for several days.
Regular approved person
A longer access arrangement where the estate's rules permit it.
The important thing is that management still knows who the person belongs to and that access can be withdrawn when it is no longer appropriate.
Longer access should not become permanent simply because the guards recognise someone.
When a domestic worker stops working for a household, their access should be cancelled.
The same applies when a tenant moves out or a relationship with a regular visitor changes.
Good access control is based on current authorisation, not familiarity.
How should deliveries and artisans enter?
A delivery rider should not need the same access arrangement as a relative staying for three days.
Estates should define separate procedures where useful.
For a delivery, the resident may approve a short visit.
The rider arrives, completes the delivery and leaves.
Some estates may require delivery riders to remain at a designated collection point rather than moving through residential streets.
For larger deliveries, such as furniture or appliances, management may need advance notice because a truck can affect traffic or gate operations.
See how to handle deliveries and dispatch riders.
Artisans need even more control.
A plumber working in one house for three days is different from a one-time delivery rider.
Management may need to know:
- who hired the worker;
- expected work period;
- working hours;
- identification;
- vehicle details;
- and which property they are authorised to enter.
Use the contractor access guide for workmen and artisans.
One visitor system can support these different use cases without making the gateman remember every arrangement personally.
What happens when the internet is down?
This is where visitor systems need careful design.
An estate gate cannot stop functioning simply because mobile data becomes unreliable.
The important distinction is between:
passes already available at the gate
and:
brand-new passes created while the gate is disconnected.
Kompound's current system keeps the approved visitor list on the gate phone and compatible barrier controller so already-synchronised visitors can still be checked without waiting for the network.
Entry and exit activity recorded while offline can sync when connectivity returns.
A brand-new pass created during an outage, however, still needs to reach the gate before it can be verified there. Kompound states that such a pass reaches the gate when the connection returns and that security is told plainly if the pass is not yet available locally.
That is a much safer approach than pretending every offline situation can magically share new information between disconnected devices.
Every estate should also have a fallback procedure.
For example, if an urgent visitor arrives while a newly created pass has not synchronised, security should know the approved manual escalation process.
The guard should not simply abandon visitor verification because the network is poor.
See how to run an estate gate when the network is down for a fuller offline procedure.
What information should an estate record about visitors?
A visitor system should collect enough information to run the gate securely without collecting unnecessary personal information.
Useful records can include:
- visitor name;
- host household;
- pass used;
- arrival time;
- departure time;
- security officer;
- purpose where required;
- and visitor photo where the resident or estate process provides one.
This creates a much stronger record than an unreadable paper book.
But access to those records should be controlled.
A resident does not need to see the visitor history of every other household.
Kompound's current privacy policy says visitor information can include names, purposes and optional photos, while gate records include entry and exit information and the security officer on duty. Access is limited according to authorised roles. (Kompound Privacy)
Visitor records should be used for estate access and security, not as entertainment for a community group.
If there is an incident, authorised management can review the relevant record.
That is the value of having a structured gate history.
Does the visitor need to install an app?
No.
This is important because visitor access becomes much less useful if every guest has to download an estate app, create an account and complete a registration process before visiting a friend.
The resident should do the approval.
The visitor only needs the pass.
Kompound's current system lets residents create a six-digit visitor code that can be sent through WhatsApp or another message.
At the gate, security can type the code or scan its QR version.
Kompound also states that visitors and even residents without the full app experience can use plain access codes shared by message or phone. (Kompound Contact)
The visitor does not need to become a platform user simply to enter once.
This keeps the process simple.
The estate gets verification.
The resident keeps control.
The visitor does not face unnecessary onboarding.
How does Kompound remove phone calls from visitor access?
Kompound is built around visitor access without phone calls.
A resident creates a pass in the app and chooses how long it should remain valid.
The current system supports one-time passes and longer passes for recurring or longer-staying guests. (Kompound)
The resident shares the pass with the visitor.
At the gate, security either:
- enters the six-digit code;
- or scans the QR pass.
The guard can then see the visitor's name, host and available photo before admitting them. (Kompound)
Entry and exit are both recorded with:
- visitor;
- host;
- time;
- and guard on duty.
That creates an estate access history automatically. (Kompound)
For estates with compatible access hardware, the same pass can work across:
- manned gates;
- keypad terminals;
- QR scanners;
- pedestrian entrances;
- and boom barriers. (Kompound Hardware)
Management can also revoke a pass when it should no longer work.
Kompound says a revoked pass is declined across connected terminals rather than requiring management to call every gate and tell each guard to remember a name. (Kompound Hardware)
The offline design also means already-approved visitors remain available to the gate when connectivity drops. (Kompound Reliability)
The result is a much simpler arrival.
Instead of:
Visitor reaches gate.
Guard calls resident.
Resident misses call.
Guard calls again.
Visitor calls resident.
Resident calls guard.
Barrier finally opens.
The process becomes:
Resident approves visitor.
Visitor receives pass.
Security verifies pass.
Visitor enters.
The telephone remains available when something unusual needs clarification.
It just stops being the normal access-control system.
That is the difference between a gate that depends on guards making calls and a gate that actually knows who has already been authorised.