Unexpected disruptions are a part of the daily operations, but they shouldn’t catch you off guard. The Exception Monitor keeps you informed by instantly alerting you when something goes off track, so you can respond quickly and minimize impact.
When you need this
Use the Exception Monitor whenever you want to be proactively notified about delays or bottlenecks in your yard process, such as:
Call-off delays: Drivers take too long to respond to a call-off message.
Extended visitor stays: Visitors are spending more time in the yard than expected.
Dispatch delays: Drivers are waiting too long before being dispatched.
In short: any time a driver or visitor is stuck in the process, the Exception Monitor helps you identify and manage it quickly.
Main idea
Define scenarios – Set the conditions when you want to be alerted (e.g., driver waiting time exceeds X minutes).
Get alerted – When a condition is triggered, the driver or visitor is automatically flagged and highlighted across the system.
Get notified and action – Notifications ensure you can quickly intervene, communicate, or escalate as needed.
Automatic resolution – Once the driver or visitor moves forward in the process, the flag clears automatically—no manual cleanup required.
How does it work
Step 1 - Configure your own exception scenarios
Define a new exceptions scenario straight from the profile and specify how long a visitor can be in a specific status before it is flagged.
Default exception scenarios: Visitors are automatically flagged when:
Peripass failed to deliver a text message or voice call
Its location is not updated to 'onsite' 15 minutes after call-off
Step 2 - Flagged visitors are highlighted
No matter where you work — in the visitor list, the dispatch dashboard, or visitor details — flagged visitors are clearly highlighted across the entire system.
Step 3 - Get notified when a visitor is flagged
Not yet available.
Step 4 - Flags resolve automatically
Flags on visitors are now automatically removed in two cases:
Status update – when the visitor’s status changes and they move forward in the process.
Location change – for example, when the visitor transitions to Onsite.
In both situations, the system detects that the visitor is no longer stuck in the process and clears the flags accordingly.
How to configure
Define an exception scenario
Go to ⚙️ Configuration > Profiles > Edit > Exceptions tab
The Exceptions tab lists all automations linked to the selected profile that contain a flag action.
From this tab, you can create new Exception Triggers.
Scope of Exception Triggers
When you create an Exception Trigger within a profile, you can extend its scope to other profiles.
Once created, the trigger will automatically appear in the Exceptions tab of every profile included in the scope.
Using Flags
You can either reuse an existing flag or create a new one.
We recommend writing actionable flag descriptions. This helps users understand how to resolve the exception scenario when a flag is raised.
Managing Flags
Currently: Flags cannot be edited once created.
Coming soon: The ability to update flag titles and descriptions.
Notifications
Currently: Notifications when visitors are flagged are not available.
Coming soon: You’ll be able to receive alerts when visitors are flagged.
More information
Microsoft Teams Integration
Coming soon: When a visitor is flagged, you’ll be able to post a message directly to a Microsoft Teams channel using the Cloud API call action.
Won't do / limitations
The following features are not yet available, but are planned for future releases:
Use flags in triggers other than Time in Status
Update flag titles and descriptions
Receive notifications when visitors are flagged
Send flagged visitor alerts to Microsoft Teams channels