Overview
After sending an Emergency Notification, it’s crucial to monitor who’s received the message and how they’ve responded. The Message log makes this easy by displaying all sent notifications in one place. Clicking on any notification will open a detailed view, where you can see the onsite status, the delivery status, and who has marked themselves as safe (if enabled). This allows admins to view real-time data about the individuals in your building.
Using the Message log
The message log will automatically open after sending an emergency notification, and you can access it by using the side menu.
Navigate to Communications > Message log.
Here, you'll see a list of previous messages. Click the message you want to open details for.
Message recipients are automatically grouped into a category for easy sorting:
Need help (if applicable)
Failed to reach: You can hover over the delivery status to see more details on why the message failed.
Delivered
Read: Only available for push notifications
Safe (if applicable)
Clicking on each accordion group will expand the section to display each recipient.
As time passes, the sent log will automatically refresh to receive new statuses. The refresh rate is as follows:
under 1 hour: every 5 seconds
1 - 24 hours: every 10 seconds
over 24 hours: every 30 seconds
When new statuses are received, the employee or visitor will sort themselves into the correct category.
Onsite status
It's easy to see who was onsite during an emergency by checking the Onsite status column in the Message sent log. 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:
Scheduled: 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 statues 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.
✨Tip: You can hover over the status to view more details.✨
Automatic sign out
The "Checked out" status will only show for employees and visitors who have manually checked out (via kiosk, dashboard, app, etc.). Out of an abundance of caution, automatic sign-outs will not be shown as checked out. This is to ensure everyone remains informed of any potential emergency.
Learn more about automatic sign-out.
Failure reasons
To see the reason a delivery method failed, hover over the delivery status in the sent log.
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’s 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.
Status bar
As the responses are reported, the status bar will automatically update. In the example below, you can see someone mark themself as safe in real time.
Exporting the Message sent log
You can export the emergency notifications sent log by clicking on the Export button in the upper right-hand side.
This will prompt a csv download to start. You can open this csv in your preferred spreadsheet application like Google Sheets or Microsoft Excel.
The exported log will contain the visitor and employee's name and email, as well as their phone number, if included in their visitor entry or employee profile. It will also include detailed failure reasons and responses (if applicable).