최근 검색


최근 검색 없음

Simon Blouner (midlertidig)'s Avatar

Simon Blouner (midlertidig)

가입한 날짜: 2021년 4월 16일

·

마지막 활동: 2024년 10월 15일

Community Moderator

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)님이 에 댓글을 입력함

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

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)님이 에 댓글을 입력함

댓글Ticket management

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)님이 에 댓글을 입력함

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

I second this request!

Would be really nice being able to order the system fields as we see fit. 

댓글 보기 · 2023년 9월 15일에 게시됨 · Simon Blouner (midlertidig)

0

팔로워

0

투표 수

0

댓글


Simon Blouner (midlertidig)님이 에 댓글을 입력함

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

This would be such a good feature! Please implement..

댓글 보기 · 2023년 8월 22일에 게시됨 · Simon Blouner (midlertidig)

0

팔로워

2

투표 수

0

댓글


Simon Blouner (midlertidig)님이 에 댓글을 입력함

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

A vote from here as well!

댓글 보기 · 2023년 8월 22일에 게시됨 · Simon Blouner (midlertidig)

0

팔로워

1

투표

0

댓글


Simon Blouner (midlertidig)님이 에 댓글을 입력함

댓글Ticket automation and collaboration

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)님이 에 게시물을 만듦

게시물 Feedback - Ticketing system (Support)

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)님이 에 댓글을 입력함

댓글Reporting and analytics for help center

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:

  1. Agent opens a ticket and acknowledges that they need to find some knowledge in the Knowledge tab.
  2. They do a search, find some Supplier info
  3. 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)님이 에 댓글을 입력함

댓글Reporting and analytics for help center

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)님이 에 게시물을 만듦

게시물 Feedback - Help Center (Guide)

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

댓글