Conversation Segment Kinds

Segments of this kind can be used to count and measure the time agents spent in the various defined activities.

An Agent Status segment is virtual - there is no Task associated with it because we're creating artificial segments to allow you to mix activity-based metrics with conversation-based ones. At the same time, it's important to remember that agent status activities are not tied to agent phone activities (unless you explicitly set it in your implementation). This means an agent status can be "Available" while they are on the call.

We gather activity values from WorkerActivityUpdate events. Agent status segments in Flex Insights do not overlap - rather, the end of one status indicates the beginning of the next.

Here's the list of built-in metrics and attributes you can use to build custom reports for agent activity analysis:

The time (in seconds) that an agent spent on this activity.

SELECT Activity Time WHERE Kind = Agent Status

The activity start time expressed in seconds.

SELECT Time in Seconds

You can segment activity-based metrics by the following attributes: Activity, Agent, Date, Time, and Segment. Make sure you also include the Kind attribute filtered for the value "Agent Status".

A sample activity report:

Agent Status in Progress is a segment that represents an activity agent was in during the last load of data into Flex Insights Historical Reporting. Agent Status in progress give more insight into what agent was doing recently and enable better reporting on intraday agent adherence. When an agent switches their agent status and new data are loaded into Flex Insights Historical Reporting the Kind attribute is set to Agent Status and Activity Time is set.

Agent Status in Progress segments are not shown in any reports by default. Built-in reports filter their content by Kind attribute which exclude Agent Status in Progress. You can build custom reports that contain both finished activities together with activities in progress. Or you can build reports dedicated to activities in progress.

Agent Status in Progress segments do not have Activity Time set to any value. Empty Activity Time will influence also metrics that depend on it. The exact behavior depends on definition of the metrics.

Conversation segments are the segments you'll use most often for analyzing conversations.

These segments contain a number of metrics, as they are populated from Task attributes in TaskRouter. Here are the basic ones:

The amount of time a customer spent in a queue before this segment.

SELECT Queue Time

The time (in seconds) that a customer or an agent spent hearing ringtones before reaching the other party.

SELECT Ring Time 

The time a customer spent speaking with an agent. This includes all periods of silence and can be thought of as the time between answering the phone and hanging up.

SELECT Talk Time 

The time an agent spent wrapping up work following a conversation with a customer.

SELECT Wrap Up Time

The segment start time expressed in seconds.

SELECT Time in Seconds

You can segment conversation metrics by many attributes. Some of the most frequently used are: Queue, Agent, Customer, Date, Time, Segment and Conversation.

Make sure you also include the Kind attribute filtered for the value "Conversation".

Conversation in Progress is segment that represents a segment on which an agent started working (accepted their reservation) but has not finished it (including wrap up) before the last load into Flex Insights Historical Reporting. Conversations in progress give more insight into longer conversations that are currently in progress. After an agent completes the segment and new data is loaded into Flex Insights Historical Reporting the Kind attribute is set to Conversation and all expected attributes and metrics become available.

Conversations in Progress are not shown in any reports by default. Built-in reports filter their content by Kind attribute which exclude Conversation in Progress. You can build custom reports that contain both finished Conversation segments together with Conversation in Progress segments. Or you can build reports dedicated to Conversation in Progress. In a multitasking environment there might be multiple conversations in progress for a single agent.

Conversations in Progress segments do not have Talk Time and Wrap Up Time metrics set to any value. Empty Talk Time and Wrap Up Time will also influence metrics that depend on them. The exact behavior depends on the definition of the metrics.

Missed Conversation segments are typically analyzed on the agent level to track individual performance.

If agents are expected to answer calls within a specified time limit, it can be useful to monitor agent performance using these records.

The distinct count of missed segments by an agent.

SELECT COUNT(Segment) WHERE Kind = Missed Conversation

The time in seconds an agent spent hearing a ringtone before the call timed out.

SELECT Ring Time

You can segment metrics related to missed conversations by the following attributes: Agent, Queue, Date, Time and Segment.

Make sure you also include the Kind attribute filtered for the value "Missed Conversation".

Queue segments show the portion of the call when a customer entered a queue and any time spent waiting in the queue before being connected with an agent.

For each queue entered by the customer, a new Queue segment is created in Flex Insights. This can come in especially handy when your customer flows from one queue to another before connecting with an agent.

Using Queue segments is also convenient if you'd like to analyze the volume of calls from the timestamp when a call entered the queue, rather than when it was answered.

The following metrics are relevant for Queue segments:

The time a customer spent in a given queue.

SELECT Queue Time

The segment start time expressed in seconds.

SELECT Time in Seconds

You can segment queue metrics by the following attributes: Queue, Date, Time, Segment and Conversation.

Make sure you also include the Kind attribute filtered for the value "Queue".

Rejected Conversation segments are typically analyzed on the agent level to track individual performance.

Because agents are not expected to reject calls, it can be useful to monitor agent performance using these records.

The distinct count of segments rejected by an agent.

SELECT COUNT(Segment) WHERE Kind = Rejected Conversation

The time in seconds the agents spent hearing a ring tone before rejecting the call.

SELECT Ring Time

You can segment metrics related to rejected calls by the following attributes: Agent, Date, Time and Segment.

Make sure you also include the Kind attribute filtered for the value "Rejected Conversation".

Flex Insights provides data on important events that happen within the life of each Task.

By breaking a conversation into segments of different kinds, you can present the path of a customer contact.

Here's how you can read this type of Flex Insights report:

07:21:33 - Customer entered the "Level 1" queue and waited for 1:12 (72 seconds).

07:22:44 - Customer connected with an agent, John Doe, from the Level 1 queue. They talked for 02:17 (137 seconds) and then the customer was transferred to the "Level 2" queue.

07:25:01 - Customer entered the "Level 2" queue.

07:25:02 - Agent Alba Perez' phone rang for 2 seconds without a connection to the customer.

07:25:04 - Customer abandoned the call after 3 seconds of waiting in the "Level 2" queue.

Corrupted Conversation Segment represents a portion of a conversation between a customer and an agent. Flex Insights was unable to determine all the metrics because some events related to the conversation are missing. These segments might appear in case there is an incident or unexpected behavior in Flex. Flex Insights provides visibility into these segments for transparency.

These segments are not reported by default. As Flex Insights could not confidently calculate some of the key metrics including them in reports could lead to skewing aggregate metrics. You can build custom reports focused on these segments.