最近の検索


最近の検索はありません

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さんがコメントを作成しました:

コメント[ARCHIVE] Documentation

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

コメントを表示 · 投稿日時:2023年5月10日 · Toshihiko Kodama

0

フォロワー

1

投票

0

コメント


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

コメント