This capability requires the member to be identified — on chat this means being signed in; on email, WhatsApp, and voice the member is identified by their email address, phone number, or caller ID. The AI will prompt unidentified users to log in or provide contact details before proceeding.
Prerequisites
Before a host can use the AI to approve visitors:- Visitor approval must be enabled for the location under Settings → Apps and integrations → Companion apps → NexIO → Require host approval for walk-in visitors
- The visitor must be registered via NexIO (walk-in self-registration) with the host assigned
- The host must be a customer with an active profile
- On WhatsApp and voice, the host’s mobile phone number must match their customer profile
Checking for pending visitors
Hosts can ask the AI at any time if they have visitors waiting:- “Any visitors?”
- “Who’s waiting for me?”
- “Do I have any pending visitors?”
- Visitor name
- Company (if provided)
- Expected arrival time
- Reason for visit (if provided)
Approving or rejecting a visitor
The approval flow
The AI uses a draft → confirm → apply flow to ensure decisions are never applied accidentally: Step 1 — Draft. The host mentions a visitor by name and indicates their decision (“approve Alex”, “reject Maria”, “approve Bob and I’ll collect him”). The AI identifies the visitor from the pending list, interprets the decision, and drafts the action. A short-lived confirmation token is issued. Step 2 — Confirm. The AI presents a summary showing:- The visitor’s full name
- Expected arrival time
- The decision that will be applied
If the confirmation window expires, the AI tells the host and asks them to confirm again. A fresh token is issued with the same decision. No changes are saved until the host confirms.
Response options
The available approval options depend on your location’s settings under NexIO → Require host approval:| Option | What it means | When available |
|---|---|---|
| Approve, I’ll collect them | Host will come to reception to collect the visitor | Enabled by default; can be disabled via Host can choose to collect visitors at reception |
| Approve, send to my unit/desk | Visitor can proceed directly to the host’s area | Enabled by default; can be disabled via Host can choose to send visitors to their unit or desk |
| Reject | Host declines the visit; visitor is turned away | Always available |
Natural language support
Hosts can reply in whatever way feels natural:- By name — “approve Alex”, “reject John”, “approve Maria and send her to my desk”, “approve Bob, I’ll collect him”
- With numbers — if the host received the original approval message with numbered options (e.g., from WhatsApp), they can reply with
1,2, or3 - By state — if there’s only one pending visitor, “approve” or “reject” on its own is enough
- With clarification — “approve and grant access”, “approve and hold”, “reject”
Approving multiple visitors at once
Hosts can process several visitors in a single conversation:- “Approve Alex but reject John”
- “Approve Alex and Maria”
- “Approve everyone”
- “Approve all”
- Drafts each decision individually
- Presents a combined summary listing all visitors and the action that will be applied to each
- Asks the host to confirm the full set
- Applies all decisions at once only after the host confirms
Auto check-in for approved visitors
When the host approves a visitor with the “grant access” option and Automatically check approved visitors in is enabled in NexIO settings, the visitor is checked in immediately. This reduces front-desk workload — the visitor can proceed directly to the host’s area without staff intervention. Check-in is only triggered for:- Visitors approved with the “grant access” decision
- When auto check-in is enabled for the location
What happens on the visitor record
Regardless of whether the host replies via chat, email, WhatsApp, or voice, the visitor record ends up in one of these states:| Status on visitor record | Meaning |
|---|---|
| Requested | Waiting for the host’s response |
| Accepted — hold for collection | Host will come to reception to collect the visitor |
| Accepted — grant access | Visitor may proceed to the host’s desk or unit |
| Rejected | Host has turned the visitor away |
Staff notifications
When a host approves or rejects a visitor through the AI, staff members with Visitor registration notifications enabled receive a system message:- Visitor accepted — includes the visitor name, host name, and approval type (hold or grant access)
- Visitor rejected — includes the visitor name and host name
Conversation examples
Single visitor approval
Host: “Any visitors?” AI: “You have one visitor waiting: Alex Smith (expected at 10:30). Would you like to approve or reject?” Host: “Approve Alex, I’ll collect them” AI: “Just to confirm: approve Alex Smith (expected at 10:30), option Approve, I’ll collect them? Reply confirm to apply or cancel to abort.” Host: “Confirm” AI: “Done. Alex Smith has been approved and is waiting to be collected.”Multiple visitor approval
Host: “Do I have any visitors?” AI: “You have 3 visitors waiting: Alex Smith (10:30), Maria Garcia (11:00), and Bob Johnson (11:30).” Host: “Approve Alex and Maria but reject Bob” AI: “Just to confirm, these decisions will be applied:- Alex Smith (10:30) — Approve, send to my unit/desk
- Maria Garcia (11:00) — Approve, send to my unit/desk
- Bob Johnson (11:30) — Reject
Approve all
Host: “Approve everyone” AI: “You have 3 visitors waiting. Which approval type should I apply to all of them?- Approve, I’ll collect them
- Approve, send to my unit/desk
- Alex Smith (10:30) — Approve, send to my unit/desk
- Maria Garcia (11:00) — Approve, send to my unit/desk
- Bob Johnson (11:30) — Approve, send to my unit/desk
Related pages
Visitor Approval
Configure the visitor approval workflow in the administration panel.
Visitor Approval on WhatsApp
Set up the WhatsApp approval message that hosts receive when a visitor arrives.
Visitors
Main visitor management — registration, check-in, and lifecycle.
Channels
Learn about confirmation windows and how they differ across channels.