Metrics and attributes for Zendesk Support

Return to top
Have more questions? Submit a request

106 Comments

  • Nuno Parreira

    Hello!

    I have the same question as Karl: https://support.zendesk.com/hc/en-us/articles/360022182114/comments/360004920854

    How can we check the current requester wait time?

    Thanks

    0
  • Devan - Community Manager
    Zendesk Community Team

    Hello Nuno Parreira,

    I would recommend utilizing the following metric in your report. You can find more info on this and more in our Metrics and Attributes article.

    Requester wait time (min) The number of minutes a ticket spends in the New, Open, and On-hold statuses. This number is only measured after a ticket status is changed from New/Open/On-hold/Pending/Solved/Closed.

    (Requester wait time (min))

     

    Best regards. 

    0
  • Jorge Yeber

    I have a question about the metric Field changes Time (min)). Im building a calculated metric using the next code 

    IF(
    [Changes - Field name]="Motivo Contacto"
    and [Changes - Previous value] = NULL
    AND [Changes - New value]!= NULL
    ) THEN VALUE(Field changes time (min))
    ENDIF

    When I use the calculated metric these returns an emptyvalue. Why could occured that?

    0
  • Elissa
    Zendesk Community Team

    Hi Jorge Yeber

    I checked in with one of our Explore team and they said the metric you made may be returning empty values for a number of reasons: you may have misspelled the field name, you could be using the wrong dataset in the report you're using it in, there may be no tickets that have Motivo Contacto as a value in the subset of ticket's you're looking at.

    Another good point is that if at any point in the life of the ticket that field changed to NULL, even if it is not NULL now, the code you have excludes that ticket. So for tickets that change back and forth, those would not show up with this metric.

    This recipe may help you get it sorted out a bit: Explore recipe: Reporting on the duration of fields.

    If that does't help I'd recommend contacting support so one of our advocates can help you troubleshoot in context and pinpoint what is going wrong!

    0
  • CJ Johnson

    The Update - Timestamp Attribute appears to be missing from the Dataset for Support Updates. I'd love to know how this is calculated, as I'd like to make one that drops off the seconds from this timestamp. 

    0
  • Rob Stack
    Zendesk Documentation Team

    Hi CJ Johnson, thanks for the question. As there are a bunch of different time-based attributes, we don't list them all individually. There are a couple of ways you could tackle this:

    1. Create your own attribute with just the elements you need like Year, Hour, etc. There's a great example of this at https://support.zendesk.com/hc/en-us/articles/360022298254
    2. I think that the timestamp is always exactly the same length so you should be able to create a standard calculated attribute that returns only the first 16 characters of the Update - Timestamp attribute. The formula would look something like:

    LEFTPART([Update - Timestamp],16)

    I hope this helps to spark some ideas!

    -1
  • David Coleman

    Does an Answer Bot reply count as a agent First Reply? 

    0
  • Brett Bowser
    Zendesk Community Team

    Hey David,

    Excellent question! Answer Bot reply does not count towards the First Reply Time metric. FRT requires a public response from an agent on the account.

    Let me know if you have any other questions!

    1
  • David Coleman

    Awesome! Thank you.

    0
  • Crawford Philleo

    I'm wondering if there is a way to get the (Agent Replies) metric on the Tickets data set to reflect only public comments by agents that do not contain a specific string. I'm noticing that this metric is pulling in values when we've merged a ticket. I wouldn't count this as a "reply" to the requester. Is this possible? So in my use case, I'd want to be able to have a metric called like "Actual Replies" which would be the same as (Agent Replies) minus comments that include the string "was closed and merged into".

    0
  • CJ Johnson

    Is there any plan to include an "end-user replies" in the Support Default dataset? It seems extremely strange that it's not available in this one. 

    0
  • Elaine Hilario
    Zendesk Customer Advocate

    Hi Crawford,

    Agent Replies metric always counts all public replies that are sent by your Agents within a ticket.

    Agent Replies      The number of public replies added to a ticket by an agent.

    If you're referring to the merging process where you're making the merge comments that include the string "was closed and merged into" public, you actually have the option to make this private so that this comment will not be included in the count of Agent Replies moving forward (kindly see Step 5 on To merge one ticket into another ticket in the article I mentioned above).

    You can also set the default privacy for all ticket comments which can be done by an Admin to make merge comments deselected, and for them to be posted as a private comment by default.

    Hope I was able to clear this out. Cheers! :)

    0
  • Elaine Hilario
    Zendesk Customer Advocate

    Hi CJ,

    If you use the Ticket updates Dataset in creating a query, you can actually find the End-user comments as a Metric.

    End-user comments The number of end-user comments on tickets. IF ([Comment present] = TRUE AND [Updater role] = "End-user") THEN [Update ID] ENDIF

    Hope I pointed you in the right direction. Cheers :)

    -1
  • CJ Johnson

    Elaine Hilario That doesn't help me unfortunately, I mentioned I was asking about the Support Default dataset. You cannot use the End User comments very effectively at all in the Updates dataset, because it gets constrained by the time frame. So if you want to see # of end user replies  on tickets created last week, you can't, because then it will only count end user replies at the time of the ticket creation, which is not helpful. That is why my question called out the default dataset. Additionally, the default set has agent replies, but not end-user, which really feels like an oversight. 

    0
  • Elaine Hilario
    Zendesk Customer Advocate

    Sorry if I wasn't able to answer you in one go. Lemme try again, CJ. :)

    You can actually use the End-user comments from the Ticket updates Dataset as how you're expecting it.

    You can use the ticket creation date as a filter and then use any ticket update metrics on your query to show the data that you needed just like on the screenshot below:

    As you can see, the End-user comments do not show just the number upon creation of a ticket only which should be a value of 1. Instead, it actually shows the total number of End-user comments in a ticket's lifetime.

    I hope this time I was able to provide you the expected answer. Cheers! :)

    -1
  • CJ Johnson

    Hi Elaine,
    Try it again with "Tickets Created" as the Metric and end user replies as the attributes, and you should get 0s across the board. My request that end user replies be included in the Default dataset still would be helpful, IMO. This was available like this in Insights. 

    0

Please sign in to leave a comment.

Powered by Zendesk