Skip to main content

Summary of Zendesk legends and terminologies

 

Total solved tickets

Solved status indicates the agent has submitted a solution. So total number of tickets marked as Solved refers to total solved tickets within certain duration.

Solving a ticket and understanding how it is closed

Once you've resolved a requester's support issue, you change the ticket status to Solved, using the Submit button as described above. This should mean that you're done with the ticket and that the requester is satisfied with the resolution you provided. However, a requester can reopen the ticket after it has been set to Solved just by responding back and adding a new comment. For example, perhaps the requester disagrees that their support issue was resolved or that something new occurred that invalidates the fix.

After you set a ticket to Solved, the next status change is to Closed. However, you can't manually change a ticket to Closed; it is set to that status via a predefined business rule called an automation. An administrator creates automations and determines just how long tickets remain in the solved state before they are closed. If an administrator deactivates the automations that close tickets, the tickets will be closed automatically 28 days after they're solved. If you would like to manually change ticket to Closed, you can create a trigger as a workaround.

After a ticket's status has changed to Closed, the requester can no longer reopen it. They can, however, create a follow-up request that references the original, now closed, ticket. Agents can also create a follow-up for a closed ticket.

First reply time (FRT)

A metric that counts the number of minutes between the time a ticket is created, and the timestamp of the first public agent comment on that ticket.

How first reply time is calculated?

The Zendesk first reply time metric measures the time between ticket creation and the first public agent comment after that.

After the first public reply, Support stores the first reply time in calendar hours and calculates and stores the first reply time in business hours.

First reply time works the same regardless of the channel from which the ticket originates. For example:

  • A customer email creates a ticket. Timing starts when the ticket is created and ends at the first public agent comment.

  • An agent creates a ticket. Timing starts when the ticket is created and ends at the agent's next public comment.

  • An agent takes a phone call that creates a ticket and solves the ticket with no new comment. The customer later re-opens the ticket, and the agent then responds with a public comment. First reply time ends when that comment is posted.

Full resolution time

It is defined as the time between ticket creation time and the time of the final (or most recent) change of status to solved.

Scenario #1

If a ticket is solved once and then goes to Closed, the "Full Resolution" and "1st Resolution" times will be the same.

Scenario #2

If a ticket is solved, then reopened, and then solved again, the "1st Resolution" metric would show the time until it was solved initially, while "Full Resolution" would display the time until it was solved the 2nd time.

Comments

Popular posts from this blog

Unlock protected blocks in Siemens SIMATIC Step 7

Recently I'd been called by Hindalco's Fabrication Plant division to unlock the protected blocks in Siemens SIMATIC Step 7. They were in need to unlock those blocks since an year because of 1 million Rupees of loss per month. They want to re-program those blocks but it was locked by the man who'd done the setup. From the people working in that department, I came to know that they were trying to call that man (someone from Italy) right here but he's not coming. Actually, what he'd done was that he'd locked some of the blocks and deleted the source file. And Siemens didn't provide any feature to unlock. Department people also told me that even the people working in Siemens don't know how to do it. Being a software engineer I know that any thing can be reverse engineered. So I took up the challenge. How did I unlocked the blocks? The first thing I'd done was searched about this software at Google and read about what is this software all about. Aft

App: Calculate your job experience or age in years

Usually, all of those who works have to put years of experience on their resume or curriculum vitae. But 90% people put it wrong when they convert their experience in years only. Although they know the exact number of months and years but the conversion, they do is wrong. This happens because there are 12 months while the digit after decimal would be 0-9, i.e., 10 digits. Which means that we have to represent the number of months in terms of year. So here I have provided a small gadget to calculate it. Just put the date when you had started working in the From Date field and put current date in the To Date field. You can also calculate your age as well with this tool by putting your date of birth in the From Date field and put current date in the To Date field. As an alternative, you can use the hassle-free and simple to use  Date Differentiator  micro webapp. Bookmark it so you may easily access it later.

How to convert JIRA story into sub-task or defect?

Many times we entangled in the situation where we have made a  story  in JIRA but later on realised that it should have to be  defect  or in other case,  sub-task  of another  story . Story → Sub-task So the workaround for converting the story into defect is given below: Open your  story Click on  more  option Click on the  Convert to sub-task  option in the dropdown You would be asked to choose  Parent  story, so chose relevant story After submit, your  story  gets converted into  sub-task Story → Defect Now if you want the story to be converted into defect, then you should first convert it into sub-task. Thereafter, you can convert that sub-task into defect as given below: Open the  sub-task Click on  more  option Click on the  Convert to issue  option in the dropdown You would be asked to fill up relevant fields required for raising a  defect , fill them up as required After submit, your  sub-task  gets converted into  defect .