Add and edit Performance Dashboards
The following permissions:
- Analytics > Conversation Aggregate > View
- Analytics > Queue Observation > View
- Analytics > Dashboard Configurations > Edit
- Analytics > Dashboard Configurations > View
- Directory > User > View
- Routing > Queue > View
Create dashboards to display the performance metrics you want to see for the queues and users that are important to you. You can see a preview of your dashboards and open dashboards to edit or view from Performance > Dashboards. Create a display for your call center by viewing your dashboard in full-screen mode.
Widgets display metrics and visual information on your dashboard. Set which queues or users, metric, time span, and media types to use for the widget. Add color-changing warnings to let you know when metrics are above or below a specified level.
- You can edit and view only the dashboards you created.
- Click Performance > Dashboards.
- Click Add a new dashboard.
- In the Add new dashboard pane, enter a name and click Add.
To view, edit, rename, or delete a dashboard from its preview on Performance > Dashboards, hover over it and click the appropriate icon.
From an open dashboard, to view a dashboard in edit mode, click Toggle edit mode. Click it again to return to viewing mode.
Widgets display metrics and visual information about the queues or users you choose. You can add up to seven rows of widgets, and each row can have up to seven metric widgets or one graph widget. For more information about adding more rows to your dashboard, see the Change the grid size section in this article.
- Click Performance > Dashboards.
- Hover over a dashboard and click Edit dashboard.
- To add a widget, click Add metric or Add graph.
- (Optional) Enter a name for the widget in the Optional custom title field. If you do not enter a name, the widget’s name defaults to the metric you first select as you configure the widget. If you select a different metric, then the widget’s name does not update.
- Search for and select either the queues or users you want represented in the widget. To see and select inactive and deleted users in the User search results, select Include inactive users or Include deleted users.
- For graph widgets, select Split filters to display each user or queue separately instead of together as one bar.
- Click Configuration.
- Select a metric from the list. Note: You cannot filter for multiple queues and select user status metrics, such as Available Agents or On Queue Agents. You can only select these metrics if you filter by a single queue. If you filter for multiple queues and select a status metric, PureCloud resets the queue filter to a single queue.
- Depending on the metric you select, you can also select the date spans and media types for the widget. Note: If you do not select any media types, the widget displays information for all of the media types.
- (Optional) To change a metric’s color when it is above or below a certain number, click Warnings, then click Add warning. Specify above or below, the number, and the color you want the metric to turn when it meets those criteria.
- Click Save.
Edit previously-created widgets.
- Click Performance > Dashboards.
- Hover over a dashboard and click Edit dashboard.
- To edit a widget on the dashboard, click Edit this widget.
Add a new widget that has the same settings as another widget. For example, if you want to add a widget with the same users, media types, and date span as a current widget but with a different metric, you can copy the widget and change the metric.
- Click Performance > Dashboards.
- Hover over a dashboard and click Edit dashboard.
- Click Copy this widget. A new widget appears on the dashboard with the same settings as the copied widget and (copied) added to the title .
Move and organize widgets on your dashboard.
- Click Performance > Dashboards.
- Hover over a dashboard and click Edit dashboard.
- To move widgets around on your dashboard, click the top bar on the widget and drag and drop it.
Change the grid size to choose how many widgets the dashboard can display on a dashboard. By default, the grid size is 3 x 4, which allows you to have four rows of up to three metric widgets or one graph widget per row. You can display up to seven rows and up to seven metric widgets or one graph widget in each row.
To change the grid size, click Grid Size. Then select which size grid you want.
You cannot select a grid size smaller than current size of grid that you are using. In the grid size selector, squares with a circle indicate which sections of the dashboard grid that already have a widget.
Display your dashboard in full-screen mode.
- Click Performance > Dashboards.
- Hover over a dashboard and click View dashboard. Tip: For the best full-screen mode viewing experience, make sure that the dashboard is in viewing mode, instead of edit mode, before viewing it in full-screen mode. To view a dashboard in viewing mode, click Toggle edit mode.
- Click View fullscreen.
- To exit full-screen mode, press Escape.
Available Metrics
| Metric | Description |
|---|---|
| Abandon | The number of interactions where a customer disconnects in an ACD queue before connecting with an agent. For example, the customer hangs up before an agent answers, or the system disconnects 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 |
| Answer | 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. |
| Answer % | The percentage of offered interactions that an agent answered. Calculated by: (Answered / Offered) * 100 |
| 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 |
| 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. |
| 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. |
| Avg Hold | The average number of seconds that interactions were placed on hold. Calculated by: Total Hold Time / Count of interactions with holds |
| 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 Wait | The average amount of time an interaction is in a queue before an agent answers it, it flows out, or the customer abandons it. Calculated by: Total Wait Time / Interactions |
| 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. |
| Flow-Out % | The percentage of offered interactions that enter and leave a queue without getting answered by an agent or disconnected. Calculated by: (Flow-Out Count / Offered Count) * 100 |
| 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. |
| Hold | The number of interactions with holds. |
| Interactions | The number of interactions assigned to the queue that agents are currently interacting with. |
| Longest Interaction | The amount of time that the longest current active interaction in the queue has been interacting. |
| Offered | The number of interactions routed into the queue for an agent to answer. Offered interactions are either answered, abandoned, or flow-out interactions. |
| Outbound | This metric represents the number of outbound interactions placed on behalf of queue. |
| 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 Admins can also choose to include short abandons in the calculation. For more information, see Configure the service level calculation. If you include short abandons, 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 short abandoned interactions) *100. |
| 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. |
| 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 Hold | The cumulative hold time for all interactions. |
| Total Talk | Amount of time spent interacting on a media type. |
| Transferred | 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. |
| Waiting | The number of interactions waiting to be answered. Waiting is calculated by the sum total of the number of interactions waiting. |
| Longest Waiting | The amount of time that the longest-waiting interaction has been waiting in queue. |
| Available Agents | The number of agents off queue and in the Available status. |
| Away Agents | The number of agents off queue and in the Away status. |
| Break Agents | The number of agents off queue and in the Break status. |
| Meal Agents | The number of agents off queue and in the Meal status. |
| Training Agents | The number of agents off queue and in the Training status. |
| Busy Agents | The number of agents off queue and in the Busy status. |
| Meeting Agents | The number of agents off queue and in the Meeting status. |
| On Queue Agents | The On Queue metric represents the number of agents that are on queue for a specific queue. |
| Off Queue Agents | Off Queue represents the number of agents that are off queue for a specific queue. These agents are in another status, such as Available, Busy, or Meeting. Agents in the Out of Office and Offline statuses are not included in this number. |
| Communicating Agents | The agent is on a non-ACD call, and, in relation to agent utilization and call routing, PureCloud treats the non-ACD call like an ACD call. For example, administrators could configure agent utilization so PureCloud does not route new interactions to agents while they on an ACD or non-ACD call. This status only appears if administrators have selected “Include non-ACD conversations” when they configured agent utilization. |
| Idle Agents | The number of agents who are on queue and available to take interactions but who are not working with interactions. |
| Interacting Agents | The number of agents working with interactions. This number includes agents completing after call work. |
| Not Responding Agents | An agent was On Queue or Interacting and did not answer an offered interaction. The agent could still be handling and completing other previous interactions. While Not Responding, the agent does not receive new interactions. |
| Offline Agents | The number of agents off queue and offline. |
| Metric | Description |
|---|---|
| Alerted | The number of times agents receive an alert for interactions. |
| Answer | 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. |
| Answer % | The percentage of offered interactions that an agent answered. Calculated by: (Answered / Offered) * 100 |
| 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. |
| Avg Alert | The average amount time PureCloud alerts agents before the agent accepts or declines an 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. |
| Avg Hold | The average number of seconds that interactions were placed on hold. Calculated by: Total Hold Time / Count of interactions with holds |
| Avg Talk | The average number of seconds spent interacting on a media type. Calculated by: Total Talk time/ Count of interactions with Talk time. |
| 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. |
| Hold | The number of interactions with holds. |
| 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. |
| Total Alert | The total time PureCloud alerts agents before the agent accepts or declines an interaction. |
| 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 Hold | The cumulative hold time for all interactions. |
| Total Talk | Amount of time spent interacting on a media type. |
| Transferred | 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. |
| Metric | Description |
|---|---|
| Abandon | The number of interactions where a customer disconnects in an ACD queue before connecting with an agent. For example, the customer hangs up before an agent answers, or the system disconnects 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 |
| Answer | 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. |
| Answer % | The percentage of offered interactions that an agent answered. Calculated by: (Answered / Offered) * 100 |
| 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 |
| 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. |
| 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. |
| Avg Hold | The average number of seconds that interactions were placed on hold. Calculated by: Total Hold Time / Count of interactions with holds |
| 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 Wait | The average amount of time an interaction is in a queue before an agent answers it, it flows out, or the customer abandons it. Calculated by: Total Wait Time / Interactions |
| 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. |
| Flow-Out % | The percentage of offered interactions that enter and leave a queue without getting answered by an agent or disconnected. Calculated by: (Flow-Out Count / Offered Count) * 100 |
| 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. |
| Hold | The number of interactions with holds. |
| Offered | The number of interactions routed into the queue for an agent to answer. Offered interactions are either answered, abandoned, or flow-out interactions. |
| Outbound | This metric represents the number of outbound interactions placed on behalf of queue. |
| 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 Admins can also choose to include short abandons in the calculation. For more information, see Configure the service level calculation. If you include short abandons, 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 short abandoned interactions) *100. |
| 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. |
| 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 Hold | The cumulative hold time for all interactions. |
| Total Talk | Amount of time spent interacting on a media type. |
| Transferred | 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. |
| Metric | Description |
|---|---|
| Alerted | The number of times agents receive an alert for interactions. |
| Answer | 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. |
| Answer % | The percentage of offered interactions that an agent answered. Calculated by: (Answered / Offered) * 100 |
| 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. |
| Avg Alert | The average amount time PureCloud alerts agents before the agent accepts or declines an 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. |
| Avg Hold | The average number of seconds that interactions were placed on hold. Calculated by: Total Hold Time / Count of interactions with holds |
| Avg Talk | The average number of seconds spent interacting on a media type. Calculated by: Total Talk time/ Count of interactions with Talk time. |
| 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. |
| Hold | The number of interactions with holds. |
| 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. |
| Total Alert | The total time PureCloud alerts agents before the agent accepts or declines an interaction. |
| 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 Hold | The cumulative hold time for all interactions. |
| Total Talk | Amount of time spent interacting on a media type. |
| Transferred | 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. |