Pesquisas recentes
Sem pesquisas recentes

Toshihiko Kodama
Entrou em 22 de out. de 2021
·
Última atividade em 30 de out. de 2023
Seguindo
0
Seguidores
0
Atividade total
99
Votos
56
Assinaturas
28
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 Toshihiko Kodama
Toshihiko Kodama criou uma publicação,
Currently, when terminating with an option in Flow Builder, an error occurs as shown in the screenshot and it cannot be saved, but if the user is treated as having entered an optional word when this option is selected with no error, other Answer data will be called, which will increase the flexibility of flow creation.
This will increase the degree of freedom in creating flows.
We would very much like to see a fix that does not make it an error to terminate with the Flow Builder option.
Thank you!
Publicado 05 de set. de 2023 · Toshihiko Kodama
2
Seguidores
3
Votos
2
Comentários
Toshihiko Kodama comentou,
Thank you for your quick reply!
I understand the current specifications. Also, it may be difficult to deal with due to the way the API works, but even if a form is open to users, we often do not want to disclose the internal name and tag information used there.
So I would like to see a separate restriction setting for the API for ticket forms.
Exibir comentário · Publicado 06 de jul. de 2023 · Toshihiko Kodama
0
Seguidores
0
Votos
0
Comentários
Toshihiko Kodama criou uma publicação,
https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_forms/
The above document states that the use of the Ticket Form API is fixed to Anyone, but since the ticket form information contains internal form names and tag information that we do not want to make public, we would like to be able to set IP restrictions and authentication restrictions.
Thank you!
Publicado 03 de jul. de 2023 · Toshihiko Kodama
3
Seguidores
2
Votos
2
Comentários
Toshihiko Kodama comentou,
The following link in this article shows "You're not authorized to access this page" even if I am signed in. Please check it.
https://support.zendesk.com/hc/en-us/articles/5524125586330
Exibir comentário · Publicado 10 de mai. de 2023 · Toshihiko Kodama
0
Seguidores
1
Votos
0
Comentários
Toshihiko Kodama comentou,
I completely agree.
I would like to see the trigger conditions and actions that can be set in Messaging Chat expanded to the same level as those in Support.
*) I have heard the following from a Zendesk support representative.
- I would like to make API requests at the timing when a Messaging Chat user posts a message, but to achieve this, I currently need to develop a Zendesk app using the Zendesk Apps Framework (ZAF)
- there are plans to expand Messaging Chat trigger conditions/actions in the future.
Exibir comentário · Publicado 08 de mai. de 2023 · Toshihiko Kodama
0
Seguidores
0
Votos
0
Comentários
Toshihiko Kodama comentou,
Thank you for your radar!
I hope you add the feature soon!
Thanks!
Exibir comentário · Publicado 15 de nov. de 2022 · Toshihiko Kodama
0
Seguidores
0
Votos
0
Comentários
Toshihiko Kodama criou uma publicação,
Feature Request Summary:
Messaging and chat support tickets often have a large number of comments in the ticket, and currently it is difficult to quickly view and reference any comment.
Description/Use Cases:
Currently, there is no URL link for each comment in Support tickets, but when comments are retrieved via the API, they are all assigned an ID internally.
If there is a way to copy and use this as a comment URL from within a ticket, it would improve convenience considerably.
Examples:
As a concrete example, a screenshot of Slack's "Copy link" function is attached.
Thank you!
Publicado 08 de nov. de 2022 · Toshihiko Kodama
6
Seguidores
4
Votos
2
Comentários
Toshihiko Kodama comentou,
Thank you, Lisa!
Happy to hear your news!
I can't wait! 🙂.
Exibir comentário · Publicado 13 de out. de 2022 · Toshihiko Kodama
0
Seguidores
0
Votos
0
Comentários
Toshihiko Kodama criou uma publicação,
Currently, it is possible to branch by the number of queues waiting in the flow-builder, but it is not possible to branch BOTs by the number of cases being handled, and with a limited number of staff, there is a risk of a flood of inquiries that exceeds capacity.
Since there is a function to branch by success/failure of API acquisition, please develop this and add a function to branch by API-acquired variables. Then the number of tickets handled can be retrieved via the API and operator calls can be avoided if the number exceeds a certain value.
Thank you!
Publicado 04 de out. de 2022 · Toshihiko Kodama
2
Seguidores
2
Votos
2
Comentários
Toshihiko Kodama comentou,
We would like to see the Export and Import functions implemented for data backup and multi-brand data reuse. For localization, we would like to be able to use dynamic content and placeholders in the Flow-builder.
Exibir comentário · Publicado 04 de out. de 2022 · Toshihiko Kodama
0
Seguidores
2
Votos
0
Comentários