Jeremy Holmes
- 총 활동 수 176
- 마지막 활동
- 회원 가입일:
- 내가 팔로우하는 사용자 수 1명
- 나를 팔로우하는 사용자 수 0명
- 투표 수 142
- 수신 설정 수 20
활동 개요
Jeremy Holmes님의 최근 활동-
Jeremy Holmes님이 에 댓글을 입력함
We are starting to run into this issue as well and don't see a solution.
-
Jeremy Holmes님이 에 댓글을 입력함
It is understandable that this takes a good bit of testing, but this feature has potential benefits across multiple scenarios. It is also one that seems that there would be greater progress on it s...
-
Jeremy Holmes님이 에 댓글을 입력함
I agree. There should be a native option to work with the data. Even a simple search or export to .csv would be better than what we have now.
-
Jeremy Holmes님이 에 댓글을 입력함
This has become an issue for us as well. We have been happy with making views for most things, but when a set of tickets that meets the criteria is closed and can not be tagged with an automation p...
-
Jeremy Holmes님이 에 댓글을 입력함
Tags would be a benefit that we could definitely work with, but we have found that taking the time to build appropriate forms is more beneficial, allows more specific reporting, and necessary for r...
-
Jeremy Holmes님이 에 댓글을 입력함
We work with a lot of vendors that handle different things for us. It is not uncommon for one ticket to be associated with four or five others for a single issue. It is then a task to track all of ...
-
Jeremy Holmes님이 에 댓글을 입력함
We came across the same issue Mike stated. I agree that this greatly reduces the functionality. The main reason we are look at this feature is so we can have communication with other services on pr...
-
Jeremy Holmes님이 에 댓글을 입력함
I agree that this would be a great feature. We are really trying to ramp up our productivity with chat and the lack of these metrics makes it difficult to fine tune the triggers. We can't effective...
-
Jeremy Holmes님이 에 댓글을 입력함
Jonathan's suggestion is still the only work around we have been able to use to compensate for the poor design. Unfortunately, the agent and their chats do not show up on the agent report page when...
-
Jeremy Holmes님이 에 댓글을 입력함
I've made all of those changes and they do help a little. However, this is a terrible oversight that the workarounds are not addressing. I don't understand the hard line Zendesk Product Managers ...