Versions Compared

Key

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

Insert excerpt
_ExcerptAnalyticsDashboardsOverview
_ExcerptAnalyticsDashboardsOverview
nopaneltrue
 

Panel
borderColor#eeeeee
bgColorwhite
titleColorwhite
borderWidth1
titleBGColor#232323
borderStylesolid
titleIn this page

Table of Contents
depth2

What is Looker?

Looker is Google's BI tool for visualizing and displaying data. For more information about Looker, see the Looker resources page.

Note
titleEmbedded view
Vonage's Historical Analytics uses Looker's embedded view. Not all of the functionality in Looker's default experience as described in the documentation is available in the embedded view. 

What are Historical Analytics dashboards?

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

  • Default. 
    Insert excerpt
    _ExcerptAnalyticsDashboardsDefault
    _ExcerptAnalyticsDashboardsDefault
    nopaneltrue
     
  • Custom. 
    Insert excerpt
    _ExcerptAnalyticsDashboardsCustom
    _ExcerptAnalyticsDashboardsCustom
    nopaneltrue

Image Modified

What are tiles?

A tile is a single item on a Historical Analytics dashboard. Tiles can be one of two types:

  • Text tiles contain static text. 
  • Visualization tiles contain configured data and have various configuration options. For more information see What visualization options are available for tile? section later this page.

Visualization and text tilesImage Modified

What data can be displayed in tiles?

Insert excerpt
_ExcerptAnalyticsDashboardsTiles
_ExcerptAnalyticsDashboardsTiles
nopaneltrue

Tile dataImage Modified

A tile can contain one type of data at any time — time 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 an agent license, or with supervisor or admin licenses if allowed to act as agents. The Agents set of data can be accessed within Agent Events, Agent Summary, Conversation Analyzer,   Interaction Events, Groups, and Users Skills explores. 

Within Agents you can report on dimensions including the following:

  • 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 each event also has a category:

  • Presence
    • Ready
    • Away
    • ExtendedAway
    • LoggedOut
  • Interaction
    • Ringing
    • Connected
    • Wrap
    • Unexpected
    • Failed

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 the Agent Events explore. 

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

Agent summary

Each row of data represents the 15-minute slot in time of agent presence and interaction activity states. Agent Summary is a dataset that describes presence and interaction activity of agents throughout the day.

Agent summary data includes the agent's presence states and time in those states, how long the agent spent in each of the interaction states, and the numbers of times events occured. Counts, percentages, and duration measures are also available. The Agent summary set of data can be accessed within the Agent Summary explore. 

For a complete list of agent summary fields and their descriptions, see Agent summary 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, Agent Summary, Conversation Analyzer, and Users explores. 

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

Interaction events

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

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

...

Interaction event data describes every call or other type of interaction in a 4-layer structure, each with its own properties or fields:

  • Interactions
    Each interaction has information applicable to the interaction as a whole. Information includes when it started, its status — completed, ongoing, internal error — 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 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 example, HangUp, Delivered or a range of 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 interactions will have the same conversation GUID, but different interaction GUID.

...

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. 

...

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?

Tiles display data in different forms, or visualizations. Visualizations  Visualizations can be divided to different types, where each type has different settings you can use to customize its look. Different data works better in some visualizations than others.

Image Modified

Visualizations can be of the following types:

  • Cartesian charts
    • Column

    • Bar

    • Scatterplot

    • Line

    • Area

  • Pie and donut charts
    • Pie

    • Donut Multiples

  • Progression charts
    • Funnel

    • Timeline

    • Waterfall

  • Text and table
    • Single Value

    • Single Record

    • Table

    • Table (Legacy)

    • Word Cloud

  • Maps
    • Map
    • Static Map (Regions)
    • Static Map (Points)
  • Other charts
    • Boxplot

For detailed information about each Looker's visualization types, see Visualization types (Looker help).

What time zone is the data displayed in?

The data in default Historical Analytics 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 Dashboard actions and select a new time zone.

...

Image Added

Where does data come from?

...

Historical Analytics can report on data from 14th February 14, 2018, onwards. Data from before February 14, 2018, can be retrieved only from Stats and Reports. 

Who can access Historical Analytics?

...

What are the current limitations of Historical Analytics?

Note
iconfalse

Functionality

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

Process

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