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

Ryan Lainchbury
参加日2021年4月16日
·
前回のアクティビティ2023年3月15日
フォロー中
0
フォロワー
0
合計アクティビティ
8
投票
0
受信登録
5
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Ryan Lainchbury
Ryan Lainchburyさんが投稿を作成しました:
Sharing a workaround that a colleague and I created for our team.
Our team really liked the old dashboard and the ability to pre-read and watch chats without joining. With the limitations in the new dashboard as a result of the new Agent Workspace, and growing concern from our team we created a custom view for active chats that replaced the functionality of the old dashboard for our team. This view also is more accessible than the old dashboard!
Here is a screenshot of the settings.
投稿日時:2021年4月09日 · Ryan Lainchbury
2
フォロワー
17
投票
7
コメント
Ryan Lainchburyさんがコメントを作成しました:
Our team deals with this issue as well.
About 50% of our ticket volume is Agent created, 30% of which customers respond to. We want to include our response time to these customers, but it often results in a skewed First Response Time because of the delay that our customers take.
Here is a solution that we made!
- The agent creates a ticket
- The agent applies a tag of 'outbound' and submits it as any status.
- I've created a trigger that looks for the 'outbound' tag and automatically sets the ticket to closed (this prevent the First Response Time for this ticket)
- The trigger notifies the requester (i.e. end-user) - let's say three days pass.
- The customer replies, creating a follow-up ticket.
- When/if the requester (i.e. end-user) responds, a follow-up ticket is created with the 'outbound' tag on it from the previous ticket.
- A trigger then removes the 'outbound' tag from the follow-up ticket and adds a 'follow-up' tag (so we can report on the number of follow-ups we get vs outbounds.)
- The Agent responds and an accurate First Response Time is recorded!
Here are my screenshots of the triggers.
Thanks,
Ryan
コメントを表示 · 投稿日時:2021年2月04日 · Ryan Lainchbury
0
フォロワー
0
投票
0
コメント