Pesquisas recentes
Sem pesquisas recentes

Marius Gavril
Entrou em 18 de dez. de 2023
·
Última atividade em 20 de jan. de 2025
Seguindo
0
Seguidores
0
Atividade total
29
Votos
13
Assinaturas
9
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 Marius Gavril
Marius Gavril comentou,
Yup, same here. Tried it with the new CSAT and placeholder is no longer viable. Are there any alternative solutions to this?
Exibir comentário · Publicado 20 de jan. de 2025 · Marius Gavril
0
Seguidores
0
Votos
0
Comentários
Marius Gavril criou uma publicação,
The new customizable CSAT experience is a great improvement from the basic CSAT setup Zendesk used to have.
My two nuggets with this update are:
- Allow for a follow-up question to be added for positive reviews as well, not just negative. Often times there is more specific feedback to be collected and while optional, it's a nice to have than not have at all.
- Allow for Admins to also edit the categorisation of negative/positive CSATs. For example, we currently use a 5 star rating scal and al 3 stars are either slightly positive or just neutral. As a result, we only define 1 and 2 stars as negative, which is manual work, but allows agents to see their true CSAT value. Having a drop-down next to the negative/positive attribute allows Admins to customise the experience even more and would be a HUGE value add to the feature and its usability.
Publicado 26 de set. de 2024 · Marius Gavril
5
Seguidores
4
Votos
2
Comentários
Marius Gavril comentou,
This is a great improvement from the basic CSAT experience Zendesk used to have.
My two nuggets with this feature are:
1. Allow for a follow-up question to be added for positive reviews as well, not just negative
2. Allow for Admins to also edit the categorisation of negative/positive CSATs. For example, we currently use a 5 star rating scal and al 3 stars are either slightly positive or just neutral. As a result, we only define 1 and 2 stars as negative, which is manual work, but allows agents to see their true CSAT value. Having a drop-down next to the negative/positive attribute allows Admins to customise the experience even more and would be a HUGE value add to the feature and its usability.
Exibir comentário · Publicado 26 de set. de 2024 · Marius Gavril
0
Seguidores
3
Votos
0
Comentários
Marius Gavril comentou,
Absolutely a low hanging fruit for the knowledge section, especially with the Knowledge Capture deprecation.
Since this is considered for development at some stage, it's worth thinking ahead and allow these self-resolves to be trackable via an identifiable event. Keep in mind some users will want to set up a trigger to tag or isolate these individual events.
Exibir comentário · Editado 23 de jul. de 2024 · Marius Gavril
0
Seguidores
1
Votos
0
Comentários
Marius Gavril comentou,
With more and more people transitioning to Messaging as a pre-requisite to Chatbot and AI add-ons, it is imperative that companies are able to attribute Offers, Acceptances and Acceptance Rate % on an individual level.
This helps alleviate the level of effort required to identify whether the right course of action is with actioning outliers or applying a team wide solution.
Offers, Acceptances and Acceptance Rate % in their current format (ticket based) are helpful, but only to a limited extent. The priority development of an agent based value for these metrics will make any Operation's life easier and help sustain performance.
In a context where:
- Conversation is offered to Agent 1
- Agent 1 does not accept
- Same conversation is then offered to Agent 2
- Agent 2 accepts
The ideal scenario would be to capture an individuals' direct performance for tickets that they have been offered and extract:
- Offers 1, Acceptances 0 and Acceptance 0% for Agent 1
- Offers 1, Acceptances 1 and Acceptance 100% for Agent 2
Exibir comentário · Editado 10 de abr. de 2024 · Marius Gavril
0
Seguidores
5
Votos
0
Comentários
Marius Gavril criou uma publicação,
Guided Mode is great and efficient for how our team operates. One improvement suggestion that we had and came across recently is tied to how collision detection operates and how an actual agent can go through tickets.
Right now, in the event that Light Agents are viewing a ticket, that ticket does not get served to the agent that's in Play Mode due to collision detection. It would be great if Guided Mode would bypass the presence of a Light Agent and still allow that ticket to be displayed for handling.
Publicado 20 de dez. de 2023 · Marius Gavril
3
Seguidores
2
Votos
1
Comentário
Marius Gavril comentou,
In the event that Light Agents are viewing a ticket, that ticket does not get served to the agent that's in Play Mode due to collision detection. Is there a way to bypass this shortcoming?
Exibir comentário · Editado 18 de dez. de 2023 · Marius Gavril
0
Seguidores
0
Votos
0
Comentários