Melissa Lucore
-
총 활동 수133
-
마지막 활동
-
회원 가입일
-
내가 팔로우하는 사용자 수0명
-
나를 팔로우하는 사용자 수0명
-
투표 수76
-
플랜 수45
활동 개요
Melissa Lucore님의 최근 활동-
Melissa Lucore님이 에 댓글을 입력함
Hi Ifra Saqlain - How would I hide multiple topics using this code? I was able to hide the button from 1 topic as shown above, but not sure how to list multiple topics to hide the post button from....
-
Melissa Lucore님이 에 댓글을 입력함
Are we able to see when a user was suspended or who did the action of suspending the user?
-
Melissa Lucore님이 에 댓글을 입력함
In our experience, that has not been true. When pulling the number of unverified articles per agent by using the COUNT(Articles unverified) metric and Agent name attribute in the Guide Team publish...
-
Melissa Lucore님이 에 댓글을 입력함
Hello - We have a large volume of suspended tickets that are recovered by our Tier 1 team. Unfortunately there is no way to identify those tickets that have been recovered or report on them. It wou...
-
Melissa Lucore님이 에 댓글을 입력함
Is there any sort of identifier on tickets that have been recovered? It would be very helpful to be able to report on the volume of recovered tickets from the suspended queue. Thanks.
-
Melissa Lucore님이 에 게시물을 만듦
Reporting in Explore on Article Verification
It would be helpful to have a list of articles by agent that have not been verified using Explore. I can get the list in Guide Admin, however, I cannot export the report and send to each agent. Wo...
-
Melissa Lucore님이 에 댓글을 입력함
This is also an issue for our team. We often have to go back to old Support Tickets to help our dev teams when they write RCA (Root Cause Analysis) documents for urgent customer issues, like Outage...
-
Melissa Lucore님이 에 댓글을 입력함
We experience this same issue. Some customers may CC colleagues that are relevant to the issue, but those colleagues are not users in Zendesk. Is there anyway to allow this?
-
Melissa Lucore님이 에 댓글을 입력함
We have a similar use case. If someone follows a topic, we'd like them to receive a weekly digest of any updates to that topic.
-
Melissa Lucore님이 에 댓글을 입력함
We also recently had an issue where a ticket was incorrectly merged. The end users kept replying to the original email so all of the information they sent was visible by the merged ticket's end use...