最近搜索
没有最近搜索

Leonardo Santos
已加入2022年7月07日
·
最后活动2024年12月13日
关注
0
关注者
1
活动总数
155
投票
62
订阅
69
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 Leonardo Santos
Leonardo Santos 进行了评论,
Is there any plan to make “Advanced customization” available for the Web Widget (Messasing) and allow editing of the default form on opening, pre-filling and hiding fields, etc. as it is in the Web Widget (Classic)?
查看评论 · 已于 2024年10月10日 发布 · Leonardo Santos
0
关注者
0
投票
0
评论
Leonardo Santos 进行了评论,
Existe alguma pretensão de disponibilizar a “Personalização avançada” para o Web Widget (Messasing) e permitir a edição do formulário padrão ao abrir, pré-preenchimento e ocultação de campos, etc. como é no Web Widget (Classic)?
查看评论 · 已于 2024年10月10日 发布 · Leonardo Santos
0
关注者
0
投票
0
评论
Leonardo Santos 进行了评论,
Hi SRIRAJVJ!
Thanks for your comment!
This fix only works if you use a custom theme and it doesn't work for my use case.
I use the Copenhagen theme without customization to receive updates without any code update, so hiding the conditional fields by some native setting would be essential for me.
查看评论 · 已于 2024年8月12日 发布 · Leonardo Santos
0
关注者
0
投票
0
评论
Leonardo Santos 创建了一个帖子,
Gostaria de reportar um bug que está ocorrendo quando utilizado o novo editor de artigos do Guide.
Caso as notificações do site estejam habilitadas no navegador, sempre que o novo editor é aberto para criar/editar um artigo uma notificação está sendo enviada conforme os prints abaixo:
Notificações habilitadas
Exemplos de notificações:
已于 2024年8月07日 编辑 · Leonardo Santos
0
关注者
1
投票
2
评论
Leonardo Santos 进行了评论,
Oi João Figueiredo , boa tarde!
Acredito que o mais próximo disso seria o EAP de tempo de espera estimado que a Zendesk anunciou recentemente.
Sobre informar o número de atendimento, no meu caso de uso com WhatsApp utilizo um gatilho para notificar um webhook do SunCo e enviar a mensagem informando o ID do ticket quando ele é criado.

查看评论 · 已于 2024年7月10日 发布 · Leonardo Santos
0
关注者
1
投票
0
评论
Leonardo Santos 创建了一个帖子,
Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.].
I would like to be able to use liquid markup in agent aliases. For security reasons, we use a generic alias name for some services and some of our agents provide support for more than one group/segment.
What problem do you see this solving?
For agents who work in multiple groups, it will be possible to customize how the end user will see the agent's name in cases where it is necessary to use a generic name.
When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business?
Where an agent that supports multiple groups/segments is assigned to a ticket. Without this functionality, the agent alias needs to be extremely generic.
Are you currently using a workaround to solve this problem? (If yes, please explain)
I need to use a generic agent alias.
What would be your ideal solution to this problem? How would it work or function?
With liquid markup enabled for agent aliases, it would be possible to include conditions according to the ticket group name or ticket brand name assigned to the agent.
已于 2024年6月17日 发布 · Leonardo Santos
0
关注者
1
投票
1
Comment
Leonardo Santos 进行了评论,
Fernando Bueno realizei alguns testes com WhatsApp e o filtro "phone:55…" só funcionou se o número estiver cadastrado no usuário com o ínicio “+55…”
查看评论 · 已于 2024年6月06日 发布 · Leonardo Santos
0
关注者
1
投票
0
评论
Leonardo Santos 创建了一个帖子,
Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.].
I would like to be able to change the email address for triggering notifications to the user via automations/triggers. I have more than one email address configured for multi-brands and some are for exclusive use by certain groups and when I need to notify a user via email, the message is sent via the brand's default email and not the correct one for the group.
What problem do you see this solving?
With this option to select the correct email for the notification, the end user would not be surprised to receive an email from an address they do not know as the default contact address.
When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business?
After migrating a department from another CRM to Zendesk, the end users who contacted that department expressed dissatisfaction with receiving notifications from a different email address. They also expressed confusion regarding which email address was the correct one to contact.
Are you currently using a workaround to solve this problem? (If yes, please explain)
No. Zendesk support team informed me that unfortunately, I cannot choose which support address will be used for ticket responses with notifications via automations/triggers.
What would be your ideal solution to this problem? How would it work or function?
I would like to when adding the "Notifications: User email" action in automations/triggers, in addition to the "Email subject" and "Email body" options, it would also be possible to select the "Email sender", which will show all configured email addresses in Zendesk Support (perhaps separated by brands, like the "Select an Address" app).
已于 2024年1月24日 发布 · Leonardo Santos
2
关注者
3
投票
1
Comment
Leonardo Santos 进行了评论,
Hi Dane!
When will it be possible to edit ticket fields with this feature in the future?
This is the main issue we are have here, tickets with incorrect brands, group assigned and forms, directly affecting the metrics extracted in Explore.
查看评论 · 已于 2023年11月17日 编辑 · Leonardo Santos
0
关注者
1
投票
0
评论
Leonardo Santos 进行了评论,
Critical functionality! Especially for custom status in the "Solved" category, as agents are already used to selecting the last option.
The ability to restrict the visibility of custom statuses by group and brand is essential, not all groups/brands use the same ticket classification flow.
查看评论 · 已于 2023年11月16日 发布 · Leonardo Santos
0
关注者
0
投票
0
评论