Loading...
Loading...
Loading...
Previous suggested step: Performance dashboards overview
Next suggested step: Performance dashboard owners
The following permissions:
The following permissions for the agent activity widget:
Notes:
To display the performance metrics that you want to see for the queues, users, wrap-up codes, flows, or flow outcomes that are important to you, create dashboards. You can also create a dashboard to view web content such as streaming videos, real-time charts, news feeds, and social media. To view dashboards, perform the following:
Create a display for your contact center by viewing your dashboard in full-screen mode.
Widgets display metrics and visual information on your dashboard. For Metric and Chart widgets, select which queues, users, wrap-up codes, flows, or flow outcomes to use for the widget. Then select the metrics, date span, and media types you want to see in the dashboard. You can add color-changing warnings to let you know when metrics are above or below a specified level. To bring interactive content into your dashboard, add a Web Content widget and specify a URL.
To rename a dashboard from the Performance Dashboard summary page:
To rename a dashboard from the Performance Dashboard detail page:
When you edit the old dashboard, the Preview Dashboard option appears at the lower right corner of the edit dashboard page.
To permanently view your old dashboard in the new dashboard format:
To continue using the old dashboard format, in the edit dashboard page, click Remind Me Later at the lower right corner of the page. You can preview your dashboard in dark/light mode. To preview the dashboard in dark/light mode, in the lower right corner, click the Dark Mode toggle switch.
Administrators can access and manage public, private, and shared dashboards created by all users in an organization. The dashboard summary page lists all the users in the organization who have dashboards. The administrators can bulk delete dashboards of a single user or multiple users to control the total number of dashboards within the organization. The administrators can delete up to 100 dashboards at a time.
To delete multiple dashboards from the Performance Dashboard summary page:
To delete a single dashboard from the Performance Dashboard summary page:
To delete a dashboard from the Performance Dashboard detail page:
You can also bulk delete dashboards from the Dashboard owners page. For more information, see Performance dashboard owners.
Widgets display metrics and visual information about the queues, users, wrap-up codes, flows, and flow outcomes that you choose. You can add up to seven rows of widgets, and each row can include up to seven single-cell widgets or one full-width widget. For more information about adding more rows of single-cell or full-width widgets to your dashboard, see the Edit layout section in this article.
When you work with widgets, you can click the following to drill down to its corresponding performance view.
This section describes configuring and adding filters to metric, chart, web content, agent status, and agent activity widgets.
Supervisors can perform real-time monitoring of the dashboards to monitor the conversation activity of the agents based on their segment types such as alert, callback, coaching, contacting, dialing, hold, interact, monitoring, parked, scheduled, sharing, transmitting, voicemail, and wrap up. Segment refers to the conversation segment.
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.
If the number of visible widgets reaches the grid size limit, Duplicate is not available. For more information about adding more rows to your dashboard, see the Edit layout section in this article.
You can move up to seven single-cell widgets to a row, or one full-width widget to a row. To change the grid size to fit more single-cell widgets in a row, see the Edit layout section in this article.
Change the grid size to choose the number of single-cell or full-width widgets to display on a dashboard. By default, the grid size is 3 x 4, which allows you to have four rows of up to three single-cell widgets or one full-width widget per row. You can display up to seven rows and seven single-cell widgets or one full-width widget in each row.
You cannot select a grid size smaller than the current grid size that you are using. In the grid size selector, squares with a circle indicate which sections of the dashboard grid already have a widget.
Public access is sharing the permission organizationally wide. Only if a person is given permission, that person accesses the widgets. A person who does not have access to the specified permission and division cannot view the widgets in a dashboard. A dashboard can have users, queues, flows, flow outcomes, and wrap-ups. Each dashboard item has permission and division requirements. For example, Jane Doe added a metric widget belonging to Division 1. James added a metric widget belonging to Division 2. If James makes his dashboard public and does not give access to Jane to view the widgets in Division 2, then Jane cannot view James’s dashboard.
You can only make the old dashboards public. The supervisors can share the performance dashboards with anyone within their organization, specific work teams, or users. For more information about performance dashboard sharing, see Share Performance dashboards.
You can add filters to restrict the person from accessing the dashboard. A yellow banner at the top of the view indicates limited access to the dashboard. If the person has no access to any widget in the dashboard, the dashboard is not visible to that person.
To make your dashboard visible to other users:
In the dashboard summary page, you can filter your dashboards to display the All, Public, Private, Shared, and Favorites dashboards. You can filter your dashboards based on dashboard ownership. To display only the dashboards that you own, choose the Owned by me filter. To display all the dashboards that you and others own or share, choose the Owned by anyone filter. To display the dashboards that others own and share, choose the Not owned by me filter.
To filter the dashboards by private, public, shared, and favorites:
To filter the dashboards based on ownership:
To filter the dashboards by dashboard types, such as active and deleted dashboards:
| Metric | Description |
|---|---|
Abandon | The number of times an end user abandoned an interaction in a queue. For example, the customer hangs up before an agent answers, or the system disconnects the interaction. |
Inbound Audio | The number of inbound audio or voice messages received from a customer. Notes: Since messaging is asynchronous, in rare instances, when an agent ends an interaction while an end customer finishes recording and sending a voice note, the last audio file attachment or voice note is not considered for analytics. The audio attachment of the conversation remains intact and is preserved as part of the conversation. There is no data loss. The agent still receives and views the voice note. You can see the impact only in the count of the inbound audio metric. The inbound audio metric can be undercounted. |
Outbound Audio | The number of outbound audio or voice messages sent by an agent. |
Abandon – No Short | Number of abandons excluding the short abandons. |
Abandon – No Short % | Percent of abandons excluding the short abandons. |
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 |
After-call work (ACW) | The number of times after-call work (ACW) was completed. 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. |
Alerting | The total number of alerting conversations. |
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 |
| Metric | Description |
|---|---|
After-call work (ACW) | The number of times after-call work (ACW) was completed. 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. |
Adherence Duration | The amount of time represented in days, hours, minutes, and seconds, of the adherence exception. |
Adherence Status | The current adherence status of the user, including In Adherence, Out of Adherence, Unscheduled, Ignored, or Unknown. |
Alert – No Answer | The number of times an agent was alerted to a conversation but did not answer the conversation. Note: This metric does not specifically count the number of times an agent was placed in a Not Responding routing status. An agent is transitioned to Not Responding status after a specific alert time threshold for ACD-routed conversations. Alert – No Answer can be incremented for all conversation types for any situation where an alert was not followed by an answer event. |
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. |
Available % | The percentage of time spent in the Available status for the specified period. |
Avg ACW | The average amount of time agents spent completing after-call work. Calculated by: Total ACW / Interactions with ACW |
Avg ACW Handled | The average time any interaction spent in ACW. This calculation takes into account all interactions handled, not just those that had ACW. Calculated by: Total ACW Time / Number of Interactions Handled |
Avg Alert | The average amount time Genesys Cloud alerts agents before the agent accepts or declines an interaction. |
| Metric | Description |
|---|---|
Available Agents | The number of agents in the work team who are off queue and in the Available status. |
Away Agents | The number of agents in the work team who are off queue and in the Away status. |
Break Agents | The number of agents in the work team who are taking a break and are not working. |
Busy Agents | The number of agents in the work team who are off queue and in the Busy status. |
Communicating Agents | The number of agents in the work team who are in the Communicating status. Note: The agent in the work team is on a non-ACD call, and, in relation to agent utilization and call routing, Genesys Cloud treats the non-ACD call like an ACD call. For example, administrators could configure agent utilization so Genesys Cloud does not route new interactions to agents while they are on an ACD or non-ACD call. This status only appears if administrators have selected “Count non-ACD calls in utilization capacity” within the agent utilization configuration. |
Idle Agents | The number of agents in the work team who are on queue and available to take interactions, but are not working on interactions. |
Interacting Agents | The number of agents in the work team who are working on interactions. This number includes the number of agents completing the after call work. |
Meal Agents | The number of agents in the work team who are off queue and in the Meal status. |
Meeting Agents | The number of agents in the work team who are off queue and in the Meeting status. |
Not Responding Agents | The number of agents in the work team who are 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. |
| Metric | Description |
|---|---|
After-call work (ACW) | The number of times after-call work (ACW) was completed. 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. |
Avg ACW | The average amount of time agents spent completing after-call work. Calculated by: Total ACW / Interactions with ACW |
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 Note: The interactions can span multiple time intervals. For example, a 45-minute call spans two 30-minute intervals. However, metrics are assigned a single timestamp and reported in the interval into which this timestamp falls. The timestamps are assigned based on when the metric calculation is complete. For instance, handle time will use the timestamp of after call work completion. In the example of a 45-minute call, the handle time falls in the second 30-minute interval because the handle time was calculated at the end of the call when ACW was submitted. |
Avg Hold | The average number of seconds that interactions were placed on hold. Calculated by: Total Hold Time / Count of interactions with holds |
Avg Park | The average amount of time an email was parked by an agent. |
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 that agents were involved in for the selected media type. 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. |
Max ACW | The maximum amount of time spent on after call work for the selected interval. |
Max Handle | The maximum amount of time agents were involved in ACD and non-ACD interactions, including answered interactions, transfers, callbacks, and outbound calls. |
| Metric | Description |
|---|---|
Active | The number of currently active flows. |
Avg Disconnect | The average amount of time until an entry disconnected in a flow. |
Avg Exit | The average amount of time that an entry spent in a flow before exiting. |
Avg Flow | The average amount of time that an entry spent in the flow. |
Avg Milestones | The average number of milestones per flow and flow outcome. |
Avg Outcomes | The average number of flow outcomes per entries into the flow. Calculated by: number of flow outcomes / number of entries |
Disconnect | The number of entries that disconnected in the flow. |
Disconnect % | The percentage of entries that disconnected compared with the total number of entries. |
Entries | The total number of times calls enter the flow or flow version. A call can enter a flow multiple times. |
Exit | The number of entries that exited the flow to another destination, such as an ACD queue, ACD voicemail, or user. |
| Metric | Description |
|---|---|
Avg Milestones | The average number of milestones per flow and flow outcome. |
Failure | The number of flow outcomes that were failures. |
Failure % | The percentage of failure outcomes compared with the total number of outcomes. |
Milestones | The total number of Milestones. |
Outcome Attempts | The number of flow outcomes. |
Outcome Avg Duration | The average amount of time that a call spent in a flow and flow outcome. |
Outcome Max Duration | The longest amount of time that a call spent in a flow and flow outcome. |
Outcome Min Duration | The shortest amount of time that a call spent in a flow and flow outcome. |
Outcome Total Duration | The total amount of time that calls spent in a flow and flow outcome. |
Success | The number of flow outcomes that were success. |
| Metric | Description |
|---|---|
Abandon | The number of times an end user abandoned an interaction in a queue. For example, the customer hangs up before an agent answers, or the system disconnects the interaction. |
Inbound Audio | The number of inbound audio or voice messages received from a customer. Notes: Since messaging is asynchronous, in rare instances, when an agent ends an interaction while an end customer finishes recording and sending a voice note, the last audio file attachment or voice note is not considered for analytics. The audio attachment of the conversation remains intact and is preserved as part of the conversation. There is no data loss. The agent still receives and views the voice note. You can see the impact only in the count of the inbound audio metric. The inbound audio metric can be undercounted. |
Outbound Audio | The number of outbound audio or voice messages sent by an agent. |
Abandon – No Short | Number of abandons excluding the short abandons. |
Abandon – No Short % | Percent of abandons excluding the short abandons. |
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 |
After-call work (ACW) | The number of times after-call work (ACW) was completed. 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. |
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 the queue before an agent answers. This metric does not include interactions that agents do not answer. Average Speed of Answer (ASA) is directly associated with the service level and provides insight into the customer service your organization provides. ASA is recorded in the interval in which the agent answered the interaction. Calculated by: Total Answered (tAnswered Sum) / Answered Count (tAnswered Count) Note: Raw values are provided in milliseconds. |
| Metric | Description |
|---|---|
After-call work (ACW) | The number of times after-call work (ACW) was completed. 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. |
Alert – No Answer | The number of times an agent was alerted to a conversation but did not answer the conversation. Note: This metric does not specifically count the number of times an agent was placed in a Not Responding routing status. An agent is transitioned to Not Responding status after a specific alert time threshold for ACD-routed conversations. Alert – No Answer can be incremented for all conversation types for any situation where an alert was not followed by an answer event. |
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. |
Available % | The percentage of time spent in the Available status for the specified period. |
Avg ACW | The average amount of time agents spent completing after-call work. Calculated by: Total ACW / Interactions with ACW |
Avg ACW Handled | The average time any interaction spent in ACW. This calculation takes into account all interactions handled, not just those that had ACW. Calculated by: Total ACW Time / Number of Interactions Handled |
Avg Alert | The average amount time Genesys Cloud alerts agents before the agent accepts or declines an interaction. |
Avg Contacting | The average amount of time an outbound interaction takes to connecting to the agent’s phone. Usually, this duration is short. However, if the agent uses a remote phone the duration may be longer. |
Avg Dialing | The average amount of time an agent spends dialing and waiting for a contact to answer during outbound interactions. Calculated by: (total dialing time/ total number of dialing segments) |
| Metric | Description |
|---|---|
After-call work (ACW) | The number of times after-call work (ACW) was completed. 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. |
Avg ACW | The average amount of time agents spent completing after-call work. Calculated by: Total ACW / Interactions with ACW |
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 Note: The interactions can span multiple time intervals. For example, a 45-minute call spans two 30-minute intervals. However, metrics are assigned a single timestamp and reported in the interval into which this timestamp falls. The timestamps are assigned based on when the metric calculation is complete. For instance, handle time will use the timestamp of after call work completion. In the example of a 45-minute call, the handle time falls in the second 30-minute interval because the handle time was calculated at the end of the call when ACW was submitted. |
Avg Hold | The average number of seconds that interactions were placed on hold. Calculated by: Total Hold Time / Count of interactions with holds |
Avg Park | The average amount of time an email was parked by an agent. |
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 that agents were involved in for the selected media type. Handle increments in the interval in which the interaction ends, after the agent completes any after call work and completes the interaction. |
Hold | The cumulative hold time for all interactions. |
Max ACW | The maximum amount of time spent on after call work for the selected interval. |
Max Handle | The maximum amount of time agents were involved in ACD and non-ACD interactions, including answered interactions, transfers, callbacks, and outbound calls. |
| Metric | Description |
|---|---|
Avg Disconnect | The average amount of time until an entry disconnected in a flow. |
Avg Exit | The average amount of time that an entry spent in a flow before exiting. |
Avg Flow | The average amount of time that an entry spent in the flow. |
Avg Milestones | The average number of milestones per flow and flow outcome. |
Avg Outcomes | The average number of flow outcomes per entries into the flow. Calculated by: number of flow outcomes / number of entries |
Disconnect | The number of entries that disconnected in the flow. |
Disconnect % | The percentage of entries that disconnected compared with the total number of entries. |
Entries | The total number of times that calls enter the flow or flow version. A call can enter a flow multiple times. |
Exit | The number of entries that exited the flow to another destination, such as an ACD queue, ACD voicemail, or user. |
Exit % | The percentage of exits compared with the total number of entries. |
| Metric | Description |
|---|---|
Avg Milestones | The average number of milestones per flow and flow outcome. |
Failure | The number of flow outcomes that were failures. |
Failure % | The percentage of failure outcomes compared with the total number of outcomes. |
Milestones | The total number of Milestones. |
Outcome Attempts | The number of flow outcomes. |
Outcome Avg Duration | The average amount of time that a call spent in a flow and flow outcome. |
Outcome Max Duration | The longest amount of time that a call spent in a flow and flow outcome. |
Outcome Min Duration | The shortest amount of time that a call spent in a flow and flow outcome. |
Outcome Total Duration | The total amount of time that calls spent in a flow and flow outcome. |
Success | The number of flow outcomes that were success. |
| Metric | Description |
|---|---|
Available | The number of agents in the Available status. |
Away | The number of agents in the Away status. |
Break | The number of agents in the Break status. |
Busy | The number of agents in the Busy status. |
Communicating | The number of agents in the Communicating status. |
Idle | The number of agents in the Idle status. |
Interacting | The number of agents in the Interacting status. |
Meal | The number of agents in the Meal status. |
Meeting | The number of agents in the Meeting status. |
Not Responding | The number of agents in the Not Responding status. |
| Metric | Description |
|---|---|
Routing Queue | The queue to which the conversation is routed and handled by the agent. |
Assigned Queue | The queue assigned to an agent. |
Segment Type | The type of segment the agent is in at the moment. For the list of supported segment types, refer to the Agent activity supported segment types section in this article. |
Media Type | The media type of the conversation that the agent handles. |
Routing Skills | The skills requested for the conversation as part of routing. |
Routing Languages | The languages requested for the conversation as part of routing. |
ACW | Displays the agents with pending wrap-up work. To view the agents who are in the after call work, click Show agents who are in ACW. |
User | The name of the agent. |
Reports to | The direct reporting manager assigned to an agent. |
Assigned Skills | The skills assigned to an agent. |
| Metric | Description |
|---|---|
Alert | Displays the duration and the list of agents in the alerting segment. |
Callback | Displays the duration and the list of agents in the callback segment. |
Coaching | Displays the duration and the list of agents in the coaching segment. |
Contacting | Displays the duration and the list of agents in the contacting segment. |
Dialing | Displays the duration and the list of agents in the dialing segment. |
Hold | Displays the duration and the list of agents in the hold segment. |
Interact | Displays the duration and the list of agents in the interact segment. |
Monitoring | Displays the duration and the list of agents in the monitoring segment. |
Parked | Displays the duration and the list of agents in the parked segment. |
Scheduled | Displays the duration and the list of agents in the scheduled segment. |
Get user feedback about articles.