最近の検索
最近の検索はありません

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
コメント