최근 검색
최근 검색 없음

Brandon (729)
가입한 날짜: 2021년 4월 15일
·
마지막 활동: 2025년 2월 14일
Full time Zendesk Architect. Cleveland born and raised. Changing the world one megabyte at a time.
팔로잉
0
팔로워
10
총 활동 수
1020
투표 수
44
플랜 수
371
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Brandon (729)
Brandon (729)님이 에 댓글을 입력함
Hi There Walter Bellante -
We noticed that Time Filters are not sharing across tabs at this point in our testing (ie, we have a Time Filter on each tab, on tab 1 we select “last 7 days” - previously this would update time filters on every tab unless “do not share across tabs” was checked. Can we expect this functionality to roll into the new dashboard experience at some point? I realize that filtered views anchored to different time periods is possible today, but for our use case we'd like to have the user select a range and have that cascade through the report). Thanks!
Brandon
댓글 보기 · 2025년 2월 12일에 게시됨 · Brandon (729)
0
팔로워
1
투표
0
댓글
Brandon (729)님이 에 댓글을 입력함
Hey Soleil Tacher Unfortunately, this is not possible - nor do I know of any end-users that are willing to wait on hold for longer than 60 minutes. The best practice here would be for a voicemail to be offered. The only other option (not recommended) would be to overflow to a secondary Talk number, which would ‘reset’ the hold time. That being said, I would encourage you to look at finding ways to perhaps use Zendesk's AI and self-service tooling to reduce the volume of inbound calls, which might alleviate your need to increase the queue wait time. Hope this helps!
댓글 보기 · 2025년 2월 04일에 게시됨 · Brandon (729)
0
팔로워
0
투표 수
0
댓글
Brandon (729)님이 에 댓글을 입력함
Hey Kévin Arnoult -
Sorry to hear you're having difficulty. You could potentially sniff for that note with a Trigger that adds a tag. There might also be an option to consolidate some of your automations.
I'm also sending this over to Amer at Qvasa to see if this is something they might be able to extract. Hope this helps!
Brandon
댓글 보기 · 2025년 1월 31일에 게시됨 · Brandon (729)
0
팔로워
0
투표 수
0
댓글
Brandon (729)님이 에 댓글을 입력함
Hey Rich Talbot - nice to see you here! This is not expected behavior as far as I know. I would recommend having Zendesk Advocacy look at the ticket(s) in question to figure out what happened. Yvonne P. the automated_resolution tag should also strip, so you might want to have Advocacy look at that as well. Hope this helps!
댓글 보기 · 2025년 1월 29일에 게시됨 · Brandon (729)
0
팔로워
1
투표
0
댓글
Brandon (729)님이 에 댓글을 입력함
Hey LD SB -
Thanks for reaching out! I can see that you are using dynamic content as placeholders inside of your dropdown. This would require you to first define the dynamic content in the admin center (under the aptly named Dynamic Content section) before adding it to your dropdown field. Once this is completed, there may be a slight delay (~15 mins) before the value is visible in the help center to end-users, but it should be available to agents internally with a simple refresh of your browser. More info is available here: https://support.zendesk.com/hc/en-us/community/posts/6595856382618-Dynamic-content-in-custom-fields
Hope this helps!
Brandon
댓글 보기 · 2025년 1월 09일에 게시됨 · Brandon (729)
0
팔로워
0
투표 수
0
댓글
Brandon (729)님이 에 댓글을 입력함
Hey Judith Ilagan -
There is a limit, but it's wayyyy more than 4. This sounds like more of an issue with the design of your help center, or maybe something with your field & form configuration. I'd recommend opening a trouble ticket with Zendesk so that they can investigate further. If they can't figure it out - I'd welcome the chance to drop into your instance and help. You can find me at 729Solutions.com. That said, it defintely sounds like a configuration error that Zendesk should be able to help you sort out.
Cheers,
Brandon Tidd
댓글 보기 · 2025년 1월 08일에 게시됨 · Brandon (729)
0
팔로워
0
투표 수
0
댓글
Brandon (729)님이 에 댓글을 입력함
Hey Jahn
That makes sense. Unfortunately, as a system Zendesk isn't going to fully understand the difference between human vs voicemail responders. That being said, you've got some options.
1) Agent Categorization. Leveraging a checkbox or dropdown to differentiate which tickets fell into one category would be the most straight-forward approach, but would require the agents to answer (and answer truthfully).
2) Evaluate Time On Call. Examining the length of calls may give you a leading indicator as voicemail calls will generally be a bit shorter than human calls, depending on the nature of the content being discussed.
3) Leverage AI. With Advanced AI, Zendesk will transcribe live calls. You could sniff for keywords in the transcriptions such as “Your call has been forwarded to an automatic voicemail system.”
Of all these, I would recommend the first option. Best of luck!
Brandon
댓글 보기 · 2024년 12월 06일에 게시됨 · Brandon (729)
0
팔로워
0
투표 수
0
댓글
Brandon (729)님이 에 댓글을 입력함
Brandon (729)님이 에 댓글을 입력함
Somewhat counterintuitively. You'll want to put in a available agent's greeting on the ivr option for five. Step one is to record a voicemail but save it as an available agent greeting. Then go to your ivr and edit extension 5. Where you choose the routing to voicemail. There should be a drop down there that will allow you to play a message in between the key press and the transfer. Hope this helps!
댓글 보기 · 2024년 11월 21일에 게시됨 · Brandon (729)
0
팔로워
0
투표 수
0
댓글
Brandon (729)님이 에 댓글을 입력함
Hi Yvonne P. -
Without authentication it will be difficult to do anything from within the help center environment, but this should be possible using autoreplies, which is now part of the AI Agents and automated resolutions workflow. Details here: https://support.zendesk.com/hc/en-us/articles/4408833721498-Using-autoreplies-to-recommend-articles-in-email-notifications
Outside of that, there are other, more hacky ways to approach this, including a key string “Solve my request” that is listened for in Triggers, or even building a simple web interface that asks for the ticket ID and then uses the API to force the ticket into a closed status.
Keep in mind that allowing end-users to self-solve might have downstream impacts on your reporting, especially when it comes to agent categorization of requests. Hope this helps!
Brandon
댓글 보기 · 2024년 11월 13일에 게시됨 · Brandon (729)
0
팔로워
0
투표 수
0
댓글