Pesquisas recentes
Sem pesquisas recentes

Phil Williams
Entrou em 15 de abr. de 2021
·
Última atividade em 03 de jun. de 2022
Seguindo
0
Seguidores
0
Atividade total
29
Votos
2
Assinaturas
17
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 Phil Williams
Phil Williams comentou,
Neither did I until then! Works a treat though :)
Exibir comentário · Publicado 03 de jun. de 2022 · Phil Williams
0
Seguidores
0
Votos
0
Comentários
Phil Williams comentou,
Actually I've thought of a way round this.
If the ticket arrives from a customer with one of our flag fields I can run an trigger to add a warning internal comment and append that immediately below the first public comment.
Right in front of the agent, job done 😀
Exibir comentário · Publicado 02 de jun. de 2022 · Phil Williams
0
Seguidores
0
Votos
0
Comentários
Phil Williams comentou,
Not really sure if that helps or not 😉
Exibir comentário · Publicado 02 de jun. de 2022 · Phil Williams
0
Seguidores
0
Votos
0
Comentários
Phil Williams comentou,
Hi Brett,
Yep but couldn't find an app that ticked my simple boxes. Aware of the customer context panel but it's not quite "in your face" enough for agents to see.
Exibir comentário · Publicado 02 de jun. de 2022 · Phil Williams
0
Seguidores
0
Votos
0
Comentários
Phil Williams criou uma publicação,
We have a need to clearly display a warning when a customer contacts us that has specific data stored on their customer profile on Zendesk. The reason being is that there are certain restricted actions for these customers.
Is anyone aware of a method to produce a visible banner at the top of the ticket when the ticket is opened based on a custom field?
Publicado 02 de jun. de 2022 · Phil Williams
0
Seguidores
4
Votos
8
Comentários
Phil Williams comentou,
Yep we use it every day. The key issue most people face is the race condition so you do need to be especially careful about that. If the desk encounters a race condition where the comments are continuously added then the API is disabled.
I've never tested this in a sandbox environment so that could be the reason it's not working for you but we use this daily in our production environment.
Exibir comentário · Publicado 04 de mai. de 2021 · Phil Williams
0
Seguidores
0
Votos
0
Comentários
Phil Williams comentou,
Excellent, not a problem! :)
Exibir comentário · Publicado 11 de jun. de 2020 · Phil Williams
0
Seguidores
0
Votos
0
Comentários
Phil Williams comentou,
If you set the URL as https://yourdomain.zendesk.com/api/v2/tickets/{{ticket.id}}.json?ticket[comment][public]=false+ and the Attribute Name as ticket[comment][body] Then this will setup the extension correctly.
Within the trigger, you would then create a Notify Target action pointing at your new extension and enter the message you wish to add.
This will then add the message as a private comment.
Exibir comentário · Publicado 11 de jun. de 2020 · Phil Williams
0
Seguidores
0
Votos
0
Comentários
Phil Williams comentou,
^^ That's the method we use. Works a treat :)
Exibir comentário · Publicado 25 de mar. de 2020 · Phil Williams
0
Seguidores
0
Votos
0
Comentários
Phil Williams comentou,
Quite surprised this is still a thing. We had a comment today on one of our posts which was dutifully turned into a ticket but I was surprised when I replied that my response didn't get added to the facebook post and was instead converted to a private message?
This doesn't make sense to me?
Exibir comentário · Publicado 27 de nov. de 2019 · Phil Williams
0
Seguidores
0
Votos
0
Comentários