最近の検索
最近の検索はありません

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
コメント
Gerardoさんがコメントを作成しました: