最近の検索


最近の検索はありません

Lucas Case's Avatar

Lucas Case

参加日2021年10月16日

·

前回のアクティビティ2024年10月30日

フォロー中

0

フォロワー

0

合計アクティビティ

63

投票

33

受信登録

17

アクティビティの概要

さんの最近のアクティビティ Lucas Case

Lucas Caseさんがコメントを作成しました:

コミュニティのコメント Feedback - Chat and Messaging (Chat)

Stephanie Langlois thanks for your reply, we had another example why this is important. Some agents were exposed to highly undesired content and couldn't be protected from it by simply suspending a user. I understand the WA API doesn't support it, but even being able to block incoming messages on the Zendesk side would be really helpful.

To further endorse/empower the desire for this functionality, I think steps need to be taken to address the Digital Services Act, which states that Digital platforms need (WhatsApp included)  User Reporting and Redress Mechanisms: Platforms must provide easy-to-use mechanisms for users to report illegal content and appeal content moderation decisions.

コメントを表示 · 投稿日時:2024年6月20日 · Lucas Case

0

フォロワー

0

投票

0

コメント


Lucas Caseさんがコメントを作成しました:

コメントManaging your email

Mike DR how about subdomains? We want to allow the main domain, and block/reject a subdomain of the main domain? So allow: main.com and block: (reject:)sub.main.com

コメントを表示 · 投稿日時:2024年6月11日 · Lucas Case

0

フォロワー

0

投票

0

コメント


Lucas Caseさんがコメントを作成しました:

コメントManaging your email

I'm wondering if it is a problem to allow a head domain and block a subdomain. This has to do with a certain subdomain that is being used for messages from users (hashed), We would like to block these messages (an integration is already in place for this). So for example:

Allowlist: main.com

Blocklist: reject:sub.main.com

コメントを表示 · 編集日時:2024年6月11日 · Lucas Case

0

フォロワー

0

投票

0

コメント


Lucas Caseさんがコメントを作成しました:

コミュニティのコメント Feedback - Admin Center

This is really strange, this is clearly not an admin (only) function. I understand that overhauling the roles structure/function is not easily done, but for the time being, changing the function Roles>Channels>Manage channels and extensions to also include the bots would be a really helpful improvement and logical (even though more fine-tuning would be desirable)

コメントを表示 · 投稿日時:2024年5月02日 · Lucas Case

0

フォロワー

4

投票

0

コメント


Lucas Caseさんがコメントを作成しました:

コミュニティのコメント Feedback - Ticketing system (Support)

In the Intelligence section the (suggested) macro's recently changed to be collapsed instead of expanded, so you can take in all the information and followup properly without "unnecessary" clicks. The macro's used to be directly visible when opening the ticket or opening the intelligence section (instead of being collapsed and only visible when clicking this tab open).

Is this a temporary change to facilitate some other changes/configurability later on? If not, this isn't a change for the better (even in the meanwhile, remembering the previous state of the suggested macro's to be collapsed or expanded would help speed up the agent).

コメントを表示 · 投稿日時:2024年3月14日 · Lucas Case

0

フォロワー

0

投票

0

コメント


Lucas Caseさんがコメントを作成しました:

コメントTicket automation and collaboration

The (suggested) macro's recently changed in the intelligence section, they used to be expanded when opening the ticket or opening the intelligence section (instead of being collapsed and only visible when clicking this tab open).

Is this a temporary change to facilitate some other changes/configurability later on? Otherwise, this isn't a change for the better (even in the meanwhile remembering the previous state of the suggested macro's to be collapsed or expanded would help).

コメントを表示 · 編集日時:2024年3月14日 · Lucas Case

0

フォロワー

0

投票

0

コメント


Lucas Caseさんが投稿を作成しました:

投稿 Feedback - Ticketing system (Support)

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.]. (2-3 sentences)

We want to use a sandbox with copied over ticket, this is currently not possible a when using Custom Objects (due to the dependencies), no notice or option to proceed copying tickets, the custom objects aren't copied anyway. This affects IT that isn't able to test an app or configuration in a non-production environment

What problem do you see this solving? (1-2 sentences) 

This is a crucial Enterprise function that is being blocked, I understand Custom Objects don’t work, but at least give us a workaround.

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? (3-4 sentences)

Continuously because there is no way around the issue atm.

Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)

NO

What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)

When creating a sandbox with tickets, give a popup stating that the customer uses Custom Objects, due to architectural limitations, this cannot be included in the sandbox, give the customer the option to proceed and copy ticket without Custom objects (more of an acknowledgement/agreement). Or fix the initial issue

編集日時:2023年12月21日 · Lucas Case

1

フォロワー

3

投票

2

コメント


Lucas Caseさんがコメントを作成しました:

コミュニティのコメント Feedback - Ticketing system (Support)

コメントを表示 · 投稿日時:2023年11月10日 · Lucas Case

0

フォロワー

0

投票

0

コメント


Lucas Caseさんがコメントを作成しました:

コメントSecurity and user access in Zendesk Support

Caroline Kello Am I correct in stating changes to an end user in their language are not captures in the Audit log? Knowing this would really be helpful because the end users language does or can be determining for routing or the offering of dynamic content. The article only states that changes in users are captured (and most changes are) but language doesn't seem to be.

コメントを表示 · 編集日時:2023年10月18日 · Lucas Case

0

フォロワー

0

投票

0

コメント


Lucas Caseさんがコメントを作成しました:

コミュニティのコメント Feedback - Ticketing system (Support)

@... I mean a vendor that created a normal ticket via channel that could be email, but also ticket form, chat (doesn't matter, the case is the same) and add that ticket as an email side conversation to another ticket. The reason why this should be an email side conversation is that the vendor is not part of your Zendesk agents (so creating a child ticket has no function, as this is normally being used for a partial responsibility or task fulfillment for another ZD department/agent not an external party).

Not every ticket is being grouped properly into the same conversation, so mostly due to improper handling of email outside Zendesk by customers/vendors. But the main reason is the first one.

コメントを表示 · 投稿日時:2023年2月02日 · Lucas Case

0

フォロワー

1

投票

0

コメント