최근 검색
최근 검색 없음

Barry Neary
가입한 날짜: 2021년 4월 14일
·
마지막 활동: 2025년 2월 04일
팔로잉
0
팔로워
11
총 활동 수
534
투표
1
플랜 수
110
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Barry Neary
Barry Neary님이 에 댓글을 입력함
Hi Jennifer Morris / Sam
Can you contact our customer support group to enable this for your account?
댓글 보기 · 2025년 2월 04일에 게시됨 · Barry Neary
0
팔로워
0
투표 수
0
댓글
Barry Neary님이 에 댓글을 입력함
HI Nico V
The only way currently to do this is to leveage the Zendesk Agent Status API to make changes to an agent status and write some type of script to call these APIs. We are currently developing a bulk edit status capabilty that you can change several agents status with one call. (cc: Jenny Gillett )
댓글 보기 · 2025년 1월 13일에 게시됨 · Barry Neary
0
팔로워
0
투표 수
0
댓글
Barry Neary님이 에 댓글을 입력함
Hi Yvonne P.
When you say ‘Agent has less than 3 open tickets - assign next 5 tickets ’ what exactly is the logic you are looking for?
Lets say the agent is one of several who are online in the group, presumably you want the tickets that are in the queue to be distributed to each of the agents on a round robin basis (rather than given one of the agents who has 3 open tickets to receive the next five from queue)?
I think we may be getting confused between ‘I want to distribute the tickets based on the round robin methodology’ vs. ‘I want OCR to work in the same way the third part round robin app does’.
Barry
댓글 보기 · 2025년 1월 13일에 게시됨 · Barry Neary
0
팔로워
0
투표 수
0
댓글
Barry Neary님이 에 댓글을 입력함
Hi
Omnichannel routing currently has round robin as a routing option. If you select it, then rather than giving the ticket to the agent with the highest spare capacity, it will select the agent who has not received a ticket in the longest time. It will still respect the agents max capacity for that channel
Barry
댓글 보기 · 2025년 1월 13일에 게시됨 · Barry Neary
0
팔로워
0
투표 수
0
댓글
Barry Neary님이 에 댓글을 입력함
Hi, currently if you dont use routing queue you can build an Explore report showing how many tickets were assigned with the auto routing tag. With routing queues we plan to have historical reports that would show how many tickets were assigned from a particular queue. However in both cases if a ticket was manually assigned we cannot differentiate that from one that was auto assigned. We are looking into ways to plug that gap….
댓글 보기 · 2025년 1월 03일에 게시됨 · Barry Neary
0
팔로워
0
투표 수
0
댓글
Barry Neary님이 에 댓글을 입력함
You could this using routing queues, but you would need to have agents 1 and 2 in a seperate group which is the primary group for the call routing queue and then the secondary group contain agents 3,4 and 5. The calls would only go to the secondary group if the primary one were not available
cc: Jenny Gillett
댓글 보기 · 2025년 1월 02일에 게시됨 · Barry Neary
0
팔로워
0
투표 수
0
댓글
Barry Neary님이 에 댓글을 입력함
Hi Zach Gilbert
Once a messaging session has been ended by an agent, the message is no longer routable - i.e. if you remove the assignee it wont be automatically be assigned to another agent in the group
We do have plans to allow these messaging tickets to be transformed into email tickets and they would be routable
Barry
댓글 보기 · 2024년 12월 16일에 게시됨 · Barry Neary
0
팔로워
0
투표 수
0
댓글