최근 검색
최근 검색 없음

AL
가입한 날짜: 2021년 4월 15일
·
마지막 활동: 2022년 3월 29일
팔로잉
0
팔로워
1
총 활동 수
17
투표 수
3
플랜 수
5
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 AL
AL님이 에 게시물을 만듦
We have an issue when the user asks this from the answer bot that is created with flow builder:
"I would like to speak with a customer service representative"
The bot answers "I didn't get that. Try rephrasing your question or start over."
This takes the user into a loop and they keep asking to speak with am agent, which is not possible. So the users get frustrated. How can we add a custom message or option to the flow builder to deal with this? For example:
"Our support is email-based. If you cannot find helpful article here, please send your question to our support team"
Followed by the option to fill out the form and send their ticket as an email?
The current response from Zendesk support is that this feature is not available for the bot and flow builder.
2022년 3월 29일에 게시됨 · AL
1
팔로워
4
투표 수
2
댓글
AL님이 에 댓글을 입력함
Hi Nicole,
I understand the idea of collecting votes for these, but the downside is that you may miss other requests that are asking the same, which I have seen on the channel.
Also, I find it interesting that something as basic as being able to offer email support to a user was missed when this feature was developed. It sounds quite fundamental, and should absolutely be an option for companies that cannot / do not want to offer live chat.
댓글 보기 · 2021년 5월 11일에 게시됨 · AL
0
팔로워
0
투표 수
0
댓글
AL님이 에 댓글을 입력함
Hi Nicole,
Sure thing.
1. Your question: Why you need these functions?
ANSWER:
We use currently only email support. No chat and no phone support. We would like to have the flow builder to first propose an article from our knowledge base to the user as the first step. Then, if the user does not find an article that is useful, flow builder should ask them to create a ticket. This ticket will then be answered by our agent by email as usual.
2. Your question: how significant of a business impact it is?
ANSWER:
We do not offer chat or phone support, so this is very important to us. It is a disappointment that this is not already standard as I think it is a very basic feature that the Flow Builder should offer.
I saw that other users were having this same need so it would be great to get this feature working. The flow builder seems to be useless for us without it.
Please let me know if you need additional information.
댓글 보기 · 2021년 5월 03일에 게시됨 · AL
0
팔로워
1
투표
0
댓글
AL님이 에 댓글을 입력함
We need the same feature. We use currently only email support. No chat and no phone support.
We would like to have the flow builder to propose article from our knowledge base to the user as the first step. Then, if the user did not find an article that is useful, flow builder should ask them to create a ticket. This ticket will then be answered by our agent as usual. There should be no option to talk to a human or chat. This should be configurable in the settings.
댓글 보기 · 2021년 4월 28일에 게시됨 · AL
0
팔로워
0
투표 수
0
댓글
AL님이 에 게시물을 만듦
We use currently only email support. No chat and no phone support.
We would like to have the flow builder to propose article from our knowledge base to the user as the first step. Then, if the user did not find an article that is useful, flow builder should ask them to create a ticket. This ticket will then be answered by our agent as usual.
2021년 4월 28일에 게시됨 · AL
20
팔로워
17
투표 수
18
댓글
AL님이 에 댓글을 입력함
Can you please add guidance for "Tags" - this is not mentioned in this article. But there is a "Tags" line in our list of Events. For example, it would be helpful to understand how to find a tag that is listed. I see some tags that I have not idea where they are coming from. So I'd like to know 1. how to find their origin, and 2. how to prevent them from getting added to a ticket in the future.
댓글 보기 · 2021년 4월 21일에 게시됨 · AL
0
팔로워
1
투표
0
댓글