최근 검색
최근 검색 없음

Gerardo
가입한 날짜: 2021년 10월 16일
·
마지막 활동: 2023년 12월 29일
팔로잉
0
팔로워
0
총 활동 수
141
투표 수
62
플랜 수
35
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Gerardo
Gerardo님이 에 게시물을 만듦
Hi whoever is able to reply to my question,
I am having trouble by creating an accurate report based on tags.
Creating a group attribute with tags and using the D_Count Ticket metric doesnt help.
Issue is that some Tickets have multiple tags of the Group created and for this reason are counted twice or more.
Example.
Group A = Tag_1 Tag_2 Tag_3
Group B = Tag_4 Tag_5 Tag_6
Ticket contains Tag_3 and Tag_5 counts as 2 tickets for Group A and Group B
Also by separeting the tags they are counted twice for tickets.
How can I count the number of tickets that contains multiple tags but not risking making it count mulitple times?
2023년 2월 10일에 게시됨 · Gerardo
1
팔로워
2
투표 수
1
댓글
Gerardo님이 에 댓글을 입력함
Hi,
how are follow-up tickets considered in the one touch tickets?
I have noticed that every ticket is counted separately.
The same for merged tickets. I know that we can exclude merged tickets, but do we consider follow-up tickets.
For me this should be not considered a one touch ticket.
Main ticket= 1 customer message + 1 agent reply = ticket closed
Follow-up ticket= 1 customer message + 1 agent reply
The above should not be considered one touch ticket, how do I calculate this?
댓글 보기 · 2022년 12월 02일에 게시됨 · Gerardo
0
팔로워
0
투표 수
0
댓글
Gerardo님이 에 댓글을 입력함
Hi there,
Will there be an option to see the live data for SLA like breached and achieved or also by SLA metrics?
Or is this already available?
댓글 보기 · 2022년 10월 12일에 게시됨 · Gerardo
0
팔로워
0
투표 수
0
댓글
Gerardo님이 에 게시물을 만듦
Hi,
The audit section could have more filters by example filtering who did the action or on which account the action was made.
Example scenario:
Agents suspends an account or marks a tickets as spam. There is no way to identify who did this action. Unless you scroll the entire audit log list until you find something, but this can take some time.
2022년 7월 26일에 게시됨 · Gerardo
2
팔로워
5
투표 수
2
댓글
Gerardo님이 에 게시물을 만듦
Hi,
Is there any workaround to create views based on SLA metrics?
Or conditions to add tags to tickets with SLA metrics?
Or anything that can be filtered in Zendesk support to identify which tickets is closed to be breached and which metric if Reply time or Solved time?
Any workaround?
I was thinking to add a tag when agent replied to a ticket and remove it when customer reply. In this way we can filter with all tickets that still need a reply and attention from us.
How would be that possible?
2022년 7월 22일에 게시됨 · Gerardo
1
팔로워
3
투표 수
0
댓글
Gerardo님이 에 댓글을 입력함
Hi there,
Is there a way to filter the SLA for reply and solving time?
Ideal would be to have a view for each. Or a to add a tag dedicated to one of both breached.
Or a way to prioritize one to another?
Example for us might be important to reply time over the solving time when breached.
Or to sort them based on metrics
댓글 보기 · 2022년 6월 17일에 편집됨 · Gerardo
0
팔로워
0
투표 수
0
댓글
Gerardo님이 에 댓글을 입력함
Hi Heather Rommel,
We followed all the steps above and thank you for this powerful hint.
I have a question about this part
We get the error that the account is not authorized, we add the email of the Jira integration account created as service account, what is the token here to add? the one of the api connection the same as for the password?
The error
댓글 보기 · 2022년 4월 28일에 편집됨 · Gerardo
0
팔로워
1
투표
0
댓글