최근 검색
최근 검색 없음

LVB
가입한 날짜: 2022년 2월 21일
·
마지막 활동: 2022년 10월 31일
팔로잉
0
팔로워
0
총 활동 수
30
투표 수
3
플랜 수
15
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 LVB
LVB님이 에 게시물을 만듦
We are looking to integrate both Zendesk Guide and Zendesk Messaging SDKs into our mobile apps. Among other things, this is to support contextual help by embedding articles throughout the app using the ViewArticleActivity object in the Support SDK - without losing Messaging.
Has anyone found a workaround to the known incompatibility between these two SDKs, or have any information on when this issue is slated to be addressed?
2022년 10월 31일에 편집됨 · LVB
0
팔로워
1
투표
0
댓글
LVB님이 에 댓글을 입력함
Thanks Barry Neary,
Definitely agree with what others have said here. The assignment of inactive chats wholesale to whichever agent goes Active first feels more like a consequence of incomplete design than of deliberate decision making.
The option to choose how these are handled will be good. Option 2 will definitely be what is selected by us.
댓글 보기 · 2022년 10월 12일에 게시됨 · LVB
0
팔로워
0
투표 수
0
댓글
LVB님이 에 댓글을 입력함
If inactive messaging conversations are different than both email and active messaging convos, I'd advocate for a third capacity limit with a checkbox to "combine active and inactive Message capacities" in the Capacity Rules. My use case would be to include inactive convos in capacity calculations for Messaging (hence the checkbox), but can understand if others do not have this workflow. Absent that, I would count them toward the email limit as they are more aligned with that channel's workflow than messaging's workflow.
댓글 보기 · 2022년 10월 10일에 게시됨 · LVB
0
팔로워
3
투표 수
0
댓글
LVB님이 에 댓글을 입력함
Regarding:
“A message remains active for 10 minutes in the queue. If it still hasn't been assigned after 10 minutes, the inactive message will be assigned to the next online agent with spare capacity (known as round-robin). It won’t use up any of that capacity. This applies only to messages that have previously been offered to an agent. Inactive messages never offered to an agent (for example, because they come in when all agents were offline) remain in the queue and are not assigned.“
Are there plans to resolve the issues this causes? For example, the following behavior is caused by the above: when agents sign in to start their day, they are dumped dozens of overnight tickets. Is there a recommended way to reassign these tickets to another group to prevent this? (My email/async support team and my live chat/messaging support teams are separate.)
Note: I believe this is inaccurate - “This applies only to messages that have previously been offered to an agent.” I do not have messaging agents (the only channel we’re using Omni routing for) online overnight and yet all overnight tickets drop onto my morning agents anyway.
댓글 보기 · 2022년 10월 08일에 게시됨 · LVB
0
팔로워
2
투표 수
0
댓글
LVB님이 에 댓글을 입력함
Is there an API to read agent statuses, or will be be able to create triggers, to integrate these statuses with a WFM solutions?
댓글 보기 · 2022년 8월 19일에 게시됨 · LVB
0
팔로워
0
투표 수
0
댓글
LVB님이 에 댓글을 입력함
@...,
That is a good solution for articles that have already been published, but does not support the pre-publish workflow of Draft → QA Ready → QA Feedback → Published (or thereabouts).
댓글 보기 · 2022년 3월 31일에 게시됨 · LVB
0
팔로워
0
투표 수
0
댓글
LVB님이 에 댓글을 입력함
Is there any documentation on how much of the inbound email is processed by Answer Bot to define the list of recommended articles?
댓글 보기 · 2022년 3월 31일에 게시됨 · LVB
0
팔로워
0
투표 수
0
댓글
LVB님이 에 댓글을 입력함
Does Zendesk support private comments, or some other mechanism by which my QA Team can provide feedback to our content authors on articles that require verification or review? Or is it necessary to manage the bulk of the authoring and maintenance in a separate platform?
댓글 보기 · 2022년 3월 30일에 게시됨 · LVB
0
팔로워
0
투표 수
0
댓글