최근 검색
최근 검색 없음

Kelsey Davis
가입한 날짜: 2022년 10월 14일
·
마지막 활동: 2022년 11월 25일
팔로잉
0
팔로워
0
총 활동 수
5
투표 수
0
플랜 수
3
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Kelsey Davis
Kelsey Davis님이 에 댓글을 입력함
Our Agents work on tickets from all channels over the course of a shift, so not being able to report on Replies & Solves for all tickets Agents manage in the same report is really crippling for our reporting (as is not having update-oriented metrics & attributes -- Assignee-based reporting completely erases record of an Agent's work if the ticket is passed to another Agent when they turn over shifts, which happens very frequently)
Without this info in one dataset, we can't report on Agent output performance in Explore & we can't pull it to our database to do so either at this point. Will Messaging Solves & Replies be available in the Ticket + Updates History datasets? Some components of those tickets are available to report on in the Ticket dataset, but not two of the most core metrics for reporting on Agent output performance.
댓글 보기 · 2022년 11월 25일에 게시됨 · Kelsey Davis
0
팔로워
1
투표
0
댓글
Kelsey Davis님이 에 댓글을 입력함
Trying to implement this Zap & got the error:
"Failed to create a run python in Code by Zapier. Your code had an error! Traceback (most recent call last): File "", line 26, in the_function KeyError: 'view_count' "
I tried the proposed workaround mentioned here & keep getting the error. Has the View Count code documentation changed? Not sure how to best troubleshoot here. Reached out to Zapier and they're not able to help review the code.
댓글 보기 · 2022년 10월 14일에 게시됨 · Kelsey Davis
0
팔로워
0
투표 수
0
댓글