Jeremy Holmes
- 총 활동 수 198
- 마지막 활동
- 회원 가입일:
- 내가 팔로우하는 사용자 수 1명
- 나를 팔로우하는 사용자 수 0명
- 투표 수 157
- 수신 설정 수 24
활동 개요
Jeremy Holmes님의 최근 활동-
Jeremy Holmes님이 에 댓글을 입력함
I like Explore and the flexibility, but it seems some features like filtering by Current User should be possible and they are not. I get the flexibility of bookmarks, but we should also still have ...
-
Jeremy Holmes님이 에 댓글을 입력함
This is still cumbersome and I have a similar issue that should be filtered by the user viewing it. We had a way to filter to current user on Insights Reporting. It seems this would be a logical op...
-
Jeremy Holmes님이 에 댓글을 입력함
Will there ever be a way to create a dashboard in Explore that can show all tickets currently being viewed? This would be beneficial when trying to monitor an individual agent's activity as well as...
-
Jeremy Holmes님이 에 댓글을 입력함
We are having a similar issue and our field type is decimal. We were fully able to use this field in all of our insights reporting and it is not even showing in Explore.
-
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님이 에 댓글을 입력함
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 ...