Joey
-
총 활동 수59
-
마지막 활동
-
회원 가입일
-
내가 팔로우하는 사용자 수0명
-
나를 팔로우하는 사용자 수0명
-
투표 수26
-
플랜 수15
활동 개요
Joey님의 최근 활동-
Joey님이 에 댓글을 입력함
It seems like ticket sharing triggers are not copied over, any other type of triggers that won't copy over to the sandbox? Prod: 378 - Sandbox: 347 = 31 missing triggers.
-
Joey님이 에 댓글을 입력함
We have the same issue as Tom, our customers have multiple products (Brands) and thus they can't see all their tickets in a single place. This is also why we don't communicate this functionality to...
-
Joey님이 에 댓글을 입력함
I'm just going to copy Dan R. because he is right (as usual): Allow admins to flag fields as read-only natively, without needing to rely on the brutally clunky Ticket Field Manager app or other ext...
-
Joey님이 에 댓글을 입력함
Completely agrees, this causes a lot of manual work. I would like to create views for agents in each office or a view were we group them by the agent office field, which is a custom field on the ag...
-
Joey님이 에 댓글을 입력함
Hey Keigo ishizaka This should be possible using dynamic content and trigger. This is how we have set up our emails: You can create a piece of dynamic content for each brand that holds the emails ...
-
Joey님이 에 댓글을 입력함
Paul Von thanks for this, can't wait to try it out. Your Rollout ends date at the top of this page is showing 2013 instead of 2023 ;)
-
Joey님이 에 댓글을 입력함
Hey Amie Brennan, Organizing views the same way Lovely Views does, having multiple folders within folders. We have 60+ groups working in hundreds of views and many hundreds of agents, thus making t...
-
Joey님이 에 댓글을 입력함
Let's just say it's a (tiny) start but unfortunately not the great feature it could have been. Still no way to organize your views, you just get whatever is at the top. We still rely on Lovely View...
-
Joey님이 에 댓글을 입력함
Lucy Husband, "the switch to messaging will happen on 18th Sept 2023" I assume you are talking about a switch that you are making? Live Chat is not being deprecated any time soon afaik.
-
Joey님이 에 댓글을 입력함
We spoke with all kinds of Zendesk representatives without a solution. My theory is an issue within Zopim's own core. We have multiple products that have the code implemented slightly different and...