최근 검색
최근 검색 없음

Kate
가입한 날짜: 2021년 10월 28일
·
마지막 활동: 2025년 1월 24일
팔로잉
0
팔로워
0
총 활동 수
241
투표 수
207
플랜 수
13
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Kate
Kate님이 에 댓글을 입력함
Chiming in to add that I agree that this announcement does not seem like an enhancement, but rather a degradation of features.
To take away the ability to query data older than 3 years is more impactful for some industries than others. We have regulatory bodies that we need to be able to provide holistic reporting too, and without the ability to easily query the entire history of our data, this will increase time, effort, and cost.
I agree with Tim that it seems like we should have two datasets. I similarly agree with Stephen that this seems to be actively discouraging customers from utilizing Explore as the default reporting tool for support data.
Ultimately, it seems like we will now need to budget to add a secondary reporting tool in order to meet our industry requirements. Which begs the question – why are we spending so much on Zendesk? We may as well begin looking for a cheaper support tool alternative if we have to duplicate funds for something Zendesk is no longer providing.
댓글 보기 · 2025년 1월 14일에 게시됨 · Kate
0
팔로워
5
투표 수
0
댓글
Kate님이 에 댓글을 입력함
We've rebuilt some of our dashboards on the new editor, but it doesn't look like there is an option to share the dashboard via link & password protection as we could for the previous dashboards.
Am I missing this option or will it be added in the future?
댓글 보기 · 2024년 11월 21일에 게시됨 · Kate
0
팔로워
1
투표
0
댓글
Kate님이 에 댓글을 입력함
Will the number of tabs restriction always be in place? We have multiple dashboards with 11-12 tabs, and it wouldn't make any sense to reduce the number of tabs based on their purpose/audience.
댓글 보기 · 2024년 11월 18일에 게시됨 · Kate
0
팔로워
1
투표
0
댓글
Kate님이 에 댓글을 입력함
Any updates Zendesk? This ask has been requested since 2020, at least (see other feedback post sitting at 74 votes: https://support.zendesk.com/hc/en-us/community/posts/4409217044250-Problem-and-Incident-tickets-need-a-way-to-view-the-subject-and-detail-of-all-incident-tickets-against-a-problem-ticket-or-vice-versa)
This is desperately needed.
댓글 보기 · 2024년 2월 07일에 게시됨 · Kate
0
팔로워
2
투표 수
0
댓글
Kate님이 에 게시물을 만듦
First off - I know that this can be done with omnichannel routing. For a multitude of reasons, omnichannel routing is not viable for our company.
However, I do still feel that Talk itself could benefit from overhauling the routing currently available on IVR menus.
Our company supports 8 languages, but not all of our agents speak each language. In order to support Talk, we now have a different group for each language, and we use these groups in the IVR to route to the appropriate agents. The purpose of these groups is solely for Talk, meaning we have extraneous group configuration that's not really necessary.
It would simplify our Talk workflows and backend configuration if rather than relying on Groups to route to agents in the IVR, we could use Skills themselves to route to the agents who speak the appropriate language.
2024년 1월 12일에 게시됨 · Kate
3
팔로워
4
투표 수
2
댓글
Kate님이 에 댓글을 입력함
When you mean closed, do you really mean solved? Meaning, when you solve a ticket you want a the following scenarios:
- Solving without notifying the user
- Solving with notifying the user
In that case, there's a simpler workaround to this by using tags to prevent the email from being sent when you don't want to email the user.
Find the trigger you have which is sending an email notification to the user whenever a ticket is solved (dependent on your customization, you may have a different trigger, but there is a default "notify requester of solved ticket" or something like that).
Add a condition to your ALL set that is tags contains none of the following [custom tag]. For us, we use silent_solve. Here's a screenshot of our solved notification trigger with this condition built in (again, all in the Meet ALL of the following conditions set):
Anytime we want to solve a ticket without notifying the requester, we add the tag silent_solve to the ticket (manually, by macro, or however you want to add it). That way, the ticket will solve (and ultimately move to close) without any notifcation to the end user.
댓글 보기 · 2022년 11월 02일에 게시됨 · Kate
0
팔로워
0
투표 수
0
댓글
Kate님이 에 댓글을 입력함
Got it - You could use the COUNT(Tickets), add a filter for ticket type (incident), add the Ticket problem ID then filter the Ticket problem ID to Null and it should return the count of all non-associated incidents.
You could add other attributes like Ticket ID, subject or other ticket fields and that will return the details of the incident ticket that is unassociated, which may help you identify which problem it should be attached to, but I understand if this may not be what you're looking for.
Overall, problem and incident reporting in explore is pretty garbage in my experience, but I hope this might help at least a bit.
댓글 보기 · 2022년 8월 18일에 게시됨 · Kate
0
팔로워
1
투표
0
댓글
Kate님이 에 댓글을 입력함
Hey Reshma Patel
You should be able to report on the count of incidents by problem ID, but you won't be able to see any details about the Problem tickets themselves on the report. If you do know the problem ticket IDs you can filter it, but from the report itself you can only pull ticket details from the incidents (since that's the metric) and nothing about the problem itself. If you only need incident counts, these should work for you.
댓글 보기 · 2022년 8월 18일에 게시됨 · Kate
0
팔로워
0
투표 수
0
댓글