Skip to contentSkip to navigationSkip to topbar
Rate this page:
On this page

Conversation Segment Kinds


While a Segment represents granular data and is primarily associated with customer conversations, we also use segments to represent other call center events and activities. You can distinguish between these using the attribute Kind in your Insights reporting.

Using Kind, you can filter the segments to analyze the following:

KindDescription
Agent StatusA segment that represents an agent's activity state in a given time period. These segments are not related to conversations.
Agent Status in ProgressA segment that represents an agent's activity state that is in progress. More precisely the agent status in which the agent was at the time of the last load of data into Historical Reporting. Kind of segments in progress change to Agent Status value once the agent transitions to another activity and new data load happens after that.
ConversationA segment representing a portion of a conversation between a customer and an agent. A conversation can consist of several segments of this kind.
Conversation in ProgressA segment representing a portion of a conversation between a customer and an agent that is in progress. More precisely an agent was in talk phase or wrap up phase at the time of the last load of data into Historical Reporting. Kind of segments in progress change to Conversation value once the agent completes the wrap up phase and new data load happens after that.
Missed ConversationA segment representing an unsuccessful attempt to connect a customer to an agent that ended because of a routing timeout (i.e., the agent didn't pick up the phone within an expected time interval), task cancelation or caller hang-up (abandoned). On the TaskRouter level, this is a reservation that an agent missed due to a timeout or because the reservation was canceled before the agent accepted it. There may be multiple missed conversation segments for a single conversation, as each agent who missed a reservation is represented by a separate segment.
QueueA segment representing a customer or agent waiting in a queue.
Rejected ConversationA segment representing a reservation that was explicitly rejected by an agent or agent went offline while the reservation was offered. There may be multiple rejected conversation segments for a single conversation, as each agent who rejected a reservation is represented by a separate segment.
Corrupted Conversation SegmentA segment representing 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.

Below you can find more details about each kind of segment, what to use them for, and with which metrics and attributes.

(warning)

Warning

Programmatically modifying the value of Kind in a conversation segment may cause Flex not to be able to play back the segment. Use a custom conversation attribute instead, as described in Enhance your Conversation Data.


Agent Status

agent-status page anchor

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:

Activity Time

activity-time page anchor

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


_10
SELECT Activity Time WHERE Kind = Agent Status

The activity start time expressed in seconds.


_10
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:

SegmentDateTimeAgentActivityActivity Time
105/09/20190:19Danny RichtPlanned Break0:15:55
205/09/20190:35Danny RichtBusy1:32
305/09/20190:36Danny RichtAvailable2h 33:34
405/09/20193:10Danny RichtLunch9:12
505/09/20194:07Danny RichtAvailable1h 29:21

Agent Status in Progress

agent-status-in-progress page anchor

Agent Status in Progress is 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.


_10
SELECT Queue Time

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


_10
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.


_10
SELECT Talk Time

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


_10
SELECT Wrap Up Time

The segment start time expressed in seconds.


_10
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".

ConversationSegmentQueueDateTime in SecondsAgentQueue TimeRing TimeTalk TimeWrap Up Time
11Level 105/10/20196h 42:15John Doe00:0800:0700:3400:57
12Level 205/10/20196h 42:59Alba Perez00:0900:0902:4008:00
13Level 305/10/20196h 45:45Dwayne Right00:0700:0602:5112:27

Conversation in Progress

conversation-in-progress page anchor

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 agent completes the segment and new data are 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 influence also metrics that depend on them. The exact behavior depends on 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.


_10
SELECT COUNT(Segment) WHERE Kind = Missed Conversation

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


_10
SELECT Ring Time

Missed Conversation Attributes

missed-conversation-attributes page anchor

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".

SegmentKindAgentQueueDateTimeMissed SegmentsRing Time
1Missed ConversationJohn DoeSupport04/03/201911:56120
2Missed ConversationJohn DoeSupport03/28/201912:34120
3Missed ConversationJohn DoeSupport04/02/201914:48120
4Missed ConversationJohn DoeSupport04/02/201914:49120

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 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.


_10
SELECT Queue Time

The segment start time expressed in seconds.


_10
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".

ConversationSegmentKindQueueDateQueue TimeTime in Seconds
12341QueueLevel 105/10/201900:076h 42:08
12342QueueLevel 205/10/201903:316h 42:50
12343QueueLevel 305/10/201900:096h 45:39

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.


_10
SELECT COUNT(Segment) WHERE Kind = Rejected Conversation

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


_10
SELECT Ring Time

Rejected Conversation Attributes

rejected-conversation-attributes page anchor

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".

SegmentKindAgentQueueDateTimeRejected SegmentsRing Time
1Rejected ConversationJohn DoeSupport04/03/201913:0612
2Rejected ConversationJohn DoeSupport03/28/201915:0214

Task Lifecycle of a single Conversation

task-lifecycle-of-a-single-conversation page anchor

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.

SegmentKindQueueAgentAbandonedTime in SecondsRing TimeTalk TimeQueue Time
1QueueLevel 1No7h 21:3301:12
2ConversationLevel 1John DoeNo7h 22:4400:0402:1701:12
3QueueLevel 2Yes7h 25:0100:03
4Missed ConversationLevel 2Alba Perez7h 25:0200:0200:00
5ConversationLevel 2Yes7h 25:0400:03

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

corrupted-conversation-segment page anchor

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.


Rate this page: