최근 검색
최근 검색 없음

Zach Gilbert
가입한 날짜: 2022년 4월 17일
·
마지막 활동: 2025년 2월 07일
팔로잉
0
팔로워
1
총 활동 수
108
투표 수
13
플랜 수
31
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Zach Gilbert
Zach Gilbert님이 에 댓글을 입력함
Luis Freitas not sure if you figured this out, but you would do the same thing, just make it a customer field vs an org and add the tag to the customer vs the organization. The rest would be the same.
댓글 보기 · 2025년 2월 07일에 게시됨 · Zach Gilbert
0
팔로워
0
투표 수
0
댓글
Zach Gilbert님이 에 게시물을 만듦
Currently doing flow charts to re-do all of our company forms for Zendesk. One form is for product support.
In some cases, the customer may use the form, or email in about multiple products. Often if the support request is different, the team will split the ticket for each product. But sometimes product A and product B from the same company can live on the same ticket.
What is everyone else doing? I'm thinking of conditions that (if it works) the user or agent can fill in the first product, but then they have a box “need to add another product?” which then opens another product filed and so on.
Is this the best way to do it? Or are there others?
Open to ideas.
2025년 2월 06일에 편집됨 · Zach Gilbert
0
팔로워
0
투표 수
0
댓글
Zach Gilbert님이 에 댓글을 입력함
Tiago Magalhaes are you able to look at ticket 13181419? We have one agent who if they have the plugin installed, they get kicked our of various AUX codes and even moved out of Zendesks Omnichannel routing statuses.
댓글 보기 · 2025년 2월 03일에 게시됨 · Zach Gilbert
0
팔로워
0
투표 수
0
댓글
Zach Gilbert님이 에 댓글을 입력함
Hey Rich Talbot simply looking at a sujjected article won't mark the ticket as solved. When the user clicks on the link they are presented with a popup near the bottom of the screen saying that they can mark this as solved.
댓글 보기 · 2025년 1월 27일에 게시됨 · Zach Gilbert
0
팔로워
0
투표 수
0
댓글
Zach Gilbert님이 에 댓글을 입력함
Orsolya Forster I've thought about this a lot more, and I actually think you would want two things. By default, they show up in search, but you have the option per placement to not be indexed by search. In many cases, I now think it makes more sense for it to show up in search for multiple locations as an end user could be looking for something on a specific product and maybe they find the duplicated article on another product in your KB, even though the info is correct, they may not understand that the information pertains to their product too. But I could see the need for the ability to not have it show. This could be as simple as a check box in the multi-placement process that says “Allow search to index this article” or something.
TLDR:
Default Search Visibility: Articles should be visible in search results by default.
- Opt-Out Search Indexing: Provide an option to exclude specific article placements from search results.
- Rationale for Search Visibility: Duplicated articles on different products can be beneficial for users seeking specific product information.
댓글 보기 · 2025년 1월 10일에 게시됨 · Zach Gilbert
0
팔로워
1
투표
0
댓글
Zach Gilbert님이 에 댓글을 입력함
Thanks, Erin O'Callaghan - Is there documentation on Auto Assist telling it how to read tags? Or is it as simple as adding a step in the procedure “Run this procedure if the ticket has the tag ”Refund_request"? We were moved over from procedures in admin to procedures in Guide a few weeks back, but not seeing any step or setting regarding tags.
댓글 보기 · 2024년 12월 20일에 게시됨 · Zach Gilbert
0
팔로워
1
투표
0
댓글
Zach Gilbert님이 에 댓글을 입력함
Erin O'Callaghan can you expand on procedure-specific tags? Not seeing anything in the KB about this and auto assist. Can auto assist apply tags when it uses a procedure? Or is this to make a trigger, that applies a tag, and then in the procedure you can tell auto assist to follow procedure X based on the tag on the ticket?
댓글 보기 · 2024년 12월 19일에 게시됨 · Zach Gilbert
0
팔로워
0
투표 수
0
댓글
Zach Gilbert님이 에 댓글을 입력함
Thanks, Barry Neary - We've turned off auto reassignment of chat until that feature is implemented.
댓글 보기 · 2024년 12월 18일에 게시됨 · Zach Gilbert
0
팔로워
0
투표 수
0
댓글
Zach Gilbert님이 에 댓글을 입력함
Barry Neary this is the same comment that was left in the other group that you replied to this morning where the agent ends the messaging conversation, then emails the customer on the same ticket, the agent goes offline, and then the customer emails back on that ticket. SInce we have the setting to re-assign chats when an agent is offline, the agent is stripped from the ticket, but the ticket is not being offered to any other agents like a messaging ticket would. It sits in the cue as an unassigned messaging conversation.
댓글 보기 · 2024년 12월 05일에 게시됨 · Zach Gilbert
0
팔로워
0
투표 수
0
댓글