최근 검색
최근 검색 없음

Dan Ross
가입한 날짜: 2021년 4월 15일
·
마지막 활동: 2022년 9월 19일
팔로잉
0
팔로워
4
총 활동 수
466
투표 수
146
플랜 수
179
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Dan Ross
Dan Ross님이 에 댓글을 입력함
Hey there! Many ways you can do this, though I am a big fan of dedicated Support Operations teams. IMO the most impactful method you can do this is have administration only be provided to people in that role, if every support manager gets admin, you get too many cooks in the kitchen and it's harder to build a cohesive Zendesk.
Depending on your team size, you might only need 1 admin. I managed ~150 agent instance solo, but as we grew past that, so did the team!
댓글 보기 · 2022년 9월 19일에 게시됨 · Dan Ross
0
팔로워
1
투표
0
댓글
Dan Ross님이 에 댓글을 입력함
this would be helpful and a better experience for customers. a lot of frustration with automated deflection comes from the fact if the user does something wrong or unintentional that they get stuck down a path and can't get help, so they either leave and change channel to something like phone (no! bad!) or change from engaging with the automated tool to requesting a human, which defeats the purpose of tool to begin with and increases customer effort to get help.
댓글 보기 · 2022년 9월 08일에 게시됨 · Dan Ross
0
팔로워
1
투표
0
댓글
Dan Ross님이 에 댓글을 입력함
Adding to the chorus on this one. Heather Rommel's feedback on the definition of 'working on' a ticket is what we align with as well.
If the goal of the live dashboards is to see what's happening live then just counting the assigned Open tickets is not meeting that goal. That's static data and could be shown on conventional boards.
For a real time dashboard, I would expect to see what is actively and dynamically being worked on by agents.
댓글 보기 · 2022년 7월 22일에 게시됨 · Dan Ross
0
팔로워
8
투표 수
0
댓글
Dan Ross님이 에 댓글을 입력함
Hey Hannah,
In Zendesk Explore, try using the Attribute for 'User Locale' in conjunction with a metric for counting the number of Tickets. That should break down the languages for you by the # tickets created attached to that requester's language.
If you have requesters who submit in multiple languages, I would suggest creating a trigger for each support language that sets a value in a custom drop down field for Ticket Language. This way you get an accurate count going forward of the ticket language, even if the requester's locale settings change.
댓글 보기 · 2022년 6월 07일에 게시됨 · Dan Ross
0
팔로워
0
투표 수
0
댓글
Dan Ross님이 에 댓글을 입력함
Thanks Ryan McGrew that's awesome to hear! Will this allow redirect to any URLs or just to Zendesk ones in the same instance? Our use case is that we wish to merge different instances of Zendesk and one of the blockers is that the help centres need to be migrated and redirected.
Thanks!
댓글 보기 · 2022년 6월 07일에 게시됨 · Dan Ross
0
팔로워
0
투표 수
0
댓글
Dan Ross님이 에 댓글을 입력함
Hey Erik,
try doing a search in Zendesk using your API field name for the org field, using 'none' as the search term.
Ex: if your field API name is 'region' then your search would be
region:none
Does that find what you need?
댓글 보기 · 2022년 5월 04일에 편집됨 · Dan Ross
0
팔로워
1
투표
0
댓글
Dan Ross님이 에 댓글을 입력함
Hey CJ,
I hear you, I just had an admin get bit by this recently.
Here's how we're doing things:
- We make a personal view for tickets assigned to the group/agent that's gonna be changed
- Add the new group to the agent's profile and set it as default
- Bulk update the tickets in the view from old agent/group to new agent/group
- Remove old group from profile
We use a tool called Lovely Views for our view management and it really helps with this problem too. It lets you select all ticket pages pages and run bulk updates in the background. I can do 1000 tickets in one shot that way easier than the max 100 at a time in the native UI with page flips every 30 tickets.
댓글 보기 · 2022년 5월 04일에 게시됨 · Dan Ross
0
팔로워
1
투표
0
댓글
Dan Ross님이 에 댓글을 입력함
We found this post because we just ran into this issue after a company wide rebrand.
Our form IDs didn't change, just the names and it's causing havoc with reports. Please, have these relations stored by the form ID and not the name.
댓글 보기 · 2022년 5월 02일에 게시됨 · Dan Ross
0
팔로워
2
투표 수
0
댓글
Dan Ross님이 에 댓글을 입력함
Hey Jasmine Winzeler - you might be able to do something with Zendesk's webhooks feature for this.
When a ticket is created and these secondary user fields are filled, you could have a trigger send a message to a webhook that passes in the field information. You can have that webhook create a user in Zendesk if they don't exist, and if your product supports receiving webhook events of some kind, potentially do the same.
There's probably be some edge cases you'd need to iron out, like what if an email already exists, does it overwrite names, org memberships etc.
댓글 보기 · 2022년 4월 25일에 게시됨 · Dan Ross
0
팔로워
1
투표
0
댓글