최근 검색
최근 검색 없음

Jennifer Landry
가입한 날짜: 2021년 4월 16일
·
마지막 활동: 2024년 12월 18일
팔로잉
0
팔로워
0
총 활동 수
24
투표 수
4
플랜 수
13
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Jennifer Landry
Jennifer Landry님이 에 댓글을 입력함
Are there any plans to enable the configuration of SLAs based on a field other than "Priority"? Our SLA agreements are centered around "Severity," which presents several challenges:
- I am unable to rename the "Priority" field to "Severity," resulting in discrepancies between our reporting and contractual language.
- It is confusing for my agents to instruct them to "Set the Priority field to match the Issue Severity."
Priority and Severity represent different concepts. While they are often aligned, there are instances where they differ, leading to reporting inaccuracies across systems. Engineering uses "Priority" to determine the resolution timeline, whereas "Severity" reflects the impact of the issue on our systems.
It would be beneficial if we could either rename the "Priority" field or configure our SLAs based on a "Severity" field.
Currently, I have created a "Severity" field and instructed our team to set both the Severity and Priority to the same values. This approach ensures our reporting terminology aligns with our contractual language and will also provides accurate SLA times based on the Priority field.
댓글 보기 · 2024년 12월 18일에 게시됨 · Jennifer Landry
0
팔로워
0
투표 수
0
댓글
Jennifer Landry님이 에 댓글을 입력함
I am having an issue when an "internal" note is placed on a ticket, then assigned, the SLA time does not get applied. Any idea why?
댓글 보기 · 2023년 2월 01일에 게시됨 · Jennifer Landry
0
팔로워
0
투표 수
0
댓글
Jennifer Landry님이 에 게시물을 만듦
Hi!
Would love to see more control around Satisfaction Survey visibility. Currently all my agents have access to see all tickets, that is how our workflow is intentionally designed. However, I don't want team members to see Satisfaction surveys that pertain to other team members.
It would be fantastic if we could limit survey responses to the ticket assignee only and/or Admin only.
2022년 11월 10일에 게시됨 · Jennifer Landry
0
팔로워
2
투표 수
0
댓글
Jennifer Landry님이 에 게시물을 만듦
Hi!
I am implementing the Satisfaction Survey in Zendesk. I have a concern about "Survey" feedback visibility.
Can you currently limit "survey response" visibility to be seen by only an "Admin" or the "ticket assignee"? If so, how do I accomplish this without affecting overall ticket visibility?
2022년 11월 09일에 게시됨 · Jennifer Landry
0
팔로워
4
투표 수
1
댓글
Jennifer Landry님이 에 댓글을 입력함
I agree, this is a necessity! While I understand it is overwhelming magnitude of data that needs to be parsed, these reports, as they currently function, are really only useful for "number" metrics and nothing else, such as the needs of "Voice of Customer". Please consider this as an addition to your product roadmap in the very near future.
댓글 보기 · 2021년 5월 14일에 게시됨 · Jennifer Landry
0
팔로워
2
투표 수
0
댓글
Jennifer Landry님이 에 댓글을 입력함
I agree with the above, this is extremely frustrating. It's been over a year. Any update on this feature? I waste more time trying to "fix" a change I made, that didn't work as intended. Please move this feature to the top of your Product Roadmap... If there is a "workaround", I would appreciate if someone could share. TIA!
댓글 보기 · 2021년 3월 12일에 게시됨 · Jennifer Landry
0
팔로워
4
투표 수
0
댓글