Conversation metric events can be used to track reply times and close times.
For example, if you want to measure reply times, you can get the time a conversation was created and the time an agent first replied to it. If you want to measure close times, you can get the time the conversation was created and the time its status was changed to closed.
The times are reported as metric events or events that are related to each of the two metrics:
close_time. You can access the following three types of metric events, with different events for each type depending on the metric:
- activate events, such as when a conversation is created in the case of all two metrics
- fulfill events, such as when an agent first replies to a ticket in the case of the reply time metric, or when a ticket is closed in the case of the close time metric
- pause events, such as when a conversation is snoozed in the case of all two metrics
Conversation Metric Events are represented as JSON objects with the following properties:
|Automatically assigned when the record is created.
|The instance of the metric associated with the event.
|Id of the associated conversation.
|The metric being tracked. Allowed values are reply_time, close_time
|The type of the metric event. Allowed values are: activate, pause, fulfill.
|If the event triggered is triggered by an agent or a pre-defined rule.
|The time the event occurred.
An activate event represents when the clock starts running for that particular metric. In the case of the
close_timemetric when instance_id is 0, the time usually corresponds to the time the ticket was created. Activate events are also used to indicate that a ticket metric is no longer snoozed.
A pause event represents a conversation metric that hasn't been fulfilled yet but was paused according to the metric's conditions. Pause event get triggered when a conversation is snoozed by an agent or a business rule. When the conversation re-opens another activate event is created. Pause events are recorded for
A fulfill event represents a conversation that was updated in such a way that the end state of that metric has been fulfilled. For example, for the
reply_timemetric, a fulfill event occurs when an agent replies to that conversation or when the conversation status is changed to closed. For the
close_timemetric, a fulfill event occurs when the conversation’s status is changed to closed. It's possible for a conversation metric to be fulfilled and then un-fulfilled. For example, the
reply_timemetric is fulfilled when a reply has been sent. If the conversation receives a new message, the
reply_timemetric starts again where it left off. Fulfill events are recorded for all metrics.
instance_id property to track each instance of a metric event that can occur more than once per conversation, such as the
reply_time event. The value increments over the lifetime of the conversation.
The actor defines who initiated the event it can be an agent, a business rule, or null.
"name": "Tushar Mahajan",