How to count the # of reassigned tickets per agent

Hi Oliver, 

Good question! The metric "assignee reassignments" is what is tripping you up I think. If you look at the underlying formula, you'll see it's entirely about the Assignee ID changing. It sounds like what you want to know, is how many times a specific agent changed the group, of a ticket though:

I would recommend creating a macro for escalations, with a specific tag that gets applied, as it will be a lot easier report on these escalations across all the datasets, and not have to use the "updates" dataset, which is particularly convoluted to understand as a human. 

However, we can still do what you want in this dataset. There's a couple of options. If your inexperienced people are all in the same group, like tier 1, and you want to know every time a ticket changes from group Tier 1, to group Tier 2, we can do that. 

You could "D_COUNT(Tickets updated)" if you just want to know the total number of tickets escalated. However, if you want to see if the agent escalated the same ticket multiple times, you'll want to use D_COUNT(Updates). 

You will also want to set up a filter for "Changes - Field Name" and set it "group_id". This is one of those "not great for humans" parts. You will need to get the group_id for the groups you are investigating. You can get this by navigating to the group page and pulling it out of the URL, or using the API. 

For the Tier 1 group_id, we're going to add another filter for Changes - Previous Value, and put in the group ID. For the Tier 2 group_id, we're going to another filter, called "Changes - New Value" with this one.

Now the Dataset knows you only want to look at Updates where the Field "group_id" changed from Tier 1, to Tier 2. We're almost there! 

Add "Updater Name" to the Rows, and filter for the specific agents you want to include. Add in a filter for "Update - Date" if you want to limit the time of the re-assignment to something like "last week".  You should have something like this:
If limited to select agents or it's not a lot of updates, you can add in Ticket Id, to see which tickets specifically were moved by that agent:

Just wanted to share that the below formula in the Updates History Dataset worked for me to be able to track the number of times an agent reassigned a ticket from themselves.
 

Create a Custom Metric called “Agent Transfers”
IF ([Changes - Field name] = "assignee_id" 

AND NUMBER([Changes - Previous value]) = [Updater ID]

AND NUMBER([Changes - New value]) != [Updater ID])

THEN [Update ID]

ENDIF

Limit the aggregator to COUNT

Hi Oliver,

The issue is that “Assignee reassignments” does not reliably represent escalation activity, especially when you’re trying to track movement between user groups.

That metric is designed around changes in assignee identity, and it won’t correctly capture group-to-group routing (like Level 1 → Senior Team), which is what you’re actually trying to measure.

A more accurate approach:
Use the Updates history dataset, since escalations are recorded as field changes rather than a single metric.

Configure the query as follows:

• Filter: Changes - Field name = group_id
• Add condition:
  • Changes - Previous value = Tier 1 group ID
  • Changes - New value = Senior Team group ID
• Metric:
  • COUNT(Update ID) → counts every escalation event
  • or D_COUNT(Tickets updated) → if you want unique tickets escalated
• Optional:
  • Filter by Updater name to attribute escalations to specific L1 agents
  • Apply Update date = last week

Why this works:
This directly captures the state transition between groups, which is the only reliable definition of escalation in Explore.