Pesquisas recentes
Sem pesquisas recentes

dschmidt
Entrou em 15 de abr. de 2021
·
Última atividade em 06 de dez. de 2024
Seguindo
0
Seguidores
0
Atividade total
62
Votos
31
Assinaturas
23
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 dschmidt
dschmidt comentou,
Unfortunately we are on Professional; multiple schedules would probably work if we were on an Enterprise plan. It would be nice if that was an a la carte add-on.
Exibir comentário · Publicado 24 de ago. de 2023 · dschmidt
0
Seguidores
0
Votos
0
Comentários
dschmidt comentou,
This is a challenge for us as well. Our approach is for admins to manually add and remove agents from the groups that correspond to the different numbers depending on coverage requirements. One issue with this is that when you remove an agent from a group, they lose ownership of any non-closed tickets they may have in that group, which can affect metrics.
Exibir comentário · Publicado 24 de ago. de 2023 · dschmidt
0
Seguidores
0
Votos
0
Comentários
dschmidt comentou,
This warm transfer functionality is highly desired by our teams too.
Exibir comentário · Publicado 17 de nov. de 2022 · dschmidt
0
Seguidores
0
Votos
0
Comentários
dschmidt criou uma publicação,
When personalized replies are enabled (Enabling personalized email replies – Zendesk help), the setting applies to both end users and agents. Including the support address name after the end user name in the From: line on email notifications can falsely imply that the end user is a member of the support team associated with that support address.
I would like the option for this setting to apply only for agents, so email notifications triggered by end users do not include the support address name. Alternatively, the appended support address name for email notifications triggered by end users should include "reply via" or another customizable string.
For example:
From: Agent Name (Support Address Name)
vs
From: End User Name
alternatively:
From: Agent Name (Support Address Name)
vs
From: End User Name (reply via Support Address Name)
Publicado 23 de ago. de 2022 · dschmidt
0
Seguidores
1
Votos
0
Comentários
dschmidt comentou,
Has anyone else seen an issue recently with the Assignment Control app where it activates immediately upon viewing a ticket, instead of only when the assignee drop-drown selection box is opened?
The result is that when viewing a ticket that is already assigned to a hidden group (by trigger, macro, etc), the assignee field is changed to blank ("-"), and the ticket cannot be updated without reassigning it to a non-hidden group.
This is happening for me in both Chrome and Edge.
Exibir comentário · Publicado 11 de jul. de 2022 · dschmidt
0
Seguidores
0
Votos
0
Comentários
dschmidt comentou,
Agreed. It should be possible to limit playback of call recordings to Admins and Team Leads. It is bad enough that full Agents can listen to each other's recorded calls, but it especially complicates the rollout of Light Agents.
Exibir comentário · Publicado 26 de mai. de 2022 · dschmidt
0
Seguidores
6
Votos
0
Comentários
dschmidt comentou,
I agree. It should be possible to enable automatic recording of inbound calls without requiring manual customer opt-in, while automatic recording of outbound calls remains disabled.
Exibir comentário · Publicado 26 de mai. de 2022 · dschmidt
0
Seguidores
0
Votos
0
Comentários
dschmidt comentou,
I suggest you add app.pendo.io to this list. I had problems with transfers / conferencing until I added that to my exceptions.
Exibir comentário · Publicado 29 de abr. de 2022 · dschmidt
0
Seguidores
1
Votos
0
Comentários