You can customize the Real-Time Queues View to display the queue statistics that you want to monitor in your contact center.
The Real-Time Queues View is rendered by the QueuesStatsView
component. This programmable Flex UI component contains the following children components:
QueuesStats.AggregatedQueuesDataTiles
(key:
tiles
)
QueuesStats.QueuesDataTable
(key:
table
)
You can modify QueuesStatsView
via the Content
property:
1// Remove all tiles from the view2QueuesStatsView.Content.remove("tiles");3// Add your own component4QueuesStatsView.Content.add(<CustomTiles key="custom-tiles" />, {5sortOrder: 06});7
1import * as Flex from "@twilio/flex-ui";2import { connect } from "react-redux";34// Connect to Flex's redux store and display the number of wrapping tasks5const WrappingTasksTile = connect((state: Flex.FlexState) => {6const queues = Object.values(state.flex.realtimeQueues.queuesList);7const wrappingTasks = queues.reduce((sum, q) => sum + q.tasks_by_status.wrapping, 0);89return {10wrappingTasks: wrappingTasks.toString(),11};12})(({ wrappingTasks }) => (13<Flex.AggregatedDataTile title="Wrapping Tasks" content={wrappingTasks} />14));151617// Add the WrappingTasksTile to the view18Flex.QueuesStats.AggregatedQueuesDataTiles.Content.add(19<WrappingTasksTile key="wrapping-tasks-tile" />,20{ sortOrder: -1 }21);
To add custom tiles or remove existing tiles, modify QueuesStats.AggregatedQueuesDataTiles
. Out of the box, this child component contains the following aggregated data tiles:
active-tasks-tile
)
waiting-tasks-tile
)
longest-wait-time-tile
)
agents-by-activity-chart-tile
)
1import { ColumnDefinition } from '@twilio/flex-ui';23// Remove the original column4Flex.QueuesStats.QueuesDataTable.Content.remove("waiting-tasks");56// Create a new column with custom formatting7Flex.QueuesStats.QueuesDataTable.Content.add(8<ColumnDefinition9key="my-waiting-tasks"10header="Waiting tasks"11content={(queue: Flex.QueuesStats.WorkerQueue) => {12// Calculate number of waiting tasks by adding pending and reserved13const { pending, reserved } = queue.tasks_by_status;14const waitingTasks = pending + reserved;1516// Set the style to color: red if # of waiting tasks is > 1017const spanStyle = waitingTasks > 10 ? { color: "red" } : {};1819// Return the element to render20return <span style={spanStyle}>{waitingTasks}</span>;21}}22/>,23{ sortOrder: 1 } // Put this after the second column24);
The child component QueuesStats.QueuesDataTable
lets you add or remove columns in the QueuesDataTable. Out of the box, the QueuesDataTable has the following columns:
friendly-name
)
active-tasks
)
waiting-tasks
)
longest-wait-time
)
agents
)
To add a column, add a ColumnDefinition
component to QueuesStats.QueuesDataTable
. If you want custom formatting on a default column, remove the original column and create a new one.
The defaultSortColumn
and sortDirection
properties are only available in @twilio/flex-ui@1.19.0 and later. Sorting capabilities are only available in @twilio/flex-ui@1.14.0 and later.
You can click on the header of a predefined column to sort the QueuesDataTable by those values. By default, the table is sorted by queue name.
To change the column the table is sorted by, set the following property to the key of the column that you want to use:
QueuesStats.QueuesDataTable.defaultProps.defaultSortColumn = "column-key"
When adding a custom column, you can specify the parameter sortingFn: (a, b) => number
, which works the same way as the compareFunction
parameter in JavaScript's Array.sort()
.
The default order of sorting is descending. To change the direction to ascending, use the sortDirection
property on the ColumnDefinition
component.
If you change the order by inverting the value returned from sortingFn
, the visualization in the column header will not display correctly.
In this example, you display a new column with pending tasks and allow sorting by the values in this column:
1Flex.QueuesStats.QueuesDataTable.Content.add(2<ColumnDefinition3key="pending-tasks"4header="Pending tasks"5content={(queue: Flex.QueuesStats.WorkerQueue) =>6queue.tasks_by_status.pending7}8sortingFn={(9a: Flex.QueuesStats.WorkerQueue,10b: Flex.QueuesStats.WorkerQueue11) => a.tasks_by_status.pending - b.tasks_by_status.pending}12sortDirection="asc"13/>14);15
Filtering is only available in @twilio/flex-ui@1.14.0 and later. Subscription filters are available in @twilio/flex-ui@1.24.0 and later.
Out of the box, all of your queues display in the Flex UI. If you want to hide queues or only show specific queues, you can apply a filter:
1QueuesStats.setFilter((queue: Flex.QueuesStats.WorkerQueue) =>2queue.friendly_name !== "Invisible Queue"3);
The setFilter
takes a single parameter, a filter function with a signature of (queue: WorkerQueue) => boolean
. This function will be evaluated for each queue and added to the view if the return value is true
.
For larger contact centers with a large number of queues, it may be more adequate to use the setSubscriptionFilter
that is available in @twilio/flex-ui@1.24.0 with the SLA feature enabled. Unlike setFilter
, this filter will stop the UI from subscribing to updates from hidden queues, which results in improved performance of the page.
We recommend to subscribe to 100 or less queues for optimal performance. Subscribing to a high number of queues may be demanding on user internet connectivity and hardware.
The setSubscriptionFilter
lets you filter queues only by name or SID:
1const visibleQueues = ["Everyone", "Sales"];23QueuesStats.setSubscriptionFilter((queue: { friendly_name: string; sid: string }) =>4visibleQueues.includes(queue.friendly_name)5);
Both filters do not affect the numbers in the global numbers of available agents. However, using a filter might cause a discrepancy between the number of agents you see in individual queues in the QueuesDataTable and the Agents panel that shows the global number of available agents.
This feature is in Public Beta and available in @twilio/flex-ui@1.27.0 and later.
The SLA metrics feature adds the following columns to Flex.QueuesStats.QueuesDataTable
:
sla-30min
)
sla-today
)
handled-tasks-30min
)
handled-tasks-today
abandoned-tasks-30min
)
abandoned-tasks-today
)
SLA metrics are calculated by both the last 30 minute floating window and the current business day.
After the feature is enabled, you can remove any of the default columns listed above or add additional columns with SLA metrics. See the full list of available metrics.
1const RenderShortAbandoned30Min = (workerQueue: Flex.QueuesStats.WorkerQueue) =>2// QueuesDataTableCell component helps us render additional expandable rows with channel specific data3<Flex.QueuesStats.QueuesDataTableCell4// Pass the queue data down5queue={workerQueue}6// Render the queue level value7renderQueueData={(queue) => queue.sla_30_min.short_abandoned_tasks_count}8// Render a value for each active channel in the queue9renderChannelData={(channel, queue) => channel.sla_30_min.short_abandoned_tasks_count}10/>1112const RenderShortAbandonedToday = (workerQueue: Flex.QueuesStats.WorkerQueue) =>13<Flex.QueuesStats.QueuesDataTableCell14queue={workerQueue}15renderQueueData={(queue) => queue.sla_today.short_abandoned_tasks_count}16renderChannelData={(channel, queue) => channel.sla_today.short_abandoned_tasks_count}17/>181920Flex.QueuesStats.QueuesDataTable.Content.add(21<Flex.ColumnDefinition22key="short-abandoned-30min"23header="Short Abandoned"24// Since our columns have the same header, we can set25// the same headerColSpanKey on both to merge their headers.26headerColSpanKey="short-abandoned"27subHeader="30 min"28content={RenderShortAbandoned30Min}29/>30);3132Flex.QueuesStats.QueuesDataTable.Content.add(33<Flex.ColumnDefinition34key="short-abandoned-today"35header="Short Abandoned"36headerColSpanKey="short-abandoned"37subHeader="Today"38content={RenderShortAbandonedToday}39/>40);
In this snippet, Flex adds two columns to QueuesDataTable
that show the number of short abandoned tasks in the last 30 minutes and for the day. You can use the QueuesDataTableCell
in the content render function to add additional expandable rows of channel-specific data.
You can configure the time a new business day starts and all SLA threshold values in the admin plugin or via the Flex Configuration API. There are three levels of SLA configurations:
default
queue_configurations
queue_channel_configurations
Each lower level overrides the one above it. For example, a queue_configurations
object has priority over the default
configuration and a queue_channel_configurations
object has priority over the default
configuration and matching queue_configurations
object.
The request body is validated by the Flex Configuration API and must adhere to the following requirements:
default
configuration, even if you set
queue_configurations
and/or
queue_channel_configurations
in the same request.
Each configuration object included in the request must contain all required properties. The required properties for each configuration object type are as follows:
default
service_level_threshold
short_abandoned_threshold
reset_timezone
reset_time
queue_configurations
queue_sid
reset_timezone
reset_time
queue_channel_configurations
queue_sid
channel_sid
service_level_threshold
short_abandoned_threshold
After you submit a configuration change, your changes are not applied until the next time a task is received. Consider creating a test task to ensure that your changes are applied right away.
When you update reset_time
, your update might cause Today metrics to show more than 24 hours of data. If the current reset time is 5:00am and you update it to 7:00am, but no tasks come in until 8:00am, the day won't reset at 7:00am because your change didn't take effect. As a result, the Today metrics will show 26 hours of data, from 5:00am through 7:00am the next day.
1# Any change to configuration will take approximately 10 min to reflect.2# New task has to land in the queue or channel with a new configuration in order to see the change.3# For the list of possible timezones see: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones45curl -X POST https://flex-api.twilio.com/v1/Configuration \6-u ACxxx:your_auth_token \7-H 'Content-Type: application/json' \8-d '{9"account_sid": "ACxxx",10"queue_stats_configuration": {11"default": {12"service_level_threshold": "20",13"short_abandoned_threshold": "5",14"reset_timezone": "GMT",15"reset_time": "08:00"16},17"queue_configurations": [18{19"queue_sid": "WQxxx",20"reset_timezone": "GMT",21"reset_time": "08:00"22}23],24"queue_channel_configurations": [25{26"queue_sid": "WQxxx",27"channel_sid": "TCxxx",28"service_level_threshold": "20",29"short_abandoned_threshold": "5"30}31]32}33}'
The WorkerQueue
data object is extended with the sla_30_min
and sla_today
keys. These keys are both of the type WorkerQueueSLA
, which contains all available SLA metrics for queues:
total_tasks_count
handled_tasks_count
handled_tasks_within_sl_threshold_count
handled_tasks_within_sl_threshold_percentage
short_abandoned_tasks_count
short_abandoned_tasks_percentage
abandoned_tasks_count
abandoned_tasks_percentage
flow_out_tasks_count
flow_out_tasks_percentage
sla_percentage
If a queue handles multiple channels, the SLA data is also available per channel. The channels
key on the WorkerQueue
contains an array of WorkerQueueChannel
, which has the following keys:
sid
unique_name
friendly_name
sla_30_min
(
WorkerQueueSLA
)
sla_today
(
WorkerQueueSLA
)
workerQueue.channels[0].sla_30_min.total_tasks_count
This feature is only available in @twilio/flex-ui@1.20.0 and later.
1Flex.QueuesStats.QueuesDataTable.Content.add(2<Flex.ColumnDefinition3key="custom-column-1"4header="My Column"5headerColSpanKey="my-column"6subHeader="Foo"7content={YourContentRenderer1}8/>9);1011Flex.QueuesStats.QueuesDataTable.Content.add(12<Flex.ColumnDefinition13key="custom-column-2"14header="My Column"15headerColSpanKey="my-column"16subHeader="Bar"17content={YourContentRenderer2}18/>19);
You can add subheaders to columns using a subHeader
property on ColumnDefinition
.
If adjacent columns have the same header and you want to merge these table header cells, set the same headerColSpanKey
on these columns.
The full screen view is only available in @twilio/flex-ui@1.14.0 and later.
To display queue statistics on a TV or a monitor, use the full screen view by clicking the small button in the bottom-right corner.
The button is hidden by default. To enable the button, set the following property:
QueuesStatsView.fullscreen.enabled = true