최근 검색
최근 검색 없음

Tommy Long
가입한 날짜: 2021년 10월 22일
·
마지막 활동: 2021년 10월 22일
팔로잉
0
팔로워
0
총 활동 수
4
투표
1
가입 플랜
1
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Tommy Long
Tommy Long님이 에 댓글을 입력함
So I struggled with this a bit this morning and have a workaround that works for our particular use case
When a ticket status is changed from solved
AND the ticket update is coming from email (or whatever channel yours come from)
The action taken is that it assigns it a new tag called "reopen"
And changes the status to solved
If you have tickets coming from multiple sources you'd need to tweak this a little bit but all of our incoming requests are happening via email.
The reason that line is important is that if the response is anything more than a thank you the agent can reopen it through the dashboard.
I added the tag in there because we have other triggers that send feedback surveys out when a ticket is solved and I didn't want them to receive multiples because of this workflow. So you will also have to go in and add language to any emails that are sent out when a ticket is solved that make it not send if it has the tag 'reopen'.
So far it has solved our issues. I don't believe it solves the SLA piece though as the ticket is still re-opened and immediately closed.
댓글 보기 · 2016년 1월 26일에 게시됨 · Tommy Long
0
팔로워
0
투표 수
0
댓글