Dan Ross
-
총 활동 수465
-
마지막 활동
-
회원 가입일
-
내가 팔로우하는 사용자 수0명
-
나를 팔로우하는 사용자 수2명
-
투표 수146
-
플랜 수179
활동 개요
Dan Ross님의 최근 활동-
Dan Ross님이 에 댓글을 입력함
Hey there! Many ways you can do this, though I am a big fan of dedicated Support Operations teams. IMO the most impactful method you can do this is have administration only be provided to people in...
-
Dan Ross님이 에 댓글을 입력함
this would be helpful and a better experience for customers. a lot of frustration with automated deflection comes from the fact if the user does something wrong or unintentional that they get stuck...
-
Dan Ross님이 에 댓글을 입력함
Also eager to hear any news on this feature, it's been requested for some time and will make a huge impact for our teams
-
Dan Ross님이 에 댓글을 입력함
Hey Hannah, In Zendesk Explore, try using the Attribute for 'User Locale' in conjunction with a metric for counting the number of Tickets. That should break down the languages for you by the # tick...
-
Dan Ross님이 에 댓글을 입력함
Thanks Ryan McGrew that's awesome to hear! Will this allow redirect to any URLs or just to Zendesk ones in the same instance? Our use case is that we wish to merge different instances of Zendesk a...
-
Dan Ross님이 에 댓글을 입력함
Hey Erik, try doing a search in Zendesk using your API field name for the org field, using 'none' as the search term. Ex: if your field API name is 'region' then your search would be region:noneDo...
-
Dan Ross님이 에 댓글을 입력함
Hey CJ, I hear you, I just had an admin get bit by this recently. Here's how we're doing things: We make a personal view for tickets assigned to the group/agent that's gonna be changed Add the n...
-
Dan Ross님이 에 댓글을 입력함
We found this post because we just ran into this issue after a company wide rebrand. Our form IDs didn't change, just the names and it's causing havoc with reports. Please, have these relations st...
-
Dan Ross님이 에 댓글을 입력함
Hey Jasmine Winzeler - you might be able to do something with Zendesk's webhooks feature for this. When a ticket is created and these secondary user fields are filled, you could have a trigger send...
-
Dan Ross님이 에 댓글을 입력함
I've run into it as well, but it self resolves after 30-60s on my end, I assuming it's just an indexing delay for search, kind like we have for brand new tickets being searchable in the system.