PRECONDITIONS
In order to see the Live View, you need to fulfill the following requirements:
- Your Administrator must complete the Nimbus Installation.
- Afterwards, you can begin Service Provisioning and add a Nimbus tab to your team. The Live View will be part of your team's Nimbus tab.
Overview
The Live View shows current activities in the team, users states and some team statistics. This page is available to all team users regardless of their team role or current status.
The Live View consists of widget elements with various purposes:
| Name | Description |
|---|---|
|
Tasks Widgets (left area) |
Task Widgets summarize incoming tasks displaying the most important metrics on top. The purpose of the Tasks widgets is to:
|
|
Users Widgets (right area) |
The team users and status widgets summarize team availability with the most important metrics on top. The purpose of the Users widgets is to:
|
|
Trend Widgets (bottom row) |
Trend widgets summarize team KPIs, both daily and in a 30-days trend Their purpose is to:
|
Tasks
Nimbus can operate in different Task Distribution methods – individually configured in the Distribution Service Settings per Service. Accordingly, the "Tasks" widget will reflect different controls and task states (e.g. Pickup or Automatic distribution), as specified by the Service's Workflows.
"Ready" Users and Nimbus Tasks
Nimbus tracks the User State in near real-time, which includes MS Teams presence (or, if Emergency Manual Presence Mode is enabled on your tenant, the manually set Nimbus presence instead — see below) and the In-Nimbus “Ready” state. Whenever you or one of your team colleagues changes this "Ready" state, Nimbus will determine if there are any task-blocking (e.g. MS Teams Status, Responsibility Profiles, Task Capacity) and change the Live View accordingly.
💡 The “Users" widget and “Availability” counter will reflect this immediately via color and counter updates.
💡Emergency Manual Presence Mode: If this mode is enabled on your tenant, Nimbus does not use Microsoft Teams presence at all — the "Available" state shown here instead reflects each user's manually set Nimbus presence (Available / Appear Offline). The widgets, colors, and counters described in this section work exactly the same way, just driven by the manual state instead.
Learn more about the Emergency Manual Presence Mode…
INC Emergency Manual Presence Mode
Emergency Manual Presence Mode allows organizations to keep task routing working when Microsoft Teams presence information is unavailable or unreliable. When enabled on Admin > Tenant > Extensions > Presence Tracking, Nimbus stops syncing presence from Microsoft Teams for that tenant, and users manage their availability directly in Nimbus instead.
✅ Supported Presence Services: Emergency Manual Presence Mode is supported for both the legacy Presence Service and the new Presence Service, and is fully optimized for the new Presence Service.
How it Works
- All users are initially set to Offline.💡Note: When Emergency Manual Presence Mode is enabled, Dashboards and Live View may not immediately update to reflect the new presence source, which can show unusual combinations of states in the UI until the user manually switches their presence.
- Users can manually set their Nimbus presence state — Available or Appear Offline — from a dropdown on the avatar icon, available on My Overview, My Sessions, and Attendant Console.
- Task routing continues to work using the manual Nimbus presence state, together with existing Responsibility Profiles and team-based Active/Inactive settings — unchanged from normal operation.
- Sessions already in progress are not affected by enabling/disabling the mode or by a user changing their manual state.
- A presence dropdown appears in the Portal. 💡Note: Once the tenant setting is enabled, the only indicators of this mode is the new dropdown.
☝ Note: All Nimbus users must manually set themselves to Available after enabling the mode — even if they already consider themselves ready to work. Enabling Emergency Manual Presence Mode does not carry over a user's previous availability. Until a user actively selects Available from the dropdown, they remain non-selectable for tasks, regardless of how they perceive their own status.
✅ Recommended action for Administrators:
- After enabling the mode: Inform all affected service owners and users to make them aware that MS Teams presence will be ignored.
- After disabling the mode: Delays in the automatic presence synchronization with Microsoft may occur. If your Nimbus presence doesn't reflect your actual Microsoft Teams status shortly after disabling. Inform users to use Reset status from your Teams presence dropdown to resolve it.
Presence Visibility Across Nimbus
The manually configured Nimbus presence is reflected in:
- Dashboards
- All Overviews (e.g. My Overview, Services Overview, Live View)
- Apps and Extensions such as Nimbus Assistant, Attendant Console
INC Emergency Manual Presence Mode Limitations
KNOWN EMERGENCY MANUAL PRESENCE MODE LIMITATIONS
- Dashboards and Live View may show inconsistent states right after enabling the Emergency Manual Presence Mode. When Emergency Manual Presence Mode is enabled, Dashboards and Live View don't always update immediately to reflect the switch to manual presence. This can result in unusual combinations of states appearing in the UI. Until a user manually sets their presence (Available / Appear Offline) via the dropdown, they remain blocked from receiving tasks.
- After disabling the Emergency Manual Presence Mode, delays in the automatic presence synchronization with Microsoft may occur. If your presence doesn't reflect your actual Teams status shortly after disabling, use Reset status from your Teams presence dropdown to resolve it.
 |
 |
State Columns
The following states are displayed in the “state” column and chart legend:
| Status | Description |
|---|---|
| Available | Users who are "Ready" and not handling other tasks. 💡Nimbus will distribute tasks to longest "Available" users first → the "Time in State" applies. |
|
Not Available
|
Users busy in call or other Nimbus task are not receiving invitations. 💡At the point of an incoming task, a different (available) user will be selected. If no one is available, the task will remain in "queued". |
| Not Ready | Users that are set "Not Ready" via any of the toggles in the Nimbus UI. 💡 The MS Teams presence is ignored in this case, Nimbus tasks will not be distributed. |
🔎USE STATE DEPENDENCIES
Several factors can influence your Nimbus User State and Service availability:
- Distribution Service Settings allow Nimbus to distribute tasks to Service Users even while "Away" or "Busy" in MS Teams. ☝ This does not apply while Emergency Manual Presence Mode is enabled: manually, only "Available" and "Appear Offline" can be set, so there is no "Away" or "Busy" state to distribute tasks against.
-
Team Owners can also change the "Ready" states of users within their Nimbus services.
💡 Affected users will see status changes mirrored within their Nimbus UI immediately (e.g. in Widgets, Dashboards, etc.). The "Ready" setting can also be disabled via User Service Settings. - Team Users (Members) - All Nimbus users may manage their own "Ready" state individually for each team they are part of, e.g. via Services Overview. They can however not change the state of others users.
Evaluating KPI Trends
As part of Nimbus Reporting, widgets at the bottom show service KPI metrics. Out of the long-term data gathered, trends will be displayed in real time.
Trend Widgets
The widgets can be separated as follows:
Daily Metric (Numeric) |
Trend Arrows (Color and Direction) |
Historic look-back (Trendline Chart) |
|---|---|---|
|
Showcases the main metric gathered for the current productive day (data gathered starting at midnight). Metrics gathered are as follows:
|
The trend arrows highlight a comparative trend. The baseline for that trend is the standard deviation taken from data metrics mean average gathered in the last 30 days. A tendency is signaled in both direction and color:
|
The trend chart is a historic comparative look-back on the last 5 productive days of operation . Data point reflects the same time of day on previous productive days.
|
🔍 RELATED TOPICS
- KPI Settings: Note that reporting (SLA) metrics configured in each Service's General Service Settings directly impacts metrics and trends. A full historical report can be generated in Power BI, where Nimbus KPI Calculations apply.
-
Other places to review data include:
- SLA metrics gathered in Live Views are also reflected in Statistics.
- Sessions List allows to dive deeper into concluded sessions and related task results.
- Contact Center users can leverage (Non-) Personal Dashboards, which are customizable with Dashboard Widgets and individual filters.