DNIS Performance Summary view
The following permissions:
- Analytics > Conversation Aggregate > View
- Analytics > Data Export > All
- Routing > Queue > View
- UI > Supervisor DNIS Performance > View
- UI > Supervisor Queue Details > View
The DNIS Performance Summary view displays statistics for inbound calls based on the DNIS a customer dials to reach your contact center. These statistics can help supervisors determine performance issues with a specific DNIS number in one or multiple queues.
To see the view, go to Performance > Workspace > Contact Center > DNIS Performance. To see a breakdown of metrics by interval for a specific DNIS number, click that DNIS to go to its DNIS Performance Detail view.
This view does not update automatically. To see the most current data, click Refresh .
Set a default time zone in the workspace
You can set the default time zone in the analytics workspace before viewing any analytics view.
To set the default time zone in the workspace, follow these steps:
- Click Performance > Workspace.
- On the left side, from the Time zone drop-down menu, select the required time zone as the default time zone for the analytics workspace.
To save the view with your filter and column settings, click Save .
To export the data in the view, click Export .
View queues in a DNIS
To see the queues and related metrics for a DNIS, click in the DNIS number’s row. The queues and their data display under the DNIS number’s row.
For more information about a queue, click the queue name. The Queue Performance Detail view for that queue opens with the DNIS and Direction: Inbound filters active to represent the DNIS.
Customize the view
To show only certain data, customize the DNIS Performance Summary view. 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 customize analytics views, use the date filter.
To filter metrics by date or configure a custom date range, use presets. When filtering metrics for this view, select any custom date range up to 6 weeks.
To use a preset to filter metrics, complete the following steps:
- To display the date filter, click the date.
- In the Presets list, select a preset date option.
Date presets
| Presets | Description |
|---|---|
| Current interval | Shows data for the current 30-minute time period. |
| Today | Shows data for the time period that includes the current interval. |
| Yesterday | Shows data for the previous day. |
| This week | Shows data for a Sunday through Saturday time period. |
| Last week | Shows data for the previous week, Sunday through Saturday. |
| Previous 7 days | Shows data for the previous seven days. |
| This month | Shows data for the current month, with no extra days. |
| This month by week | Shows data for the current calendar month starting on Sunday and ending on Saturday, including extra days if the month does not start on Sunday or end on Saturday. |
| Last month | Shows data for the previous calendar month with no extra days. |
| Previous 30 days | Shows data for the previous 30 days. |
| Previous 3 months | Shows data for the previous 3 months. For example, Nov 1, 2022 – Jan 31, 2023. |
| Interval | Shows data for a 30-minute time period. |
| Day | Shows data for a single 24-hour day. |
| Week | Shows data for a Sunday through Saturday time period. |
| Month | Shows data for the exact month with no extra days. If the current month is selected, you can see the data up to the current date. |
| Month by Week | Shows data for a calendar month starting on Sunday and ending on Saturday, including extra days if the month does not start on Sunday or end on Saturday. |
To use a custom date range to filter metrics, complete the following steps:
- Click the date to display the date filter.
- Select a start date and an end date on the calendar, and click the filter arrow .
To view data for a different time period using the same date presets, click the arrows on either side of the date display. 
For example, to view data for the previous day, click the Day preset, and then click the arrow on the left side of the date.
To view data for a different time zone using the same date presets, from the Time zone drop-down menu, select the required time zone. You can create and save reports with the same selected time zone.
Data in the view can be displayed in a chart. To view the chart, click the Show/Hide chart icon .
To show or hide topic columns, click the Pick columns icon on the right side and then search or scroll to select the columns you want to view.
To rearrange topic columns, click a column header and drag it.
To reset a view to default column settings, click Reset view to defaults 
.
You can select up to 20 topic columns.
For more information about the metrics shown in the columns, see the Available Columns section in this article.
To enter the DNIS number you want to view, click the Filter by full DNIS search icon . Enter the full DNIS number in the Filter by full DNIS field, and select the DNIS number from the search results. You can continue to enter and select additional DNIS numbers to add to the view.
- Enter only the DNIS number, including the country code. For example, enter 13172223333. Do not include other characters such as +, -, or ( ).
- Enter the full DNIS number, such as 13172223333. The filter cannot search for a partial DNIS number.
Filter by selecting multiple DNIS numbers
You can select multiple DNIS numbers to filter by.
- In the DNIS number’s row, select the check box.
- Continue selecting DNIS number check boxes to add to filters.
- Click Add to filters.
View aggregate data
To view aggregate data for the filtered DNIS numbers, click View as group. Genesys Cloud displays the DNIS Performance Detail view with aggregate data for the DNIS numbers you selected.
To filter by information about the interaction, click Filters , and then search or scroll to select the filter you want to use.
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. |
| Skills |
Displays metrics for interactions with agents who have the selected skills. Filter for multiple skills at one time by entering other skills and searching again. |
| Languages |
Displays metrics for interactions with agents who have the selected languages. Filter for multiple languages at one time by entering other languages and searching again. |
| User |
Displays metrics for interactions associated with the selected users. Filter for multiple users at one time by entering other users and searching again. To see and select inactive users in the User filter search, select Include inactive users. |
| Wrap-Up |
Displays information for interactions that have the selected wrap-up codes. Filter for multiple wrap-up codes at one time by entering other wrap-up codes and searching again. |
| Originating Direction | The initial direction of the interaction, such as inbound or outbound. |
| Provider | The source provider for the conversation. For example, Genesys Cloud EMAIL, Edge, and so on. |
| Routing Used | Displays the routing method that was used to get to the agent who answered the interaction. The routing data is relevant beginning September 5, 2020. |
| Routing Requested | Displays the routing methods that were requested for the interaction. Gives insight into each of the routing methods the conversation went through prior to being answered, abandoned, or flow-out. The routing data is relevant beginning September 5, 2020. |
| External Tag | Displays information for interactions that have the External Tag attached to the conversation record. Note: External tag data is not available for web chat interactions. |
To filter by information about the Predictive Engagement journey details of the interaction:
- Click Filter .
- Click the Journey tab.
Journey filters
| Filter | Description |
|---|---|
| Has Customer Journey Data | Displays data for interactions that have customer journey data related to Predictive Engagement. |
| Proactive | Displays data for interactions where Predictive Engagement offered a chat during a customer's website visit based on the Predictive Engagement action map settings. |
To filter by information about External Contact details of the interaction:
- Click Filter .
- Click the External Contact tab.
External Contact filters
| Filter | Description |
|---|---|
| External Contact | Displays information about interactions associated with the selected external contact. You can filter for:
When you filter by external contact, the contact name appears with the associated organization name. Filter for multiple external contacts at one time by entering another contact and searching again. Enable Include merged contacts to search all the contacts that relate to the external contacts in the filter. Note: You can associate each merged contact with many individual contact IDs. When you enable the Include merged contacts, all merged contact IDs are automatically added to the search. The search filters are limited to 200 total search dimensions.
For example, if you merge one contact into five other contacts, the search, performed along with the merged contacts, filters a total of six contacts. If an organization heavily uses the merged contacts, a search for a few external contacts can hit the search filter limit. |
| External Organization | Displays information about interactions associated with the selected external organization. You can filter for:
Filter for multiple external organizations at one time by entering another organization and searching again. |
Available columns
Your customizations determine which metric columns the view shows.
| Column | Description |
|---|---|
| Column | Description |
| DNIS | The number dialed by the calling party. |
| 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. |
| Avg Abandon | The average amount of time before 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. |
| 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. |
| 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 the 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 Answered (tAnswered Sum) / Answered Count (tAnswered Count) Note: Raw values are provided in milliseconds. |
| Service Level % |
Service level target is a contact center performance statistic expressed as “X percent of conversations 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. Note: In the skill group row, the Service Level target displays a -. To view individual queue service level target values for each queue, click the + to expand the row.
The service level % is the percentage of interactions that meet your contact center's service level target. The formula to calculate the service level % is:
Number of Conversations Answered within SLA The numerator is calculated by taking the total answered conversations and subtracting the conversations that were not answered within the SLA threshold. Calculated by: (Answered Count – SLA Violation Count) Total Number of Conversations The Service Level Options configuration determines the denominator. With all the options below unchecked, the denominator is the count of answered conversations.
As the service level calculation depends on an organization’s configured options, the final formula to calculate the service level is:
Note: With the Flowouts and Abandons enabled, the Flowouts and the Abandons are added into the denominator when calculating the service level. With the Short Abandons disabled, the Short Abandons are subtracted from the Abandons when calculating the service level.
In this view, the service level set for the queue appears as a gray number beside the service level percentage for the interval. If the service level percentage for the interval is lower than the set service level, then the service level percentage is red. |
| IVR | The number of times interactions entered an IVR. An interaction can enter an IVR more than one time. |
| Avg IVR |
The average amount of time interactions that enter an IVR stay in an IVR. Calculated by (Total IVR time / number of interactions with IVR) |
| Total IVR | The total amount of time that interactions spent in IVRs. |
| 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. |
| 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. 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 with ACW |
| Total Handle | The total amount of time agents spend on an interaction including time spent contacting, time spent dialing, talk time, hold time, and after call work. |
| Total Talk | The total amount of time spent interacting on all the conversations by the agent, within an interval. For example, in an interaction, where an agent accepts an interaction, talks to the customer for two minutes, places the customer on hold for one minute, and then talks to the customer again for two minutes, the Total Talk equals 4 minutes. |
| Total Hold | The cumulative hold time for all interactions. |
| Total ACW | The cumulative time spent in after-call work (ACW) on all interactions. 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. |
| 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. |
| Connection | The number of interactions that initially connected to the contact center in a particular location, such as a queue or IVR. |
| Transfer % | The number of transfers compared to the total number of interactions answered. Calculated by: (# of transfers / interactions answered) * 100 |
| Max Abandon | The maximum time of an abandoned interaction for the selected interval. |
| Min Abandon | The minimum time of an abandoned interaction for the selected interval. |
| Max Wait | The maximum amount of time spent waiting in queue for the selected interval. |
| Min Wait | The minimum amount of time spent waiting in queue for the selected interval. |
| Max Talk | The maximum amount of time spent interacting for the selected interval. |
| Min Talk | The minimum amount of time spent interacting for the selected interval. |
| Max Hold | The maximum amount of time spent on hold for the selected interval. |
| Min Hold | The minimum amount of time spent on hold for the selected interval. |
| Max ACW | The maximum amount of time spent on after call work for the selected interval. |
| Min ACW | The minimum amount of time spent on after call work for the selected interval. |
| Over SLA | Number of interactions that were over the defined Service Level. |
| Met SLA | Number of interactions that met the defined service level. |
| Short Abandon | Number of interactions that were short abandoned. |
| Short Abandon % | Percent of interactions that were short abandoned. |
| Abandon – No Short | Number of abandons excluding the short abandons. |
| Abandon – No Short % | Percent of abandons excluding the short abandons. |
| Outbound Attempt | Attempted outbound interactions for Dialer campaigns. |
| Voicemail | Count of voicemails received. |
|
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. |
|
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. |
|
Max Handle |
The maximum amount of time agents were involved in ACD and non-ACD interactions, including answered interactions, transfers, callbacks, and outbound calls. |
|
Min Handle |
The minimum amount of time agents were involved in ACD and non-ACD interactions, including answered interactions, transfers, callbacks, and outbound calls. |
|
Max IVR |
The maximum amount of time interactions that enter an IVR stay in an IVR. |
|
Min IVR |
The minimum amount of time interactions that enter an IVR stay in an IVR. |
|
Talk |
The number sessions where user(s) interacted during conversations. A session includes the point where the agent joins the conversation to the point where they disconnect. |
|
Total Abandon |
The total amount of time interactions are in queue waiting for an agent to answer them before customers abandoned the interactions. |
|
Total Wait |
The total amount of time an interaction is in a queue before an agent answers it, it flows out, or the customer abandons it. Genesys Cloud calculates the wait time in milliseconds. |
|
Wait |
The number of interactions that waited in the queue. |
|
Avg Flow Out |
The average amount of time an interaction spends in queue before it flows out. Calculated by: Total Flow Out Time / Count of interactions with flow-outs For more information, see Queues Performance Summary view. |
|
Max Flow Out |
The maximum amount of time an interaction spends in queue before it flows out. For more information, see Queues Performance Summary view. |
|
Min Flow Out |
The minimum amount of time an interaction spends in queue before it flows out. For more information, see Queues Performance Summary view. |
Extra columns for export
The export contains two extra columns: DNIS and DNIS Name.
| Location | Column Name | Description |
|---|---|---|
| DNIS Performance Export | DNIS | The number dialed by the calling party or the raw sip address value |
| DNIS Performance Export | DNIS Name | The number dialed by the calling party |
