Who can use this feature?
Plan: Call Center AI
Supported app version: 2.73.5 and above
Managed from: Admin Portal
User type: Admin, Analyst
Live Monitoring gives Admins a real-time view of every agent's Krisp status across the team: who's online, who's in a call, which features are active, and where issues need attention.
Overview
Managing a large Krisp deployment means you need to know what's happening on the floor right now, not hours later when analytics catch up. Live Monitoring gives you a dedicated dashboard in the Admin Portal that reflects the current state of your entire team in near real-time.
Live Monitoring is team-scoped: the dashboard displays only the users and devices that belong to the selected Krisp team. Each row corresponds to a Krisp application instance running under a specific logged-in user or device.
The dashboard refreshes automatically at regular intervals. A manual refresh option is also available. Most status changes are reflected within a few seconds.
Unlike Analytics, which shows historical data about your team, Live Monitoring shows your team's current state.
Hint
Devices or users that have not been seen in the last 72 hours are automatically hidden from Live Monitoring until they reconnect.
Requirements
For Live Monitoring to function correctly, the following must be in place.
- Krisp version: Agents must be running Krisp version 2.73.5 or above on their devices for Live Monitoring reporting to receive accurate data.
-
Network/firewall: Your network must allow outbound and inbound traffic over port 443 to the following domains:
- wss://websocket.krisp.ai - Maintains an active WebSocket connection and updates user profile data.
- https://websocket.krisp.ai - Supports secure communication for connection management and profile updates.
- analytics.krisp.ai - Used for sending analytics data.
If these domains are blocked or restricted, devices may appear offline, unavailable, or report inaccurate data in Live Monitoring. To verify domain access directly from the Krisp app, open the app, click on your profile badge, and run the Network checker.
Hint
For the complete list of domains required for optimal performance, see Configuring network firewall or proxy server settings.
Navigating the dashboard
To access Live Monitoring, go to the Admin Portal and select Live Monitoring from the left-side navigation. Use the team selector at the top to switch between teams.
Status tabs
Use the tabs at the top of the dashboard to filter by connectivity state.
The app is running and actively reporting status data.
The app is not running or reporting at this time.
The app reported a connectivity issue with the WebSocket service. An error was received from the device, but its current status cannot be determined.
Filters
Use the filter bar to narrow down the agent list.
| Filter | Description |
|---|---|
|
Active features
|
Filter by Noise Cancellation, Accent Conversion, Voice Translation, or Agent Assist. |
| Krisp state | Filter by Ready, In Call, or Unhealthy. |
| Issue | Narrow the list to agents with active warnings or errors. |
| Last seen | Identify the date the app was last active and reporting. |
| Last call | Filter by a specific date/time or date/time range. |
| Username | Search by hostname or email address. |
| Last headset | Filter by the headset used on the agent's most recent call. |
| Groups | Filter by team groups. Groups must be created and assigned in User Management before they appear here. |
Understanding the Live Monitoring dashboard
The monitoring table shows a detailed per-user/device view. Columns can be customized for visibility and reordered by dragging them to suit your workflow. Click on any row to expand it and see the full details for a given agent or device.
| Column | Description |
|---|---|
| User/Device | Hostname or email address, depending on how the team authenticates. |
| Username | The last system username logged into the device. |
| Features | Icons representing the Krisp features enabled for this agent. Hover over an icon to see the feature name. |
| Issues | The highest-priority active issue. If multiple issues exist, a +n indicator appears. Hover over the issue label to see the full list. |
| Krisp state | The current application state. |
| Last seen | The last time the app was active and reporting. |
| Last call | The date and time of the agent's most recent call. |
| Headset | The last headset used by the agent. |
| Version | The latest Krisp version installed on the agent's device. |
Krisp State
The Krisp State column shows the current status of each agent's Krisp app.
The app is online with no critical errors. Krisp can be used if the calling app is configured correctly.
The Krisp Microphone or Speaker is currently in use.
The app cannot process calls due to a critical error.
Action Needed panel
The panel on the right side of the dashboard gives a quick summary of agents with active Errors or Warnings, and a donut chart breaking down the team by In Call, Ready, and Unhealthy states.
Click on the Errors or Warnings count to instantly filter the affected devices/agents.
Errors and warnings
When an agent has multiple active issues, only the highest-priority one is shown in the Issues column. Additional issues are indicated by a +n count. Hover over the issue label to see the full list.
Issues remain active until the application confirms they are resolved. The Issue filter includes all active issues, including those not shown as the top priority.
Type: Error
Description: The app could not establish a WebSocket connection with Krisp's backend.
Recommended action: Make sure the domains listed in the Requirements section are allow-listed on the agent's network. To verify, open the Krisp app, click the profile badge, and select Network checker.
Type: Error
Description: A critical error is preventing Krisp from functioning. Hover over the issue label to see the specific reason (e.g., Krisp Microphone or Speaker disabled, Krisp drivers not available, unexpected app failure).
Recommended action: The action depends on the specific reason shown in the tooltip. Common fixes include enabling the Krisp Microphone or Speaker in Device Manager, or rebooting the PC.
Type: Error
Description: At least one enabled feature could not be activated. Calls can still proceed, but not all features are working.
Recommended action: Allow a few minutes and check again. If the issue persists, contact the Krisp Customer Engineering team.
Type: Error
Description: A call is in progress on the agent's system but the Krisp Microphone is not in use.
Recommended action: Select Krisp Microphone as the microphone input in the calling app.
Type: Error
Description: Krisp Speaker is not selected in the calling app. Speaker-dependent features may not work as expected.
Recommended action: Select Krisp Speaker as the audio output in the calling app.
Type: Error
Description: Krisp does not have permission to access the system microphone.
Recommended action: Grant microphone access to Krisp in the system settings.
Type: Warning
Description: The agent's selected microphone is not compatible with Voice Isolation.
Recommended action: If the agent is using a wired headset with a boom mic, enforce Agent Voice Isolation from the Krisp app. Otherwise, switch to a VI-compatible headset.
Exporting data
Click the Export button in the top-right corner of the dashboard to download the current user/device list as a CSV. The export reflects the state at the time of the action.
Info
Live Monitoring shows your team's current state only. For historical call data and usage trends, go to Analytics.
Recommended workflow
Use the following steps when investigating agent issues from the dashboard.
- Filter by Issue or Krisp state: Unhealthy to identify affected agents.
- Check Last seen to confirm the device was recently seen as active and reporting.
- Review Last call to assess how recently the agent was active.
- Confirm the agent's Features, Headset, and Version are as expected.
- Take corrective action or escalate to Krisp Customer Engineering as needed.
- Use Export to download a CSV if documentation or escalation is required.