최근 검색


최근 검색 없음

Toshihiko Kodama's Avatar

Toshihiko Kodama

가입한 날짜: 2021년 10월 22일

·

마지막 활동: 2023년 10월 30일

팔로잉

0

팔로워

0

총 활동 수

99

투표 수

56

플랜 수

28

활동 개요

님의 최근 활동 Toshihiko Kodama

Toshihiko Kodama님이 에 게시물을 만듦

게시물 Feedback - Chat and Messaging (Chat)

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!

2023년 9월 05일에 게시됨 · Toshihiko Kodama

2

팔로워

3

투표 수

2

댓글


Toshihiko Kodama님이 에 댓글을 입력함

커뮤니티 댓글 Developer - Zendesk APIs

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.

댓글 보기 · 2023년 7월 06일에 게시됨 · Toshihiko Kodama

0

팔로워

0

투표 수

0

댓글


Toshihiko Kodama님이 에 게시물을 만듦

게시물 Developer - Zendesk APIs

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!

2023년 7월 03일에 게시됨 · Toshihiko Kodama

3

팔로워

2

투표 수

2

댓글


Toshihiko Kodama님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Chat and Messaging (Chat)

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.

  1. 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)
  2. there are plans to expand Messaging Chat trigger conditions/actions in the future.

댓글 보기 · 2023년 5월 08일에 게시됨 · Toshihiko Kodama

0

팔로워

0

투표 수

0

댓글


Toshihiko Kodama님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Ticketing system (Support)

Thank you  for your radar!

I hope you add the feature soon!

Thanks!

댓글 보기 · 2022년 11월 15일에 게시됨 · Toshihiko Kodama

0

팔로워

0

투표 수

0

댓글


Toshihiko Kodama님이 에 게시물을 만듦

게시물 Feedback - Ticketing system (Support)

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!

2022년 11월 08일에 게시됨 · Toshihiko Kodama

6

팔로워

4

투표 수

2

댓글


Toshihiko Kodama님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Chat and Messaging (Chat)

Thank you, Lisa!
Happy to hear your news!
I can't wait! 🙂.

댓글 보기 · 2022년 10월 13일에 게시됨 · Toshihiko Kodama

0

팔로워

0

투표 수

0

댓글


Toshihiko Kodama님이 에 게시물을 만듦

게시물 Feedback - Chat and Messaging (Chat)

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!

2022년 10월 04일에 게시됨 · Toshihiko Kodama

2

팔로워

2

투표 수

2

댓글


Toshihiko Kodama님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Chat and Messaging (Chat)

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.

댓글 보기 · 2022년 10월 04일에 게시됨 · Toshihiko Kodama

0

팔로워

2

투표 수

0

댓글


Toshihiko Kodama님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Reporting and analytics (Explore)

I understand to some extent that the current specification does not properly reflect the tag exclusion setting on Explores, but user psychology leads them to think that "as long as it can be set, it should work".

If the exclusion setting does not work correctly as a specification, I would like to request a modification to disable the tag exclusion setting in the UI.

Thank you!

댓글 보기 · 2022년 9월 30일에 편집됨 · Toshihiko Kodama

0

팔로워

3

투표 수

0

댓글