Visitor Incident to Operations Resolution in One Flow
Quick Summary
When a visitor exception happens at your front desk, escalate it into a work request that carries the full context -- who the visitor is, who denied them, which site, and why. The operations team responds with everything they need. The visit record keeps the linked resolution so nothing falls through the cracks.
The Problem: Two Systems, No Link
You're the operations manager for a mixed-use business park with three buildings. Your reception team handles 80-120 visitors daily across the sites.
Tuesday morning, Building B reception calls you:
"There's a man here who says he's here for a meeting with someone on the 5th floor. The host says they're not expecting anyone. He's getting agitated. I've turned him away but he's still in the lobby."
You ask: "Who is he? Has he been here before? Is he on any list?"
Reception checks. The visitor log is a separate system from your maintenance and operations platform. They find his name in the visitor log from two weeks ago -- same host, same floor. That time he was admitted. But today the host says no.
You send a security guard to the lobby. The guard has no context -- doesn't know what the visitor looks like, why he was denied, or what the host said. You text the guard the details. The guard handles it.
A week later, building management asks: "What happened with that visitor incident at Building B?" You dig through emails, texts, and two separate systems trying to reconstruct the story. The visitor log shows "denied." Your operations platform shows a work order was created. But there's no link between them. You spend 45 minutes piecing together a timeline for a 10-minute incident.
This is what happens when visitor records and operations handling live in separate systems.
The Infodeck Solution: Escalation with Connected Context
In Infodeck, visitor management and operations handling are the same platform. When reception escalates a visitor exception, the context travels with it.
Here's the same Tuesday morning with Infodeck:
9:15 AM: Walk-in visitor arrives at Building B kiosk. Enters name, selects host on the 5th floor, states purpose as "Meeting."
9:16 AM: Infodeck creates the visit as Approval Pending (Building B policy requires host approval for walk-ins).
9:17 AM: Host receives an email with the visitor details. Clicks the response link. Selects Not expecting. Adds remark: "I don't have any meeting scheduled with this person."
9:18 AM: Reception sees the host response on the visit record: "Not expecting." The visit status is now pending action.
9:19 AM: Reception speaks to the visitor. He insists he has a meeting. Reception opens the visit detail and clicks Escalate.
9:20 AM: The escalation form is pre-filled with:
- Visitor name, company, and photo (captured at kiosk)
- Host name and their "Not expecting" response
- Site: Building B, Lobby
- Visit status: Approval Pending
- Entry decision: Pending
Reception selects the Unauthorized Visitor incident template (pre-configured by the admin). Adds a note: "Visitor is in the lobby and refusing to leave. Requesting security escort."
Clicks Submit.
9:21 AM: A work request is created and assigned to the security team. The security officer opens it on their phone and sees everything: visitor photo, host response, denial context, and the reception note.
9:25 AM: Security officer escorts the visitor out. Updates the work request: "Visitor escorted from premises. No further incident."
9:26 AM: The visit record in Visitor Management now shows:
- Host response: Not expecting
- Escalation: Linked work request (auto-created)
- Resolution: "Visitor escorted from premises"
One week later: Building management asks for the incident report. You open the visit record. Everything is there -- the timeline, the host response, the escalation, the resolution. You export it in 30 seconds.
Before vs After
| Aspect | Separate Systems | Infodeck (Connected) |
|---|---|---|
| Context for security team | Texted or verbal -- incomplete | Pre-filled from the visit record -- photo, host response, denial reason |
| Link between visit and response | None. Two separate records in two systems | Automatic. Visit record links to work request |
| Incident reconstruction | 30-60 minutes of digging through emails, texts, logs | Open the visit record. Everything is linked |
| Watchlist awareness | Reception relies on memory or a spreadsheet | Automatic screening at check-in. Flag visible on the visit |
| Repeat visitor detection | Manual lookup in a separate system | Visitor profile tracks visit history and flags |
| Audit trail | Fragmented across systems | Single timeline: arrival, host response, denial, escalation, resolution |
How It Works
1. Visitor Arrives and Policy Applies
When a visitor checks in (kiosk or operator), Infodeck applies the site's visitor policy. If approval is required, the visit enters Approval Pending. If the visitor is on the watchlist, the configured action triggers (block, warn, or allow with a flag).
2. Host Responds
The host receives an email with a direct response link. They choose from:
- Approved -- admit the visitor
- On my way -- visitor should wait
- Ask to wait -- visitor should wait
- Not expecting -- host does not recognise the visitor
- Rejected -- host denies the visit
Reception sees the response immediately on the visit record.
3. Reception Escalates
From the visit detail, reception clicks Escalate. The work request form is pre-filled with visit context:
- Visit reference and visitor name
- Host name and their response
- Site and location
- Visit status and entry decision
- Watchlist or blacklist flag and reason (if applicable)
- Visitor photo (if captured at kiosk)
Reception chooses:
- Incident template -- for situations with a defined handling process (e.g. "Unauthorized Visitor", "Watchlist Alert", "Escort Required")
- Standard work request -- for situations that need manual routing or approval
4. Operations Team Responds
The assigned team (security, facilities, management) sees the full context on the work request. They handle the situation and update the request status as they go.
5. Resolution Flows Back to the Visit
The visit record in Visitor Management shows:
- That an escalation was created
- The linked work request reference
- The latest resolution status
Reception and security can follow up from either the visit record or the work request -- both show the same linked context.
Step-by-Step Setup
Step 1: Configure Visitor Policies Per Site
- Go to Visitor Management → Policies
- For each site, set:
- Walk-in mode: Receptionist-assisted or Self-service (depending on the site)
- Approval required: Yes (for sites where hosts must confirm visitors)
- Photo capture: Yes (so escalations include a visitor photo)
- Save
Learn more: Set Up Visitor Policies
Step 2: Set Up Your Watchlist
- Go to Visitor Management → Watchlist
- Add known flagged individuals with a reason
- Set the policy action per site:
- Block for blacklisted individuals
- Warn for watchlisted individuals (reception decides)
Learn more: Manage Watchlist
Step 3: Create Incident Templates
- Go to your work request or work order templates
- Create templates for common visitor escalation scenarios:
- Unauthorized Visitor -- assign to security team, high priority
- Watchlist Alert -- assign to security + facilities manager
- Escort Required -- assign to on-site security officer
- These templates appear in the escalation form when reception escalates from a visit
Step 4: Train Reception on the Escalation Flow
- Open any visit in Visitor Records
- Click Escalate
- Show the pre-filled context
- Demonstrate choosing an incident template vs a standard request
- Show how the resolution appears back on the visit record
Real-World Scenarios
Scenario 1: Denied Contractor Returns
A maintenance contractor was denied entry last week because their safety certification expired. They return this week claiming it's been renewed.
Without Infodeck: Reception doesn't remember. They admit the contractor. Building management finds out during an audit.
With Infodeck: The contractor's visitor profile shows the previous denial reason. The watchlist flag triggers a warning at check-in. Reception verifies the renewed certification before admitting them. The visit record logs the verification.
Scenario 2: VIP Visit Requires Escort
A government inspector arrives for a scheduled facility inspection. The site policy requires an escort for all external visitors to restricted areas.
Without Infodeck: Reception calls the host. Host is in a meeting. Inspector waits 25 minutes. Nobody arranges an escort.
With Infodeck: The pre-registered invitation already flagged "escort required." The host received advance notification. At check-in, the visit record shows the escort requirement. Reception escalates to the facilities team if the host hasn't arrived, and security provides an interim escort.
Scenario 3: After-Hours Delivery Refusal
A delivery driver arrives at 8 PM. The building's visitor policy blocks walk-ins outside business hours. The kiosk denies the check-in.
Without Infodeck: The driver calls the tenant, who calls you, who calls security. Nobody has the full picture.
With Infodeck: The denied visit is logged automatically. Security sees it in the visitor workspace. If the delivery is legitimate, reception or security can use operator check-in to override and create the visit with a documented reason.
Common Questions
Q: Can reception escalate without an incident template? A: Yes. They can submit a standard work request. The incident template is optional -- it just provides a faster, more structured path for common scenarios.
Q: Does the security team need access to Visitor Management? A: The security team sees the visitor context on the work request itself. They don't need to open Visitor Management separately. However, giving security read access to visitor records helps them monitor flagged arrivals proactively.
Q: What if the visitor was already admitted before the escalation? A: Escalation works at any point in the visit lifecycle. You can escalate a checked-in visitor who is causing an issue on site, not only visitors who were denied at the door.
Q: Can I see all escalated visits in one view? A: Filter the visitor records by visits with linked escalations to see all cases that were routed into operations handling.
Related Articles
- Escalate a Visitor Exception
- Manage Visitor Arrivals
- Manage Watchlist
- Review a Visitor Record
- Work Orders
Next Steps
- Review your current visitor incident process -- How does your reception team escalate today? How long does it take to reconstruct an incident?
- Set up incident templates -- Create 2-3 templates for your most common visitor escalation scenarios.
- Enable photo capture -- Ensure your visitor policy captures photos at kiosk check-in so escalations include a face.
- Run a drill -- Have reception practice the escalation flow on a test visit. Verify the context appears on the work request and the resolution links back to the visit.
When visitor exceptions happen, the question isn't whether your team will respond. It's whether they'll have the context to respond well.