最近の検索
最近の検索はありません

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
コメント