Jacob J Christensen - Cloudhuset A/S
I work as a Solution Consultant at Cloudhuset A/S, helping clients create the best possible customer experience with Zendesk. Previously I have worked as the administrator of the Zendesk account at TOP-TOY, a major toy retail company in the Nordics. We used Zendesk (and Zopim) primarily for Customer Service, but also as an internal knowledge center for store-to-HQ communication (via Web widget & HC).
-
총 활동 수2181
-
마지막 활동
-
회원 가입일:
-
내가 팔로우하는 사용자 수9명
-
나를 팔로우하는 사용자 수15명
-
투표 수1060
-
수신 설정 수644
활동 개요
Jacob J Christensen - Cloudhuset A/S님의 최근 활동-
Jacob J Christensen - Cloudhuset A/S님이 에 댓글을 입력함
Hi Haaji SB That comment was explaining how this trigger works (at ticket creation): You can use the same condition (Priority is -) to have the trigger skip any tickets that already have a priorit...
-
Jacob J Christensen - Cloudhuset A/S님이 에 댓글을 입력함
Thanks Ben, it makes sense 👍
-
Jacob J Christensen - Cloudhuset A/S님이 에 댓글을 입력함
Hi Lester Gaddy I suspect that what you're seeing is that you have defined your target in business hours, but the Next breach value is always displayed (as I recall) in calendar hours. This articl...
-
Jacob J Christensen - Cloudhuset A/S님이 에 댓글을 입력함
Hi Ofer, The trigger conditions (see below) will fire the action for all new tickets unless there already is a priority set.
-
Jacob J Christensen - Cloudhuset A/S님이 에 댓글을 입력함
With these two conditions Ticket is created Priority is - Any tickets that already have a priority set will not be changed. You could also start with something other than "Normal", of course, age...
-
Jacob J Christensen - Cloudhuset A/S님이 에 댓글을 입력함
☝️ with this, SLA's should kick in from ticket creation.
-
Jacob J Christensen - Cloudhuset A/S님이 에 댓글을 입력함
Hi Ofer, There is a lot of flexibility available in regard to SLA's. In your case I would recommend having a trigger set a default priority at ticket creation. For example: Conditions (all) Ticket...
-
Jacob J Christensen - Cloudhuset A/S님이 에 댓글을 입력함
What is the reasoning for needing to remove the "requester is not current user" condition for triggers? remove the Requester - is not - (current user) condition if it exists. And what are the conse...
-
Jacob J Christensen - Cloudhuset A/S님이 에 댓글을 입력함
Will these Agent Workspace limitations be crossed off the lists as they are resolved? I would like to know how best to keep an eye on the development towards feature parity.
-
Jacob J Christensen - Cloudhuset A/S님이 에 댓글을 입력함
Yes, the requester would be the same for both parent and child tickets in this scenario.