Learn how High-Risk Visitor Check-In Alerts notify your security team about flagged visitors, and when an alert is or isn't sent.
What the alert does
SV3 Enterprise checks visitors against the Watchlist and your background check providers. When a visitor is flagged at check-in, their status changes to Pending Approval instead of Checked In. A Security Officer, Local Admin, or Global Admin then approves or denies the visitor.
With High-Risk Visitor Check-In Alerts turned on for a Location, the users you choose are notified at the same moment the visitor is held:
- Email: includes the visitor's details, the Location, and the reason the check failed.
- Text message (SMS): a short, high-priority message that says action is needed now.
This way your security team can respond quickly, while every other visitor checks in as usual. You turn on the alert and choose its recipients separately for each Location.
When background checks run
Background checks run when a visit is created and again at check-in. For a scheduled visit, the check at arrival is limited to Family Watchdog, because the visitor was already checked when the visit was scheduled. This avoids running the same checks twice and keeps check-in fast.
The Watchlist applies to every check-in, including visits checked in from the Dashboard.
When an alert is sent
- Walk-in visitors: a walk-in visitor (an Unscheduled Visitor) is flagged by any check, such as the Watchlist, a Visual Compliance list, or Family Watchdog.
- Scheduled visitors: Family Watchdog flags the visitor when they arrive to check in.
When an alert isn't sent
- Visitors added to the Watchlist after scheduling: a visitor scheduled before being added to the Watchlist doesn't trigger an alert at check-in.
- Recurring Visits: a visitor who is added to the Watchlist or a compliance list after their Recurring Visit is created isn't checked again at later check-ins, except by Family Watchdog.
If a visitor's risk changes after their visit is scheduled, see what to do when a visitor is flagged after their visit was scheduled.
Comments
0 comments
Article is closed for comments.