최근 검색
최근 검색 없음

Preveena Balasubramanian
가입한 날짜: 2022년 3월 25일
·
마지막 활동: 2023년 8월 17일
팔로잉
0
팔로워
0
총 활동 수
6
투표 수
2
플랜 수
2
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Preveena Balasubramanian
Preveena Balasubramanian님이 에 댓글을 입력함
Hello,
What works well today with the SLA feature?
SLA allows to have comprehensive conditions with different targets.
What limitations do you hit while using it?
The main limitation comes to one touch tickets where the status is changed from New to Solved, there is no SLA target activated. While in Ticket events we could see the SLA with no targets applied, the explore reports this as No SLA triggered.
What do you wish it would do differently for you? Why?
Enforce a ticket background update so that SLA target gets activated before the ticket is marked solved. When the agent submits the ticket as solved with SLA trigger conditions, ticket should have an auto update identifying the SLA and then mark as solved.
What is the impact on your business?
We have a majority of tickets falling under one touch resolution and has huge impact to our SLA metrics. Manual intervention is required to update the SLA status in our report.
댓글 보기 · 2022년 3월 25일에 게시됨 · Preveena Balasubramanian
0
팔로워
0
투표 수
0
댓글