I got alerted about a visitor that is not mine
Notification and messages about visitors not for the resident
How does the visitor process work
It can be a little unsettling to receive alerts about a visitor arriving at your property when they’re not actually there for you - so let’s break down why this might happen.
At many estates or buildings, visitors need to provide an access code to security before entering. If they don’t have a code, the rules vary:
Some properties allow security to check the visitor in manually.
Others allow the guard to call the resident directly (this only happens at sites using our VOIP calling feature).
In these situations, security must manually select the address the visitor is going to - and that’s where mix-ups can happen.
Mistakes happen....
Even though we prompt the security team with “Are you sure this is correct?” messages, mistakes can still happen. Sometimes the wrong address gets entered, which then triggers an alert on your app for a visitor who isn’t actually coming to you.
The easiest way to address this is to let your management team know as soon as it happens. They can then follow up with security and make sure the correct protocols are being reinforced.
How do notifications work
If you’ve generated an access code for your guest, only you (the resident who created it) will receive the arrival notification when they check in.
If a guest arrives without a code and security manually checks them into your unit, then everyone linked to that unit will receive the notification.
For sites using VOIP calling, the process works a little differently. The guest will arrive at the gatehouse, let the guard know which unit they’re visiting, and the guard will call the unit for approval. If the guest is allowed in, they’ll be checked in — but because they arrived without a code, everyone in the unit will still receive the arrival notification.
Need more help?
Open a ticket with us and we'll get back to you as soon as possible!