Overview
The Envoy mobile Incident Responses log provides a detailed record of your emergency notification. It shows who received the message, when and how it was delivered, their onsite status, and whether recipients marked themselves as safe (if included).
This article will show you how to use the Envoy mobile Incident Responses log. Are you looking to learn how to send an emergency notification via mobile? Learn here!
Using the Incident Responses log
Once your emergency notification is sent, you will land on a page that details who successfully received your notice and who marked themselves as safe.
You can also access the responses log from the app home page by tapping on the Incident in the communications section > Manage incident.
The response tracker automatically updates to show the current response counts, and tapping the ellipses opens a list breakdown.
By tapping on a recipient's name, you can view more details about their status.
The mobile responses log is view-only, but you can export the message response log by using the web dashboard.
The responses log is broken up into five status categories, and you can tap each one to filter it as needed.
Needs help
Failed to reach
Delivered
Read (only available with Push notifications)
Safe
You can also filter recipients by type (Visitor or Employee) using the menu in the top-left corner.
Failure reasons
By tapping on the user's name, you can view the detailed status of each delivery type.
Potential failure reasons include:
Email: Email missing, Email was dropped and not delivered to the recipient, Email bounced due to an invalid recipient address or domain issue, Email was blocked by the recipient鈥檚 server (possible spam filter).
Push notification: No active Envoy account or account not properly linked, Not logged into Envoy mobile app or push notifications disabled, Push notification endpoint is disabled, Invalid push notification parameters, Authorization error for push notification
SMS: Invalid message destination: Number is invalid, Device unreachable: Destination device could not be reached, Message blocked: User has opted out of receiving messages, Message blocked: Number doesn't exist, Message blocked: Carrier blocked, The mobile subscriber is unreachable, Message blocked by Twilio
Slack: The Slack integration is not installed or configured, This channel is only available for employees, We could not authenticate with your Slack workspace, We could not find a matching user in your Slack workspace, This slack user or the linked workspace has been deleted.
Teams: The Microsoft Teams integration is not installed or configured, This channel is only available for employees, A tenant admin has disabled our integration from being able to access your Microsoft organization, This user has not installed the Envoy for Microsoft Teams integration, We could not find a matching user in your Microsoft organization, This user has blocked the integration from sending any notifications, Admin consent has not been granted for the Envoy for Teams integration and the user has not logged into the integration.
Onsite Status
It's easy to see who was onsite during an emergency by checking the Onsite status details on the recipient. This captures the presence information for both employees and visitors at the time of sending the notification. It will not update as time passes and real-time statuses change.
Onsite status does not show on non-emergency announcements.
Potential employee statuses include:
Invited: This employee has a workplace reservation but has not been checked in.
Checked in via Access Control (Kisi, Brivo, etc): This employee has badged into the workplace via an access control integration.
Checked in via Okta: This employee has been checked in via SSO integration
Checked in via Wi-Fi (Cisco Meraki, etc): This employee has been checked in via Wi-Fi integration
Checked in via Envoy Mobile: This employee has been detected by geolocation or manually checked in on the mobile app
Checked in via Dashboard: This employee has checked in using the web dashboard
Checked out: This employee had been in the workplace previously on this day, but has since checked out.
Potential visitor statuses include:
Invited: This visitor has an existing invitation, including invites that have not yet been approved. Learn more about invite approvals.
Checked in via dashboard: The visitor has been signed in via an admin on the web dashboard
Checked in via kiosk: The visitor has been signed in at the visitors kiosk.
Checked out: The visitor has been signed out.
Mark as Safe
See main article: Two-way emergency communication
The responses log will show who has marked themselves as safe or needs help. This allows admins to view real-time data about the individuals in your building.
Admins can edit any status by tapping on an Employee's name and providing a response.
Employees and visitors can learn how to mark themselves as safe here.
End and Archive an Incident
Once a situation is resolved, you can end the incident to lock the record, or end and archive it to remove it from employee view.
Ending an incident stops all reminders, locks responses and chat, and ends any screen takeovers. The incident remains visible to admins in the Incident log.
Archiving an incident hides it from employee view in the app. Archiving an active incident ends and archives it simultaneously.
To end or archive an incident on mobile:
On the homepage, scroll down to the Communications section and tap the active incident.
Scroll down and tap End incident to end it.
The incident will remain visible in the communication section of the employee's homepage until it is archived, which occurs automatically after 7 days.
To end and archive the incident at the same time, tap the ellipsis option on the top right (路路路) and select Archive incident.
Confirm when prompted.
Note: Incidents are automatically ended after 48 hours if not manually ended.
For step-by-step instructions, see End Emergency Notification Incident [Web & Mobile].