Skills Performance view


Prerequisites

The following permissions:

  • Analytics > Conversation Aggregate > View
  • AnalyticsData Export All
  • Routing > Queue > View
  • UI > Supervisor Performance > View
  • UI > Supervisor Queue Details > View

The Skills Performance view displays statistics based on the skills and languages required for interactions as they enter a queue. These statistics can help supervisors determine performance issues with a specific skill in one or multiple queues. The statistics can also help supervisors evaluate the effectiveness of their evaluation and routing methods.

To see the view, go to PerformanceSkills Performance.

In the view, skills and languages selected for interactions display as skill groups. If an interaction does not require any skills or languages, it counts in the None group. 

This view does not update automatically. To see the most current data, click Refresh .

To save the view with your filter and column settings, click Save .

To export the data in the view, click Export .

View more details about a skill group

To see the queues and related metrics for a skill group, click the + beside the skill group’s row. The queues and their data display under the skill group row. 

Note: If None displays in the Queue column, then a skill group occurred without a queue.

None displayed in the Queue column of the None skill group represents non-ACD interactions. For example, if a user places a non-ACD call on hold, that call’s hold data displays in the None row under the None skill group. 

For more information about a queue, click the queue name. The Queue Performance Detail view for that queue opens with skill group and language group filters active to represent the skill group from the Skills Performance view. You can also save and export the data shown in the in Queue Performance Detail view with the skill and language group filters active.

To save the view with your filter and column settings, click Save .

To export the data in the view, click Export

Customize the view

Customize the Skills Performance view to show only certain data. For example, you can choose to show only certain columns or filter to see certain types of interactions. You can also save your filter and column settings as a saved view to quickly switch between different data of interest in the same view. 

To use date filters to customize analytics views:

  1. Click the icon for a date filter. Queues Performance date filter
  2. Click a view option for the chosen date filter.Queues Performance date filter options

The view displays data for the selected date filter.

If the view updates automatically and the selected date filter includes the current interval, then PureCloud continually updates the view to get the most up-to-date information. If you would like to update the current interval statistics manually, then click Refresh. If the selected date filter shows historical data (past intervals), then the view does not refresh.

Note: Some views do not include all date filter options.

Icon Time Period Options
Queues performance day icon Day

Day: Shows data for a single 24-hour day.

Interval: Shows data for a 30-minute time period. To view the current interval, click Current Interval next to the date display. 

Note: The Queues Performance Detail view does not include this option because the view already shows intervals in the data grid.

Queues performance week icon Week

Week: Shows data for a Sunday through Saturday time period.

Previous 7 days: Shows data for the previous seven days, with today being the seventh day.

Queues performance month icon Month

Day: Shows data for the exact month with no extra days.

Week: Shows data for a calendar month starting on Sunday and ending on Saturday. Includes extra days if the month does not start on Sunday.

Queues performance custom icon Custom date range Date range picker: Shows data for the range of dates that you select with the date picker. Click a start date and an end date on the calendar, then click Date picker apply

To view data for a different time period using the same filter settings, click the arrows on either side of the date display. For example, to view data for the previous day, click the day filter and then click the arrow on the left side of the date.Queues performance date

To view data for the time period that includes the current interval, click Today or Current Interval as applicable. These links only appear when you view historical data that do not include the current date and time. Queues Performance view current day or interval


To filter by media type, click a media type.Media type filter


To show or hide columns, click and then select the columns you want to view. 

To rearrange columns, click a column header and drag it.

Drag columns Queue Performance views


To filter by information about the interaction, click Filter

Interaction filters

Filter Description
Queue

Displays metrics for interactions associated with the selected queues.

Filter for multiple queues at one time by entering other queues and searching again.

DNIS

Displays information for interactions with the selected original DNIS number. This DNIS number was dialed at the beginning of the interaction.

  • Enter only the DNIS number. For example, enter 13172223333. Do not include other characters such as +, -, or ( ).
  • You can use partial numbers that start from the beginning of the number. Numbers can optionally include the country code: 1317222 or 317222 are valid partial searches. However, you cannot search for a partial string that occurs in the middle of a number. For example, if the entire number is 3172223333, then 7222 is an invalid search.
  • Filter for multiple numbers at one time by entering other numbers and searching again.
Session DNIS

Displays information for interactions with the selected DNIS number. The DNIS number could have been dialed any time during the interaction.

  • Enter only the DNIS number. For example, enter 13172223333. Do not include other characters such as +, -, or ( ).
  • You can use partial numbers that start from the beginning of the number. Numbers can optionally include the country code: 1317222 or 317222 are valid partial searches. However, you cannot search for a partial string that occurs in the middle of a number. For example, if the entire number is 3172223333, then 7222 is an invalid search.
  • Filter for multiple numbers at one time by entering other numbers and searching again.


To filter by information about the Altocloud journey details of the interaction:

  1. Click Filter
  2. Click the Journey tab.

Journey filters

Filter Description
Has Customer Journey Data Displays data for interactions that have customer journey data related to Altocloud.
Proactive Displays data for interactions where Altocloud offered a chat during a customer's website visit based on the Altocloud action map settings.   


Available columns

Your customizations determine which metric columns the view shows.

Column Description
Offer

The number of interactions routed into the queue for an agent to answer. Offered interactions are either answered, abandoned, or flow-out interactions. 

Answer %

The percentage of offered interactions that an agent answered. 

Calculated by:  (Answered / Offered) * 100

Answered (in Answered % column)

A measurement of the number of assigned ACD interactions answered by an agent in a given period. Answered increments when the agent is the first to connect to the interaction.

Abandon %

The percentage of offered interactions in which the customer disconnected before connecting with an agent. The abandon rate can identify queues that require extra staff to handle interactions in a timely manner.

Calculated by: (Abandoned Count / Offered Count) * 100

Flow-out

Flow-outs are interactions that enter and leave a queue without getting answered by an agent and without getting disconnected. Flow-outs are an indication of customer service level and queue productivity. High numbers of flow-outs can indicate staffing issues or ineffective agents when used with high handle times (bullseye matching metrics).

Flow-outs can include transfers to voicemail, callbacks, and any system-driven events such as in-queue flows that transfer to another queue or external party after a certain amount of time. Flow-outs can also occur if the caller opts to exit out of the queue and return to the IVR. Offered interactions are either flow-out, answered, or abandoned interactions.

ASA

The average amount of time an interaction waits in queue before an agent answers it. This metric does not include interactions that agents do not answer. ASA is directly associated with service level and provides insight into the customer service your company provides. ASA is recorded in the interval in which the agent answered the interaction.

Calculated by: Total Time to Answer / Number Answered 

Service Level %

Service level target is a contact center performance statistic expressed as “X percent of contacts answered in Y seconds.” For example, a goal of answering 80% of voice calls within 20 seconds provides a service level target of 80/20. You can set the service level target for each media type in a queue. Analytics uses this service level target to calculate whether you are within the service level % defined by your service level agreement (SLA). For more information about setting the service level target, see Create queues or Edit or delete queues.

The service level percentage is the percentage of interactions that meet your contact center's service level target. Calculated by: (Number of answered interactions - number of answered interactions that miss the service level target) / (Number of answered interactions + number of abandoned interactions)*100

Admins can also choose to include flow-outs in the calculation. For more information, see Configure the service level calculation. If you include flow-outs, the service level calculation is: (Number of answered interactions - number of answered interactions that miss the service level target) / (Number of answered interactions + number of abandoned interactions+ number of flow-outs)*100

Note: Any interactions that leave a queue without an agent handling or transferring the interaction, including callbacks, count as flow-outs. Callbacks do not count as answered within service level, even if the callback was offered before the Service Level Target was reached.

Handle

The total number of ACD and non-ACD interactions agents were involved in, including answered interactions, transfers, callbacks, and outbound calls. Handle increments in the interval in which the interaction ends, after the agent completes any after call work and completes the interaction. 

Avg Handle

The average amount of time agents spent handling interactions. This calculation includes talk time, hold time, and after-call work. For outbound calls it also includes dialing and contacting time.

Calculated by: (cumulative talk time + cumulative hold time + cumulative after-call work + cumulative dialing time + cumulative contacting time) / Number of interactions handled.


In these views, the Avg Talk, Avg Hold, and Avg ACW columns do not equal the Avg Handle column because only some interactions include holds. This view calculates average handle column using cumulative counts rather than averages.
Avg Talk

The average number of seconds spent interacting on a media type.

Calculated by: Total Talk time/ Count of interactions with Talk time.

Avg Hold

The average number of seconds that interactions were placed on hold.

Calculated by: Total Hold Time / Count of interactions with holds

Avg ACW

The average amount of time agents spent completing after-call work.

Calculated by: Total ACW / Interactions

Note: ACW for callback interactions is always zero. 

Total Handle

The total amount of time agents spend handling interactions. This calculation includes talk time, hold time, and after-call work. For outbound calls it also includes dialing and contacting time.

Calculated by: (cumulative talk time + cumulative hold time + cumulative after-call work + cumulative dialing time + cumulative contacting time)

Total Talk

Amount of time spent interacting on a media type.

Total Hold

The cumulative hold time for all interactions.

Total ACW

The total time spent in after-call work (ACW). After-call work is the work that an agent performs immediately following an interaction. Work may involve keying activity codes, updating customer databases, filling out forms, or initiating outbound contact. As a metric, it indicates the total time an agent takes to finish working on a call. If an agent must complete work before the agent can handle the next contact, then ACW is factored into the average handle time. 
Note: ACW for callback interactions is always zero. 

Hold

The number of interactions with holds.

Transfer

A measurement of the number of interactions an agent answered in one queue and then transferred. A transfer counts for the queue in which an agent answers the interaction. This measurement is calculated by the number of interactions blind transferred or consult transferred.