최근 검색
최근 검색 없음

Steve Steffel
가입한 날짜: 2021년 4월 16일
·
마지막 활동: 2024년 10월 17일
팔로잉
0
팔로워
0
총 활동 수
33
투표 수
12
플랜 수
11
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Steve Steffel
Steve Steffel님이 에 댓글을 입력함
This is a wonderful and very useful feature for us! One question: Can dashboard restrictions be copied to multiple dashboards? For example, maybe my restriction is "Group ABC" and it's a filter on ticket group with values "Group A", "Group B", "Group C". I'd like to reuse that filter across different dashboards instead of recreating it. Is that possible? Thanks!
댓글 보기 · 2023년 1월 31일에 게시됨 · Steve Steffel
0
팔로워
3
투표 수
0
댓글
Steve Steffel님이 에 게시물을 만듦
We have our product documentation hosted outside of Zendesk, so being able to surface it for customers as they create a ticket would be great. The crawler used to gather external content for federated search in Guide seems like it would work, but external content isn't available for this type of search yet.
2022년 11월 29일에 게시됨 · Steve Steffel
4
팔로워
6
투표 수
6
댓글
Steve Steffel님이 에 댓글을 입력함
Hello! Will external content show up in the customer side of the ticket request form? That would be massively helpful for us (as well as appearing in the agent workspace, which it looks like it will). Thank you!
댓글 보기 · 2022년 11월 08일에 게시됨 · Steve Steffel
0
팔로워
0
투표 수
0
댓글
Steve Steffel님이 에 댓글을 입력함
I wanted to come and add my support for this idea. We have groups in different countries, and if an agent makes an outbound call and forgets to switch to the correct number, they're suddenly making an international call to a customer. Depending on the number of outgoing calls, there's a pretty big chance for someone to miss that they're calling out of the wrong phone line.
I like the idea of setting the default by group, though I understand this would get confusing for agents in multiple groups. A field in the agent profile that's a dropdown for default Talk outbound line would be perfect.
Thank you!
댓글 보기 · 2022년 8월 16일에 게시됨 · Steve Steffel
0
팔로워
0
투표 수
0
댓글
Steve Steffel님이 에 댓글을 입력함
Steve Steffel님이 에 댓글을 입력함
Just wanted to add that I'd also love this feature. Right now I have 15 different reports for support team leads in our company which has turned out to be a lot of work to update with even very simple changes. If I could just define that a team lead has permission to view tickets assigned to this list of people (and the same for other datasets) that would be great. Then I would be able to have one report and still be assured that it follows our privacy restrictions.
댓글 보기 · 2020년 11월 16일에 게시됨 · Steve Steffel
0
팔로워
1
투표
0
댓글
Steve Steffel님이 에 댓글을 입력함
Just adding that we'd also love this to be separate permissions. We would like agents to update organization fields as needed, but the fact that allowing them to do this also allows them to delete the organization and add a new one (both of which mess up connections with other systems) is frustrating. Not to mention how agents should not be messing with internal groups at all as that can affect routing, reports, etc. Our options right now are to restrict all the permissions to a small group and burden them with changes needed by everyone, or just risk having people make changes they shouldn't.
댓글 보기 · 2020년 11월 10일에 게시됨 · Steve Steffel
0
팔로워
1
투표
0
댓글