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

Chad Dodds
参加日2021年4月15日
·
前回のアクティビティ2021年10月26日
フォロー中
0
フォロワー
0
合計アクティビティ
28
投票
14
受信登録
9
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Chad Dodds
Chad Doddsさんがコメントを作成しました:
@..., I think your radio buttons can be eliminated with a couple of notes and a behavior clarification for checkbox #2 to preserve the assigned agent: checking it would require and also auto-check the box to preserve the group.
Follow-up ticket options:
[] Preserve assigned group when a follow-up ticket is created. If the group no longer exists, assigns to NO group.
[] Preserve assigned agent when a follow-up ticket is created. If the agent account no longer exists or is no longer a member of the assigned group, assigns to NO group with NO agent.
コメントを表示 · 投稿日時:2021年4月07日 · Chad Dodds
0
フォロワー
0
投票
0
コメント
Chad Doddsさんが投稿を作成しました:
We have several teams operating in Zednesk Support from technical support to equipment service to order management. Our customers sometimes email us and place multiple different support address on the To: line. I would like to request a new trigger condition under Received at that allows us to detect Greater Than or Greater Than or Equal To conditions, same for Less Than. Right now, the only choice under Received at is the 'is' condition to specify a single email. With this in hand, I could take a variety of actions including just letting the team know to review the ticket to determine if a second ticket should be manually created.
投稿日時:2019年9月24日 · Chad Dodds
13
フォロワー
14
投票
9
コメント
Chad Doddsさんがコメントを作成しました:
Thanks for the article Amanda. I'm sure the method works well, but I am not willing to create or maintain a trigger for each agent in our Zendesk as we have nearly 80 of them and the list is not always static due to turnover. This functionality could be made available via a setting with a few choices to pick from:
- Automatically assign a new follow-up ticket to the original assignee
- Automatically assign a new follow-up ticket to the original group
- Do not automatically assign new follow-up tickets (this is today's behavior)
It could also be incorporated into the trigger system for greater flexibility, but I'm not sure if great flexibility is needed for this.
コメントを表示 · 投稿日時:2017年8月17日 · Chad Dodds
0
フォロワー
12
投票
0
コメント
Chad Doddsさんが投稿を作成しました:
Hello, I would like to request that you add a placeholder for the customer satisfaction bad rating reason. We use a trigger to notify all team leads when a bad rating is received. This notification includes information about the rating and ticket, and I would like to add the reason to this list:
Requester: {{ticket.requester.name}}
Assignee: {{ticket.assignee.name}}
Group: {{ticket.group.name}}
Ticket ID: {{ticket.id}}
Link: {{ticket.link}}
Satisfaction comment: "{{satisfaction.current_comment}}"
Thanks!
投稿日時:2016年8月17日 · Chad Dodds
42
フォロワー
36
投票
32
コメント