최근 검색
최근 검색 없음

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
댓글