最近の検索
最近の検索はありません

Simon Blouner (midlertidig)
参加日2021年4月16日
·
前回のアクティビティ2024年10月15日
Zendesk consultant with 3+ years experience with the entire Zendesk product portfolio, from small scaleups to major enterprise clients
フォロー中
0
フォロワー
0
合計アクティビティ
97
投票
33
受信登録
28
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Simon Blouner (midlertidig)
Simon Blouner (midlertidig)さんがコメントを作成しました:
This is very much needed in our use case as well!
For the same reasons Reshma explains; Our more experienced agents need to have the internal comment, potentially also side conversations included. This way the Summary will give the agents much time saved, and the entire dialogue on the ticket is included.
コメントを表示 · 投稿日時:2023年11月06日 · Simon Blouner (midlertidig)
0
フォロワー
1
投票
0
コメント
Simon Blouner (midlertidig)さんがコメントを作成しました:
We are also only seeing the 12/8 split, and not the new 30/10 - when will this be activated since it has been announced to be available?
コメントを表示 · 投稿日時:2023年10月02日 · Simon Blouner (midlertidig)
0
フォロワー
3
投票
0
コメント
Simon Blouner (midlertidig)さんがコメントを作成しました:
I don't see anyone mentioning side conversations being included in the summary.
We would also very much like to see internal notes being included in the ticket summary.
コメントを表示 · 投稿日時:2023年8月10日 · Simon Blouner (midlertidig)
0
フォロワー
1
投票
0
コメント
Simon Blouner (midlertidig)さんが投稿を作成しました:
Feature Request Summary:
If we can interact with closed tickets from an Automation, we can become more GDPR compliant towards our customers, as we would be able to delete tickets based on our own easily maintained rules.
Description/Use Cases:
Right now if one wants to be able to e.g. delete closed tickets in an automatic setup, one would need to utilize a third-party integration/custom build to handle rules and deletion.
If we were able to act on Closed tickets from an Automation, we would be able to maintain simple Automation rules that would delete tickets via. a Webhook.
This will make us much more GDPR compliant, and potentially also be able to automatically redact ticket content.
I'm sure, being able to act upon Closed tickets, would also bring a lot of other different opportunities.
The business impact of limitations or missing features:
This is critical for our business as maintaining a custom build/third-party integration for deletion/redacting is a lot more expensive and expensive in resources, than being able to define rules from a known configuration way like Automation.
投稿日時:2023年8月10日 · Simon Blouner (midlertidig)
1
フォロワー
2
投票
1
コメント
Simon Blouner (midlertidig)さんがコメントを作成しました:
Hey Dane
Thanks for the reply.
It is however still unclear to me "if where any update using Knowledge or the Knowledge Capture app took place", implying that the reading/opening of an article, inside Knowledge or Knowledge Capture, is counted as an event.
Concrete scenario:
- Agent opens a ticket and acknowledges that they need to find some knowledge in the Knowledge tab.
- They do a search, find some Supplier info
- They don't Link, Create, Flag, or Edit the article - they only View it
Is the Viewing of an Article through Knowledge or Knowledge Capture, counted as an event in the dataset or not?
コメントを表示 · 投稿日時:2023年6月07日 · Simon Blouner (midlertidig)
0
フォロワー
0
投票
0
コメント
Simon Blouner (midlertidig)さんがコメントを作成しました:
It is unclear to me, what is covered in the "Agent engagement ratio" metric.
What is considered to be "Knowledge or Knowledge Capture app activity"?
More specifically, we want to know if it includes Agents' Opening articles, not necessarily linking them.
I feel the Agent engagement ratio only consists of Flagged, Created and Linked events.
Can anyone here shed som light on this?
コメントを表示 · 投稿日時:2023年5月01日 · Simon Blouner (midlertidig)
0
フォロワー
0
投票
0
コメント
Simon Blouner (midlertidig)さんが投稿を作成しました:
Feature Request Summary:
It would be really beneficial to have some sort of placeholders available in Content Blocks.
Description/Use Cases:
Similar to the placeholders that are used in Zendesk Support, it would be cool some something similar available in Guide in general, but especially in Content Blocks.
E.g. being able to use the same Content Block across Branded Help centers, where we in the content block could add something like {{content.brand.name}}, {{content.brand.form.id.link}}, {{content.category}}
Business impact of limitation or missing feature:
Enabling something like this will make usage of Content Blocks across brands more feasible, and easier to make branded communication in Content Blocks that is used across multiple branded Help Centers.
投稿日時:2023年4月21日 · Simon Blouner (midlertidig)
9
フォロワー
8
投票
2
コメント