Jeremy Holmes
-
Total activity206
-
Last activity
-
Member since
-
Following1 user
-
Followed by0 users
-
Votes160
-
Subscriptions25
Activity overview
Latest activity by Jeremy Holmes-
Jeremy Holmes commented,
We are already trying to get this data in to another service for the same reason. This is a major oversight in the design of this product.
-
Jeremy Holmes commented,
I can understand that, but if you are bulk updating a set of end users that are not part of an organization, it is much harder to update all of their existing tickets and there is no logic to do so...
-
Jeremy Holmes commented,
This does not seem to update existing tickets. It is possible to automate adding the tag to the customer's tickets that may already be in the system?
-
Jeremy Holmes commented,
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 commented,
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 commented,
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 commented,
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 commented,
We are starting to run into this issue as well and don't see a solution.
-
Jeremy Holmes commented,
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 commented,
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 ...