Understand how Flex Insights splits voice conversations into segments and how it calculates handling time. Conversations are the backbone of the Insights Analytics Data Model.
Segment is an atom of any conversation. A segment represents an interval in time dedicated to certain phases during a
Segments can be of different
- This segment captures the time from when a customer entered the queue until they left that queue. Queue time is captured during this segment.
- This segment defines the time from when a customer is connected to an agent until the communication ends or they are transferred elsewhere.
Conversation represents communication between one customer and any agents with whom they interact within the contact center.
A conversation where one customer speaks to one agent will be composed of (at least) two segments:
In a call with one cold transfer, the conversation will typically have four segments (2 of Queue & 2 of Conversation kind segments):
Conversations can be further organized into
Initiatives, which provide higher-level groupings of Conversations. For more details, check out the Insights Analytics Data Model.
Handling and Experience Time
Handling Time is the time an agent spends handling a customer task, including wrap-up work that happens after the task is completed.
Handling Time- The time agents spend handling a customer task.
Experience Time- The time a customer spends trying to resolve their issue, including time spent in queue and time communicating with your agents.
Depending on the communication channels involved, all handling and experience time information may not be available.
Your agents will make outbound calls when they do cold calling, warm calling, or reach out to your existing customers.
Handling Time of an Outbound Conversation is the sum of
Talk Time and
Wrap Up Time.
Ring Time in the total handling time, as your agent is blocked from other activities when trying to reach customers.
If a dialer places the call, the time the dialer spends ringing is not included in
Ring Time and therefore not included in
When a customer calls your contact center, they can go through a sequence of steps depending on your infrastructure.
Usually, the following activities occur. A Twilio phone number is dialed and, depending on the phone number's configuration, the customer can go to an IVR. If the customer was not able to solve their problem, they queue up to wait for an available agent. This all happens before the customer speaks with an agent.
Handling Time for inbound conversations does not include
Ring Time as the agent is not blocked at the moment.
Handling Time starts when the customer connects to an agent.
Ring Time is part of Queue Time in Flex Insights. Queue time ends when a call is answered by an agent.
IVR Only conversations are conversations where customers managed to solve their request using an IVR application or they were not successful and just gave up before entering a queue.
Handling Time for IVR-Only conversations is always
Time spent in an IVR is not captured in Flex Insights by default. In order to surface IVR related metrics, you'll need to pass them through TaskRouter events as attributes.
Cold (blind) transfers
If an agent cannot handle a customer request for some reason, they can forward it to another agent or a queue.
For example, a Level 1 support agent can transfer customers with very technical questions to the Level 2 support queue.
conversation with a transferred call normally has 4 Segments.
Handling Time represents how much time your agents spend handling the customer's inquiry. The Handling Time of this conversation is the sum of the Handling Times of two conversation segments (where
Conversation), even when the Handling Times overlap because they are handled by two agents.
Need some help?
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.