최근 검색
최근 검색 없음

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
댓글