최근 검색
최근 검색 없음

Mia Smith
가입한 날짜: 2023년 7월 06일
·
마지막 활동: 2024년 9월 10일
팔로잉
0
팔로워
0
총 활동 수
6
투표
1
플랜 수
3
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Mia Smith
Mia Smith님이 에 댓글을 입력함
Likewise, our organization needs a similar use-case for trigger differentiation.
Our team uses Side Convo via Ticket for internal SOPs. For example, I will open a Side Convo via Ticket to direct an escalation to another department. The other dept will review the case and either reply on the side ticket for our team to handle or the parent ticket if they want to take over the parent ticket. Because both are “tickets," we already have triggers in place to notify the team when these tickets are replied on.
Our team uses Side Convo via Email for external communications (we are in the B2B space and often involve multiple parties on a specific case). There is no way for our team to know if a Side Convo via Email is replied on without proactively checking the ticket. Because of this, the Side Convo via Email is quite useless unless we are able to be proactively notified about it.
What we'd like to be able to do is set up a trigger where tickets with Side Convo via Email attached are re-opened. But not that same for Side Convo via Ticket.
댓글 보기 · 2024년 9월 10일에 게시됨 · Mia Smith
0
팔로워
0
투표 수
0
댓글