Pesquisas recentes
Sem pesquisas recentes

Melissa Lucore
Entrou em 15 de abr. de 2021
·
Última atividade em 14 de fev. de 2023
Seguindo
0
Seguidores
0
Atividade total
133
Votos
76
Assinaturas
45
VISÃO GERAL DA ATIVIDADE
MEDALHAS
ARTIGOS
PUBLICAÇÕES
COMENTÁRIOS NA COMUNIDADE
COMENTÁRIOS EM ARTIGOS
VISÃO GERAL DA ATIVIDADE
Atividade mais recente por Melissa Lucore
Melissa Lucore comentou,
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.
Thanks,
Melissa
Exibir comentário · Publicado 08 de dez. de 2022 · Melissa Lucore
0
Seguidores
0
Votos
0
Comentários
Melissa Lucore comentou,
Are we able to see when a user was suspended or who did the action of suspending the user?
Exibir comentário · Publicado 26 de jul. de 2022 · Melissa Lucore
0
Seguidores
6
Votos
0
Comentários
Melissa Lucore comentou,
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 publishing dataset, it shows the agent who is responsible for unverifying the articles. None of our agents manually mark articles as unverified, so this metric is not helpful. The report does not provide the information we want which is number of articles that are unverified that are owned by a particular agent. We have reviewed this with our CSM and they have confirmed that what we are seeing is not the number we are looking for.
Exibir comentário · Publicado 19 de jan. de 2022 · Melissa Lucore
0
Seguidores
0
Votos
0
Comentários
Melissa Lucore comentou,
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 would be helpful to have a tag or event or some sort of identifier that would allow our managers to report on this volume and assist in resource planning (assign a certain number of agents to monitor the suspended queue).
Exibir comentário · Publicado 10 de jan. de 2022 · Melissa Lucore
0
Seguidores
1
Votos
0
Comentários
Melissa Lucore comentou,
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.
Exibir comentário · Publicado 10 de jan. de 2022 · Melissa Lucore
0
Seguidores
0
Votos
0
Comentários
Melissa Lucore criou uma publicação,
Publicado 15 de out. de 2021 · Melissa Lucore
6
Seguidores
13
Votos
11
Comentários
Melissa Lucore comentou,
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 Outages. Because of the ticket time being changed in the interface, what I reported to Dev for timing ended up being wrong. We're now correcting the RCA, but just didn't even think to check, and we don't want to have misses like that with our customers. Is there any plan to change this?
Exibir comentário · Publicado 24 de mar. de 2021 · Melissa Lucore
0
Seguidores
3
Votos
0
Comentários
Melissa Lucore comentou,
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?
Exibir comentário · Publicado 11 de fev. de 2021 · Melissa Lucore
0
Seguidores
2
Votos
0
Comentários
Melissa Lucore comentou,
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.
Exibir comentário · Publicado 19 de jan. de 2021 · Melissa Lucore
0
Seguidores
0
Votos
0
Comentários
Melissa Lucore comentou,
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 user. This is a huge security issue. I second a previous comment that asks for a confirmation prompt at the very least, if un-merging isn't feasible.
Thanks.
Exibir comentário · Publicado 16 de out. de 2020 · Melissa Lucore
0
Seguidores
9
Votos
0
Comentários