Live View

PRECONDITIONS

In order to see the Live View, you need to fulfill the following requirements:

 

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.

Nimbus Live View consisting of Tasks, Service Users, Service KPI Trends

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:

  • List the total amount of incoming tasks for your currenctly selected service. Tasks are distributed among available → Users.
  • Show the waiting tasks at a glance, longest waiting time first. Their "time in queue" / " connected time" contributes to the " Ø time " trend widgets.
  • Provide manual call pickup controls or distribute calls automatically, depending on Modalities Service Settings.
    🔍 Also see chapter → "Handling Tasks" below

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:

  • List (not) available team users as well as inactive ones. "Active " users become " Not available " once they handle a task
  • Allow users to directly set the "Active" state and thus availability to take calls.
  • Allow team owners and admins to set the activity state for respective team users
    🔍 Also see chapter → "Managing States" below

Trend Widgets

(bottom row)

Trend widgets summarize team KPIs, both daily and in a 30-days trend

Their purpose is to: 

  • Show the daily task resolution (handled / not handled)
  • Show the daily average time (queue / connected ) of your callers
  • Show the daily reachability of your team users.
  • Provide comparative trends for all of the aforementioned metrics. 
    🔍 Also see → "Evaluating Trends" below.

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.

Inspecting tasks in the Live View “Tasks” widget. Pickup controls will only be available if allowed by the receiving Service.

🔎Good to know:

  • Regardless the task distribution configured within Service Settings, your MS Teams interaction will behave as you know it from regular “Non-Nimbus” calls. 
  • Tasks will be distributed to you when you or other users are “Active” in Nimbus and in a User States that Nimbus considers as "Selectable"
  • When your Distribution Service Settings and Workflows are configured to distribute calls automatically (and not via "Pickup" controls in the Live View itself), Nimbus can operate completely in the background if needed. You can leave the “Live View” to focus elsewhere.
  • Many other views in Nimbus – e.g. My Sessions or Attendant Console – allow you to inspect and accept tasks in a similar fashion. You can work with your personal preference.
 

"Active" Users and Nimbus Tasks

Nimbus tracks “Active” Service Users in near real-time. Whenever you or one of your team colleagues changes this "Active" state, Nimbus will determine if there are other blocking User States (e.g. MS Teams Status, Responsibility Profiles) and change the Live View accordingly. 

💡 The “Users" widget and “Availability” counter will reflect this immediately via color and counter updates.

Your MS Teams Status and Nimbus “Active” toggle determine if you are Available to a Service

The following columns and status are displayed:

Status Description
Available Users who are "Active" 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.
Inactive Users that are set "Inactive" via any of the toggles in the Nimbus UI. 
💡 The MS Teams presence is ignored in this case, Nimbus tasks will not be distributed.

🔎STATUS 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.
  • Team Owners can also change the "Active" 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 "Active" setting can also be disabled via User Service Settings.
  • Team Users (Members) - All Nimbus users may manage their own "Active" state individually for each team they are part of, e.g. via Services Overview. They can however not change the state of others users. 
 

As part of Nimbus Reporting evaluation widgets continuously monitors service KPI metrics. Out of the data gathered, trends will be displayed on the Live View in real time.

Trend widgets and metrics in the Live View

The widgets can be separated into several concepts: 

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:

  • Amount of (un)handled tasks by the team today
  • Average time callers spent in queue today (not including IVR-time)
  • Average time callers were connected to Nimbus users today
  • Percentage of  Nimbus users being reachable today

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:

  • Direction - either up, down, or stable horizontal tendency
  • Color - green = better, red = worse. Purple is neutral (no change in tendency)

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.

  • Overall tasks done (any task result) up until the same point of time
  • ∅ Queue time up until the same point of time
  • ∅ Connected time up until the same point of time 
  • % User Reachability percentage up until the same point of time
 

Table of Contents