Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Insert excerpt
_ExcerptAnalyticsDashboardsOverview
_ExcerptAnalyticsDashboardsOverview
nopaneltrue
 

...

A dashboard is a collection of tiles, displaying data about agent events or , groups, interaction events or summary, skills, and users. Analytics offers two types of dashboards:

...

A tile can contain one type of data at any time—agents, agents events, interaction events, or userstime — agent event, group, interaction event or summary, skill, or user

Agents

Each row of data represents a single agent. The data is presented for all users with license of Agent or Supervisors and Admins if an agent license, or with supervisor or admin licenses if allowed to act as agents. The Agents set of data can be accessed within Interactions and Agents Agent EventsInteraction Events, Groups, and Users explores. 

Within Agents you can report on:

  • Email

  • Licence

  • Name

  • Phone number

  • Physical location

  • Username

  • WebRTC

For a complete list of agent event fields and their descriptions, see Agents fields.

Agent events

Each row of data represents a single event for an agent. Agent events can be one of two types—presence and interaction—and types — presence and interaction — and each event also has a category:

...

Other agent event data includes start time and date, duration of event, and agent ID. Average, maximum, and minimum duration, and count measures are also available. The Agent events set of data can be accessed within Agents the Agent Events explore. 

For a complete list of agent event fields and their descriptions, see Agent events fields.

Groups

Each row of data represents a single group and its settings. When agent and group dimensions are shown, a row of data represents a group and agent combination, where the agent is in the group. Within groups you can report on:

  • Group display ID
  • Group name
  • Maximum unexpected time
  • Maximum wrap time
  • Agent ID (ID of agent in the group)

Count, maximum unexpected, maximum wrap, and group list measures are also available. The Groups set of data can be accessed within Agent Events, Groups, Interaction Events, and Users explores. 

For a complete list of groups fields and their descriptions, see Groups fields.

Interaction events

Each row of data represents a single interaction. Interactions can have channels, events, start and end dates, and so on. Interactions Interaction events have many more dimensions and measures than agent events. The Interaction events set of data can be accessed within Interactions  Interaction Events explore. 

For a complete list of interactions fields and their descriptions, see Interaction events fields.

...

  • Interactions
    Each interaction has information applicable to the interaction as a whole. Information includes when it started, its status—completedstatus — completed, ongoing, internal error—and its direction—inbounderror — and its direction — inbound, outbound or internal.
    Interactions have one or more channels:
    • Channels
      A channel represents a party who is connected or attempted to be connected to the interaction. If a party leaves and rejoins, there are two channel instances associated with that party. A party can be external, an agent, or a monitor (a supervisor monitoring an interaction).
      Channels have one or more channel events:
      • Channel Events
        A channel event represents each human or system activity instigated by or affecting the channel—party—or channel — party — or the interaction. Examples of channel events include Ringing, DeliveryFailed, Connected, Applet, Queue, Held, CallRecording, Disposition, Wrap. Multiple channel events can occur at the same time. For example, a Held channel event can occur within a Connected channel event.
        Each channel event has a type, an offset (by default, in milliseconds from the start of the interaction), and a duration (by default, in milliseconds). Queue, Applet and some other events carry a Customer-defined Name
        • Channel Event Properties
          Some channel events, specifically Queue channel events, have additional properties. A queue channel event has a result—for result — for example, HangUp, Delivered or a range of breakouts—a breakouts — a list of presented skills, and virtual queue (or agreement) names.

All interactions have a conversation GUID. A conversation GUID connects all interactions that make up a conversation. For example, a conversation may contain an initial phone call and a callback—both callback — both interactions will have the same conversation GUID, but different interaction GUID.

Interaction summary

Interaction summaries include data that can describe the lifecycle of the interaction. This data includes, for example, for an inbound interaction, when it started, the interaction plan it started in, what happened in the queue, the agent it was routed to, and how long it lasted. Other data includes whether any issues with call quality were reported, if the interaction was analyzed, and whether a payment was taken.

Several measures are available, including count, Mean Opinion Scores (MOS), and wrap time. The Interaction summary set of data can be accessed within Interaction Events and Interaction Summary explores.

For a complete set of interaction summary fields and their descriptions, see Interaction summary fields.

Skills

Each row of data represents a single skill and its settings. When agent and skill dimensions are shown, a row of data represents a skill and agent combination, where the skill is assigned to the agent. Within skills you can report on:

  • Skill display ID
  • Skill name
  • Skill level
  • Agent ID (ID of agent in the group)

Count and skills list measures are also available. The Skills set of data can be accessed within Agent EventsInteraction Events, Skills, and Users explores. 

For a complete list of skills fields and their descriptions, see Skills fields.

Users

Each row of data represents a single user. The data is presented for all users that exist in your account, including archived ones. The Users set of data can be accessed within Users explore. 

Within Users you can report on:

  • Active

  • Agent configuration

    • Agent ID

    • Phone number

    • Physical location

    • WebRTC

  • Days since last login

  • Email

  • Last login date Date

  • Licence

  • Locked

  • Name

  • User ID

  • Username

For a complete list of users fields and their descriptions, see Users fields.

What visualization options are available for tiles?

...

The data in default dashboards is displayed according to the viewer's time zone. The time zone is taken from the viewer's browser configuration. To change the dashboard's time zone, go to dashboards setting Dashboard actions and select a new time zone.

Where does data come from?

Analytics is powered by the same data used in Dashboards—Insights Dashboards — Insights Stats API.

What range of historical data is available?

...

Analytics read-only access is available only to Admin admin users. The view  Viewer access is by default assigned to all Admin admin users. There is no action needed to assign this access.

Info
In future releases, when Analytics is generally available, both Admin admin and Supervisor supervisor users can be assigned with Analytics license.  

...

Info
titleEARLY ACCESS

Only users who are assigned an Analytics license can access it. Users can have either view  Viewer or create access Creator access to Analytics and only Admin admin and Supervisor supervisor users can be assigned with Analytics access.

The number of these different types of licenses depends on your package type (Express, Essentials, Select, and so on), contract type (named or concurrent), and number of seats. You can buy more licenses. For more information, contact your Account Manageraccount manager.

Users who do not have access to Analytics can still benefit from its data. You can schedule delivery of dashboards to any user, by providing their email addresses. For more information, see the Scheduling delivery a dashboard section in Using Analytics.

...

Note
iconfalse

Functionality

  • Cannot report by Group or Skill.
  • No clear ownership of Analytics dashboards: All dashboards can be viewed (and potentially edited) by all users with access to Analytics.
  • Personal Dashboards not accessible: User can create personal dashboards in Looker—these Looker — these are inaccessible within VCC.
  • Models require steep learning curve. Event-based models are the most flexible, but require a deeper understanding.
  • Embedded The embedded version of Looker does not contain exactly the same information as described in Looker's documentation.

Process

  • Analytics dashboards no longer work when the data model is updated.

...