최근 검색
최근 검색 없음

Tom J
가입한 날짜: 2024년 6월 27일
·
마지막 활동: 2025년 1월 15일
팔로잉
0
팔로워
0
총 활동 수
24
투표 수
12
플랜 수
6
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Tom J
Tom J님이 에 댓글을 입력함
‘If you turned on solved ticket reassignment, you can choose what happens to solved tickets after the assigned agent is removed from the group.’
I wish there was a way to ‘Do nothing’ when an agent is removed from a group. If the ticket reopens, it will still be in the relevant teams inbox.
If I remove an agent from a group, they unassign from the ticket. Finding a workaround for this isn't easy, and I am in the process of working it out currently.
The issue is that is messes up ‘Assignee name’ on reporting, as it will change it to ‘Null’. The agent did do work in that group at the time, so I don't want it to unassign them. A workaround might be force closing the ticket - Also not an ideal solution.
Updates history dataset springs to mind, but there are certain metrics that I want to track that are not available there.
댓글 보기 · 2025년 1월 15일에 게시됨 · Tom J
0
팔로워
1
투표
0
댓글
Tom J님이 에 댓글을 입력함
It doesn't really work as initially advertised. Lets say I restricted an agent who is working on brand A to brand A, and then when clicking ‘New ticket’, they can still choose to create the ticket as brand B, ‘Brand restriction per agent’ has not been achieved.
댓글 보기 · 2025년 1월 02일에 게시됨 · Tom J
0
팔로워
0
투표 수
0
댓글
Tom J님이 에 댓글을 입력함
+1 I cant believe that this isn't included in Suite Enterprise.
댓글 보기 · 2024년 12월 11일에 게시됨 · Tom J
0
팔로워
2
투표 수
0
댓글
Tom J님이 에 댓글을 입력함
+1 can't believe this is a paid add on and not included in Suite enterprise
댓글 보기 · 2024년 12월 11일에 게시됨 · Tom J
0
팔로워
3
투표 수
0
댓글
Tom J님이 에 댓글을 입력함
I agree with Kris, no need to change the status as the ticket may need to be escalated, solved, or whatever. But simply releasing the capacity if its inactive would be the ideal feature. Because of this, we have not enabled it, unfortunately.
댓글 보기 · 2024년 10월 22일에 게시됨 · Tom J
0
팔로워
0
투표 수
0
댓글